Some getters (ii.wsyn.get('fm_ratio'), ii.wtape.get('echo_mode') crash the ii bus, resulting in:
> ii.wtape.get('echo_mode')
ii: lines are low.
check ii devices are connected correctly.
check no ii devices are frozen.
and the same message shown for any subsequent ii command until a power cycle. In this case both crow and the W/ front panel remain functional, only ii is affected, as though W/ is holding the lines low. In some cases this seems to be intermittent, e.g. (running the command repeatedly right after boot, tape is stopped (according to the front panel? but return value seems to disagree), no CV or front panel interactions)
> ii.wtape.get('speed')
^^ii.wtape({name=[[speed]], device=1, arg=0}, 0.9998169)
> ii.wtape.get('speed')
^^ii.wtape({name=[[speed]], device=1, arg=0}, 0.9998169)
> ii.wtape.get('speed')
^^ii.wtape({name=[[speed]], device=1, arg=0}, 0.9998169)
> ii.wtape.get('speed')
ii: lines are low.
check ii devices are connected correctly.
check no ii devices are frozen.
Occasionally I have seen the ii.wtape.get('timestamp') getter crash W/, I2C, and crow completely until a power cycle, that is, druid hangs and will not evaluate further commands.
It's possible this is attributable to a physical issue with my I2C bus, though I've used the same connections successfully for many combinations of crow / JF / Teletype / Ansible / TELEXo. I'm using a short ribbon cable with 2x3 pin IDC connectors I crimped on. Furthermore any amount of interaction using only setter commands seems to work as expected.
I'm testing with the
w2b04.zip
firmware, and seeing the same behavior with either crow firmware built from source at https://github.com/monome/crow/commit/df354016d9446759f03353ed5ccccf66054b0ee6 or thecrow-931e0d967a44f786d94494d8f047a20c3ea13e6d.zip
file posted on lines. Only crow and W/ are on the I2C bus.ii.wsyn.get('fm_ratio')
,ii.wtape.get('echo_mode')
crash the ii bus, resulting in:and the same message shown for any subsequent ii command until a power cycle. In this case both crow and the W/ front panel remain functional, only ii is affected, as though W/ is holding the lines low. In some cases this seems to be intermittent, e.g. (running the command repeatedly right after boot, tape is stopped (according to the front panel? but return value seems to disagree), no CV or front panel interactions)
ii.wtape.get('timestamp')
getter crash W/, I2C, and crow completely until a power cycle, that is, druid hangs and will not evaluate further commands.It's possible this is attributable to a physical issue with my I2C bus, though I've used the same connections successfully for many combinations of crow / JF / Teletype / Ansible / TELEXo. I'm using a short ribbon cable with 2x3 pin IDC connectors I crimped on. Furthermore any amount of interaction using only setter commands seems to work as expected.