I am having intermittent communications problems between my LJ T7-Pro and the Kipling and LJLogM software. I am connecting to the T7-Pro wirelessly through a router like this: (I've attached all images separately in case you cannot see these embedded images)
Often Kipling can see the T7-Pro but can't connect to it. Sometimes it can connect. The LJLogM software similarly often fails to connect. I did 50 trials.
Error 1298 - 30% Error 1314 - 56% Works Normally - 14% I tried connecting the PC to the router via Wired Ethernet like this: Results were similar but slightly different. Error 1239 - 2% Error 1314 - 50% Works Normally - 42% Error 1298 - 6% When I connect the T7-Pro to the router by wired Ethernet, it connected normally 10 times out of 10, even though the link between the router and the PC is wireless. Ping latencies are in the 15ms range, with a lot of variability, a little lower when I replace one leg with wired Ethernet. This is on 2.4GHz in a modestly dense area, so these ping times sound normal.Can anyone explain why LJLogM only connects 14% of the time when I connect wirelessly and why connecting to the LabJack via Wired Ethernet works?
My first thought is latency. I'm imagining the associated with clear-channel assessment and retries are sometimes exceeding some timeout. I don't have cables and attenuators to test this hypothesis. Are there any maximum allowable response time settings that I can control?
In my application I really need to connect to the LabJack wirelessly. In my current setup, the WiFi functionality of the T7-Pro is barely usable.
.png%3Fitok=PHGBxf6M "EEV Blog Reviews LabJack T7-Pro & Software Tools")
.jpg%3Fitok=B1YcuDFK)
.png%3Fitok=Ybt-OlgU "LabJack + JEDI One Can Create a Powerful Distributed DAQ Ecosystem")
What you are describing does not sound normal. See the following which even has a WiFi testing app attached:
https://labjack.com/forums/t7/t7-pro-wi-fi-disconnections
That topic is really talking about the uptime once you are connected. There are many useful tips at the end of this page:
https://labjack.com/support/app-notes/wifi-and-ethernet-t7-t4-t7-pro
One other thing, it that it sounds like you are not doing long term communication testing, but rather open testing. You are repeatedly trying to open the device and noting how often that is successful. One immediate suggestion for opening is to use a static (manually assigned) IP and do a specific open (don't pass any for any of the open parameters).
Another thing for open testing, is that you can use the TCPOpenTesting app from the page linked above to test if the success is different for the 3 different types of opens described in step 15).
I ran the WiFi Testing program overnight here at our office and it stopped twice. It stopped at 2:40 AM and took 9 seconds to start again, and then stopped at 4:59 AM and took 10 seconds to start again.
This worked. Thanks!! LJLogM must have some protocol, maybe using broadcast packets, to find the IP address of the LJ. Maybe those packets cause a problem, the same problem that causes the LJ T7-Pro to temporarily top responding to pings when I start LJLogM. That's speculation. The important thing is going to a static IP as suggested in the app note you referenced. Thanks.
It's in the open call to the LJM library. When you pass "any" for any of the parameters, LJM has to do a search. Searching a network is not a standard thing so LJM has to use various techniques and tricks. Sometimes these things just don't work, or don't work 100%, on a particular network.