Did you know that the Misfit Flash has an nRF51822 device at it's heart? I do. And when repurposed, they make great little devices for beacons, or temp monitoring, or acceleration measurement (via the built-in LIS2DH), or a single button remote, etc. Here are a few pics ... I'll try to include the code and pinouts (for the LED's / switch / accelerometer) at a later date.
Anyone know why there is the symbol for "Sputnik" on the silkscreen? Just curious...
|@ February 14, 2016 1:47:38 PM CST ( )|
So, for the past 6 months (from Feb. '16), I have been successfully using Xcode as my development environment for ARM cortex-mX devices (mainly cortex-m0).
August '15 I finished creating an Xcode platform for ARM devices copied from the existing iPhone platform (with additional inspiration from Appportable's Android development platform for Xcode) ... unfortunately, it doesn't do native (meaning built-in) debugging. This is primarily for 2 reasons - 1) I haven't figured it out ... yet. But I WILL. And 2) The JLink tools require the use of GDB instead of LLDB, causing all sorts of headaches getting GDB running in the latest edition(s) of Xcode. Again, I WILL solve this. For the time being, I'm using the Segger JLink Debugger app; it's OS X native, and is scriptable, so it can be called from Xcode.
If you would like more information, or have suggestions on how to fix the GDB / JLink problem(s), drop me a line.
|@ August 26, 2015 3:02:37 PM CDT ( )|
In a previous post I briefly talked about a 6GHz (002, 006, 010, 011) HP8753D that I had recently purchased on eBay. And along the way I had also acquired all of the other bits and pieces (mainly from Eric Haskell in Texas) to turn an 011 unit into a non-011 (with integrated test set) unit. Well, it's finally done - fully cal'd and ready to go! The hardware conversion only took a couple of hours. The full cal took longer.
|@ January 11, 2015 3:57:36 PM CST ( )|
I purchased this Tektronix 2782 SA a few years ago. And for the most part I've been very happy with its performance. There were a few things that did bother me though. One was a cold start issue where the unit couldn't detect one of the YIGs. After a warm up (and an unplug / replug / restart cycle) the unit would work fine. The second issue was a little more mundane, but annoying none the less ... the Real Time Clock was stuck! How could that be?!
So, a trip to eBay to find some NOS Statek RTC-58321 real time clock IC's (really only needed one, but bought a few). And after a bit of minor surgery to remove and replace the part, all is well (at least for the clock). The startup issue was a little harder to fix. I had to replace the internal 500Mhz oscillator, as the module that was in there was previously (incorrectly) replaced from an older rev. So that's 2 for 2. In the end, I now have a fully functioning 2782.
Perhaps (as John Miles KE5FX warns me) I might need to replace the electrolytic caps someday soon ... apparently they come from an era where they leak electrolyte and can cause lots of issues.
|@ January 11, 2015 3:46:12 PM CST ( )|
So we ran into an issue working with a client using this module. Specifically, we couldn't figure out why we were NOT getting full output power (RSSI with Lightblue from only a few feet away was -90dBm). Long story short, Laird has a special whisper mode. If you have similar issues, see this blog post on the Nordic Semiconductor Dev Forums --- https://devzone.nordicsemi.com/question/4629/laird-bl600/
Lazy? ... to paraphrase:
"It seems Laird uses pin 20 to enable whisper mode, so if it is not explicitly set to low, then you will get terrible RF performance.
Response from Laird:
If you are using the Nordic SDK, the output of GPIO 20 must be set as a low (0v) to enable the RF transmit power circuitry. Your reference to a 10m range is the most commonly reported symptom for this issue. Setting GPIO 20 low is done via the Nordic application that you are using. We instituted GPIO 20 programmatically with smartBASIC however if you are indeed using the Nordic SDK you must set it manually."
Here's an image of what's under the can. You can see a three terminal device in the lower right that goes to GPIO 20 and the PA Enable pin. They are probably throttling the amount of power available to the output stage on the nRF51822, thus limiting the range.
|@ January 11, 2015 3:00:28 PM CST ( )|
Previous 1 2 3 4 5 Next