|
Nerobro posted:I got a Christmas present from Kickstarter. My Digisparks showed up Monday. A full review will follow. So far.. I've run into two things. First, the documentation isn't immediately obvious, and you need a custom version of the IDE. But... that only set me back half an hour. Mine arrived on tuesday, I pulled out my parts bin and found I have jack all in the way of useful components (plenty of resistors, capacitors, transistors and unlabelled LEDs of various colours and sizes, but no solid core wire to hook up any of it). I've so far only bothered modifying the USB2LCD example to autoscroll (ie, move a complete line from the bottom to the top row and start writing on the bottom line) and haven't yet got a daemon running on my pc to send data to it. Eventually I think I'll try make it run standalone with an ethernet module and basic http stack so it can pull data from twitter and display tweets, since that's what all the cool kids seem to do. It'll be interesting to see if I can get that to fit on a digispark solo or if I need to use the eeprom module.
|
# ¿ Jan 24, 2013 03:41 |
|
|
# ¿ May 15, 2024 17:36 |
|
I've got a digispark pro (ATtiny167 based device) and I'm trying to read temp/humidity data from an AM2320. I can't get a proper read from it. The datasheet says the response should be a sequence of bytes confirming the instruction, the datagram length, the requested data, then a two byte CRC. What I'm actually getting back is the instruction confirmation, a zero byte, the expected length, then 0 bytes for the rest of the data. I've got it hooked up to 5v and to the SDA/SCL pins on the pro (with 4.7k pullups) and the basic code I'm using is as follows: code:
As far as I can tell the timings in the USI_TWI_Master files are exactly what the sensor expects but I'm not confident enough to try change any of those values. I've also seen other code samples for this sensor put a delay between reads but with the tinywire library the requested data is prefetched when requestFrom is called so there's no point. Any ideas what's loving up and how I can fix it?
|
# ¿ Mar 14, 2016 13:22 |
|
Captain Cool posted:You're not actually talking to the device. The device should ack its address. The response you're getting -- 03 00 04 00 ... -- is the same as the command you sent. I'm guessing the Wire library uses the same buffer for sending and receiving. Welp, that seems so obvious in retrospect. Thanks, I'll see if I can get this thing to respond.
|
# ¿ Mar 15, 2016 01:11 |