Problem in communication Publish/Subscribe [message #1741864] |
Tue, 30 August 2016 09:23 |
Michele Citro Messages: 29 Registered: June 2016 |
Junior Member |
|
|
Hi,
I want report an error in the communication Publish/Subscribe in my distribuited application (on 3 device).
I explain the problem better.
1. I have to publish the event CONTATTA_ZONAA on 225.0.0.1:61341 (in the attachement ZonaB).
2. This event, published, isn't received from PRONTA_ZONAB in 225.0.0.1:61341 (in the attachement ZonaA). But socket status is ok.
So, I tried to change ip and port also but nothing good result.
3. So, I tried to receive this event on another device (in the attachement ZonaC_trial) on 225.0.0.1:61341 always, and it's ok there.
Another trial:
4. I tried to receive this event on the same device of Publish (in the attachement ZonaB_trial) on 225.0.0.1:61341, and it's ok there.
Thus, in my opinion, the problem is on the device ZonaA.
What could be the problem?
Thank you.
Best regards,
Michele Citro
-
Attachment: ZoneA.png
(Size: 82.10KB, Downloaded 142 times) -
Attachment: ZoneB.png
(Size: 61.06KB, Downloaded 133 times) -
Attachment: ZoneB_trial.png
(Size: 70.10KB, Downloaded 130 times) -
Attachment: ZoneC_trial.png
(Size: 62.79KB, Downloaded 134 times)
|
|
|
|
|
Re: Problem in communication Publish/Subscribe [message #1741872 is a reply to message #1741869] |
Tue, 30 August 2016 10:45 |
|
Hi,
this is strange. My question for the other communication is are these mulitcast or point to point connections? Because I see that you are using addresses starting with 224 which is to my knowledge no multicast address. Or am I missing something. If this is the case what kind of devices are you using? RaspberryPIs? On these you often have to activate multicast routing so that multicast packets are sent over the network.
BR,
Alois
|
|
|
|
|
|
|
|
|
Re: Problem in communication Publish/Subscribe [message #1742788 is a reply to message #1741948] |
Wed, 07 September 2016 15:05 |
yuvaraj velumani Messages: 15 Registered: April 2016 |
Junior Member |
|
|
If possible, try to look the run time log or trace. There may be possibility of dropping the events since Forte is only capable of storing 254 events in it queue.
Or else there may be a chance of Publish happening before the Subscribe function block getting initialized.
Other option that you could try out is complete all subscribe initialization after E_RESTART and then start you application by connection the last Subscribe function block INITO.
As suggested by Gerhard, you can try with "Trigger Event" also
[Updated on: Wed, 07 September 2016 15:06] Report message to a moderator
|
|
|
Powered by
FUDForum. Page generated in 0.04157 seconds