Showing posts with label morse. Show all posts
Showing posts with label morse. Show all posts

Wednesday, December 27, 2023

Remote (POTA) operation from the Conger Mountain BLM Wilderness Area (K-6085)

It is likely that - almost no matter where you were - you were aware that a solar eclipse occurred in the Western U.S. in the middle of October, 2023.  Wanting to go somewhere away from the crowds - but along the middle of the eclipse path - we went to an area in remote west-central Utah in the little-known Conger Mountains.

Clint, KA7OEI operating CW in K-6085 with Conger
mountain and the JPC-7 loaded dipole in the background.
Click on the image for a larger version.

Having lived in Utah most of my life, I hadn't even heard of this mountain range even through I knew of the several (nearly as obscure) ranges surrounding it.  This range - which is pretty low altitude compared to many nearby - peaks out at only about 8069 feet (2460 Meters) ASL and is roughly 20 miles (32km) long.  With no incorporated communities or paved roads anywhere nearby we were, in fact, alone during the eclipse, never seeing any other sign of civilization:  Even at night it was difficult to spot the glow of cities on the horizon.

For the eclipse we set up on BLM (Bureau of Land Management) land which is public:  As long as we didn't make a mess, we were free to be there - in the same place - for up to 14 days, far more than the three days that we planned.  Our location turned out to be very nice for both camping and our other intended purposes:  It was a flat area which lent itself to setting up several antennas for an (Amateur) radio propagation experiment, it was located south and west of the main part of the weather front that threatened clouds, and its excellent dark skies and seeing conditions were amenable to setting up and using my old 8" Celestron "Orange tube" C-8 reflector telescope.

(Discussion of the amateur radio operations during the eclipse are a part of another series of blog entries - the first of which is here:  Multi-band transmitter and monitoring system for Eclipse monitoring (Part 1) - LINK)

Activating K-6085

Just a few miles away, however, was Conger Mountain itself - invisible to us at our camp site owing to a local ridge - surrounded by the Conger Mountain BLM Wilderness Area, which happens to be POTA (Parks On The Air) entity K-6085 - and it had never been activated before.  Owing to the obscurity and relative remoteness of this location, this is not surprising.

Even though the border of the wilderness area was less than a mile away from camp as a crow files, the maze of roads - which generally follow drainages - meant that it was several miles driving distance, down one canyon and up another:  I'd spotted the sign for this area on the first day as we our group had split apart, looking for good camping spots, keeping in touch via radio.

Just a few weeks prior to this event I spent a week in the Needles District of Canyonlands National Park where I could grab a few hours of POTA operation on most days, racking up hundreds of SSB and CW contacts - the majority of being the latter mode (you can read about that activation HERE).  Since I had already "figured it out" I was itching to spend some time activating this "new" entity and operating CW.  Among those others in our group - all of which but one are also amateur radio operators - was Bret, KG7RDR - who was also game for this and his plan was to operate SSB at the same time, on a different band.  As we had satellite Internet at camp (via Starlink) we were able to schedule our operation on the POTA web site an hour or so before we were to begin operation.

In the late afternoon of the day of the eclipse both Bret and I wandered over, placing our stations just beyond the signs designating the wilderness study area (we read the signs - and previously, the BLM web site - to make sure that there weren't restrictions against what we were about to do:  There weren't.) and several hundred feet apart to minimize the probability of QRM.  While Bret set up a vertical, non-resonant end-fed wire fed with a 9:1 balun suspended from a pole anchored to a Juniper, I was content using my JPC-7 loaded dipole antenna on a 10' tall studio light stand/tripod.

Bret, KG7RDR, operating 17 Meter SSB - the mast and
vertical wire antenna visible in the distance.
Click on the image for a larger version.
Initially, I called CQ on 30 meters but I got no takers:  The band seemed to be "open", but the cluster of people sending out just their callsign near the bottom of the band indicated to me that attention was being paid to a rare station, instead.  QSYing up to 20 meters I called CQ a few times before being spotted and reported by the Reverse Beacon Network (RBN) and being pounced upon by a cacophony of stations calling me.

Meanwhile, Bret cast his lot on 17 meters and was having a bit more difficulty getting stations - likely due in part to the less-energetic nature of 17 meter propagation at that instant, but also due to the fact that unlike CW POTA operation where you can be automatically detected and "spotted" on the POTA web site, SSB requires that someone spot your signal for you if you can't do it yourself:  Since we had no phone or Internet coverage at this site, he had to rely on someone else to do this for him.  Despite these challenges, he was able to make several dozen contacts.

Back at my station I was kept pretty busy most of the time, rarely needing to call CQ - except, perhaps, to refresh the spotting on the RBN and to do a legal ID every 10 minutes - all the while making good use of the narrow CW filter on my radio.

As it turned out, our choice to wait until the late afternoon to operate meant that our activity spanned two UTC days:  We started operating at the end of October 14 and finished after the beginning of October 15th meaning that with a single sitting, each of us accomplished two activations over the course of about 2.5 hours.  All in all I made 85 CW contacts (66 of which were made on the 14th) while Bret made a total of 33 phone contacts.

We finally called it quits at about the time the sun set behind a local ridge:  It had been very cool during the day and the disappearance of the sun caused it to get cold very quickly.  Anyway, by that time we were getting hungry so we returned to our base camp.

Back at camp - my brother and Bret sitting around
the fake fire in the cold, autumn evening after dinner.
Click on the image for a larger version.

My station

My gear was the same as that used a few weeks prior when I operated from Canyonlands National Park (K-0010):  An old Yaesu FT-100 equipped with a Collins mechanical CW filter feeding a JPC-7 loaded dipole, powered from a 100 amp-hour Lithium-Iron-Phosphate battery.  This power source allowed me to run a fair bit of power (I set it to 70 watts) to give others the best-possible chance of hearing me.

As you would expect, there was absolutely no man-made noise detectable from this location as any noise that we would have heard would have been generated by gear that we brought, ourselves.  I placed the antenna about 25' (8 meters) away from my operating position, using a length of RG-8X as the feedline, placing it far enough away to eliminate any possibility of RFI - not that I've ever had a problem with this antenna/radio combination.

I did have one mishap during this operation.  Soon after setting up the antenna, I needed to re-route the cable which was laying on the ground, among the dirt and rocks, and I instinctively gave it a "flip" to try to get it to move rather than trying to drag it.  The first couple of "flips" worked OK, but every time I did so the cable at the far end was dragged toward me:  Initially, the coax was dropping parallel with the mast, but after a couple flips it was at an angle, pulling with a horizontal vector on the antenna and the final flip caused the tripod and antenna to topple, the entire assembly crashing to the ground before I could run over and catch it.

The result of this was minor carnage in that only the (fragile!) telescoping rods were mangled.  At first I thought that this would put an end to my operation, but I remembered that I also had my JPC-12 vertical with me which uses the same telescoping rods - and I had a spare rod with that antenna as well.  Upon a bit of inspection I realized, however, that I could push an inch or so of the bent telescoping rod back in and make it work OK for the time-being and I did so, knowing that this would be the last time that I could use them.

The rest of the operating was without incident, but this experience caused me to resolve to do several things:

  • Order more telescoping rods.  These cost about $8 each, so I later got plenty of spares to keep with the antenna.
  • Do a better job of ballasting the tripod.  I actually had a "ballast bag" with me for this very purpose, but since our location was completely windless, I wasn't worried about it blowing over.
  • If I need to re-orient the coax cable, I need to walk over to the antenna and carefully do so rather than trying to "flip" it get it to comply with my wishes.

* * *

Epilogue:  I later checked the Reverse Beacon Network to see if I was actually getting out during my initial attempt to operate on 30 meters:  I was, having been copied over much of the Continental U.S. with reasonably good signals.  I guess that everyone there was more interested in the DX!

P.S.  I really need to take more pictures during these operations!


This page stolen from ka7oei.blogspot.com

[END]

Tuesday, October 17, 2023

Remote (POTA) operation from Canyonlands National Park (K-0010)

As I am wont to do, I recently spent a week camping in the "Needles" district of Canyonlands National Park.  To be sure, this was a bit closer to "glamping" in the sense that we had a tent, a flush-toilet a few hundred feet away, plenty of food, solar panels for power and didn't need to haul our gear in on our backs - at least not any farther than between the vehicle(s) and the campsite.

While I did hike 10s of miles during the week, I didn't hike every day - and that left a bit of "down time" to relax and enjoy the local scenery.

As a first for me - even though I have camped there many times and have even made dozens of contacts over the years on HF - I decided to do a real POTA (Parks On The Air) activation.  In the days before departure I finally got around to signing up on the pota.app web site and just before I left the area of cell phone coverage (there is none at all anywhere near where we were camping) I scheduled an activation to encompass the coming week as I had no idea exactly when I would be operating - or on what bands.

Figure 1:
The JPC-7 loaded dipole at 10', backgrounded by red rock.
Click on the image for a larger version.

* * *

It wasn't until the day after I arrived that I finally had time to operate.  As it was easiest and most convenient to do so, I deployed my "modified" JPC-7 loaded dipole antenna (an antenna I'll describe in greater detail in a future post) affixing it atop a tripod light stand that could be telescoped to about 10 feet (3 meters) in height - attaching one of its legs to the swing-out grill of the fire pit to prevent it from falling over.  Being only about 10 feet from the picnic table, it offered a relatively short cable run and when it came time to tune the antenna, I simply disconnected it from the input of the tuner, connected it to my NanoVNA and adjusted the coils:  In so-doing, I could change bands in about two minutes.

The radio that I usually used was my old FT-100 - typically running at 50 watts on CW, 100 watts on SSB, but I would occasionally fire up my FT-817  and run a few contacts on that as well.  As you would expect, the gear was entirely battery-powered as there is not a commercial power line within 10s of miles of this place:  Often, one of my batteries would be off being charged from a solar panel, requiring that I constantly rotate through them.

* * *

For reasons of practicality - namely the fact that I would be operating in (mostly) daylight - and for reasons related to antenna efficiency, I mostly operated on 30 meters and higher.  Because we were outside, this made a computer screen very difficult to see so I logged on a piece of paper - also convenient because this method required no computer or batteries!  The very first contact - a Park-to-Park - occurred on 15 meter SSB, but I quickly QSY'ed down to 17 meters and worked a few dozen stations on CW - breaking in my "CW Morse" paddle for the first time on the air:  It would seem that my scheduling the activation and my Morse CW being spotted by the Reverse Beacon Network caused the notice to go out automatically where I was quickly pounced on.

In using this paddle - made by CW Morse - for the first time I quickly discovered several things:

  • I've seen others using this paddle by holding it in their hand - but I was completely unable to do that:  I would get into the "zone" while sending and inevitably put my fingers on the "dit" and "dah" paddle's tension adjustment screws, causing me to send random elements:  At first I thought that something was amiss - perhaps RF getting into the radio - but one of the other folks I was with (who are also hams) pointed out what I was doing.
  • Since my CW Morse paddle has magnets in the base - and since the picnic table's top was aluminum - I stuck it to the bottom of a cast-iron skillet which solved the first problem, but I quickly discovered that the bottom of a well-used skillet is really quite smooth and lubricated with a fine layer of carbon.  What this meant was that not only did I have to use my other hand to keep the key from sliding around, I started looking like the carbon-covered operators of high-power Poulsen Arc transmitters of a century ago:  My arm and hand quickly got covered with a slight residue of soot!  I then made it a practice to at least wipe down the bottom of the pan before operating.
  • During contacts, I would randomly lose the "Dah" contact.  I was presuming that this was from dust getting into the contacts (I'm sitting outside!) as it usually seemed to "fix" itself when I would lean over and blow into the paddle, but in once instance when this didn't work at all I wiggled/rotated the 3.5mm TRS jack on the back and it started working again.  I'm thinking that the issue was just a flaky contact on the jack.

At some point I'll need to figure out a better means of holding this paddle down to keep it from sliding about - perhaps a small sheet of steel with bumpers and rubber feet - or simply learn to use the paddle with a much lighter touch!

Figure 2:
Operating CW from the picnic table, the paddle on a skillet!
Click on the image for a larger version.

With a few dozen CW contact under my belt I readjusted the antenna and QSYed down to 20 meter SSB where I worked several pages of stations, my voice getting a bit hoarse before handing the microphone over to Tim, KK7EF who continued working the pileup under my callsign.

* * *

After a while, we had to shut down as we needed the picnic table to prepare dinner - but this wasn't the last bit of activation:  Over the next few days - when time was available - I would often venture out on 40, 30, 20 and 17 meter CW - occasionally braving 17 meter SSB:  I generally avoided 20 meter SSB as the band generally seemed to be a bit busy - particularly during the weekend when some sort of activity caused the non-WARC bands to be particularly full.

* * *

By the end of the trip I had logged about 387 total contacts - roughly 2/3 of them being CW.  When I got home I had to transcribe the paper logs onto the computer and learned something doing this:  If you do such a transcription, try to avoid doing so late at night when you are tired - and always wait until the next day - whether you were tired or not - and go back and re-check your entries BEFORE uploading the logs to LOTW, eQSL and/or the POTA web site!  Being tired, I hadn't thought the above through very well and later had to go back and make corrections and re-upload.


This page stolen from ka7oei.blogspot.com

[END]


Sunday, June 7, 2020

An ESP8266-based Temperature, Humidity and Line Voltage monitor

Figure 1:
The completed Temperature/Humidity/Line Voltage web
server/telemetering device.  The remote temperature/humidity
sensor is the unit to the left.  The two AC-DC wall adapters used for
powering the unit and monitoring mains voltage are not visible.
Click on the image for a larger version.
As anyone who reads this blog probably knows, I have a bit to do with the operation and maintenance of the Northern Utah WebSDR - a remote receiver system that allows anyone with Internet access and a web browser to listen to the LF, MF, HF and some of the VHF bands as heard from a rural site in Northern Utah.  The equipment for this receiver system is located a small building in the middle of mosquito and deer-fly infested range land near brackish marshes - no-where that anyone in their right mind would like to be during most of the year.  With the normal weather in the summer and many clear days, this building gets hot at times:  It's been observed to exceed 130F (55C) on the hottest days inside - a temperature that causes the fans on the computers scream!

Even though electronic equipment is best kept at much lower temperatures, this isn't practical in this building as it would be prohibitively expensive to run the on-site air conditioner full time - but all we really need to do is to keep the building closer to the outside temperature and even though it may be uncomfortable for humans, it is enough to keep the electronics happy.  To that end, vents have recently been installed to allow convection to pull away most of the heat and the exterior will soon been painted with white "RV" paint to (hopefully) reduce the heating effects of direct sun.

It would make sense, then, that we had a way to remotely monitor the building's internal temperature as a means of monitoring the situation.  Additionally, temperature information can also be used to make minor adjustments to the frequencies of some of the receivers' local oscillators to help counter thermal drift.

Figure 2:
The "business end" of the small board that contains the
ESP8266 module - the device with the metal shield.
This board also includes a USB plug, a CH340-like
USB to serial converter that allows for programming
and debugging and a voltage regulator that allows direct
operation of this board from a 5 volt supply.
As can be seen here and in Figure 4, the ESP8266 board was,
itself, mounted to a larger prototyping board for construction
of the ancillary circuitry.
Click on the image for a larger version.
On site we do have an Ambient Weather (tm) station, but anyone who has used this (or similar) hardware knows that some vendors of this type of gear make it difficult to obtain your own data without jumping through hoops:  Although this data is visually available on the local display or even on a web site, it is a bit awkward to pull this data from their system and (at least with the newer versions of the hardware) one cannot get this data locally from the weather station itself.

Fortunately, the most-needed data - temperature inside the building - is easily measured using inexpensive sensors, so it made sense to throw together a device that could make these measurements and present them in an easy-to-use web interface.

The ESP8266 "Arduino" board:

As is often the case with projects like this, the Internet has the answer.  The ESP8266 is an inexpensive embedded computer module that has a reasonable amount of program memory and RAM and it also sports hardware such as a WiFi module, several digital  I/O pins and a 10 bit A/D converter.  What this means is that for less than U.S.$12 you can get two of these delivered to your doorstep that contain an already-mounted ESP8266 module on a carrier board with a USB port in a format that strongly resembles that of the ubiquitous Arduino development board.  More importantly, the Arduino IDE supports this board meaning that it is pretty easy to use this hardware in your own projects.

Because the '8266 board has been available for quite a while, there is a large library of software for it - including a small web server and code to interface with many types of devices, including the well-known (and relatively inexpensive) DHT-22 temperature and humidity sensor.

Comment:  The ESP8266 variant used here appears to be the "12E" version which has 32 Mbit (4 Mbytes) of Flash memory and "around 50k" of RAM.

The "DHT Humidity and Temperature web server":

It took only a few minutes to find online several implementations of a web server coupled with the DHT-22 sensor - and I chose what seemed to be a popular version on a web site by Rui Santos - to look at it yourself, go here:

randomnerdtutorials.com/esp8266-dht11dht22-temperature-and-humidity-web-server-with-arduino-ide/

Presented in good detail, it was only about 20 minutes from the start to tack a few flying leads to my $6 ESP8266 "Arduino" board to connect the DHT-22 sensor before I had a wireless web server on my workbench that was happily reading the temperature and humidity.

Of course, getting something working can be miles from a finished project and that was certainly the case here as the project was about to be subject to self-inflicted feature creep and code bloat as I'd already decided that I wanted it to do two other things as well:
  • Monitor the AC line voltage.  The WebSDR receive site - being rural - suffers from very dirty AC mains power.  We have seen the nominal 120 volt mains exceed 140 volts for brief periods in addition to the frequent outages - and it would be nice to have a device that would allow us to record such excursions.
  • Telemeter the gathered information via RF.  Because the ESP8266 is a small computer - and it has data that we want - and we are at a radio receive site - it would be a simple matter to have this unit tap out the information using Morse code on a low-power, unlicensed (part 15) transmitter that was capable of being received by the on-site receivers.
The final result is this, in schematic form:
Figure 3:
The schematic of the support circuitry of the ESP8266 unit described, including a pictorial representation of the processor board itself.
Click on the image for a larger version.
Circuit description:

The ESP8266 is treated as a single component - the support circuit being connected to the pins as noted with the '8266 itself being mounted on a larger board as can be seen in Figure 4, below.  It's worth noting that this is a 3.3 volt device which means that the "high" output voltage is around 3 volts:  If I'd needed a digital input, I would have had to make sure that the logic high input level was appropriately limited in voltage.

Power supply and monitoring:

There are two uneregulated AC-DC transformer "wall warts", both being a low-voltage transformer (9-12 volts AC) with full-wave rectification and capacitive filtering  - one to power the unit and the other to monitor the line voltage.  The separation of these two function is necessary for obvious reasons:  We'd want the unit to continue to function when the AC mains was out, but continue to run from the UPS which means that we can't monitor or own power supply!  Even if we could, the current consumption of the unit varies a bit and as a consequence, so does the unregulated voltage from the monitor supply.  The source of power for the unit itself could be anything that can provide 10-15 volts DC - regulated or not - but these AC->DC transformers were on-hand, plus being simple transformer-rectifier-filter units, they do not generate RF noise - unlike some switching-type devices - a factor important at a radio receive site.

The power from each of the AC-DC adapters enter via a screw terminal strip and immediately passes through a pair of bifilar-wound inductors - the purpose here being to provide RF isolation:  Because this device contains a computer and a low-power transmitter, we don't want any signals on this device from being radiated on the power leads.

The first AC-DC adapter is used to power the unit - a red LED indicating that voltage is present.  Following this is a "bog standard" 5 volt regulator using a 7805 to provide a lower voltage to feed to the "VIN" pin of the ESP8266 board and to run other circuitry on board.

The other wall wart has only a light load - most of the current being consumed by D4, an orange LED used to indicate that the mains voltage being monitored is present.  As you would expect, an unregulated AC-DC supply like this isn't a precision instrument when it comes to measuring line voltage as it is not any sort of RMS measuring device and with its built-in filter capacitor, it's also relatively slow to respond  - but it is "good enough" for the task at hand.

This voltage is divided down via R3 and variable resistor R4 for the 0-3.3 volt input range of the "A0" (analog input) pin on the ESP8266 module.  (Note:  It's reported that A/D range of the "raw" '8266 module is 0-1 volt - apparently this board includes a voltage divider to scale from 3.3 volts.)  Resistor R4 is 10 turn unit used for calibration of the line voltage.

Watchdog timer:

Figure 4:
The completed ESP8266-based temperature, humidity and line voltage
monitoring device.  The CW transmitter portion is in the upper-left corner
of the board with the 555-based watchdog timer below it.  In the lower-
right corner is the 7805 regulator with its heat sink with R4, the
calibration for the line voltage being seen just below the lower-left
corner of the ESP8266 board.  The gray wire at the top connects to the
small board containing the DHT-22 temperature/humidity sensor.
The entire unit is mounted via stand-offs into the lid of the plastic case
depicted in Figure 1.  Inside the lid I placed a sheet of self-adhesive
copper foil that is used as a ground plane to which the input filter
capacitors (C1, C3), the LEDs and the ground connections of the
board are soldered.
Click on the image for a larger version.
Because this device is unattended in a remote location I took the precaution of adding a simple hardware watchdog timer.  The software generates a pulse train (nominally a square wave) on pin "D2" which is then applied to transistor Q1:  Capacitive coupling, via C7, is used as a DC coupled signal would have made it possible that a watchdog reset condition could have been simulated if the pin were stuck "high".  The timer itself is the ubiquitous NE555 "programmed" via C8 and R7/R8 to have an approximately 45 second period.

The pulse train from pin D2 pulses Q1, keeping timing capacitor C8 discharged - but if the pulse train stops, pin 3 will go high after the timing period, briefly pulsing the "RST" (reset) pin of the EP8266 via capacitively-coupled Q2.  A 45 second period was chosen as it takes about 8 seconds for the ESP8266 to "boot up" enough for the software to generate the - and it also allows just enough time to upload the program.

During initial development one would probably not plug a 555 into its IC socket as spurious resets would likely be an annoyance as there may not be code to create the reset pulses, but with the size of the code for this project the reset period is long enough to allow uploading of the code before a reset occurs and the pulses resume.

Temperature/Humidity sensor:

The readily-available DHT-22 sensor is used, chosen over the slightly cheaper DHT-11 as the '22 offers a wider temperature and humidity measurement range - although the software can be configured to work with either one. To avoid erroneous temperature or humidity measurements from the unit's heat generation, this sensor is mounted on its own board as depicted in Figure 3.  On this small board is not only a power supply bypass capacitor (C20) but also a pull-up resistor R19.

The "sensor module" - visible in Figure 1 - was placed inside a small piece of ABS tubing (gray non-metallic electrical conduit) for protection with small pieces of nylon window screen glued to each end to keep out insects, but allow air flow to permit accurate measurements.

CW transmitter:

Because it is a computer - and there was plenty of code space - I decided to add Morse Code generation to provide telemetry that could be picked up by the HF receivers on site.  Stealing my own Morse-generating C code from a 20+ year old PIC project, I made minor modifications to it, using a hardware-derived timer in the main loop to provide a sending clock.  The Morse generating code toggles D3, setting it high to "key" the transmitter.

The signal from pin D3 goes to Q3 which is wired via current-limiting resistor R13 to Q4, a PNP transistor to provide "high side" keying of the unregulated V+ supply.  This voltage is then passed through resistor R14 which provides both a bit of current limiting and, with C12, some R/C filtering to slow the rise/fall of the voltage:  Without it the RF would have been keyed very "hard" causing objectionable "key clicks" on the rise and fall of the RF waveform.  This voltage is used to key both the buffer and the output amplifiers, described below.

The signal source is a 28.57 MHz crystal "can" oscillator module that I found in my junk box.  While I could, in theory, have done CW keying by turning this oscillator on and off, these oscillators aren't designed to be particularly stable and doing so would have caused the oscillator to "chirp" - that is, the short-term frequency drift that occurred when power was applied would have caused an objectionable shift in the received audio tone during keying.

Instead, the oscillator was powered continuously with its output fed to Q5, an emitter-follower buffer:  R15 "decouples" the oscillator from Q5 somewhat and without it, the RF current into the base of Q5 would increase when its collector voltage was switched off causing the oscillator to heat internally, resulting in a frequency shift.  The output of the buffer circuit is then passed via resistive and capacitive coupling to Q6 which is used as the final RF amplifier.  L1 is used to decouple its collector from the power supply while C16 removes the DC voltage from the RF output.  The remaining components - C17-C19 and L2/L3 comprise a low-pass filter resulting in harmonics that are at least 40dB below the fundamental.

This circuit was originally built without Q5, the buffer amplifier, but I had two issues that could only be resolved by its addition:
  • Backwave.  Because the oscillator runs continuously, there will inevitably be a bit of leakage - and in CW where it is the very presence and absence of the signal that is used to convey the information, having a rather strong signal when there is supposed to be silence made it difficult to "copy" the code.  When Q6 was turned off, there was enough leakage between its base and collector to offer only about 15 dB of attenuation when the transmitter was "un keyed".
  • Oscillator stability.  As noted above, R15 was used on Q5 to limit the current out of the oscillator to prevent frequency drift as buffer transistor Q5 was keyed.  When I'd tried to drive the output (Q6) directly - without a buffer - I had the same problem:  If I coupled enough energy to drive the transistor, the frequency would vary with the CW keying - and the backwave would get worse - but if I increased the resistor enough to reduce the problem, the transistor would be properly driven - which also increased the backwave as the transistor's output would fall in comparison to the signal leakage.
With the circuit built as shown the backwave is at least 40dB below the keyed output  - which is more than adequate for the task.

The code:

As noted above, the basis of the project was that published by Rui Santos - and in the spirit of open source, the code was modified:
  • The original code included some small graphics served on the web page - but in line with the KISS principle, this was stripped out in favor of the simplest text, using only standard HTML formatting.
  • Additional code was added to read the AC mains voltage via pin "A0".  In the main "loop" routine, this input is read 100 times a second and then averaged, with a new reading made available every second.  This average removes most of the noise on the pin - some of which is internal to the '8266 itself, but the majority of which is due to a small amount of AC ripple on the voltage monitoring line.
  • Additional code was added to record the minimum and maximum of all of the monitor parameters - that is, temperature, humidity and line voltage.
  • The default of the code was to read the temperature in Celsius, but being in the U.S. I added code to give the readings in Fahrenheit as well. 
  • The web server code was modified to display all of the available data - the temperature in Fahrenheit and Celsius, the humidity and line voltage - and their minimum and maximum values.
  • Addition modification was made to the web server code to allow each of the data points to be read in simple text format to simplify parsing for remote monitoring and logging of this data.  The nature of the the web server actually made it very easy!
  • Yet another modification was made to reset the minimum and maximum readings and to provide information as to how many seconds it had been since a reset had occurred.  The temperature/humidity min/max reset is separate from the line voltage min/max.
  • The code also keeps track of mains voltage that falls below a threshold (an outage) or exceeds a threshold (a "surge") - both of which are extremely common at the remote receive site. 
  • I added my own Morse generation code, ported from some PIC-based "C" code that I wrote about 25 years ago and interfaced it with the main timing loop.

Source Code:

If you are interested in the source code (sketch) you may find it at THIS LINK.

A few minor changes/improvements - noted in the source code's header - have been made since the original posting.

Implementation:

Figure 5:
 A screen shot of the web page.  This same information is available
from individual links (on the bottom half of the page) that will
return just the information requested, making it trivial to obtain
individual data points using something like WGET.
Click on the image for a larger version.


As mentioned, with the WiFi capability of the ESP8266, the information that this device records is available via a web page on the wireless network:  One only need enter the SSID and wireless password at compile time.  For reasons obvious to anyone familiar with the Internet, this device won't be accessible from the web itself, but only to devices on the local network.

With the CW generator operating on 28.57 MHz, this signal lands within the 10 meter amateur band - and with this device being co-sited with receivers, it is a simple matter of tuning to that frequency to hear the telemetry.  Even though the RF output power is on the order of 50 milliwatts, the actual transmit "antenna" is a very small piece of wire - large enough to radiate just enough signal to be heard via the nearby antennas but not nearly enough to exceed FCC part 15 rules, eliminating the need for this device to transmit an FCC-issued callsign.

Comment:

This device was installed at the Northern Utah WebSDR shortly after this article was originally posted.  You may hear the Morse portion of this device via this link


This page stolen from ka7oei.blogspot.com

[END]