Hi,
we were able to improve the situation a little bit. It looks like the native usbtmc support is broken since kernel 2.6.28-11. We installed the driver from Agilent
on our Debian 3.2.46-1 x86_64 machine and now we have /dev/usbtmc0 which returns information about the connected devices and /dev/usbtmc1 ... usbtmc16. With the latter we can now repeatedly communicate
using echo (for example 'echo *IDN?>/dev/usbtmc1') and cat with the device and we get meaningful results. However, using the serial driver from asyn does not work, I guess since it is not
a pure serial device but rather a normal file in the linux file system where you can write to and read from.
Is there any possibility to get this working with asyn or do we have to find a new solution?
Cheers,
Flo
> From the device name this is is a USBTMC device, not a serial port. I've seen similar behavior in older linux kernels, you might have more luck
> updating to a more recent kernel.
>
> Guy Jennings
>
> On Aug 2, 2013, at 10:36 AM, Eric Norum <[email protected]> wrote:
>
>> Since you can communicate with the unit using simple shell commands I'm inferring that the unit presents itself as a USB-connected serial port. Standard StreamDevice + ASYN support should work fine.
>>
>> On Aug 2, 2013, at 5:42 AM, "Drube, Hardy" <[email protected]> wrote:
>>
>>> Dear all,
>>>
>>> I have some problems to establish a longer lasting connection with a Thorlabs PM100USB Powermeter.
>>>
>>> It is listed in /dev as usbtmc0 and I can communicate with it through echo –e. But this is only possible for one time. A second time echo –e won’t work. I have to disconnect and reconnect the USB-cable. Then again it will work one time.
>>> Could you help me with this problem?
>>>
>>> Note: This device has two chips, the first one is a XILINX XCR3064XL (AD Converter) and the second a NXP LPC2387FBD100.
>>>
>>> Best regards,
>>> Hardy Drube
>>>
>>
>> --
>> Eric Norum
>> [email protected]
>>
