Replaced Arduino Ethernet Shield with Wifi Shield

-
We bought a new home a few months ago, and I'm finally getting around to some updates on the Whereabouts Clock.  I decided that hosting an 802.11b WEP secured Wifi network just to host the clock was a bit silly.

Prior to the move, I was using the Arduino Ethernet Shield attached to a 3Com OfficeConnect WL-524 to bridge the clock data to my Wifi network.  The only way to connect it as a bridge was to use WEP security, which by all accounts is now completely insecure.

I saw that Arduino now sells a shield with a built-in 802.11g that supports open, WEP, WPA networks.  I picked one up and after much frustration with upgrading the firmware on my Arduino (Uno rev. 1) and the shield itself, I finally got it online.  This reduces the number of components in the clock, and certainly the power consumption as well.

I also redid my homebuilt servo shield because the Wifi shield required the use of one of the pins I had been using for the clock servos.  Here's the schematic:

I used a perfboard that I cut to size and recut to fit around the wacky pin spacing on the Arduino between digital pins 7 and 8.  The jumper J6 is only needed if your Arduino is a rev 1 or is missing the IOREF pin.  Rev. 3 and I think rev. 2 have these extra pins and the jumper may be omitted.  Without the jumper, the Wifi shield will not initialize.  The LEDs 1-3 are green, yellow, and red, respectively, and are used to indicate a connection to Wifi/power, data processing/waiting, and error.  Each servo drives one hand of the clock.

Here are the finished photos:




Comments

Post a Comment

Popular posts from this blog

V-22 Osprey Project - Design Changes for v3

-
Image
It's been a busy end of 2021, and as we start 2022 I'm getting closer to building version 3 of the Osprey wing.  The single biggest problem I've faced is the amount of backlash in the direct spur gear drive of the tilt mechanism.  It introduces some nasty instability that, left unchecked, would likely destroy the model in flight. I've investigated other tilt mechanisms, but the one I keep coming back to is the rack and pinion design that Tom Mast uses in his model at Rotormast.  His design uses a high-torque digital servo with a small pinion gear driving a rack attached to the rotor nacelle.  The servo has been modified with an external potentiometer that's driven by a gear on the translation tube to give positional feedback to the servo.  I like this design a lot because 1) It works, and his model is proof, and 2) it requires less torque from the servo and has less backlash. I ordered the pair of modified servos, potentiometer, and rack from Tom's site and star
Read more

V-22 Osprey Project - Flight Control

-
Image
Now that I have a conceptual idea of how to build a V-22 using leftover mCPX BL parts, how do I go about controlling such an aircraft? I own a Taranis X9D+, and it can control up to 32 channels using dual receivers, so that won’t be a problem. I’m sure that I can create a mixing profile in the transmitter to handle just about anything, but I’m also sure that just like any multi-rotor “drone," this thing will need some form of automatic flight stabilization. I own a few multirotor aircraft and I’m familiar with how they function. Some research into the popular flight control software (Betaflight, iNav, Cleanflight, LIbrepilot, etc.) all came up short. No one has written code for off-the-shelf flight controllers to manage a dual-swashplate aircraft. I would have to build my own. I have not delved into writing code for flight controllers, but I have built a number of Arduino projects, and some of them utilize RC inputs to control servos and motors. It occurred to me that I
Read more

Whereabouts Clock Update

-
Image
After a few months, Life360 has gone the way of Apple and locked down the API I used to get location data from the phones.  This is disappointing, but inevitable. I found on a forum for Home Assistant that the app OwnTracks might be a suitable alternative. It's a neat little app that will trigger the phone to send its location data via MQTT to a server that you specify. I had to rework the code a bit, but the new operation is as follows: OwnTracks on the phone will push location data per its configuration to the MQTT server (Docker container) The Mosquitto (MQTT Broker) container will receive the data and forward the data to its subscribers The MQTTWarn container is a subscriber and translates the received data and adds it to the MariaDB database The Apache web server hosts a Python CGI script that is checked each minute by the Arduino microcontroller.  If the data has changed, the hands are moved to the new location. The only exposed port to the Internet is TCP 1883 for MQTT
Read more