T7 Network connection problem

5 posts / 0 new

Wed, 10/21/2020 - 10:58

Paragraph

Dear Team at LabJack,

I'm experiencing a connection issue.

I'm running a mobile logging rig that reads modbus registers of AINs and FIOs. It’s a autonomous unit that just has a Laptop and the T7 connected via LAN-cable and the IP-adresses configured statically.(Screenshot 6)

The system has been working like this just fine for quite some time. Now all of a sudden while the system was running the modbus connection got severed and I can’t reestablish the connection via Lan no matter what I try. In Kipling in can establish a connection via USB without any problems.

I have tried the following:

Restarted Labjack and computer
Updated firmware and Kipling

The LEDs on the Labjack’s Lan-Port are flashing as they should, the device answers to pings. (Screenhot 1 attached)

When in hover over the “Ethernet” button in Kipling, I get a Tooltip that says: “Ethernet connection type was found but failed verification” (Screenshot 3 attached) This message is what lead me to this Thread.

When I click that button, I get the message from Screenshot 5.

When I run the TCPOpenTest from Step of the basic network troubleshooting page, I get an error code “60” (screenshot 4).

Since the system was running perfectly up to this point I’m at a loss what to try next.

Also the system isn’t connected to the Internet, so no automatic updates.#

Any help would be greatly appreciated.

Norman

File Attachment:

Wed, 10/21/2020 - 15:31

LabJack Support

I would not expect the IP 192

I would not expect the IP 192.168.178.122 to work with the gateway 192.168.1.109 because the subnet 255.255.255.0 is too small for both those IPs to exist on the same subnet. Maybe you meant the T7 IP to be 192.168.1.122 and the gateway to be 192.168.1.1?

If nothing else, are you able to directly connect the T7's Ethernet port to the computer's Ethernet port? It simplifies troubleshooting by removing the network from the list of things to check:
https://labjack.com/support/faq/how-do-i-connect-t7-directly-my-computer...

Thu, 10/22/2020 - 02:03

Paragraph

I saw that misconfiguration

I saw that misconfiguration afterwards in the screenshot. From my understanding it shouldn’t matter though since no gateway and dns are required for offline usage anyway and ping is working.

The computer has it’s ethernet IP statically configured as 192.168.178.109. So, both T7 and the computer sit in the same subnet. LabJack and Computer are directly connected via LAN-cable, there is no further network. I’ll try and configure both devices as described in the Direct Ethernet Connection App Note.

Thu, 10/22/2020 - 09:14

LabJack Support

Sounds good. Please let us

Sounds good. Please let us know how it goes.

Sun, 10/25/2020 - 10:29

Paragraph

When I booted up the system

When I booted up the system the problem was magically gone even before I went to reconfigure the network as decribed in the Direct Ethernet Connection App Note.

I nonetheless set the network config as planned with both devices on the .1 subnet. Works just as well.

Now I have no idea what the problem was, why it went away or if it will appear again. For now I will leave the system running over night to see how stable it really is. Will report back here if the problem returns.

Thank you very much for the moral support so far.