Error 20001: StarIO10IllegalDeviceStateError

[joarwilk]

Description

When discovering, it fails with error 2001: StarIO10IllegalDeviceStateError.

When shipping a batch of, say, 5 terminals, this can happen on 1-5 of those. It seems to be random.

How can we debug this invalid state?

Your device where the bug occurs

• Device: Castle S1F2
• OS: Verifone / Adyen, not sure about version

Your printer

• Model Names: mC-Print3
• Firmware Version: Unsure
• Interface: LAN

To Reproduce

Start discovery. An error is caught with error code 2001 and description StarIO10IllegalDeviceStateError. Sometimes its error 2000, with description "y"

Expected behavior

Printers are found

[can-miki]

I would like to ask you a few questions to confirm the situation.

My understanding is that there are 5 terminals (Castle S1F2) connected to 1 printer (mC-Print3) via LAN. Is that so? What API do you use for discovery?

Also, regarding StarIO10IllegalDeviceStateError I would like to check the following:

• Is there a problem with your network equipment?
• Is the printer turned on?

The flow when connecting the printer and device is "PortOpen → Status acquisition → PortClose".

• Is the application configured to communicate between the device and the printer after "PortClose"?

[joarwilk]

My understanding is that there are 5 terminals (Castle S1F2) connected to 1 printer (mC-Print3) via LAN. Is that so? What API do you use for discovery? Correct, but not connected at the same time. For any action they open, , and close.

We use this library to discover. Using starDeviceDiscoveryManagerFactory.create([InterfaceType.Lan]);

Is there a problem with your network equipment? Is the printer turned on?

It works for some terminals and some not in the same network. This is consistent across different venues so it doesnt seem to be a local thing.

Is the application configured to communicate between the device and the printer after "PortClose"?

We dont even get to that state. It simply doesnt return any printers during discovery.