I have run in to a problem since upgrading Loggernet Admin to version 4.2.1.1 with my RF450 network. It seems to be locking up the computers comm port. It will either try to collect data from most of my stations continuously,at the same time, or lockup and not do anything for a random time period.
At first I thought the RF450 base station Radio had failed, but the problem continued after setting up a new RF450.
I have updated the RF450 firmware, updated the comm port drivers, and still no luck.
I don't work much with RF450s, but a couple of suggestions:
* LoggerNet has a setting "Collect X records on first call". The default is to collect all records. If you already have data collected for these stations, you may want to change this setting for each datalogger to a specific number of records. That being said... you say you "upgraded". If you are using the same network map that was used in a previous version, data collection in LoggerNet should pick up where it left off. Note that data collection pointers for each datalogger are stored on the computer, not in the datalogger. So if you changed computers, or deleted the file that LoggerNet uses for the network map, then it would start all over again.
* Without log files/log messages, it is hard to understand what might be occurring, but you could be overrunning the serial buffer for the computer. One way to avoid this is to reduce the baud rate for the COM port.
Dana W.
Thanks for the reply. This happened after I installed 4.2.1.1 in late May, before that it was running fine. There were no computer or other changes made.
What files or logs would be helpful?
I will drop the baud rate and see how it goes.
Thanks again for the help.