Your data logger may record great data, but if you can't retrieve it, the data isn’t going to do you much good. To ensure your successful data retrieval, it’s essential that you can troubleshoot possible problems that may arise with PC-to-data-logger communication over a serial connection. This article looks at six of the most common problems and explains how you can easily resolve them.

#1 - Power Connection

Most Campbell Scientific data loggers need between 10 and 16 Vdc connected to the power input. A good power supply is between 12 and 14 Vdc. To ensure your data logger is getting the power it needs, make sure your power supply is not switched off. Some data logger models make this easy to do by having a light on them that flashes when they are active. Even if your data logger doesn’t have this feature, you can still use a voltmeter to check the voltage at the power input.

TLazSerial v0.1 EDIT (january 2017): new version v0.2 in Github Serial Port Component for Lazarus (windows and linux). By Jurassic Pork 03/2013 This library is Free software; you can rediStribute it and/or modify it under the terms of the GNU Library General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version.

Re: TLazSerial: serial port component for Lazarus (windows and linux). « Reply #283 on: December 21, 2018, 07:27:36 am » Quote from: Jurassic Pork on December 17, 2018, 05:54:37 pm.
Hello: I want to use Arduino with Delphi controlling the serial port. Use Delphi Tokyo 10.2. What you have to do is the interface of Delphi is to turn on and off a Led, then you get messages from Arduino indicating when the Led is on or off.

#2 - Serial Cable Connection

A serial cable must be properly connected between the PC and the data logger. For example, some data loggers have two types of ports, and it is important to use the correct cabling for the one you are connected to. On Campbell Scientific data loggers, there are two types of 9-pin connectors: CS I/O and RS-232. With RS-232, you can either connect a straight-through cable between the RS-232 port on the PC and the RS-232 port on the data logger, or you can use a USB to RS-232 cable. If you are connecting to a CS I/O port, you must also use an RS-232 to CS I/O converter, such as the SC32B Optically Isolated RS-232 Interface.

#3 - Baud Rate Selection

The baud rate you select in the software must match the baud rate of the data logger serial port. For example, CR200-series dataloggers and CR10X dataloggers are always 9600 baud. CR1000 and similar data loggers can handle baud rates up to 115200. The CR1000 defaults to a baud rate of -115200, which means 115200 with autobaud enabled. The autobaud option tries to adjust the baud rate automatically to match the PC. Although autobaud is reliable at adjusting down the baud rate, it does have trouble adjusting up from 9600 to 115200. So, if someone else connects to your CR1000 at 9600 baud, you may have trouble connecting at 115200. After you successfully connect, you can change the baud rate setting for the serial port on the data logger.

#4 - COM Port Selection

The COM port you select in the software must match the physical port on the PC used for the connection. This was rarely a problem on older computers with a built-in serial port because the port was almost always COM1 and didn’t change. These days, however, most of us use USB to RS-232 cables, and Windows assigns a COM number to the cable. It is common for Windows to assign a different COM port number to the cable depending on which USB port you plug it into. Depending on the driver, however, you may be able to specify the port number to use. Invalid COM port selection is one of the most common communication problems:

Figure 1: Error seen when an invalid COM port is selected.

Use the selectable list of COM ports in the software to verify what port number is assigned to your cable:

Figure 2: USB to RS-232 cable in list of available COM ports.

Lazarus Log Homes Problems

If your USB to RS-232 cable does not appear in the list of available COM ports, check that the USB driver is properly installed.

#5 - COM Port Availability

The COM port you want to use must be available and not already in use by another software program. When a piece of software has a COM port open, Windows prevents all other software from accessing it. You will receive an “Access is denied” error (Figure 3) when attempting to use an already open COM port. Close other software that may be using the port, and try again.

Figure 3: Error received when COM port already in use by other software.

#6 - PakBus Address Selection

The PakBus address you specified in the setup of the software must match the PakBus address of the data logger. All data loggers with PakBus operating systems have a default PakBus address of 1. If you previously connected successfully with the data logger using the same computer, the setting is likely correct. If you are unsure of the PakBus address of the data logger, you can use the Device Configuration Utility to check the PakBus address of the data logger when it connects.

Additional Insight

When it comes to problems connecting with a serial cable, don’t be afraid to check the simple, obvious things first. Now and then, we all forget to flip a power switch or accidentally plug a cable into the wrong spot.

│Deutsch (de) │ English (en) │ español (es) │ suomi (fi) │ français (fr) │ magyar (hu) │ Bahasa Indonesia (id) │ italiano (it) │ 日本語 (ja) │ 한국어 (ko) │ português (pt) │ русский (ru) │ slovenčina (sk) │ 中文（中国大陆）‎ (zh_CN) │ 中文（台灣）‎ (zh_TW) │

2Lazarus-CCR Released Components
3Packages/Programs for FPC/Lazarus (not hosted here)
- 3.15Hardware Access

Default components provided by Lazarus

The rest of this page covers components not delivered with Lazarus. For the default components provided with Lazarus, please see Lazarus Components Directory.

As Lazarus uses the FPC compiler, you can also use packages provided by FPC. See Package List.

Lazarus-CCR Released Components

Note: This list is not complete. A lot of components in Lazarus-CCR are mentioned under the not hosted here section

Note: Please move ONLY the components/applications/programs in the Lazarus CCR repository from the list below into this list

Archiving

FreePascalArchivePackage - Conversion of TurboPower Software's Abbrevia library for the Free Pascal Compiler

File formats

CsvDocument - CSV files handling using parser or cell-based API similar to one of StringGrid component.
FPSpreadsheet - A library for handling spreadsheet files. Supports the formats from MS Excel (XLS, XLSX, Excel XML) and OpenOffice. It also supports these file types: CSV, HTML, Wikitables.
fpvectorial - Text Document Support - A library for handling text document files. Currently supports exporting to .docx and .odt file formats only.

Tools

ExtraSyn - Additional highlighters for TSynEdit
LazBarcodes - Generate barcodes (QRCode, Aztec, DataMatrix, ...)

Visual components

Flag component is a collection of flags.
Fshcomp - Edit components.
HistoryFiles - A component for store the recent files list into an .ini file and show the result into a menu.
LongTimer - Visual component based on TIdleTimer working with long intervals (Daily, Weekly or Monthly)
Poweredby - Visual drop-in component to show a 'Powered by Lazarus' splash screen for 1 second on form.create() Promote Lazarus/FPC!
ScrollText - Visual component that displays up-scrolling text (like a Credits screen)
TPlaySound - Visual component to play WAV files in Windows and Linux

Packages/Programs for FPC/Lazarus (not hosted here)

Uncategorized

5dpo (5dpo Component Library - Sdpo) is a set of components released by the 5dpo Robotic So

Serial Port Component For Lazarus Log