I bought a T7 pro device and changed the IP address to 192.168.177.101 over the USB connection. Tested the ethernet connection and all worked fine. Later on I changed it again but made an error with the change to 192.168.177.300, received an error and since than I can't change the IP address anymore. It showed me always 0.0.0.0.
Over the USB connection,
- I installed again the latest firmware (no changes)
- tried to load the installed json file from ProgramData (not possible)
- tried to use the command to read the current ip address
and since then, I can't connect the device anymore over USB and Ethernet as well. Restarted the PC, disconnected the device, used another USB port -> no device found. Just the status LED is green.
Is there any option of another reset of the device?
.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")
So USB worked until the following:
Can you detail a little more what you did to make USB stop? Something in Kipling? We will try to reproduce here.
Anyway, have you tried any of the reset jumpers?
https://labjack.com/support/datasheets/t-series/spc
Here is an app note about USB trouble:
https://labjack.com/support/app-notes/usb-communication-failure
Yes - it stopped by using the lua script debugger. I tried to use the MB.R(<address>) function to read out the current ip address. Used for that an example script, clicked on "run script" and lost the connection over USB.
Thank you for the link - started by "factory reset", "force copy of backup" and finally it worked with "load emergency image". I could again setup the IP address 192.168.177.101.
I will try to force this USB stop again and give you some more information about it.
A little bit late but attached, what I did and tried. I could not reproduce the USB behaviour but could set up my whished ip address 192.168.177.30.
Does the load emergency image not erase all parameters which I have set before?
For example, I execute this load emergency image and have all network parameters set to 0.0.0.0. After loading the latest firmware version, I get again some parameters which I have set before loading the image.
Some things that stand out to me:
Ok, thank you for this information about DHCP.
About the 192.168.177.300, this was a mistake. Goal was to give the address 30 but I configured as 300, received an error and had this communication issue with ethernet, that I could not change anymore the address. That was the reason for this ticket. I had every time 0.0.0.0 even if I changed the address to 192.168.177.30 or 101.
But the reset with SPC and FIFO3 was working.
How did you manage to set the IP to ...300? I tried to reproduce this, but Kipling 3.1.17 displays an error and grays out the apply button.
I could click on the apply button, received an error and from than, the device did not work anymore. But as I wrote I could reset the parameters and now use the device. Strange but I would not reproduce it, because the project is urgent.