For the past 3 hours or so, eagle.io has not been able to connect to my CR1000 datalogger. As far as I know, nothing in my eagle.io or datalogger configuration has changed and LoggerNet has continued to collect data during this time.
A few possibilities come to mind:
- An eagle.io outage of some sort. I did receive the communication and outdated alarms, so it doesn't seem like a complete outage.
- Someone on the datalogger LAN changed the network configuration such that incoming traffic from eagle.io is being blocked, but incoming traffic from my remote LoggerNet server is not being block. This is extremely unlikely, not impossible.
- A PakBus conflict, i.e., something else is connected on the same PakBus port that eagle.io. By the way, what port does eagle.io use? If eagle.io uses something other than the standard 4094 LoggerNet port, I doubt this is the problem.