Hi, I have a problem with a dual remote connection setup through RS232 and NL115 and CR1000.
Basic problem is that the NL115 connection becomes non responsive to loggernet4.1 connection when I plug anything into the RS232 port. This is either direct connection via usb/RS232 or using a Wavecom WMOD2B GSM Modem remotely.
However the programme that is running on the CR1000 has a web page for quick client reference of the public and tables via the web.
This still functions when I have the RS232 in use, so the NL115 is passing some traffic through to the router and web.
If I unplug any device link from the RS232 port the CR1000/NL115 can be connected to via loggernet4.1, via the router or remotely.
Setup:
Netgear 614, 4 port router, Wireless modem always on,
static ip and fixed network ip addresses on router and CR1000/NL115
CR1000 (updated to op 22)
Attached: NL115
CS I/O: RF411
RS232: Wavecom WMOD2B modem
2x CS450
Relay control via 12v switch and Control ports
Other loggers on network (pakbus)
2x CR800
CS I/O: RF411
OTT bubbler system
CS450
One station with rain gauge and Ground & water temps (107)
Notes: The Netgear614 router is used because I have 2 other probes which run as independent devices over eithernet. I added the wavecom modem as a backup communication device to the logger system if the router or web modem fails. (Which has happened already due to weather & lightning )
I suspect I need to change something in the deployment setup, but can’t see what I need to alter; the CR1000 manual has no examples of deployment.
Also can the deployment settings be altered via the Wavcom modem/RS232 remotely?
Regards
Nigel
hi,
this smells like duplicate Loggernet Pakbus Addresses (default 4094) concurrently in use.
Try to change it via Setup Screen (Options->Loggernet Pakbus Settings), so you have a unique pakbus address for each pakbus port in use.
e.g.
Link via RS232 : change from 4094 to 4001
Link via IP : change from 4094 to 4002
Link via Modem : change from 4094 to 4003
As long each Loggernet Pakbus address is unique there is no need to change it from default.
Thanks anyway Artmann, I looked into your suggestion but you cannot set pakbus individual addresses on the rs232, TCP or CS I/O. The pakbus address is a single device address only.
Problem solved though, turned out to be a Router rule problem.
I had set HTTP to port forward, but forgot to set port forwarding for 6785. Hence why I could see the web page on the logger but not connect via loggernet.
Just in case others suffer this fate, Artmann is correct in what he said. He was referring to the Pakbus address of the Loggernet servers that are contacting the single logger. If you have multiple servers connecting to one logger or one server connecting to the same logger via different interfaces. The pakbus ports used in Loggernet must all have distinct Pakbus addresses.
You set this Pakbus address in Loggernet, using the Setup tool, under options.
To be honest we find the networking always a bit hard to follow logically, an example of this is the connection tree in the loggernet where you add the packbusport(which is the PC loggernet) after the ip address of the device like the NL100.
Actually we have a case for 3 NL100's in a group acting as group wireless coverage so that they act as one device...but to us it still looks like one of those has to be a master and the others clients.
There is no step by step setup directions/instructions for this sort of thing.
"There is no step by step setup directions/instructions for this sort of thing."
I would say that, to date, what you are describing is a corner case. So it does not surprise me that a step-by-step has not been laid out. However, I can agree that a Q&A or network examples document could be useful. A clearing house if you will for reported network architectures and how they were accomplished - could get messy though.
It seems that the PakBus TcpServer node type would be a perfect fit for what you are trying to do. Section 4.2.4.20 of LoggerNet manual.
+ PakBusTcpServer (specify PB and IP Addresses of NL100 1,2, and 3)
- pbRouter_1 (NL100 1)
- pbRouter_2 (NL100 2)
- pbRouter_3 (NL100 3)
- CR1000_1
- CR1000_2
- CR1000_3
Note the flatness of the tree structure implying that we don't care which NL100 the CR1000 is currently a neighbor of. Make sure that the NL100's are beaconing and verifying at a palatable rate. Try to find a balance between network traffic and the acceptable delay when the logger roams from one NL100 to the next. As long as one NL100 knows how to route to the CR1000, LoggerNet should be able to contact it.