Has anyone connected a CR1000 to Loggernet Admin using the starlink network and wifi? I have a site without cell coverage, but has a nearby starlink base station and I can see the starlink wifi using my phone at the station. I'm thinking I could use an industrial wifi gateway to connect the CR1000 to the starlink hotspot. I do not believe I can get a static ip through starlink, so I think any data transfer will need to be iniated by the CR1000 back to my server, Does anyone have experience with this?
I agree, Paul, that the CR1000 will need to initiate the connection out.
Campbell Scientific offers multiple solutions, including Konect Data Services and Konect PakBus Router (https://www.konectgds.com/). With Konect Data Services, you can collect, store and visualize your data. With Konect PakBus Router, you can route to and from the datalogger with LoggerNet and LoggerLink.
Alternatively, you can have the CR1000 initiate a connection back to your own LoggerNet server or a publicly accessible PakBus datalogger used as your router.
The easiest (and also very aggressive) connection method is to use the datalogger Network Services setting PakBus/TCP Clients Address, where you would indicate the destination URI or IP address.
Alternatively, you can use the TCPOpen() instruction under program control.
Is this also applicable for CR1000X?
Hi, Jon. I've been successful personally now using the Starlink Mini with Roam service to connect CR1000, CR1000X, CR1000Xe, CR350-WIFI to Konect GDS and the later two to CampbellCloud. Some over Wi-Fi, some over Ethernet.
Sam are you utilizing the Konect PakBus Router in these applications/proof of concept setups? any hiccups due to the CGNAT protocol that Starlink utilizes? or special formatting needed? or does the Konect PakBus Router seem to work transparently?
Hey Furban,
Konect PakBus Router usually works transparently. For me, the router handles communication without any special formatting.
This post is under review.