When you have work to do, there’s nothing more frustrating than being unable to connect to your datalogger in the field. We’ve all been there: You’re in LoggerNet’s Connect window pressing the Connect button, and you’re met with nothing but the endless flashing “connecting cable” icon.
Before panicking, there’s a setting you’ll want to check in LoggerNet’s Connect window, which may be the culprit. Fortunately, if it is the culprit, it’s a quick and easy fix to restore your connection.
Force Connection is a toggle that you can access from the Connect window’s Edit menu. When a checkmark appears beside the menu item, the setting is enabled (on). When the checkmark is cleared, the setting is disabled (off).
By default, the Force Connection setting is enabled. This means that whenever you press the Connect button, the LoggerNet server immediately attempts to establish communication with the datalogger. Once connected, you’ll see data updating in the Connect window’s Table Monitor, as well as regular datalogger clock updates.
Disabling the Force Connection setting is a handy feature in certain scenarios, but it can also cause you a lot of grief if the feature is disabled unintentionally.
If the Force Connection setting is disabled, whenever you press the Connect button, the LoggerNet server does not immediately attempt to establish communication with the datalogger. Rather, LoggerNet waits until it has a task to perform with the datalogger before attempting communication. For example, if the Force Connection setting is disabled, and you press the Connect button and then the Collect Now button (or some other button that requires communication with the datalogger), LoggerNet will then attempt communication.
Huh… “So what good is THAT?” you might ask. Yes, there is a positive side to disabling the Force Connection setting.
Disabling the Force Connection setting can be useful in scenarios where the LoggerNet server cannot directly access the datalogger because of a firewall or other security restrictions, but the datalogger is able to call in to the LoggerNet server. If the Force Connection setting is turned off, and you’ve pressed the Connect button, when the datalogger calls in (via callback), the LoggerNet server opens the connection with the datalogger to collect the callback data. The connection remains open until you close it. While the connection is active with the datalogger, you can check Station Status values, send a new program, or perform other station maintenance activities.
To recap, here are a few things to remember about the Force Connection setting:
I hope this tip has been informative and helped you uncover your connection culprit. If you think intentionally disabling the Force Connection setting could be a useful feature in your application, leave a comment below and let me know!