It's not just the ambient-attx4
that is experiencing the Invalid response from CRC check error seen here a couple weeks ago.
I have trimmed my IR script down the the point where it talks to the module...
var tessel = require('tessel');
var infraredlib = require('ir-attx4');
var infrared = infraredlib.use(tessel.port['A']);
... and I get the following output:
> tessel run scan.js
TESSEL! Connected to TM-00-04-f0009a30-005a4343-663845c2.
INFO Bundling directory /Users/john/Documents/Experiments/tessel/aircon
INFO Deploying bundle (366.50 KB)...
INFO Running script...
Old module firmware detected. Updating...
Uploading new firmware...
Update finished!
Error: Invalid response from CRC check.
at _new ([string "colony-init.lua"]:1)
at callback (...modules/ir-attx4/node_modules/attiny-common/lib/index.js:277)
at func ([string "tessel.js"]:1110)
at apply ([string "colony-js.lua"]:1)
at func ([string "events.js"]:180)
at call ([string "colony-js.lua"]:1)
at emit ([string "events.js"]:89)
at <anonymous> ([string "colony-node.lua"]:1)
I tried rolling back ir-attx4
versions from 0.2.8
until I started getting the Wrong module plugged into port error.
Here's some other debug info:
> tessel version --board
TESSEL! Connected to TM-00-04-f0009a30-005a4343-663845c2.
INFO Serial #: TM-00-04-f0009a30-005a4343-663845c2
INFO Wifi Version: 1.28
INFO Firmware Commit: 5c46cb0
INFO Runtime Commit: f33115d
INFO Firmware Build: 0.1.26
Running node v0.12.7
on Mac OS X 10.11.1
Merry Christmas, and I'm looking forward to T2!
Cheers,
John