You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Feb 2, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Feb 2, 2026. It is now read-only.
Overflow during instrument initialization Chroma Power supply #34
I am trying to run a simple example, but even if the device is enumerated properly with:
>>> usbtmc.list_devices()
[<DEVICE ID 1698:0837 on Bus 003 Address 005>]
The initialization code fails with an overflow.
File "./chroma.py", line 7, in <module>
supply = ivi.chroma.chroma62012p8060('USB::5784::2103::009000000571::INSTR')
File "/usr/local/lib/python3.5/dist-packages/ivi/chroma/chroma62012p8060.py", line 35, in __init__
super(chroma62012p8060, self).__init__(*args, **kwargs)
File "/usr/local/lib/python3.5/dist-packages/ivi/chroma/chroma62000p.py", line 37, in __init__
super(chroma62000p, self).__init__(*args, **kwargs)
File "/usr/local/lib/python3.5/dist-packages/ivi/chroma/chromaBaseDCPwr.py", line 43, in __init__
super(chromaBaseDCPwr, self).__init__(*args, **kwargs)
File "/usr/local/lib/python3.5/dist-packages/ivi/scpi/dcpwr.py", line 48, in __init__
super(Base, self).__init__(*args, **kwargs)
File "/usr/local/lib/python3.5/dist-packages/ivi/extra/common.py", line 33, in __init__
super(SerialNumber, self).__init__(*args, **kwargs)
File "/usr/local/lib/python3.5/dist-packages/ivi/scpi/common.py", line 104, in __init__
super(SelfTest, self).__init__(*args, **kwargs)
File "/usr/local/lib/python3.5/dist-packages/ivi/dcpwr.py", line 56, in __init__
super(Base, self).__init__(*args, **kwargs)
File "/usr/local/lib/python3.5/dist-packages/ivi/ivi.py", line 1691, in __init__
self.initialize(resource, id_query, reset, **kw)
File "/usr/local/lib/python3.5/dist-packages/ivi/scpi/dcpwr.py", line 89, in _initialize
self._clear()
File "/usr/local/lib/python3.5/dist-packages/ivi/ivi.py", line 2000, in _clear
return self._interface.clear()
File "/usr/local/lib/python3.5/dist-packages/python_usbtmc-0.8-py3.5.egg/usbtmc/usbtmc.py", line 690, in clear
File "/usr/local/lib/python3.5/dist-packages/python_usbtmc-0.8-py3.5.egg/usbtmc/usbtmc.py", line 349, in open
File "/usr/local/lib/python3.5/dist-packages/python_usbtmc-0.8-py3.5.egg/usbtmc/usbtmc.py", line 699, in clear
File "/usr/local/lib/python3.5/dist-packages/usb/core.py", line 1043, in ctrl_transfer
self.__get_timeout(timeout))
File "/usr/local/lib/python3.5/dist-packages/usb/backend/libusb1.py", line 883, in ctrl_transfer
timeout))
File "/usr/local/lib/python3.5/dist-packages/usb/backend/libusb1.py", line 595, in _check
raise USBError(_strerror(ret), ret, _libusb_errno[ret])
usb.core.USBError: [Errno 75] Overflow
I Added some printout of the ctrl_transfers as they go, it is the last one that produces the overflow:
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File
"/usr/local/lib/python3.5/dist-packages/python_usbtmc-0.8-py3.5.egg/usbtmc/usbtmc.py",
line 629, in ask
File
"/usr/local/lib/python3.5/dist-packages/python_usbtmc-0.8-py3.5.egg/usbtmc/usbtmc.py",
line 609, in write
File
"/usr/local/lib/python3.5/dist-packages/python_usbtmc-0.8-py3.5.egg/usbtmc/usbtmc.py",
line 475, in write_raw
File
"/usr/local/lib/python3.5/dist-packages/python_usbtmc-0.8-py3.5.egg/usbtmc/usbtmc.py",
line 349, in open
File
"/usr/local/lib/python3.5/dist-packages/python_usbtmc-0.8-py3.5.egg/usbtmc/usbtmc.py",
line 699, in clear
File "/usr/local/lib/python3.5/dist-packages/usb/core.py", line 1043, in
ctrl_transfer
self.__get_timeout(timeout))
File "/usr/local/lib/python3.5/dist-packages/usb/backend/libusb1.py",
line 883, in ctrl_transfer
timeout))
File "/usr/local/lib/python3.5/dist-packages/usb/backend/libusb1.py",
line 595, in _check
raise USBError(_strerror(ret), ret, _libusb_errno[ret])
usb.core.USBError: [Errno 75] Overflow
>>
On Thu, Aug 10, 2017 at 12:12 AM, Alex Forencich ***@***.***> wrote:
Can you connect directly and send commands like this?
instr = usbtmc.Instrument('USB::5784::2103::009000000571::INSTR')
print(instr.ask("*IDN?"))
The only thing that I can think of is the power supply may not implement
the clear command correctly.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#34 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AcxqLS58xHSmd_dECgML1JbxsWBfDL7xks5sWi7MgaJpZM4OYA1g>
.
Hi,
Thanks for your answer, this is what I get. To me this looks like an
overflow when handling a response
Thanks in advance
>>> import usbtmc
>>> instr = usbtmc.Instrument('USB::5784::2103::009000000571::INSTR')
>>> print(instr.ask("*IDN?"))
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "/usr/local/lib/python3.5/dist-packages/python_usbtmc-0.8-py3.5.egg/usbtmc/usbtmc.py",
line 629, in ask
File "/usr/local/lib/python3.5/dist-packages/python_usbtmc-0.8-py3.5.egg/usbtmc/usbtmc.py",
line 609, in write
File "/usr/local/lib/python3.5/dist-packages/python_usbtmc-0.8-py3.5.egg/usbtmc/usbtmc.py",
line 475, in write_raw
File "/usr/local/lib/python3.5/dist-packages/python_usbtmc-0.8-py3.5.egg/usbtmc/usbtmc.py",
line 349, in open
File "/usr/local/lib/python3.5/dist-packages/python_usbtmc-0.8-py3.5.egg/usbtmc/usbtmc.py",
line 699, in clear
File "/usr/local/lib/python3.5/dist-packages/usb/core.py", line 1043,
in ctrl_transfer
self.__get_timeout(timeout))
File "/usr/local/lib/python3.5/dist-packages/usb/backend/libusb1.py",
line 883, in ctrl_transfer
timeout))
File "/usr/local/lib/python3.5/dist-packages/usb/backend/libusb1.py",
line 595, in _check
raise USBError(_strerror(ret), ret, _libusb_errno[ret])
usb.core.USBError: [Errno 75] Overflow
>>>
On Thu, Aug 10, 2017 at 12:12 AM, Alex Forencich ***@***.***
> wrote:
> Can you connect directly and send commands like this?
>
> instr = usbtmc.Instrument('USB::5784::2103::009000000571::INSTR')
> print(instr.ask("*IDN?"))
>
> The only thing that I can think of is the power supply may not implement
> the clear command correctly.
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <#34 (comment)>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AcxqLS58xHSmd_dECgML1JbxsWBfDL7xks5sWi7MgaJpZM4OYA1g>
> .
>
Activity
alexforencich commentedon Aug 9, 2017
Can you connect directly and send commands like this?
The only thing that I can think of is the power supply may not implement the clear command correctly.
spsmspsm commentedon Aug 11, 2017
spsmspsm commentedon Aug 11, 2017