SparkFun Electronics Commentsurn:uuid:214d0e4e-f1b1-d287-ce26-ac5b4c9f82492024-03-28T13:50:23-06:00SparkFun Electronicssantaimpersonator on Friday Product Post: Everyone Wants a Logsantaimpersonatorurn:uuid:f5eac894-4bcc-b2f5-60ab-fb8bed3596de2019-05-20T15:34:36-06:00<p><em>Keep an eye out for a new "log" board...</em><p>There was an issue with some of the RTCs (by the manufacturer) on <a href="https://www.sparkfun.com/products/14558" rel="nofollow">Qwiic Real Time Clock Module</a>, which is why it was on backorder. We just got the issue fixed.</p><p>As far as making a 5-pin connector to expose the INT pin... I'll mention it, but I think the focus is to stick to the 4-pin system and let users "<em>hotwire</em>" (aka solder) the INT pin on their own. Also, I don't think all interrupts work the same so there might be an issue if the connection was shared by multiple devices... the microcontroller might not know which device sent the interrupt/alert and it would need to ping all devices on the bus.</p></p>
UpGoer on Friday Product Post: Everyone Wants a LogUpGoerurn:uuid:717f9734-88d9-306b-c614-070d8f66f4232019-02-09T01:01:03-07:00<p>It's better than bad. It's good!</p>
Customer #134773 on Friday Product Post: Everyone Wants a LogCustomer #134773urn:uuid:cd95171f-e41b-e8c4-12f8-a00ea4b77bf62019-02-08T21:37:53-07:00<p>The Qwiic OpenLog looks good, <em>BUT</em> (and frequent readers of my comments will be able to guess what's coming next) it would be a lot better if it had an RTCC (Real Time Clock Calendar) on board. Many of the data logging "use-cases" (at least in my experience) are dependant upon reasonably accurate time stamps. The reprogrammability of the '328 would allow for a very small (and reasonably low power and low cost) data collection systems.<p>I can hear the screams "but what about the <a href="https://www.sparkfun.com/products/14558" rel="nofollow">Qwiic Real Time Clock Module</a>?" Going to that item, though, besides the banner saying "You last purchased this item" (so yes, I know about it), it's also on Backorder, and there's a banner saying "We do not currently have an estimate of when this product will be back in stock."</p><p>There's another advantage of putting the RTCC onto the same board -- the "INT" output pin could be connected to one of the '328's IO pins so that the user could set up to have the RTCC produce "alarm clock" interruptss and the '328 act upon them.</p><p>Another thought: The I2C is a bus where only the "master" can initiate a data transfer, I've seen several I2C "slave-only" devices, including RTCCs, IMUs, and even GPS, and other sensors, that can generate an INT (interrupt) signal, usually set up so that it can be "wire-ored" together, to get word to the "master" that it has something "interesting". I'd like to see a "Qwiic Plus" that adds a wire for interrupts. Since we typically have fairly few things on the Qwiic/I2C bus, it wouldn't be a major problem to have to poll the ones that can generate an interrupt to find out which one(s) have actually asserted the interrupt.</p><p>If I recall correctly, the ATmega328 doesn't have a "sleep mode", only waking up on an interrupt. Too bad -- that can really help the bottom line in a power budget!</p></p>
Sembazuru on Friday Product Post: Everyone Wants a LogSembazuruurn:uuid:64d52029-2a3a-9c75-fe46-658fa198a4b72019-02-08T18:15:51-07:00<p>Thanx for the clarification. Easy enough mistake to make.</p>
ROB-24601 on Friday Product Post: Everyone Wants a LogROB-24601urn:uuid:c27de79f-3abc-b093-178e-d9cc8a5f43872019-02-08T13:48:15-07:00<p>Rats, I did say byte, didn't I? Sorry, that one's totally on me. It should be Megabit per second. Good catch, thank you!</p>
Sembazuru on Friday Product Post: Everyone Wants a LogSembazuruurn:uuid:4950cc67-9831-7f5d-5cc7-9a1c4c4783052019-02-08T12:08:46-07:00<p>Question about the XBee modules. For the speed is the text or Rob right? For the RF speed both match (kilobytes per second or KBps), but for the serial speed there is a mismatch. Rob says "1 megabyte per second", but the text is written as 1Mbps which is one megabit per second. Did Rob just accidentally misread his notes? (I'm not trying to blame him, it is an easy mistake to make.)</p>
QCPete on Friday Product Post: Everyone Wants a LogQCPeteurn:uuid:7b6e54fe-8166-66b4-48f2-3f20c294e91d2019-02-08T11:59:57-07:00<p>Looping in my head all morning: "What's good for a snack and fits on your back?"<p>Thanks a lot Chris!</p></p>