Content Comparison

Instec said: “While we do have sample code for Python, it is based on a USB connection, not Ethernet. 

Our documentation on Ethernet programming is limited because it isn’t very frequently used for custom applications.

This ZIP file contains example code for python using a USB connection. It could serve as the basis for an ethernet version.”

email from Instec

Ethernet communication setup from Instec.

Mainly describes how to write code to find Instec devices on a network.

Note PacketSender image within, which shows correct port to use for ethernet communication.

email from Instec

PacketSender connection example

Screengrab of SG’s successful connection to device through PacketSender. Note port is 50292.

Instec App for Windows
(standalone program; not useful for KTL but included here for completeness)

email from Instec

Steve’s python code that uploads a PID table from a .csv file (in Instec format) to the device over USB.

Example PID tables also included (one with actual values, and one with integers that was useful for testing code).

Code:

PID files:

Steve’s test of parsing and uploading Instec .csv file

Calibration table decoder ring
(output of CAL:TAB command)

The data is formatted as follows:

The return data is 171 bytes long.

The first byte is “#”, while the last two bytes are the “return” (0x0D) and “New line” (0x0A) characters.

The 6^th byte describes the data type; 0 = TM, 1 = Calibration Table C1, 4 = Calibration Table C4 etc…

The 7^th byte is the number of entries in the calibration table.

The actual calibration data begins at the 10^th byte. For each in the calibration table, there are two floating point numbers which correspond to T0 and Ts.

Each floating point number consists of 4 bytes, which are arranged in little endian order.

email from Instec

Controller calibration file example.

Filename structure is:

“cold_head_SN & mK2000B_SN cal.clb”