User Forum A 24/7 resource for Campbell Scientific users

Hi,
I am trying to connect to a remote data logger using version 2.28.00.19 of Device Configuration Utility (DCU). I am trying to do this from both a laptop with the software installed separately and on a server with Loggernet installed.
I have previously connected to this logger using DCU from my laptop but recently when I try to connect (by clicking on the "Connect" button in the main screen) I get the error below:

The detected device type, coralib3.dll, is not currently supported

Furthermore, I have tried to update Device Configuration Utility to version 2.29.00.81 using both the "Update" tab in DCU and the Campbell Scientific Software Updater.
In both cases I get the following error:

Failure
Failed to finish update

I would be grateful for any advice you can give.

Thank you,

Tom O'Flynn

Hi,

I have looked at this again and realise I made a simple oversight.

I had omitted to include the PakBus address.

Once this is included the problem is resolved.

Tom

What troubleshooting steps can I take if I encounter the "coralib3.dll is not currently supported" error when trying to connect to a remote data logger using DCU?

hi i mentioned the pakbus but the error message still showing, any advice

The device configuration utility was originally designed to support only local direct communications with the devices that it configures.  In order to make the user experience as simple as possible, it uses the PakBus protocol to discover any neighbours that are connected when the link is opened and, by default, will latch onto the first PakBus address that it sees.  I'm not sure what you mean exactly by "connecting remotely" but I do suspect that it may involve using a service like Konect PakBus Router which uses an instance of LoggerNet to support incoming PakBus/TCP connections.  If that is the case or if your network topology is similar, the connection to LoggerNet will always be the first address that devconfig sees.  To make a long story short, if you are attempting to connect devconfig into a PakBus network that has more than one node, you will need to specify the PakBus address of your datalogger in devconfig's left panel.

With respect to the Software Updater, in order to do its task, your host computer needs to have a network connection that will allow HTTPS traffic to one of Campbell's servers.  If your host machine is isolated, this obviously will not work.  It's also possible that your network is configured to block all but allowed addresses in which case, you would need to communicate with your network admin.

I am also facing the same problem, the internet in my place is also not secure, is there any way to solve this problem? Thanks a lot!

The error with the coralib3.dll library in the Device Configuration Utility (DCU) often stems from either compatibility issues with the device model or an outdated software version. Here’s a structured approach to troubleshoot this:

1. Verify Device Compatibility: Ensure that your logger model is fully supported by your DCU version. Check if your model requires a newer DCU release to function without compatibility errors. Version updates sometimes resolve compatibility with certain loggers, especially newer or firmware-updated devices.

2. Manual Update Installation: Since the software updater is failing, try manually downloading the latest version of DCU (2.29.00.81) from Campbell Scientific’s official site. Then, install it directly without using the internal update tool, as issues with internet security settings might interfere with the updater tool on an insecure network.

3. LoggerNet and DCU Synchronization: Ensure both LoggerNet and DCU are up-to-date, as mismatched versions between these tools can sometimes lead to connectivity issues. A full reinstall of both may resolve persistent configuration issues, especially if they use shared DLLs or settings.

4. Network Security and Direct Connection: Given the security concerns on your network, connect to a more secure network (if possible) while performing software updates or connecting to the logger. Alternatively, download software updates on a secure connection and transfer them to your primary network if needed.

5. Alternate PC or Clean Installation: If these solutions don’t work, try installing DCU on a separate, clean system to rule out configuration issues on your primary setup. This approach can sometimes identify whether the issue is software-related or due to network/configuration constraints.