Member #140606

Member Since: June 30, 2010

Country: United States

  • Can I underline the “…take all 3 tests in one session…” part? You should always take all three. Worst that happens is you only pass the ones you’re ready for. Best that happens is you’re ready for more than you expected!

    As for the comments about Morse Code above…

    I’m pretty good at Morse. (I won the 2014 ARRL DX Contest and the 2018 Kansas City DX Club pileup contest)
    However, I don’t feel it should be a requirement for an amateur license. There are too many worthwhile things to do with amateur radio that don’t require code.

    That said… don’t write off Morse as obsolete. Transmitting equipment for Morse code is almost trivially simple – which means it’s also light, reliable, and power-efficient. Portable operation in remote locations is popular, and Morse makes it much easier. (“Islands on the Air” and “Summits on the Air” are things…) For many of us, it’s just plain fun!

    Morse even has some applications outside the context of radio. It’s easy to generate in a microcontroller and doesn’t require much hardware. (a piezo buzzer will do the trick) I carry an Arduino-based audible thermometer in my truck.. and once had a UPS that sent error codes in Morse. In both cases the “vocabulary” is limited, and at low Morse speeds you don’t have to know the code to look up the dots & dashes. (if you use it often enough, you’ll learn the code without even trying:) )

  • Mine is successfully speaking with a DS18B20, using the OneWire library. I haven’t gone any further than having it spit the temperature reading out the serial port yet.

    (had some issues on the WiFi side which have since been pretty much resolved. It was a Christmas present so obviously I haven’t been working on it for very long:) )

    I would say that for your purposes, this thing (Thing) is an Ardiuno with a WiFi shield.

  • I’m having problems with the Arduino library on Linux. I’ve got a Weather Shield. (which uses this sensor and the MPL3115A2 library) I successfully built the sample code, and successfully made a few changes to send the readings inside with a set of Xbees. All that was, however, done using a Windows 7 machine. The Windows box is inconvenient for further development. (it’s in a room full of ham gear & there’s really no space for a set of weather sensors:) ) I have a Linux (Ubuntu) machine in a much larger room.

    But I can’t get the code to build on the Linux box. I get a few dozen “MPL3115A2.h:619:9: error: stray ‘#’ in program” errors, and a dozen or two other errors of various types. I’ve tried re-downloading the library, both from the link on this guide and the one on the WeatherShield guide. (they point to two different URLs) I’ve tried simply copying the folder from the Windows machine. I’ve tried running “dos2unix” on the .h and .cpp files in case there was a line-ending disagreement. None of it has worked.

    The Weather Shield also uses the HTU21D humidity sensor. I downloaded that library from the link on the WeatherShield guide & it works fine. (at least, there are no compile errors citing that library)

    Again, the same sketch will build (and run) perfectly if I build it on the Windows box. I’m confused.

No public wish lists :(