Jump to content
  • 0

Timer's status getter returns incorrect state


Oswin

Question

I'm using the `uldaq` Python library with a USB-CTR04 device.

Whenever I call the `get_pulse_out_status` method, it always gives me `TmrStatus.RUNNING`, regardless of the actual state of the timer.

Python 3.10.6 (main, May 29 2023, 11:10:38) [GCC 11.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information. 
>>> import uldaq 
>>> devices = uldaq.get_daq_device_inventory(uldaq.InterfaceType.USB) 
>>> daq = uldaq.DaqDevice(devices[0]) 
>>> daq.connect() 
>>> tmr.get_pulse_out_status(0)
<TmrStatus.RUNNING: 1> 
>>> tmr.pulse_out_stop(0) 
>>> tmr.get_pulse_out_status(0) 
<TmrStatus.RUNNING: 1> 
>>> tmr.pulse_out_start(0, 100, 0.5, 0, 0.0, uldaq.TmrIdleState.LOW, uldaq.PulseOutOption.DEFAULT)
(100.0, 0.5, 0.0)
>>> tmr.get_pulse_out_status(0)
<TmrStatus.RUNNING: 1>
>>> tmr.pulse_out_stop(0)
>>> tmr.get_pulse_out_status(0)
<TmrStatus.RUNNING: 1>

I believe this is a bug. The method should return `TmrStatus.IDLE` when the pulses have ceased.

P. S. Issue raised on Github as well: https://github.com/mccdaq/uldaq/issues/56

Edited by Oswin
Add Github link
Link to comment
Share on other sites

1 answer to this question

Recommended Posts

  • 0

Hello,

I am unsure why, but the USB-CTR04 and CTR08 do not have get_pulse_out_status support. The following is a link to the hardware reference page: https://www.mccdaq.com/PDFs/Manuals/UL-Linux/python/hwov.html#ctr0x

By contrast, the USB-1608G does show support for get_pulse_out_status

https://www.mccdaq.com/PDFs/Manuals/UL-Linux/python/hwov.html#g

Best regards,
John

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...