Rock Seven has launched a board that takes care of the PSU and antenna requirements to support the Iridium 96090 module https://www.iridium.com/products/iridium-9602/
This enables fast time to market and coverage in remote areas on customers IoT devices.
The Arduino platform has gained a fantastic popularity over the past ten years. For small quick and dirty projects, the .ino files and the standard IDE is OK. However, for professional development projects and for developers that want control over the .hpp and .cpp files the standard Arduino IDE is somewhat regarded like a toy. Furthermore there is no proper debugger in the Arduino IDE (whaaat?, you gotta be kidding?)
Well, this has changed as Visual Micro has developed a plugin to Microsoft Visual Studio. You can write code the normal way you do it with .cpp and .hpp files. You can also run the GDB debugger. The IDE has support for the regular .INO files and Arduino libraries. Here is how both .cpp and .ino files are handled: http://www.visualmicro.com/page/User-Guide.aspx?doc=INOs-and-CPPs.html
There is a free version of Visual Micro and it works against the free versions of Microsoft Visual Studio 2017 Community Edition. All you need is a Microsoft account to be able to download and install Visual Studio 2017 Community edition. Then in MSVC 2017, go to tools, Extensions and Updates and enter a search for Arduino in the search bar. It will will offer to automatically install the Arduino tools and the GDB debugger. Click install and you are on the right path.
If you find this tip useful, please share on facebook and share the link. Also, feel free to report your experiences in the comment field.
I have been working on a trackball based controller for my HDSDR SDR project lately. This is a small R&D project that is run on my spare time where the goal is to determine if it is possible to use a trackball as a VFO for software defined radio (SDR) in contests. The project started out based on a demand for a more ergonomic way to operate a mult receiver in a contest environment that is less fatiguing during 48hours duration of a major contest like CQWW or CQWPX. The goal is that it should be possible to operate all radio functions you need from one hand only: VFO, speed of vfo, band, mode, filter width, volume, gain. I have modified a Marconi trackball and the controller is a Trinket Pro controller (Arduino)
I recently needed a new CW keyer with Winkey compatibility for use with my N1MM logging setup. K3NG has written some nice keyer code that I compiled and uploaded to one of my Arduino UNO boards that I had laying in the shack (if you want to try it, you need the latest – above 1 – version of the Arduino “IDE”). Below you can see some pictures from making the prototype thru to ready made keyer with USB interface and adjustable speed button. I did not install the memory buttons, as I control the CW keyer via USB from N1MM or Hamradio Deluxe. It works very well with my Yaesu FT-450D but instead of the UNO I will eventually use a Mini Pro board with the Atmel Atmega 328. You can see more info on K3NGs site http://radioartisan.wordpress.com/arduino-cw-keyer/#comment-3255
Below is the schematic (remark: full credit is given to to K3NG!). I have modded the design for my own needs. Instead of the 2N2222 I use a TTL tolerant FET of type IRLIZ44N to drive the keyer output. Then I don’t need the 100 ohm resistors in series. I also did connect a piezo tweeter directly to the CPU without using the 2N222 transistor. It works OK. However, the sound of the piezo tweeter is not the best in the world. Finally, as mentioned above, I did not install all the buttons. I installed only the command button to save space. There is a need to do a small mod on the UNO hardware due to some reset issues. For that I will have to add another button that needs to be pressed when I want to upload code.
I also needed a CAT interface. It is possible to use a FTDI chip for this task, however the signal levels need to be transformed to +/- 12V. This I solved with a MAX232 board that I had laying around in the shack. So now I have a CAT interface that is compatible with Win XP, NT, 2000, 98, Windows 7, Windows 8 etc since the FTDI chips are widely supported. It looks like … but works like …