Hi,
We have a freewave radio network connected to CR10x's. I have the schedule set to collect data hourly. Primary retry interval is 15s and number of retries is 5. Secondary retry is off.
My question is, why does loggernet keep trying to to connect to these loggers even after 5 tries are exhausted. If they don't connect it keeps trying over and over the whole hour!
Any ideas?
Thanks
What version of LoggerNet are you working with? Do you have any extra response time on the devices (COM ports, dataloggers, etc.) in your netwrok map? If so how much?
I am using Loggernet 3.4.1
There are 2s of response time on the NL100 and 2s on the PakBus Port
Though this doesn't explain the behavior you described, the speed at which you're trying your retries is being complicated by the delays you've added. In my testing of a NL100 to CR10XPB link (no FreeWave radio) with the same collection schedule as yours and the same 2 second delays added, the first retry attempt occurred at 00:00:45, the second at 00:01:30, the third at 00:02:15, the fourth at 00:03:00, the fifth at 00:03:45, and then the next time an attempt was made was at 01:00:00. This is as it should be other then the fact that the retries happened later then they were scheduled to.
This is probably too complex of a problem to resolve in this forum. Feel free to contact me at GELyon at campbellsci.com if you'd like me to look into this further with you. Before doing so however I'd like you to confirm the retries are being racked up as you describe.
In the Status Monitor select the "Edit" pull-down menu and then the "Select Columns" menu item. In the resulting interface add the "Coll Retries" column to your "Selected Columns" list and then click "Ok". Use this statistic to confirm that more than 5 retries are occurring within the same hour.