Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [4diac-dev] Fw: Re: Milestone and release of forte/open62541
Great and thanks again for your support!
 
Alois
 
Gesendet: Sonntag, 17. September 2017 um 07:13 Uhr
Von: Jake <thatcadguy@xxxxxxxxx>
An: "4diac developer discussions" <4diac-dev@xxxxxxxxxxx>
Betreff: Re: [4diac-dev] Fw: Re: Milestone and release of forte/open62541
Hi again Alois,
 
Understood. I'll take a look at the bugzilla and forums. I'd be happy to look at the Modbus client support, fairly well-versed with the protocol.
 
Best,
Jake
 
On Fri, Sep 15, 2017 at 11:23 AM, Alois Z. <alois.zoitl@xxxxxx> wrote:
Jake,
 
any help is more then welcome. Bringing FORTE to new devcies and test it on them is definitly worht the effort. When you plan to implement IO access I would wait till the embrick branch with the new IO architecture will be mreged back to the development branch. I expect this to happe by the end of this month.
 
Also writing new test cases would be helpfull.
 
There are currently quite some FORTE bugs in the bugzilla. This could also be worth a look. But maybe some of them require quite some diving into FORTE.
 
Finally a point which needs more work is the modbus Client support. There are several discussions in the current forums as well as the old forums on SF what the issue is.
 
Best,
Alois
 
Gesendet: Donnerstag, 14. September 2017 um 23:03 Uhr
Von: Jake <thatcadguy@xxxxxxxxx>
An: "4diac developer discussions" <4diac-dev@xxxxxxxxxxx>
Betreff: Re: [4diac-dev] Fw: Re: Milestone and release of forte/open62541
Alois,
 
Very exciting and impressive regarding progress so far.
 
Does the team have any development needs on the runtime side? I am fairly good with C++ but have zero Java experience.
 
Also, I have a Siemens IOT2040 collecting dust in the closet. I'll also have the FreeWave ZumLink programmable radio soon. I can try to compile the runtime and test things out on both if that hasn't been done for those products.
 
Best,
Jake
 
On Thu, Sep 14, 2017 at 9:58 AM, Alois Z. <alois.zoitl@xxxxxx> wrote:
Jake,
 
thanks but espcially on the RAM side we are not where I would like to be.
 
Regarding the PLCs we share the same vision, and maybe this vision is not so far fethed. Around 2010 I got a Mitsubish C controller for testing with 4diac. It somehow worked and soon after a new version of the controller was introduec. Unfortunately sofar I didn't get one for testing. Also there are now more open Siemens controllers. We have one where we are also running 4diac inside. Currently a little bit to clumsy to use for a public version but who knows what the future brings.
 
With three major European PLC brands (i.e., Wago, Bosch Rexroth, Bachmann) and two in the makeing (hopefully I can say soon more) I think we are in a good starting position.
 
Best,
Alois
 
Gesendet: Donnerstag, 14. September 2017 um 16:39 Uhr
Von: Jake <thatcadguy@xxxxxxxxx>
An: "4diac developer discussions" <4diac-dev@xxxxxxxxxxx>
Betreff: Re: [4diac-dev] Fw: Re: Milestone and release of forte/open62541
Hi again Alois,
 
That small memory footprint is impressive!
 
Sorry, what I meant was that hopefully someday we could have 4diac firmware images for many different PLCs, such as: Allen-Bradley, Siemens, Mitsubishi, to replace factory firmwares.
 
Best,
Jake
 
On Thu, Sep 14, 2017 at 6:16 AM, Alois Z. <alois.zoitl@xxxxxx> wrote:
Hi Jake,
 
we'll ty our best. I'm not sure if i understand the second part of your comment. We tried hard that FORTE is very portable. We run it on 4-6 different operating systems and also on rather small µControllres with rather little memory. So systems even below 256k of flash and 256k of RAM should be possible.
 
cheers,
Alois
 
Gesendet: Mittwoch, 13. September 2017 um 22:38 Uhr
Von: Jake <thatcadguy@xxxxxxxxx>
An: "4diac developer discussions" <4diac-dev@xxxxxxxxxxx>
Betreff: Re: [4diac-dev] Fw: Re: Milestone and release of forte/open62541
Thanks Alois, will keep that in mind. I would love to see every HMI/PLC/IPC/IoT manufacturer out there offering 4diac as an option. Price, usability of programming software, and hardware specs are altogether rarely ideal, but with the distributed processing scheme and one-stop-shop IDE, more ideal hardware choices can be made per application without sacrificing programmability.
 
Keep up the good work all!
 
-Jake
 
On Wed, Sep 13, 2017 at 8:24 AM, Alois Z. <alois.zoitl@xxxxxx> wrote:
Hi Jake,
 
Wow! Thanks a lot for your support. If you need any material or support let me know!
 
Cheers,
Alois
 
 
Gesendet: Mittwoch, 13. September 2017 um 17:20 Uhr
Von: Jake <thatcadguy@xxxxxxxxx>
An: "4diac developer discussions" <4diac-dev@xxxxxxxxxxx>
Betreff: Re: [4diac-dev] Fw: Re: Milestone and release of forte/open62541
Hi Alois,
 
Hoping to help you out there -- trying to convince FreeWave to give me a ZumLink radio to use with 4diac. I'm trying to introduce some PLC and automation manufacturers here in the US to 4diac as well. In an ideal world, every PLC should have an open-source option.
 
-Jake
 
On Wed, Sep 13, 2017 at 8:16 AM, Alois Z. <alois.zoitl@xxxxxx> wrote:
Hi,
 
to give also some ideas about the FORTE plans: We typically do synched releases featuring all 4diac components. Curerntly our biggest show stopper are some broken features in the IDE which we hope to fix in the next months. The code cleanup and model improvements we started there turned out to be bigger then expected. Furthermore there are also some license issues to be solved for the library and the example. See here also my mail on the incubation mailing list. But I hope that we can have a 1.9.0.M2 by mid of October.
 
I want to repeat here also my call for testers of the current state of 4diac ide. Please grab 4diac-ide's development branch from the git repo and use it for your work with 4diac instead of any released version. This would give us the feedback on where we stand with the clean-up and infrastructure improvements of the ide.
 
Cheers,
Alois
 
Gesendet: Mittwoch, 13. September 2017 um 16:29 Uhr
Von: "Jens Reimann" <jreimann@xxxxxxxxxx>
An: "Stefan Profanter" <profanter@xxxxxxxxxxx>, "4diac developer discussions" <4diac-dev@xxxxxxxxxxx>
Betreff: Re: [4diac-dev] Milestone and release of forte/open62541
Hi,
 
sorry for the confusion .. I just double checked the Fedora 28 release schedule and the branch off point will be 2018-02-20 [1].
 
What that work better?
 
Cheers
 
Jens
 
On Wed, Sep 13, 2017 at 4:24 PM, Stefan Profanter <profanter@xxxxxxxxxxx> wrote:
Hi Jens,
there is currently no concrete plan for the release of open62541 version 0.3
 
We (open62541) will probably wait until the current open Pull Requests and features like encryption and nodeset compiler are ready and then release 0.3. but this will take a few more weeks, and then there will be a release candidate before the 0.3 release.
So unfortunately we will not be able to get everything ready until the end of october.
 
So even if there would be a new release of forte until then, open62541 will not be ready to be tagged as 0.3.
 
BR
Stefan
 
-----Original Message-----
From: Jens Reimann <jreimann@xxxxxxxxxx>
Reply-to: 4diac developer discussions <4diac-dev@xxxxxxxxxxx>
To: 4diac developer discussions <4diac-dev@xxxxxxxxxxx>
Subject: [4diac-dev] Milestone and release of forte/open62541
Date: Wed, 13 Sep 2017 14:15:00 +0200
 
Hi,
 
I know this is a cross-project topic, but maybe we could have the discussion here.
 
As I would like to continue bringing 4DIAC forte into Fedora 28, I would like to evaluate how we can time this. Fedora 28 will branch off of Rawhide at the end of October IIRC.
 
1) Can we have a final version of open62541 0.3 by then?
2) Can we have a forte milestone tag using open62541 0.3 around the same time?
 
No pressure :-D I am just trying to figure out how we can approach this from a release perspective ;-)
 
Cheers
 
Jens
  
_______________________________________________
4diac-dev mailing list
4diac-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/4diac-dev

--
fortiss · Landesforschungsinstitut des Freistaats Bayern
An-Institut Technische Universität München
80805 München
Germany
 
Amtsgericht München: HRB: 176633
USt-IdNr.: DE263907002, Steuer-Nr.: 143/237/25900
Rechtsform: gemeinnützige GmbH
Sitz der Gesellschaft: München
Geschäftsführer: Dr. Harald Rueß, Thomas Vallon
Vorsitzender des Aufsichtsrats: Dr. Manfred Wolter

_______________________________________________
4diac-dev mailing list
4diac-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/4diac-dev
 



--
Jens Reimann
Senior Software Engineer / EMEA ENG Middleware
Werner-von-Siemens-Ring 14
85630 Grasbrunn
Germany
phone: +49 89 2050 71286
_____________________________________________________________________________

Red Hat GmbH, www.de.redhat.com,
Registered seat: Grasbrunn, Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Paul Argiry, Charles Cachera, Michael Cunningham, Michael O'Neill
_______________________________________________ 4diac-dev mailing list 4diac-dev@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/4diac-dev

_______________________________________________
4diac-dev mailing list
4diac-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/4diac-dev
 
_______________________________________________ 4diac-dev mailing list 4diac-dev@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/4diac-dev

_______________________________________________
4diac-dev mailing list
4diac-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/4diac-dev
 
_______________________________________________ 4diac-dev mailing list 4diac-dev@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/4diac-dev

_______________________________________________
4diac-dev mailing list
4diac-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/4diac-dev
 
_______________________________________________ 4diac-dev mailing list 4diac-dev@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/4diac-dev

_______________________________________________
4diac-dev mailing list
4diac-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/4diac-dev
 
_______________________________________________ 4diac-dev mailing list 4diac-dev@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/4diac-dev

_______________________________________________
4diac-dev mailing list
4diac-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/4diac-dev
 
_______________________________________________ 4diac-dev mailing list 4diac-dev@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/4diac-dev

Back to the top