Hello,
I have a cr1000 with a NL120 in a meteorological station, the station work perfectly, but a few days back all the communication have lost, I can't connect with ip access and direct connection neither, the only way to connect the logger is shutt off the power for a couple of seconds and power again, but the communication are lost a few minutes after.
I can not establish communication using the "dev config", I can only communicate PC-CR1000 if I remove the power for a few seconds and then I reconnect.
The batery is Ok and all the data are saved in the logger, only the comunication have lost, the next errors are show:
*Packbus framing error”, “invalid low level signature
*transaction failure, timed out or resource error, check/set clock
*transaction failure, timed out or resource error, table poll, program.status_clone
You know what can i do??
Thank you in advance
Regards
The Pakbus framing error would be indicative of poor quality communications which is corrupting or more likey, in the case of TCP/IP comms, losing data.
On bad connections older versions of the logger could stop communicating via TCP/IP. So I would advise upgrading the datalogger operating system as one measure, because that may stop the logger refusing to talk altogether.
If this lets you get a more permanent communications connection check the error rate. If non-zero it is possible there is a hardware fault or some fault in communications link away from the logger. You should use standard networking techniques to check the link and likely cause, e.g. use ping to test for lost packets and tracert to check for faults between you and the logger.
Simple hardware issues could be the NL120 is not fully plugged in, loose or broken cables etc. If the link back to you includes a radio link (GPRS/Satellite) check aerial connections, alighnment etc. More serious faults could be lightning damage of the NL120 or other parts of the communications link back to you.
Thanks for the reply
In a couple of days I will return to the station and will update the operating system also will check the connections to the logger or something that I have missed the last time to review the station
What catches my attention is that the station was working well for several months and a couple of days ago communication was lost, something I forgot to mention is that this same problem occurs if you try to connect by direct connection to the logger (using a cable RS-232), I can only connect a couple of minutes if I disconnect the power to the logger a couple of seconds before you connect to the logger, during these minutes online communication also works well
Best regards
I wonder if this might be another issue entirely. Are you sure that nobody else is trying to connect to the datalogger at the same time as you. This will normally work fine but the Pakbus address of the calling PCs must be different. If they are the same you will end up with the connections coming and going every few seoncds. Resetting the logger breaks all current connections so the first one after that will get the connection until the other server tries to talk too.
You can change the Pakbus server address for any Pakbus server via the setup screen of Loggernet.
Hello,mmmm I have a PC running Loggernet4 and LNDB to collect the data every 15 minutes from 2 station (CR800 and CR1000), the station with CR800 don't have problems, some days i connect to both stations with the laptop to look the data (and the PC with LNDB still collect the data every 15 minutes), but now can't connect from the PC and can't connect from the laptop, nobody can connect to the CR1000 station!! but the station with CR800 still work fine.
I will update the operating system and see what happens
Thank you for the help
I will comment news
As Andrew points out in his post, the problem is likely the conflicting PakBus addresses of the PC and the laptop. Try changing the PakBus address of one of them -- ALL devices in a PakBus network must have a unique address.
In LoggerNet, go to the Setup window. Under the Options menu you will find LoggerNet PakBus Settings. This needs to be set to a value between 4000 and 4093 (since one copy of LN is already using 4094).
Dana
Hello Dana and Andrew,
Just returned from the station, try to change only addresses packbus both PCs but gave no results, then update the CR1000 operating system to the latest version and so far everything works fine.
Thank you very much for the support
kind regards
Hello Andrew and Dana
Just returned from the station, try to change only addresses packbus both PCs but gave no results, then update the CR1000 operating system to the latest version and so far everything works fine.
Thank you very much for the support
kind regards
Hello
It's me again with the same problem as before, my station was working normally a couple of weeks but again I can not connect to the station, get the following error:
unexpeckted socket error "," 10060 "," connection timed out
i was Change the direction packbuss of PCs and upgrade the firmware (CR1000 recorder) to the latest version, as suggested. But the solution only worked a couple of weeks
Can you help me with some other suggestions???
It could be any connection setup from my internet provider? when I ping to the IP address of the CR1000 always get an answer in my pc.
Is there any way to update the firmware of NL120?
Thank you
Best regards
I am guessing you have a router of some sort between the logger and the wider internet? Is this a wired or wireless router (GPRS perhaps)?
If there is a router it is likely to be it that is responding to the ping requests rather than the datalogger.
If the connection is GPRS is there a chance that your internet provider does not allow you to hold TCP/IP connections open for long periods - some do not, on some networks.
Even on wired connections some will throttle or even block non-standard connections if they suspect Point to Point connections are being made to run torrents protocols, which may be in breach of their contracts.
You will need to check with them if either are likely.
Regarding the NL120 there is no separate firmware for that product - it is built into the main logger operating system.
* Last updated by: aps on 3/5/2012 @ 10:17 AM *
Hello,
Was there any resolution to this topic? I too have 8 separate wx stations that are using CR1000s and NL120s or NL115s and they seem to experiencing the same problem. TCP/IP coms fail randomly and infrequently.
This is occurring using both OS 24 and 27. we are in the process of trying the latest OS 28 to see if the problem persists into that OS too. The only solution to restore TCP/IP transactions is to power cycle the logger. Our com path is Loggernet Server Admin>LAN>WAN>Sierra Wireless Cellular Data modem>NL120/115>CR1000.
We have multiple servers and it occurs on separate servers as well. I have ruled out any failure on the modem side as we still have LAN>WAN connectivity back thru the cell modems after this problem occurs. It appears to be a problem somewhere between the network link and logger.
I have been in conversation with my local CSI rep and they suggested I post in the forum. I may start a new topic on this depending on response to this post.
Regards,
Joshua Handley
BC MoTI
Weather Network Program
We did discover an issue in the logger operating system that was fixed in an interim release (27.05) last year that could have symptoms like those you report. The issue was usually only seen on public networks (or where public traffic can route to the logger). The issue was often triggered by repeated connection attempts to the Telnet socket of the datalogger (as can happen with hackers port scanning). Memory was not being freed properly in this event and the logger would eventually run out of communications memory and stop communicating until reset. How long this would take varied with the network and local traffic.
As you were advised I would upgrade to OS28 which not only includes that fix but is based upon a new, more resilient TCP/IP stack.
As a follow up to this thread. We have upgraded some weather stations with the NL120 CR1000 combination to os 28. Unfortunately the problem has reoccurred with the latest operating system. Same symptoms as documented previously communications failure via tcp/ip and unresponsive cr1000.