Hi everybody!
My DevConfig (under Windows 11, LoggerNet 4.10) cannot get "fully" in touch with CR3000, CR6 and CR1000Xe dataloggers anymore.
I mean: it is apparently able to connect with the loggers, but cannot proceed after the "Find Dataloggers" panel. After 60 s, without getting a response by the DL, it says "Could not locate PakBus devices" and gives up.
Actually, the whole LoggerNet suite *is* still able to connect (locally) to the loggers. I did even update OS's through file trasfer and "Connect" can connect to all of them. So, communication links do work properly, but configuration for deployment (through a fully functional DevConfig) is not possible any more.
Has anybody found similar problem with DevConfig 2.35.01? Apparently, I am experiencing this trouble after the recent update.
I have tried to uninstall DevConfig 2.35.01 and go back to 2.34, but that does not seem fully possible (after successful uninytalling and installing 2.34, it keeps showing 2.35.01 as version number), and - anyway - does not change anything in the (annoying) behaviour.
Thanks for any hint!
Andrea
I am experiencing the same issue.
Jim B.
Device Configuration Utility v2.35.01 – Communication Issue
An issue has been identified with the Device Configuration Utility v2.35.01 were trying to connect to devices locally over serial connection fails to connect. For this reason, v2.35.01 has been removed from the website and v2.34 has been reposted. A fix is being worked on, and a new release will be posted soon.
The Device Configuration Utility can be installed on a computer by installing LoggerNet, PC400 or by installing it as a standalone. Because of this, you will need one of the following two methods to install v2.34 after having installed v2.35.1.
Method 1
Method 2