LabJack T7 Pro WiFi with LabVIEW | LabJack
 
Wednesday June 3rd 2020
Support: LabJack engineers available through email and chat.
Shipping: We are processing and shipping all orders.
Stock: 51 of 56 products are in stock. More details.
Supply Chain: Minor impacts. More details.

LabJack T7 Pro WiFi with LabVIEW

4 posts / 0 new
Last post
Steve M
Stephen McVey's picture
LabJack T7 Pro WiFi with LabVIEW

I can't find any way to initiate data capture/logging/streaming over WiFi via LabVIEW. Using the LabJack as a standalone device I use Kipling to select the T7 as a WiFi device and then run the standalone LJStream or LJLog to capture data and it works fine. It looks like the WiFi is setup by Kipling and LJStream/LJLog just accept it, but if I try to run the LabVIEW versions of LJStream/LJLog it fails with 'Can't find Device' error or  'LabJack error #1239:LJME_RECONNECT_FAILED' Any ideas?

LabJack Support
LabJack Support's picture
So Kipling does show a green

So Kipling does show a green button for the WiFi connection, and if you click that to connect over WiFi you can then go to the Dashboard and other tabs?

Is LJLogM connecting over WiFi or another pipe that you have connected (USB or Ethernet)?  Look at the ConnectionType returned as shown in LJLogM.  ctUSB = 1, ctETHERNET = 3, ctWIFI = 4.

Make sure you only run 1 program at a time.

Can you ping the T7 at it's WiFi IP address?

Perhaps troubleshooting item #5 from the Basic Networking App Note where search does not work but a direct TCP open is fine:

https://labjack.com/support/app-notes/basic-networking-troubleshooting

Steve M
Stephen McVey's picture
I finally got back onto this

I finally got back onto this after a while - seems that the IP has to be specified explicitly in the config file or else it fails 9 times out of 10, not an ideal scenario but for now it works at least...

LabJack Support
LabJack Support's picture
This is something we see on

This is something we see on some networks.  With some networks the "tricks" used to broadcast and find all T7s on the network just do not work, perhaps blocked by firewalls or other network configuration details.  The simple solution in such a case is to do an open where you specify the IP address you want to open.  This is very network friendly as the software simply does 1 TCP open attempt with that specific IP.

Note that this also suggests that a static (manually assigned) IP is often preferred over a dynamically (DHCP) assigned IP.  That is something you will typically configure on the T7 using Kipling.

If developing your own application in LabVIEW, just use the specific parameters in your open calls rather than any-any-any.

For LJLogM/LJStreamM you can edit the _open.cfg file to tell it to do the specific open, or another strategy is to edit the ljm_specific_ips.config file which configures LJM to always try certain IP addresses directly.  Doing this affects all software that uses the LJM library on the machine, including LJLogM and LJStreamM:

https://labjack.com/support/software/api/ljm/constants/SpecificIPsConfigs