Hello,
Have a CR1000x connected to a RV50 with a RS-232 to RJ45 to the CPI port of the CR1000x. It communicates with PPP. I've been messing around with the Web API trying to get it to work but can't seem to get it right. I'm using the modems IP, is there something i need to do to signify that I want to access a datalogger behind a modem?
Thanks,
Chris
The datalogger's HTTP Server needs to be turned on (should be by default). You will also need to setup a administrative user in the logger's web server. This can be done using Device Configuration Utility.
The modem also needs to have port forwarding turned on for port 80 (HTTP) and have it pointing to the datalogger's PPP TCP/IP Address.
1. HTTP Server is on
2. Set up a user, although not entirely sure how to pass that information on. Still getting 502 errors though, so not even getting there.
3. The PPP tab in DevConfig lists the 192.168.15.100 as the IP and 192.168.15.31 as the gateway. I assume it is the 192.168.15.100? I've tried both.
4. On the RV50 I have the Public start/end at 80, protocol as TCP, Host IP as 192.168.15.100 and private start port at 0 also tried 80
Does that all sound correct?
Url im trying to use:
http://my-modems-ip/?command=ClockCheck
If the modem's firewall is setup correctly, you should be able to to http://my-modem-ip/ and see the datalogger's default web page. Private port for 80 should be 80 not 0. Yes, the IP address assigned to the datalogger is 192.168.15.100.
Is the IP address of your modem a static reachable IP address? What does the IP address start with XXX.XXX? I ask because some data accounts for cellular modems are dropped behind the providers firewall as well using private non-routeable IP addresses.
Static IP with ATT, 166.213.XXX.XXX not on a private network.
You're running a CR1000X via port forwarding on a public static IP?
So you count on the rareness of Campbell Loggers and the 'firewall' of the logger to take care of any traffic that is coming in from the internet trying to take over that machine?
The modem has got an Ethernet port, why don't you plug the logger into that?
Then get an account with a OpenVPN service and set up the modem as client and you can talk to the modem via Loggernet directly via that VPN.
The firewall of the modem then will protect your logger (it at least got one), you can drop the public IP requirement (saves cost and lands your modem behind a ISP NAT IP) and all your traffic to the logger will be secured by the VPN.
If you add a switch between the modem and the logger you can have several more Ethernet capable devices where the logger is located, like an IP camera for example.
Just my 2 cents..