03-14-2024 04:03 PM
Hi,
I use the NexeedIPScanner-Peripheral with the NexeedScanner Object. It is working fine when after the read-command a code is received. Then, the next read-command is working ok. But if i cancel the unit (Execute to false), the unit is ready, but after starting reading command again, i have to scan two times. The first scan has no affect (unit is still in running and no OutCmd.Code), the second scan is working normal (unit in done and Code present). Does somebody have a solution for this? At the moment it is ok because the worker knows to scan 2 times 🙂
03-15-2024 11:07 AM - edited 03-15-2024 11:15 AM
What version of IP scanner you used.
i think the cancel is needed here because the scanner is a handheld scanner.
In the newest version of the IP scanner peripheral you have a option for select what type of scanner you used.
With this you no needet cancel the cmd and start this from new.
This is the ReleaseNote
https://community.developer.bosch.com/t5/Release-notes/Object-Release-07-23/ba-p/80253#56_en
03-15-2024 03:27 PM
I use Scanner peripheral 1.1.20 and Scanner object 1.2.4. Yes it is a handheld scanner. But this schould not have any influence, because the only difference between fix scanner and handheld should be the trigger (hardware or Sign). But after Cancel both scanner should be able to work normally. The trigger is empty (and this is also mentioned in parameter discribtion from peripheral for handhendheld scanners).
I tried the cancel input, but this has no effect.
03-18-2024 11:50 AM
Hi,
you are not using the actual peripheral and object version.
Peripheral --> 1.2.1
Object --> 1.3.1
03-18-2024 12:35 PM
I know that. But the version history of the new objects does not say that such an error has been fixed. The problem is not new either; I've seen it in many older versions here too. I helped myself to swap the scanner from IP to serial; But that is not possible here