[Question]: Unable to connect instrument 2470 SourceMeter

[ucycg]

Pre-check

• I have searched the existing issues and discussions to make sure my problem has not already been addressed.
• I have looked at the "Known Issues" Section of the marketplace page of all TSP Toolkit extensions.

Search Terms

Unable to connect to instrument at IP address could not get instrument information
Connection issue
TSP Toolkit Version: 1.2.1
Operating System: Ubuntu 22.04.5
2470 Firmware version: 1.7.14j

TSP Toolkit Version

None

TSP Toolkit Develop Version

None

Steps to Reproduce

TSP Toolkit Version: 1.2.1
Operating System: Ubuntu 22.04.5
2470 Firmware version: 1.7.14j

1. Connect 2470 SourceMeter via Lan to Internet and power up the device
2. Try to connect the 2470 SourceMeter via the TSP Toolkit VS Code

Expected Behavior

I would expect to be able to connect via clicking the + symbol and typing the IPv4 address shown from the device that i can find for example under Menu->Communication->LAN

Also as far as i have undertood a terminal connection to the device should launch too.

Actual Behavior

1. I am able to connect to the Instrument via my Firefox Browser when i type the IPv4 address

2. I am able to ping the instrument under its IP address

3. I am able to send SCPI commands via terminal i.e. *IDN? and receive an answer from the SMU

4. I am even able to detect the device inside the TSP Toolkit VS Code extension, when i click the 'Refresh' Icon

5. However when i click on the Play button / 'Connect' I receive an Error Message inside VS Code:
   Unable to connect to instrument at 'MYIPADDRESS' could not get instrument information
   Source: Tektronix TSP Toolkit

[ucycg]

I upgraded the firmware to the latest version: 1.7.16e
but the issue remains sadly

[ucycg]

My Workaround currently is to use pyvisa and python3 on my laptop and access the SMU2470 with TSP commands via a .py script via LAN which is also working, but i would really prefer using your VS Code Extension if only i could get it working.

[esarver]

@ucycg This is Edwin Sarver, one of the maintainers of TSP Toolkit. Thanks so much for the feedback! Could you send the logs from the date of this issue to edwin.sarver@keithley.com so I can take a look. Feel free to go through the logs and remove any information you deem sensitive (rest assured, I will not share it with anyone). They will likely be large files, so you will likely need to use some aggressive compression.

You can find the logs on Ubuntu at ${XDG_STATE_HOME}/tsp-toolkit or ~/.local/state/tsp-toolkit. There should be 3 files all prepended with the date the log was written.

• tsp-toolkit.log
• kic.log
• kic-discover.log

Sorry this is such a manual process. We plan to implement a better bug-reporting feature in the future.

[ucycg]

I send you the requested files via private Email. Couldnt find any kic.log yet sadly.

ty for your reply

[esarver]

@ucycg Thanks for sending that! And thanks again for your interest. Unfortunately, we currently only support Linux distributions which ship with glibc version 2.39 or newer. This is because we are building on Ubuntu 24.04. I have added a ticket internally to correct this problem by building on a distro with an earlier version of glibc, such as RedHat 9, CentOS 9, or even Ubuntu 22.04.

[ucycg]

@esarver Does that mean I HAVE to upgrade my linux to 24.04 in order to have an ASAP fix or can i try to install this glibc manually on my Ubuntu 22.04? Ty for the clarification

If simply my OS version is not supported that is actually pretty good news, because you give me the final push to do the update :)
I thought it was something much more difficult to solve or an actual bug.

In the meantime before you are able to realize the enhancement

Could you maybe create an automatic recognition of the OS in the installation process and INFORM the user that his OS is currently not supported? The current error message is quite missleading in that aspect I figure

[esarver]

@ucycg Unfortunately, at the moment, yes. I don't think Ubuntu has options to install newer versions of glibc between versions.

I agree, we could absolutely do more to inform the user of what is going on. The same goes for checking other libraries as well. We do have internal tickets for these things.

Thanks again for all your feedback! It helps us immensely to make sure we are covering our customer use-cases!