We have a CR1000 connected to a Moxa NPort6250 and we wish to get the data to our LoggerNet server. The NPort is on a LAN on an island in the south Pacific using an ISP that changes the IP daily so we use dyndns.org to resolve the IP. The server running loggernet is in California. We can reach the server from a laptop on the same LAN as the Moxa but we cannot reach (via telnet, ping or traceroute) any port behind that LAN's exterior IP except port 80.
We think we should be using the TCP client mode on the NPort. We think the loggernet software needs to be able to reach the CR1000, through the NPort, to see the table definitions.
We do have port 6785 open on the server with a hole through the firewall to the outside.
We think the NPort is reached through port 4001 or 4003.
There is a narrow window of time while someone is on the island to change settings on that end. We have no (successful) experience with this setup and do not know the correct terminology. We seek advice how to set the NPort, what settings to use in LoggerNet, and how to diagnose the lack of connection.
Opening port 6785 on the server allows the CR1000 to connect to loggernet. For loggernet to connect to the CR1000 you need to open up a port on the LAN and firewall.
Alternatively program the CR1000 to connect to the server.
The NPort6250 encrypts the data according to the manual. You need to ask if this is an issue.
* Last updated by: EarlyBird on 2/7/2014 @ 4:32 AM *
We would like to do either of those solutions but have not figured out how. What mode should the NPort be set to for each of these? Is it "TCP Client" or "TCP Server" or one of the other modes? If the CR1000 sends its data to LoggerNet, how does LN get the table definitions? How do we see the data is arriving? The setup page for defining files to save to seems greyed out, likely because I have not configured something right.
As a test, I have successfully gotten data from a colleague's CR1000 by calling it from LoggerNet, but that one is on an easier IP to access (no routing, firewall, or whatever is blocking access to ours.) Loggernet just detected the settings it needed.
We do not know how to "open up a port on the LAN". We do not think it is the firewall, as we did a test where we completely disabled the firewall and still could not get through to any but port 80. I realize this may be vendor specific to the modem, switch, and router. There is a Linksys and a Cisco.
Hello Gastil,
I will be of little help on the NPort, but on the datalogger side, one solution to try is, you can set the PakBus/TCP Client Connection setting to the IP address of LoggerNet. In this way, the datalogger will always attempt to maintain a connection to LoggerNet. For data collection, use the SendVariables command in the datalogger, using Public as the table, and Call-back as the Fieldname.
When LoggerNet "sees" the Public, Callback message from the datalogger, it will initiate data collection. Table definitions will be resolved from that communication. Also, in LoggerNet's Connect window, you can go to the Datalogger menu, "Associate Program" and choose the TDF with the same name as your program. This will provide LoggerNet with the table definitions, and it will then only have to request a "summary" table definition file from the datalogger. If the information LoggerNet has matches what the datalogger has, then collection will begin, otherwise LN will update the table definitions first and then collect.
Dana
The way I do this with my network of loggers is to have the loggers initiate the communication, I never have a static IP.
The logger is programed using TcpOpen() using the dyndns address to resolve the IP of the PC running Loggernet.
My router has port 6785 opened and set to direct data to the PC running loggernet.
Loggernet is set for call back and to maintain the link.
I use the connect screen-status monitor-log tool to check activity.
When a connection is established Data Tables and Data Collection are automatic as described by Dana.
From your description you have this all in place except setting the logger to initiate the connection. To do this you add a TcpOpen() and a Senddata() instruction in a slow sequence.