If there were to be a new revision of the eChook board, how about reassigning the analogue inputs used in order to free up A4 and A5, rather than A1 and A6 that are unused at present. This would allow A4 and A5 to be used for the I2C interface allowing the connection of a range of additional devices, such as displays, non contact temperature sensors, accelerometers, etc.
How to get the data back is the subject of the next new feature request.
There is a reason for how they currently are which was to keep code commonality with a Micro so we could run a 3v3 version of the eChook with more processing power, but then that never really went anywhere.
We'd wanted to keep legacy compatibility with the code, but access to hardware i2c is a compelling argument.
Thanks for the suggestion. Would a software i2c implementation work for you in the mean time?
Hi Rowan … good to hear from you. For sure I could use a s/w bit banging I2C for now if necessary, though h/w would be better :-). Would really want this to go along with the user defined data. For our current car we've added a couple of I2C MLX90614 non-contact temperature sensors looking at our disc brakes for signs of overheating (if binding!). We have connected the sensors to a separate ESP32 based board which uses its on-board WiFi to dweet the temperatures back to our dashboard in the pits (via a hotspot on the phone running the eChook app in the car). Works for now, but would be fantastic to be able to exploit all the good stuff that the eChook ecosystem already provides :-).
Hardware i2c is certainly preferable to software i2c, it probably works in a squeeze though.
Hardware changes are unlikely to come around in a hurry to be honest, partly because Greenpower have quite recently re stocked in the current kits, but when we do update it we will make sure i2c is free!
In the mean time if you want the hardware i2c, it should be possible to cut the tracks on the PCB and add a couple of jumper wires to free up the pins... I'm away at the mo but I can have a look at the PCB when I get back.
ESP to dweet via a hotspot is great workaround though, great idea. I could have saved myself a lot of time with the app...