|
| Re: IP_ADD_MEMBERSHIP [message #1837548 is a reply to message #1837543] |
Tue, 02 February 2021 07:27   |
|
As already pointed out in another message the default SUBSCRIBE FB expects as configuration parameter a UDP Multicast address and a port. However you gave a UDP Uni-Cast address. In oder that 4diac FORTE can receive UDP multicast data in a real network it needs to send out this IGMP Membership message. However you are lucky and 4diac FORTE should still receive the data. The reason that you are not receiving any data is most probably your Ubuntu setup. You need to check if your loop back device is configured correctly and that you are routing UDP messages via loop back device. I noticed with some of my students using Ubuntu that there is a problem.
Furthermore I saw that you are using an E_CYCLE connected to the INIT of your SUBSCRIBE FB. This is not needed. IEC 61499 is fully event driven. That means you don't need to continuously trigger SIFBs. Especially resource initiated SIFBs like the SUBSCRIBE FB (you can identifie these with the IND output). These FBs will register themselves to the 4diac FORTE with the INIT event and will produce IND events as soon as they have some data ready for the application.
Cheers,
Alois
|
|
|
|
|
|
|
| Re: IP_ADD_MEMBERSHIP [message #1837703 is a reply to message #1837673] |
Thu, 04 February 2021 11:30 |
|
Hi Asterios,
sorry for confusing you. I think I have to clarify a few things. The description there mentions java classes but this is IMHO just a bad description because it also describes the underlying protocol which is a UDP multicast message for PUBLISH or SUBSCRIBE and TCP for CLIENT SERVER.
The reason I pointed you to that is that this document describes what a default 4diac FORTE subscribe FB expects. So you don't need to implement anything on 4diac FORTE side but you need to send the right message format from your phyton code and that is described there.
My other comment was that if you are not able to change the message format on your sender side (you mentioned some SCADA system) than you need to change the way 4diac FORTE works.
Cheers,
Alois
|
|
|
|
| Re: IP_ADD_MEMBERSHIP [message #1837730 is a reply to message #1837706] |
Thu, 04 February 2021 20:08 |
|
Hi,
Asterios Badios wrote on Thu, 04 February 2021 12:15
All good mate, no stress. The python test code sends the test message to the other 3 types of plcs perfectly (the pdf I send you on last message). so I don't want to change it.
I expected that. for that it would be good to have a description of the format and protocol.
Asterios Badios wrote on Thu, 04 February 2021 12:15
Just need to understand how I do this in 4diac.
Happy to pay for someones time or make a donation to a good cause to help me work it out to start with an example how I would do this ?
Thanks for the offer. this is kind. We would also do paid development. But given your description it should be rather low effort. As written above the first point is a description of the kind of data and I guess the interface you would like to use in 4diac. Should it be an array, should it be separate outputs. A simple starting point could be that you write your own com layer sitting above the ip layer. Hereby you can use as staring point the port and IP that is already working. In that layer you get data from the ip layer and you process it and apply it to the output. i think a good starting point would be the raw layer. Although this one excepts only ports of type string it nicely shows how such a layer would work.
I hope this gets you started.
Cheers,
Alois
|
|
|
|
| Re: IP_ADD_MEMBERSHIP [message #1837766 is a reply to message #1837737] |
Fri, 05 February 2021 17:46 |
|
Hi,
As pointed out above a starting point could be the Class CRawDataComLayer. you will not need to implement a full FB but just such a communication layer. Please have a look at the communication architecture documentation I already posted above. with such a layer you can use all of our standard communication function blocks.
If you provide us with some explanation of your packet format we can even draft you with a layer that you refine and debugg.
Alois
|
|
|
|
|
| Re: IP_ADD_MEMBERSHIP [message #1838774 is a reply to message #1838115] |
Thu, 04 March 2021 20:12 |
|
Hi,
sorry for the late reply. I've been pretty busy with the semester ending here in Austria. As pointed out above we would need a specification of your packet format and what should happen. With the current information I have a hard time to understand what you need.
Alois
|
|
|
|
Powered by
FUDForum. Page generated in 0.03944 seconds
] 
Search
Help
Register
Login
Home
