I have one Cr1000 connected in the following way:
Cr1000-CS/IO <> PC with Loggernet
Cr1000-RS232 <> Wavecom Modem
Cr1000-Nl120 <> 5 network connected PC with Loggernet
The network PC's are not connecting all the time to the NL120. I get it working sometimes, but there is no clear reason why it should not be working and think it is something very obvious.
All help will be welcome
Sincerely
James Kennedy
Make sure all the copies of Loggernet on different PCs have different Pakbus addresses for the Pakbus ports used to connect to the same logger. (Configure the address away from the default of 4094 in the Setup screen under Options.) If you do not do this the connections will be intermittent as each new connection will cause any existing connection to be lost as the logger will get "confused" several devices connecting to it with the same Pakbus address.
In addition make sure you have the latest release of operating system in the logger, as earlier versions had quite a low limit on the number of TCP/IP connections that could be made at one time.
Andrew,
Thanks. I forgot it also have a few connections via the loacal Inttranet to the published webpages.
Cr1000-CS/IO <> PC with Loggernet
Cr1000-RS232 <> Wavecom Modem
Cr1000-Nl120 <> 5 network connected PC with Loggernet
Cr1000-Nl120 <> 3 Pc's via published webpage
Will it make any difference to your previous answer to me ? I did upload OS ver 19.
Sincerely
James Kenney
No. You would definitely need OS19 though as the older OS'es had a limit of 12 TCP connections and quite a few were used for background tasks, such as DHCP, DNS etc.
I would also warn that you need to keep a careful eye on the logger status, in terms of skipped scans and records. I say this as if all these connections were current you would put a lot of load on the logger (which is optimised for low power use not web serving). If the datalogger is making a lot of frequent measurements it may get overloaded.