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
First a couple of notes on the release: Like others, when I install relaase 4.0.2 (via fledge or via dfu-util) crow reports in druid that it is running v4.0.1-14-g7721314, not v4.0.2. I note that github has a 4.0.2RC tag, but no actual 4.0.2 tag. 4.0.2RC contains a commit that does bytecode cross-compilation, but does not contain the i2c fixes in commit 34166ec.
The issue I see is: if I connect to crow running v4.0.1-14-etc via druid I get the following response if I try to access the inputs:
//// druid. q to quit. h for help
<crow connected>
<listening at ws://localhost:6666>
> print(input[1].volts)
?:-1: attempt to call a nil value (field 'io_get_input')
stack traceback:
?: in function <?:44>
(...tail calls...)
repl:1: in main chunk
runtime error.
If I do not try to interact with the DAC, things seem to work fine. I haven't attempted to use any of the v4 functionality, though.
This crow is serial number 0x002e00133756501420383558.
I am running druid 1.1.4 under python 3.8 on Windows.
The text was updated successfully, but these errors were encountered:
First a couple of notes on the release: Like others, when I install relaase 4.0.2 (via
fledge
or viadfu-util
) crow reports in druid that it is running v4.0.1-14-g7721314, not v4.0.2. I note that github has a 4.0.2RC tag, but no actual 4.0.2 tag. 4.0.2RC contains a commit that does bytecode cross-compilation, but does not contain the i2c fixes in commit 34166ec.The issue I see is: if I connect to crow running v4.0.1-14-etc via druid I get the following response if I try to access the inputs:
If I do not try to interact with the DAC, things seem to work fine. I haven't attempted to use any of the v4 functionality, though.
This crow is serial number 0x002e00133756501420383558.
I am running druid 1.1.4 under python 3.8 on Windows.
The text was updated successfully, but these errors were encountered: