U3 Wireless communication using Silex SX-DS-3000WN

2 posts / 0 new

Tue, 11/15/2016 - 15:10

Don Easton

Hi, I'm operating a home weather station using a U3 and LabView. The U3 is at the weather station and transmits wirelessly using a Silex USB device server. Occasionally connectivity is lost. I would like LabView to stop trying to collect data and wait until connectivity is restored. I can use LJUD_ListAll to check for a stop or go condition and it works well when the U3 is connected directly to my computer. When it's connected wirelessly with the Silex server, Any power interruption to the device server results in a fatal error and LabView shuts down. Is there a way to deal with this?

Thanks, Don

Tue, 11/15/2016 - 17:32

LabJack Support

First, check that you have

First, check that you have the latest Silex software installed on your computer. Our latest U3 software/drivers can be found here:

https://labjack.com/support/software/installers/ud

Second, if power interruption is an issue, consider getting a battery backup UPS to power your Silex server and U3.

Third, it may be tough to handle this issue in software if the Silex layer of software/drivers are causing the fatal error. If you want to try to troubleshoot the application after installing the latest Silex and LabJack software, what version of Windows and LabVIEW are you running? Does the fatal error (crash?) occur when the power is lost on the Silex server and during the LJUD_ListAll call, or in general when power is lost on the Silex server? You can check by removing LJUD_ListAll for the stop and go condition, and see if your fatal error still occurs.

Keep in mind that after you open a U3 in the application and get its handle, the UD driver will automatically attempt to reconnect with the U3 if the connection was lost. With a valid handle but a lost connection to the U3, UD calls will return errors like LJE_COMM_FAILURE (1008) and LJE_DEVICE_NOT_CONNECTED (1015). So you may not need the LJUD_ListAll call in your application if you are only using it to detect when the U3 has reconnected. Calls should just start working again.