Metrics tell me (and confirmed on the CMRI Monitor) that my Arduinos respond to a poll in 50-150ms, depending on which of my Arduino code sketches I¡¯m running. ?None of these times seem to be a problem for JMRI as I¡¯m getting regular polling with no extra ¡°INIT¡±s. ?
What the metrics don¡¯t tell me but is easily determinable via the CMRI Monitor is that JMRI cycles its next poll in 15-16ms (JMRI 4.15.1 running on an old Dell with Windows 7 running a single Arduino as a SMINI node). ?When I add a node to the JMRI configuration but don¡¯t actually attach hardware, JMRI waits for 250-280ms before timing out on the phantom node before doing its next poll of the real node. ?When I had three phantom nodes (which were all there at one time or another but removed for upgrade or testing), I was seeing about a 1 second full cycle time. ?Moral of the story: ?disable polling to any nodes not physically present. ?Uncheck box to do this on the CMRI Network Manager window.
In the course of doing this testing, I found several things in the use of CMRI tools that either I don¡¯t understand or are idiosyncratic to the use of Arduinos as CMRI nodes or possibly are real bugs, all of which I will document in a new thread tomorrow.
Jerry
___________________________________
jerryg2003@...
