I’ve tried that, but I get this error when I do:
2015-01-17 11:30:50 UTC-6 [Agent] ERROR: cannot convert the string
2015-01-17 11:30:50 UTC-6 [Agent] ERROR: in unknown vimp:68
2015-01-17 11:30:50 UTC-6 [Agent] ERROR: from unknown overrides:3
2015-01-17 11:30:50 UTC-6 [Agent] ERROR: from unknown vimp:31i think this should also work:
register = 0x3B.tochar();
This is weird:
server.log(0x3B.tochar()); <— logs ```;```
server.log(0x3B.tostring()); <— logs ```59```
server.log(“\x3B"); <— logs ```;```
so server.log(0x3B.tostring()) is equivalent to server.log(59.tostring())
whereas the \x00 notation (inside of quotes) is a way of building strings with hex bytes
so you can do things like:
local someString = "\x00\x01\x02";
for i2c.read you want a string of characters (a ; in your case)
Thank you for looking at this. I’ll post back tonight with the Squirrel only result
register is being passed in as a string, so we need to .tointeger() it before we can .tochar() it
(or rather, it was getting .tostring()'ed in the update function).. I updated it to look like this, and I'm getting expected results:
i2c_addr = pin[0] << 1;
register = pin[1];
numbytes = pin[2].tointeger();
local word = i2c.read(i2c_addr, register.tochar(), numbytes);
@dtex I just finished setting up my imp. I've got the IR sensor and I just finished soldering headers to the Adafruit I2C PWM driver, so let me know if I can do anything with those to help you test
@beardedinventor Woo hoo, it works!
@rwaldron I just need to add support for i2cReadOnce, some tests and I’m done. I also think I should explore passing the frequency to Tyrion since so many posts to the agent will never even be read.
@frxnz It’d be helpful to test the PWM driver and make sure I didn’t break that while trying to get I2C reads working.
@rwaldron I just need to add support for i2cReadOnce, some tests and I’m done. I also think I should explore passing the frequency to Tyrion since so many posts to the agent will never even be read.
@frxnz It’d be helpful to test the PWM driver and make sure I didn’t break that while trying to get I2C reads working.
I got
servo.sweep() to work once, but it the steps were kind of erratic. And now I can't get the servo to move
Also, guessing you'll want to add this line:
Imp.prototype.sendI2CConfig = Imp.prototype.i2cConfig;
It started working again, not sure what happened there. Here's a video of
servo.sweep() weirdness https://www.dropbox.com/s/bvbkm8mwfpr085a/servo.mov?dl=0
I noticed there were timing issues even with
led.blink(), so may not be an I2C issue?
All of the other servo methods seem to work fine
That all makes sense and works as expected. Keep in mind that any commands sent from Johnny-Five are relayed through a cloud service and all the timing for both sweep and blink are handled in Johnny-Five. A new command is sent for each change of state and each command has to go through the cloud service. In sweep, we literally set each and every position throughout the sweep from Johnny-Five. Thank you for checking this out.
I just watched the video. Honestly, I’m really impressed that sweep worked as well as it did.
@rwaldron There are two things I would like to add to imp-io but they are not things found/done in Firmata. I think they are important given the nature of how the Imp works.
- Add a reporting frequency parameter to the io opts with a default of one whole second. This allows us to set the interval that is used for Reporting.update(). A typical IoT project could have a value measured in minutes instead of milliseconds. Currently most reports back to the agent are ignored so they are wasting bandwidth.
- Add a command to remove elements from the Reporting.pins array. I would like to tell the Imp to stop reporting when I get the result of an i2cReadOnce call.
Both of this things are easily done, but for the second I need to add a command. What is the authoritative source for this list and can I add new ones?
const PIN_MODE = 0xF4;
const ANALOG_WRITE = 0xE0;
const SERVO_WRITE = 0xE1;
const DIGITAL_WRITE = 0x90;
const REPORT_ANALOG = 0xC0;
const REPORT_DIGITAL = 0xD0;
const I2C_REQUEST = 0x76;
const I2C_REPLY = 0x77;
const I2C_CONFIG = 0x78;
const SYSTEM_RESET = 0xFF;
one sec
for i2cReadOnce:
The naming has always been backwards here
When I added i2cRead to Firmata.js, I wanted that to match analogRead, digitalRead
so if you adjust your i2c command params with the read “mode” after the address and bfore the register, you’ll be all set
mode = READ_MODE & MASK