A Data Logger Connection Culprit with Benefits

de Dana Worley | Atualizada: 11/18/2015 | Comentários: 0

Pesquisar o Blog

Inscrever-se para o Blog

Receber e-mail quando um novo artigo é publicado. Escolha os temas de seu interesse.

Area / Application

Product Category


Corporate / News

Insira o seu endereço de email:

Sugerir um artigo

Existe um tópico que você gostaria de saber mais à respeito? Nos informe.

Leave this field empty

When you have work to do, there’s nothing more frustrating than being unable to connect to your data logger 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.

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

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).

Force Connection option with checkmark

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 data logger. Once connected, you’ll see data updating in the Connect window’s Table Monitor, as well as regular data logger 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.

Benefits and disadvantages of disabling the Force Connection option

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 data logger. Rather, LoggerNet waits until it has a task to perform with the data logger 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 data logger), 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.

The Benefits of Disabling Force Connection

Disabling the Force Connection setting can be useful in scenarios where the LoggerNet server cannot directly access the data logger because of a firewall or other security restrictions, but the data logger 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 data logger calls in (via callback), the LoggerNet server opens the connection with the data logger to collect the callback data. The connection remains open until you close it. While the connection is active with the data logger, 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:

  • If LoggerNet won’t communicate with the data logger, but no error messages are returned, take a look at the Force Connection setting in LoggerNet’s Connect window.
  • If the Force Connection setting is disabled, communication will not be established with the data logger until you initiate an action such as pressing the Collect Now button.
  • The Force Connection setting is a handy way to hold open a connection with a data logger that calls in via callback so that you can perform maintenance.
  • Once connected, the LoggerNet server maintains the connection to the data logger until you disconnect, or until the Maximum Time On-Line is exceeded. Thus, it’s a very good idea to set a Maximum Time On-Line (in the Setup window) for communication links.
  • The Force Connection setting is a global setting. When it is enabled, it applies to all data loggers in your LoggerNet Network map.

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!

Compartilhe este artigo

Sobre o autor

dana worley Dana Worley joined Campbell Scientific, Inc., as an Applications Engineer in 1997. During her career she has provided customer support and technical training, developed on-line and written documentation, managed a software test and support group, and managed a software product line. Dana currently works as a Project Manager in the Research & Development department. Outside of work, Dana enjoys hiking, biking, travelling, and photography. She is also an accomplished glass artist with expertise in glass fusing.

Veja todos os artigos deste autor.


Please log in or register to comment.