Member Since: February 23, 2010

Country: United States



Geek, pilot, dad.


Network engineer

  • Will this work at the same time as an external HDMI? I'm looking for a way to have a small controller like this to run a scoreboard which is an HDMI monitor.. I"d want the display duplicated across both screens, displaying the same things..

  • Will the smaller one, built for the Zero, actually also work on the regular PI? Assuming I dont need the larger display and want to save some money??? Or, is there something fundamentally different about how they work??

  • Come to think of it.. If Sparkfun were to start something like this, it could use the phant.io to actively collect the data for the mapping of the found devices. I'd LOVE to just put a small box on my dashboard and leave it there if the range was good enough to detect from there (which I suspect, it is..)

  • That's a great idea. I do have an android, so I'll probably download and use this app, but if I could build a bunch of small boxes to give to family and friends, that would be great... Could even be a good project for my son's boy scout troop to work on their electronics merit badge. I haven't looked at the details yet, but I'd be in for testing/helping with something like this...

  • I'm interested to use one of these to try to make my above ground pool into a "speaker".. Or more accurately, I want to be able to hear the music while under water. I know it's not going to be HiFi or anything, but I'm curious about a few things.. 1: has anyone ever tried anything similar that can give me any idea of what I can expect? And, 2: I've already got speakers outdoors near the pool, and I'd love to be able to use the same signal for this, but it's already amplified at what is probably way more than this can handle long-term.. Is there something I could hook up in parallel to another existing speaker to bring it back to line level, to then re-amplify the signal with a smaller amplifier outside so that I dont have to run new wires to the outside?

  • So.. Instead of the transistors, you used a microcontroller... That's fine, but now that it's there.. USE IT! I wanna know how fast this thing goes.. How about an LCD with current and max RPMs? Also, a video of it running instead of just the GIF?

  • I dont think this is entirely true.. Saying that "The worst-case for acoustic couplers talking to carbon microphones is somewhere around 300 baud" can only be true when you take into account several other factors, such as acceptable error rate (what is "worst case" based on? one error bit out of how many???) and also, saying it's how fast the carbon mic can react ignores the fact that it's using FSK and the actual tone being sent is between 1070hz and 2225hz depending on whos the initator/answerer, and if it's a 0 or 1 being sent. (https://en.wikipedia.org/wiki/Bell_103_modem).. In the 80s, we were sometimes able to get these couplers to run at 150% rate (450 baud) depending on the quality of the phone line (some of my friends were out of the same telco CO, so better quality between us) so this isn't telling the whole story. The frequencies chosen for the FSK had to take into account that the 4 tones needed (for each side to have separate frequency for 0 and 1), and make sure each tone fell within the range the phone system was created to convey ( I believe 300-3300 hz) and that the frequencies weren't going to be related in frequency in such a way that they could cancel each other out or otherwise be confused for one another by the PLL circuitry on the other end that had to decode it. Once optimal frequencies were determined, I'd bet that the speed of a bit (and therefore BPS) had more to do with how long it took the PLL to lock on and detect the bit, while still having over 1/2 bit time to actually convey the correct bit to the attached computer. At 2225hz, with 300 BPS, that's just over 7 audible sine waves per bit. That seems reasonable, considering it probably needs 2 cycles to lock.. I have no hard evidence that this had anything to do with design, but from years of playing with 300 baud modems and the physics of sound, I'm betting this is what was boiled down to "how fast a carbon mic can react"

  • I snipped the wires and used it on a Raspberry pi with a screw terminal proto top.. Not pretty but it works..

  • So.. This seems like a great little GPS.. I am making a position logger for a cruise I'm going on this weekend, and I've got it set just to record everything into giant NMEA text files, and I'll figure out what to do with it when I get back, but I have one big problem.. There doesn't seem to be a provided GPS sentence that would give me the current DATE.. I can get the TIME from the $GPGGA but there's no DATE! It doesn't send the $GPZDA sentence apparently, so I'm bummed.. I wanted this thing to set the time and name the output files based on the GPS provided date/time, but now I'm going to have to plug it in and make sure it gets the date set at least, so my files are correct.. Does anyone see anything I'm missing? --EDIT -- False alarm... It DOES send the $GPRMC sentence, which also has the date, so it looks like I'm good!!

    That being said, sitting here in my house on my workbench, I just turn it on and I get 4 sats and a good fix in just a few seconds. I'm sure it'll be great when it can see the sky!

  • OK.. This is a cool product, but in the demo video, he talks about effects pedals like the one that made Frampton's "talk box" sound.. If I'm not mistaken, I believe there was no box for that.. He connected a tube from a funnel by the speaker to pick up the guitar sound, and then put that tube in his mouth by the mic, and used the shape of his mouth to make the guitar sound like it was talking... No box needed!

No public wish lists :(