lostcontrol
Lifetime Supporting Member
Hi Chaps,
We had to try and diagnose an issue today, with a SLC & 2x ML1500's connected via Serial Comms over a Radio.
One of the sites was not responding (2), which in turn was giving false information from the 2nd site (3).
The attached .rss file is a snippet of how the comms are done. I saw this, and thought that this is not the best way to handle this type of comms, especially over radio.
If I were to do it from scratch, I would of made each MSG instruction mutually exclusive.
Anyway, as this site has been running for 8+ years, with occasional issues if one of the sites failed, we had to get to the bottom of it.
My understanding of this code config, is that as the poll to Site 2 is first, then that MSG instruction will execute, then the 2nd instruction will be queued in the buffer, and sent when the port is available, unless of course it is possible to poll 2x nodes at the same time over a serial link?
If there is then a failure, or partial reply, it is possible that the successful poll registered as a failed poll, therefore not sending the data to the required destination??
When we first got to site today, we noticed that the Send data was working, as the remote sites were responding to commands from the master, but the data coming back was what appeared to be corrupted.
What I did, was disable comms to the site that was not responding, and the active site worked fine, without skipping a beat.
Our plan is to correct the code, so that each MSG instruction is executed exclusively (unless there is a valid reason why not ??), then diagnose the potential faulty radio at the site that is not responding, if indeed it is faulty...
Are my assumptions about what the potential issues with the buffer are, and the rectification of the polling sequence correct?
Thanks
We had to try and diagnose an issue today, with a SLC & 2x ML1500's connected via Serial Comms over a Radio.
One of the sites was not responding (2), which in turn was giving false information from the 2nd site (3).
The attached .rss file is a snippet of how the comms are done. I saw this, and thought that this is not the best way to handle this type of comms, especially over radio.
If I were to do it from scratch, I would of made each MSG instruction mutually exclusive.
Anyway, as this site has been running for 8+ years, with occasional issues if one of the sites failed, we had to get to the bottom of it.
My understanding of this code config, is that as the poll to Site 2 is first, then that MSG instruction will execute, then the 2nd instruction will be queued in the buffer, and sent when the port is available, unless of course it is possible to poll 2x nodes at the same time over a serial link?
If there is then a failure, or partial reply, it is possible that the successful poll registered as a failed poll, therefore not sending the data to the required destination??
When we first got to site today, we noticed that the Send data was working, as the remote sites were responding to commands from the master, but the data coming back was what appeared to be corrupted.
What I did, was disable comms to the site that was not responding, and the active site worked fine, without skipping a beat.
Our plan is to correct the code, so that each MSG instruction is executed exclusively (unless there is a valid reason why not ??), then diagnose the potential faulty radio at the site that is not responding, if indeed it is faulty...
Are my assumptions about what the potential issues with the buffer are, and the rectification of the polling sequence correct?
Thanks