??? 03/07/07 15:16 Read: times |
#134488 - As I said, it is not easy to find an example thst Responding to: ???'s previous message |
As I said, it is not easy to find an example thst is simple to explain, but I have had cases of such. I tried to come up with an example that was easy to explain NOT something for you to find a way around.
disabling all interrupts for the time of "measurement" and let the master recover from this not a good idea. In any serious 485 multinode system, the master will report "node x failed" after n requests without responses. Actually, here you stumbled on another example of the 2% being 100%. Any serious master will only wait so long for a reply and if the 2% can not be started 100% of the time a "master did not get response" error will occur. This one could be REALLY juicy. Just visualize a slave that 'goes dead' for n milliseconds x milliseconds after being asked "do you have anything" and responding "no". In that case the network would find this slave dead if there was between y and z nodes on the network since the time between being asked "do you have anything" requests is related to the number of nodes and also if any slaves say "no" or "yes" just imagine the intermittency of this one. NO, Jan I am not asking you to find a way around this, just accept that such can happen both when "it was the worst of times and it was the best of times". Erik |