Trouble on Ubuntu with a Rigol DP832 ...

[jjhatt]

I just don't know how to trouble-shoot this problem:
$ ./tmc
USBTMC debug: Using TermChar $VAR1 = '
';

USBTMC debug: enable auto detach of kernel driver.
USBTMC debug: Found USBTMC interface at number 0
USBTMC debug: Claiming interface no. 0
USBTMC debug: Found bulk-in endpoint with address 0x82
USBTMC debug: Found bulk-out endpoint with address 0x3
USBTMC debug: dev_dep_msg_out with data :SYST:REM

USBTMC debug: dev_dep_msg_out: write failed. Aborting bulk transfer.
USBTMC debug: initiate abort bulk out
INITIATE_ABORT_BULK_OUT failed with status 128 at ./tmc line 17.
error in libusb_bulk_transfer_write: Operation timed out at /usr/local/lib/x86_64-linux-gnu/perl/5.26.1/USB/LibUSB/Device/Handle.pm line 22.
at ./tmc line 17.

The code picks up the device, including it serial number. However, the writes get bounced.

Any insights? Source code below.
---jjh

#!/usr/bin/perl -w

File: tmc

use strict;
use USB::TMC;

my $d = USB::TMC->new(
vid => 0x1ab1,
pid => 0x0e11,
serial => 'DP8C210100038',
reset_device => 0,
debug_mode => 1,
term_char => "\n",
) or die "Cannot open PS.\n";

$d->write(data => ":SYST:REM\n");
$d->write(data => "*IDN?\n");
print $d->read(length => 100);

[amba]

Dear @jjhatt,

Rigol devices are notorious for non-standard behavior of the USBTMC interface.
Some USBTMC drivers, like the linux kernel driver and python-usbtmc include special code to deal with the Rigol quirks. For some Rigol devices, the issue can be fixed by updating the firmware:
python-ivi/python-usbtmc#23

Hope this helps,
Simon

[jjhatt]

Simon, Wow! Thank you so much for the quick reply! There is an option on this Rigol PS to turn on RS232 and Ethernet for $140. I will ask Rigol for a firmware update, but if that does not fix the problem, I'll go with Ethernet for $140. Looking at the code I sent, does everything look ok to you? I tried the query method for USB::TMC and got an error. You had a call to query in your example code, is it still supported? I wanted you to know also that I had a speed bump installing the USB::TMC module. Your installer failed pkg-config for libusb-1.0. I pulled my hair hard on this one. I am running Ubuntu 18.04. I had libusb-1.0 installed. Ubuntu apt-get could see it, but pkg-config could not. As a shot in the dark, I removed libusb-1.0. I then reinstalled, rebooted, and suddenly; pkg-config saw libusb-1.0 and cpanm then could install USB::TMC with no errors. Thank you for your help. ---jjh *James Hatt |* *Sr. Software Developer* | *Viking Technology* RF, Optical, and Microelectronics Division A Division of Sanmina Corporation Telephone: +1.972.512.5605 email: [email protected], [email protected] 1201 W. Crosby Rd., Carrollton, TX 75006 www.vikingtechnology.com | <http://www.twitter.com/vikinology>*t <http://www.twitter.com/vikinology>* <http://www.twitter.com/vikinology>| <http://www.facebook.com/pages/Viking-Technology/106725999413927>*f <http://www.facebook.com/pages/Viking-Technology/106725999413927>* <http://www.facebook.com/pages/Viking-Technology/106725999413927>| <http://www.linkedin.com/company/86313?trk=tyah>*l <http://www.linkedin.com/company/86313?trk=tyah>* <http://www.linkedin.com/company/86313?trk=tyah>| <http://vimeo.com/vikingtechnology>*v* <http://vimeo.com/vikingtechnology>

…

On Wed, Mar 27, 2019 at 9:29 AM Simon Reinhardt ***@***.***> wrote: Dear @jjhatt <https://github.com/jjhatt>, Rigol devices are notorious for non-standard behavior of the USBTMC interface. Some USBTMC drivers, like the linux kernel driver and python-usbtmc include special code to deal with the Rigol quirks. For some Rigol devices, the issue can be fixed by updating the firmware: python-ivi/python-usbtmc#23 <python-ivi/python-usbtmc#23> Hope this helps, Simon — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#2 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AYLaQCETKhze1NIXZtjlTrwZtqwn8zMLks5va4AygaJpZM4cN5fY> .

-- CONFIDENTIALITY This e-mail message and any attachments thereto, is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail message, you are hereby notified that any dissemination, distribution or copying of this e-mail message, and any attachments thereto, is strictly prohibited. If you have received this e-mail message in error, please immediately notify the sender and permanently delete the original and any copies of this email and any prints thereof. ABSENT AN EXPRESS STATEMENT TO THE CONTRARY HEREINABOVE, THIS E-MAIL IS NOT INTENDED AS A SUBSTITUTE FOR A WRITING. Notwithstanding the Uniform Electronic Transactions Act or the applicability of any other law of similar substance and effect, absent an express statement to the contrary hereinabove, this e-mail message its contents, and any attachments hereto are not intended to represent an offer or acceptance to enter into a contract and are not otherwise intended to bind the sender, Sanmina Corporation (or any of its subsidiaries), or any other person or entity.

[amba]

I have removed the "query" call from the POD. Thanks for the hint!

I wanted you to know also that I had a speed bump installing the USB::TMC module. Your installer failed pkg-config for libusb-1.0. I pulled my hair hard on this one.

Did you have the "-dev" version of the libusb package installed?

[jjhatt]

Simon, libusb-dev was not installed. It is now. Tanks! ---jjh *James Hatt |* *Sr. Software Developer* | *Viking Technology* RF, Optical, and Microelectronics Division A Division of Sanmina Corporation Telephone: +1.972.512.5605 email: [email protected], [email protected] 1201 W. Crosby Rd., Carrollton, TX 75006 www.vikingtechnology.com | <http://www.twitter.com/vikinology>*t <http://www.twitter.com/vikinology>* <http://www.twitter.com/vikinology>| <http://www.facebook.com/pages/Viking-Technology/106725999413927>*f <http://www.facebook.com/pages/Viking-Technology/106725999413927>* <http://www.facebook.com/pages/Viking-Technology/106725999413927>| <http://www.linkedin.com/company/86313?trk=tyah>*l <http://www.linkedin.com/company/86313?trk=tyah>* <http://www.linkedin.com/company/86313?trk=tyah>| <http://vimeo.com/vikingtechnology>*v* <http://vimeo.com/vikingtechnology>

…

On Wed, Mar 27, 2019 at 10:17 AM Simon Reinhardt ***@***.***> wrote: I have removed the "query" call from the POD. Thanks for the hint! > I wanted you to know also that I had a speed bump installing the USB::TMC > module. Your installer failed pkg-config for libusb-1.0. I pulled my hair > hard on this one. Did you have the "-dev" version of the libusb package installed? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#2 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AYLaQAzDS6Nby47VuRtcdzLapEDSdUEmks5va4uIgaJpZM4cN5fY> .

-- CONFIDENTIALITY This e-mail message and any attachments thereto, is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail message, you are hereby notified that any dissemination, distribution or copying of this e-mail message, and any attachments thereto, is strictly prohibited. If you have received this e-mail message in error, please immediately notify the sender and permanently delete the original and any copies of this email and any prints thereof. ABSENT AN EXPRESS STATEMENT TO THE CONTRARY HEREINABOVE, THIS E-MAIL IS NOT INTENDED AS A SUBSTITUTE FOR A WRITING. Notwithstanding the Uniform Electronic Transactions Act or the applicability of any other law of similar substance and effect, absent an express statement to the contrary hereinabove, this e-mail message its contents, and any attachments hereto are not intended to represent an offer or acceptance to enter into a contract and are not otherwise intended to bind the sender, Sanmina Corporation (or any of its subsidiaries), or any other person or entity.