LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Error 56 on IRDA read

Im trying to do an IDRA communication via a USB IRDA device through LabVIEW (8.6) to an external device.

I know communications can be established because the IRDA comms works in a C based program using the same device and driver.

When I do get Comms, I get extra bytes back that I do not see in the C based program.

The whole of yesterday afternoon I was getting failed Comms and not reading any data back from the device at all.

I started off getting error 56 appearing infrequently, but it appeared to increase in frequency rate throughout the afternoon and I now can't run the code without getting it.

 

Any ideas for where I should even start looking please?

 

Cheers James

CLD; LabVIEW since 8.0, Currently have LabVIEW 2015 SP1, 2018SP1 & 2020 installed
0 Kudos
Message 1 of 3
(3,004 Views)

IRDA device is connected to USB port on Win XP machine.

Tried to monitor with Portmon.exe , but I'm not seeing any activity on any of ports on the machine at all. Even when I know the IRDA is Sending signals.

Hyperterminal only allows monitoring in ASCII with another IRDA device, so this is not very easy or safe.

Any ideas? Anyone?

CLD; LabVIEW since 8.0, Currently have LabVIEW 2015 SP1, 2018SP1 & 2020 installed
0 Kudos
Message 2 of 3
(2,998 Views)

Hi James

 

Can I ask what kind of device you are using to send the Infra red. I think that error 56 may be comming form the device itself and previously I have found this means that The network BIOS command limit has been reached. This would explain why it is coming at a variation of times. If the error is being genorated directly from the PC then it may be a timing issue.

 

Where is the error generated from, can you define more accuratly when it is occuring. which VI for example.

 

best regards

 

 

Graham Green
Software Product Marketing
NI | Emerson
0 Kudos
Message 3 of 3
(2,960 Views)