Here’s what more than 2,500 business decision-makers around the world say.Download the report
...with the Facility Hero app in hand! Discover how you can optimize your maintenance efforts today.Learn more
Access tailored services, 24/7 self-service and expert help. Anywhere, anytime, any project.Discover now
Everything you need to know about our IoT technology backbone.Learn more
Explore our global offerings or select your country from one of our five regions.Global
Découvrez nos offres globales ou sélectionnez votre pays dans l’une de nos cinq régions.
Goals and Symptoms
After reading barcode variable, cursor keeps blinking and seems to stay in input mode. Why ?
Using a barcode reader in Direct Input mode :
Normally, when barcode data is read, the barcode input data is stored in the barcode string variable and the input data is written to a device address.
But sometimes, the input data isn't written to the device address, and the numeric display stays in "input mode" (the cursor still is blinking, and seems to be in write mode).
Facts and Changes
XBTG Vijéo-Designer V4.4 barcode reader direct input mode
Causes and Fixes
This is due to the length of the string PLC variable : if the num of bytes of this variable is less than the length of the barcode variable, maybe the end character of this barcode variable (CR, or LF in general) won't be read.
Then, the result is that the string PLC variable remains in "input mode" since Vijeo-Designer hasn't recognized the variable as a barcode variable (and it is waiting for the end character CR or LF in general).
The solution is to set a higher length (num of bytes) for the PLC variable, so that Vijeo-Designer can read the end character (CR or LF in general) and recognize the string as the barcode variable.