Bench PSU remote control application for TTi PL-P series (Win/Linux/Mac)

[jc101]

Well with the lxi benchmark tool (updated to 1.15) it seems the MX180TP is quite nippy...

Code: [Select]

lxi benchmark --address a.b.c.d --port 9221 --raw
Benchmarking by sending 100 ID requests. Please wait...
Result: 358.4 requests/second
For actual time to change to a command I think I'd need to try and work something out over serial though.

[lundmar]

Well with the lxi benchmark tool (updated to 1.15) it seems the MX180TP is quite nippy...

Code: [Select]

lxi benchmark --address a.b.c.d --port 9221 --raw
Benchmarking by sending 100 ID requests. Please wait...
Result: 358.4 requests/second
For actual time to change to a command I think I'd need to try and work something out over serial though.

Not bad at all. I would think you should have enough room for implementing a poor mans data logger by remote polling voltage and amp readings at maybe 100 Hz, provided the measurement operations do not add significant delays.

[lundmar]

The lxi discovery only sees the 34465A too, although I can see both the 34465A and the MX180TP if I use the LXI Discovery tool from the www.lxistandard.org website though...

Besides VXI-11 and mDNS there is a 3rd way to retrieve the instrument ID and that is by retrieving an XML file hosted by the instrument via http.

Can you please try visit the following page of your TTi instrument:

http://<instrument ip>/lxi/identification

If you see an XML file here it is working and I can implement a way for lxi discover to find and resolve it.

Thanks.

[jc101]

The lxi discovery only sees the 34465A too, although I can see both the 34465A and the MX180TP if I use the LXI Discovery tool from the www.lxistandard.org website though...

Besides VXI-11 and mDNS there is a 3rd way to retrieve the instrument ID and that is by retrieving an XML file hosted by the instrument via http.

Can you please try visit the following page of your TTi instrument:

http://<instrument ip>/lxi/identification

If you see an XML file here it is working and I can implement a way for lxi discover to find and resolve it.

Thanks.

Yes, I do get an xml file back.

Code: [Select]

<LXIDevice xmlns="http://www.lxistandard.org/InstrumentIdentification/1.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.lxistandard.org/InstrumentIdentification/1.0 http://x.x.x.x/LXIIdentification.xsd">
<Manufacturer>THURLBY THANDAR</Manufacturer>
<Model>MX180TP</Model>
<SerialNumber>000000</SerialNumber>
<FirmwareRevision>1.02-1.00-1.03</FirmwareRevision>
<ManufacturerDescription>375W Multi Range Triple Output PSU</ManufacturerDescription>
<HomepageURL>http://www.aimtti.com/go/lanxi</HomepageURL>
<DriverURL>http://www.aimtti.com/go/lanxi</DriverURL>
<UserDescription>THURLBY THANDAR-MX180TP-000000</UserDescription>
<IdentificationURL>http://t000000.local/lxi/identification</IdentificationURL>
<Interface xsi:type="NetworkInformation" InterfaceType="LXI" IPType="IPv4" InterfaceName="eth0">
<InstrumentAddressString>TCPIP::x.x.x.x::9221::SOCKET</InstrumentAddressString>
<Hostname>x.x.x.x</Hostname>
<IPAddress>x.x.x.x</IPAddress>
<SubnetMask>255.255.255.0</SubnetMask>
<MACAddress>80:E4:DA:22:23:16</MACAddress>
<Gateway>x.x.x.x</Gateway>
<DHCPEnabled>true</DHCPEnabled>
<AutoIPEnabled>true</AutoIPEnabled>
</Interface>
<Interface InterfaceType="" InterfaceName="">
<InstrumentAddressString>x.x.x.x:9221</InstrumentAddressString>
</Interface>
<Domain>1</Domain>
<LXIVersion>1.4</LXIVersion>
</LXIDevice>

[lundmar]

The lxi discovery only sees the 34465A too, although I can see both the 34465A and the MX180TP if I use the LXI Discovery tool from the www.lxistandard.org website though...

Besides VXI-11 and mDNS there is a 3rd way to retrieve the instrument ID and that is by retrieving an XML file hosted by the instrument via http.

Can you please try visit the following page of your TTi instrument:

http://<instrument ip>/lxi/identification

If you see an XML file here it is working and I can implement a way for lxi discover to find and resolve it.

Thanks.

Yes, I do get an xml file back.

Code: [Select]

<LXIDevice xmlns="http://www.lxistandard.org/InstrumentIdentification/1.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.lxistandard.org/InstrumentIdentification/1.0 http://x.x.x.x/LXIIdentification.xsd">
<Manufacturer>THURLBY THANDAR</Manufacturer>
<Model>MX180TP</Model>
<SerialNumber>000000</SerialNumber>
<FirmwareRevision>1.02-1.00-1.03</FirmwareRevision>
<ManufacturerDescription>375W Multi Range Triple Output PSU</ManufacturerDescription>
<HomepageURL>http://www.aimtti.com/go/lanxi</HomepageURL>
<DriverURL>http://www.aimtti.com/go/lanxi</DriverURL>
<UserDescription>THURLBY THANDAR-MX180TP-000000</UserDescription>
<IdentificationURL>http://t000000.local/lxi/identification</IdentificationURL>
<Interface xsi:type="NetworkInformation" InterfaceType="LXI" IPType="IPv4" InterfaceName="eth0">
<InstrumentAddressString>TCPIP::x.x.x.x::9221::SOCKET</InstrumentAddressString>
<Hostname>x.x.x.x</Hostname>
<IPAddress>x.x.x.x</IPAddress>
<SubnetMask>255.255.255.0</SubnetMask>
<MACAddress>80:E4:DA:22:23:16</MACAddress>
<Gateway>x.x.x.x</Gateway>
<DHCPEnabled>true</DHCPEnabled>
<AutoIPEnabled>true</AutoIPEnabled>
</Interface>
<Interface InterfaceType="" InterfaceName="">
<InstrumentAddressString>x.x.x.x:9221</InstrumentAddressString>
</Interface>
<Domain>1</Domain>
<LXIVersion>1.4</LXIVersion>
</LXIDevice>

Great thanks - it is a bit convoluted but I can make it work. I'll implement it as a fallback solution to retrieving the ID in case retrieving ID via VXI-11 fails. I'll get back to you once its ready to be tested.

[lundmar]

Yes, I do get an xml file back.

Great thanks - it is a bit convoluted but I can make it work. I'll implement it as a fallback solution to retrieving the ID in case retrieving ID via VXI-11 fails. I'll get back to you once its ready to be tested.

If you feel brave, the latest snap on the edge channel includes the new HTTP/XML ID fallback implementation for discovery. It has been partially tested with my Rigol scope. It should discover your device but if it does not work perhaps we should move any continued debug discussions to the lxi-tools thread. Thanks.