I tried a bunch of diff resistor values, 1k, 2.2k, 3.3k, 4.7k, 10k for the pull-ups on the lines, and though without pull-ups, the I2C's cant communicate at all, with any of these, the values on request only give me FF.
Looks like it's the same shit, the amount of bytes to be recieved back is a match, sent 4 bytes, recieved 4 bytes, but all the bytes are of value "FF", hence, 255. I loaded up the example programs that are 100% working in the TinyWireS library, which does a stress test and compares if the value sent, and value recieved is a match or not. I've got sending data working, why does requesting it from the dang thing total shit.īTW the response i get when testing this in the Serial Monitor looks like this: Please let me know wtf im doing wrong here.
However, when trying to Request data from it, it doesn't trigger the function on the ATTiny slave (Tried many diff LED indications if the function is triggering, and sadly, it is not.) I got the Teensy 3.5 programming, and succesfully SENDING data out to the ATTiny, and the ATTIny, depending on the amount of bytes, is flashing an LED so many times. The answer: Using ATTiny85 per module, and communicating to the master (Teensy 3.5).Īnd so far, development is working dandy: I have most all of the design down, and have figured out how to achieve this. I recently got the teensy, and am working on a project to create modular buttons that can attach to each other in a multitude of fashions.
0 kommentar(er)
