HF Antenna Analyser With Arduino and DDS Module

34,787

221

43

Published

Introduction: HF Antenna Analyser With Arduino and DDS Module

Hi

In this Instructable I'll show you how I built a low-cost antenna analyser which can measure an antenna and display its VSWR over any or all of the HF frequency bands. It will find the minimum VSWR and corresponding frequency for each band but also will display a realtime VSWR for a user-selected frequency to facilitate antenna adjustment. If sweeping a single frequency band, it will display a graph of VSWR versus frequency. It also has a USB port on the back for outputting frequency and VSWR data, to allow more refined graph-plotting on a PC. The USB port can also be used to reflash the firmware if needed.

I recently got into amateur radio (because I liked the idea of peer-to-peer communication over huge distances without infrastructure) and rapidly made the following observations:

1. All of the worldwide communications that interested me take place on the HF bands (3-30 MHz)

2. HF transceivers are very expensive and will break if you don't drive them into a reasonably well-matched antenna

3. You are generally expected to rig up your own HF antenna from bits of wire strung across the garden (unless you want to spend even more money than you spent in 2).

4. Your antenna might be a bad match but you won't know till you try it.

Now a purist would probably say that one should first test the antenna on very low power at the frequency of interest and check the VSWR on the rig's meter to assess the quality of the match. I don't really have the time to muck about with that sort of thing for every frequency I might want to use. What I really wanted was an antenna analyser. These devices can test the quality of the antenna match at any frequency over the HF bands. Unfortunately they are also very expensive, so I set about considering whether I could make my own. I stumbled upon the excellent work carried out by K6BEZ (see http://www.hamstack.com/project_antenna_analyzer.html), who investigated the use of an Arduino to control a cheap direct digital synthesiser module (DDS). He soon abandoned the Arduino on cost grounds, preferring to use a PIC. Well, in 2017 you can buy an Arduino Nano for about £3.50, so I thought it was time to revisit his work, pick up where he left off and see what I could come up with (note that I'm not the only one who has done this: there are some very nice examples to be found on the internet).

Update - I've been getting into 60 m recently, which the original sketch didn't cover. So now I've uploaded firmware version 7, which adds the 160 m and 60 m bands. These aren't add-ons; they are fully integrated into the operation of the analyser. It was fortunate that I could find an u8glib font that was still legible but allowed me to display ten bands simultaneously on that little screen (although it wasn't monospace, which caused some grief). I have estimated calibration values for the new bands, based on interpolation / extrapolation of the existing calibration values. I then checked these out with fixed resistors and they give pretty good results.

Update - as several people have asked about schematics, the fundamental Arduino / DDS / VSWR bridge circuit is largely unaltered from K6BEZ's original work. Please check out the above URL for his original schematic on which I based this project. I've added an encoder, an OLED screen and fully developed firmware to make for an effortless user experience.

Update - This system uses a very low voltage DDS signal source in conjunction with a resistive bridge containing diode detectors. Thus the diodes are operating in their non-linear regions and my first version of this system tended to under-read VSWR. As an example, a 16 ohm or 160 ohm impedance load should show a VSWR of about 3 in a 50 ohm system; this meter indicated a VSWR closer to 2 in this situation. I therefore carried out a software calibration using known loads which seems to be an effective fix for this problem. This is described in the penultimate step of this instructable and a revised sketch has been uploaded.

Update - on-board graphing facility added to single sweeps as it was too useful to leave out, particularly when tuning antenna lengths for minimum VSWR : a graph gives you an instantly visible trend.

Step 1: Buy Your Stuff

You will need the following items. Most of them can be obtained cheaply from Ebay. The most expensive single item was the box, at close on £10! It might be possible to substitute some items (I used 47 Rs instead of 50 Rs, for example). The diodes were rather unusual (I had to buy 5 off from Italy) and would be worth substituting for more readily available items if you know what you are doing.

  • Arduino Nano
  • DDS module (DDS AD9850 Signal Generator Module HC-SR08 Signal Sine Square Wave 0-40MHz)
  • 1.3" i2c OLED display
  • MCP6002 op-amp (8 pin)
  • 2 off AA143 diode
  • Ceramic capacitors: 2 off 100 nF, 3 off 10 nF
  • 1 uF electrolytic capacitor
  • Resistors: 3 off 50 R, 2 off 10 K, 2 off 100 K, 2 off 5 K, 2 off 648 R
  • 2.54 mm pitch screw terminal blocks: 3 off 2-pin, 2 off 4-pin
  • Single-core hook-up wire
  • 702 or similar hook-up wire
  • Stripboard
  • Square header strip (female) for plugging the Arduino and DDS into - don't buy the round socket stuff by mistake!
  • SO-239 chassis-mount socket
  • Rotary encoder (15 position, 30 detent) with push switch and knob
  • Cheap rotary encoder 'module' (optional)
  • Project box
  • Toggle switch
  • Right-angle mini-usb to USB B bulkhead mount lead (50 cm)
  • PP3 and battery clip / holder
  • Self-adhesive PCB mounting posts / standoffs

You'll also need a soldering iron and electronics tools. A 3D printer and a pillar drill are helpful for the enclosure, although if you wanted you could probably assemble the whole thing on the stripboard and not bother with a box.

Naturally you undertake this work and exploit the results generated at your own risk.

Step 2: Lay Out the Stripboard

Plan out how you are going to arrange the components on the stripboard. You can either do it yourself, referring to K6BEZ's original schematic (which lacks an encoder or screen - see Page 7 of http://www.hamstack.com/hs_projects/antenna_analyzer_docs.pdf), or you can save a load of time and copy my layout.

I do these layouts the simple way, using squared paper and a pencil. Every intersection represents a stripboard hole. The copper tracks go horizontally. A cross represents a broken track (use a 6 mm drill or the proper tool if you have one). Lines of circles with a box round them represent headers. Large boxes with screws denote the connector blocks. Note that in my diagram there is an extra line which runs horizontally through the middle of the board. Leave this out when you are putting it together (it's marked 'omit this line').

Some of the components may appear to be laid out strangely. This is because the design evolved once I'd got the basic hardware working (particularly when I realised that the encoder needed hardware interrupts, for example).

When soldering components onto the board, I use Blu-Tak to hold them in firmly in place while I turn the board over to solder the legs.

I tried to minimise the amount of wire I used by aligning the Arduino and the DDS module and just using the stripboard to connect key pins. I didn't realise at the time that the hardware interrupts needed to read the encoder only work on pins D2 and D3, so I had to move DDS RESET from its original D3 connection with a bit of wire:

DDS RESET - Arduino D7

DDS SDAT - Arduino D4

DDS FQ.UD - Arduino D5

DDS SCLK - Arduino D6

Arduino D2 & D3 are used for the encoder inputs A & B. D11 is used for the encoder switch input. D12 isn't used but I thought I'd make a screw terminal for it anyway, for future expansion.

Arduino A4 & A5 provide the SDA & SCL (I2C) signals for the OLED screen.

Arduino A0 & A1 take the inputs from the VSWR bridge (via the OPAMP).

Step 3: Install the Modules, Attach the Peripherals and Flash the Code

It's worth testing the board before going to the trouble of mounting it into an enclosure. Attach the following components using flexible wire to the board using the screw terminal blocks:

  • 1.3" OLED display (SDA and SCL are connected to Arduino pin A4 and A5 respectively; ground and Vcc go to Arduino GND and +5V, obviously)
  • Rotary encoder (this needs a ground, two signal lines and a switch line - you might need to flip the switch lines round if the encoder works the wrong way - connect these to Arduino ground, D2,D3 & D11 respectively). Note that for my prototyping work I mounted the 15/30 encoder onto a KH-XXX encoder module board, as the pins on the bare encoders are very flimsy. For the final job I soldered wires straight onto the encoder.
  • 9V battery
  • SO-239 socket - solder the centre pin to the antenna signal line and use an M3 ring terminal and screw for the antenna ground

Flash the following sketch onto the Arduino. Also make sure you have included the very good OLED driver library from Oli Kraus, or the complilation will crash and burn : https://github.com/olikraus/u8glib/

If your OLED display is slightly different you may need a different configuration setting in u8glib; this is well documented in Oli's example code.

Step 4: Put It All in a Nice Box (optional)

I seriously considered leaving the analyser as a bare board, as it was only likely to be used occasionally. On reflection though, I thought that if I was doing a lot of work on a single antenna, it might end up getting damaged. So everything went in a box. There's no point going into details about how this was done, as your box will likely be different, but some key features are worth mentioning:

1. Use self-adhesive PCB standoffs for mounting the stripboard. They make life really easy.

2. Use a short USB adaptor lead to bring out the Arduino USB port to the rear of the enclosure. Then it's easy to access the serial port to obtain frequency vs. VSWR data and also to reflash the Arduino without taking the lid off.

3. I developed a custom 3D-printed part to support the OLED display, as I couldn't find anything on the web. This has a recess to allow one to insert a 2 mm piece of acrylic to protect the fragile screen. It can either be mounted using double-sided tape or self tapping screws (with the tabs on either side). Once the display has been fitted, you can use a hot wire (think paperclip and blowlamp) to melt the PLA pins onto the back of the circuit board to secure everything. Here's the STL file for anyone who's interested:

Step 5: Calibration

Originally I didn't do any calibration but discovered that the VSWR meter was consistently reading low. This meant that although an antenna appeared to be okay, my rig's autotuner wasn't able to match to it. This problem arises because the DDS module gives out a very low amplitude signal (about 0.5 Vpp at 3.5 MHz, rolling off as frequency increases). The detector diodes in the VSWR bridge are therefore operating in their non-linear region.

There are two possible fixes for this. The first is to fit an broadband amplifier to the output of the DDS. Potentially suitable devices are available cheaply from China and they will boost the output to about 2 V pp. I have ordered one of these but have yet to try it. My feeling is that even this amplitude will be a bit marginal and some non-linearity will remain. The second method is to put known loads on the output of the existing meter and to record the displayed VSWR at each frequency band. This allows you to construct correction curves for actual versus reported VSWR, which can then be put into the Arduino sketch to apply correction on the fly.

I adopted the second method as it was easy to do. Just get hold of the following resistors: 50, 100, 150 and 200 ohms. On this 50 ohm instrument these will correspond to VSWRs of 1,2,3 and 4 by definition. In the sketch there is a switch 'use_calibration'. Set this to LOW and upload the sketch (which will display a warning on the splash screen). Then carry out measurements at the centre of each frequency band for each resistor. Use a spreadsheet to plot expected versus displayed VSWR. You can then do a logarithmic curve fit for each frequency band, which gives a multiplier and intercept of the form TrueVSWR=m.ln(MeasuredVSWR)+c. These values should be loaded into the swr_results array in the last two columns (see the preceding comment statement in the sketch). This is an odd place to put them but I was in a hurry and as this array stores floats it seemed like a sensible choice at the time. Then put the use_calibration switch back to HIGH, reflash the Arduino and off you go.

Note that when doing the spot frequency measurements, the calibration is applied for the initial choice of band. This won't be updated if you make gross changes in frequency.

Now the meter reads as expected for the fixed loads and seems to make sense when measuring my antennas! I suspect I may not bother trying that broadband amp out when it arrives...

Step 6: Using the Analyser

Attach an antenna via a PL-259 lead and switch the device on. It will display a splash screen then automatically perform a sweep of all the main HF bands. It doesn't do topband or any of the newer bands, but it's an easy matter to extend the sketch to do this. The display shows the frequency under test, the current VSWR reading, the minimum VSWR reading and the frequency at which it occurred. In order to reduce measurement noise, five measurements are taken of VSWR at every frequency point; the mean value of these five readings is then passed through a nine-point moving average filter with respect to frequency before the final value is displayed.

If you want to stop this sweep, just press the encoder knob firmly. The sweep will stop and a summary of all the band data gathered will be displayed. A second press will bring up the main menu. Choices are made by rotating the encoder and then pressing it at the appropriate point. There are three choices in the main menu:

Sweep all bands will restart the sweep of all the main HF bands. When it finishes, it will display the summary screen described above. Write this down or take a photo if you want to keep it.

Sweep single band will allow you to select a single band with the encoder then sweep it. Both the wavelength and frequency range are displayed while making the selection. When the sweep has finished, a second press of the encoder will display a simple VSWR versus frequency graph of the band just swept, with a numerical indication of minimum VSWR and the frequency that it occurred. This is very handy if you want to know whether to shorten or lengthen your dipole arms, as it shows the VSWR trend with frequency; this is lost with the simple numeric report.

Single frequency allows you to choose a single fixed frequency and then continuously updates a live VSWR measurement, for antenna tuning purposes in real time. First select the relevant frequency band; the display will then show the centre frequency of the chosen band and a live VSWR reading. One of the digits of the frequency will be underlined. This can be moved left and right with the encoder. Pressing the encoder emboldens the line; then rotating the encoder will reduce or increase the digit (0-9 with no wrap or carry). Press the encoder again to fix the digit, then go on to the next one. Note that you can access pretty much any frequency across the entire range using this facility - the band selection at the start just helps to get you close to where you probably want to be. When you have finished with this mode, move the underline all the way to the right until it's under 'exit', then press the encoder to return to the main menu.

If you connect your PC to the USB socket on the rear of the analyser (i.e. into the Arduino), you can use the Arduino serial monitor to collect frequency versus VSWR values during any sweep operation (it's currently set to 9600 but you can change that easily by editing my sketch). The values can then be put into a spreadsheet so you can plot graphs etc. If I get time I might build in a simple graphing facility on the analyser itself, although the OLED drivers aren't ideal for this: every time you make a change to the display (e.g. plot a point), a complete screen refresh is needed, so all the results would need to be stored in memory somewhere.

The screenshot shows the VSWR summary for my 7.6 m fishing pole vertical antenna with 9:1 UNUN. My rig can accommodate a 3:1 max SWR with its internal auto-tuner unit. You can see that I will be able to tune it over all bands except 80 m and 17 m. So now I can relax in the knowledge that I've got a passable multi-band antenna and I'm not going to break anything expensive when transmitting on the majority of bands.

Good luck and I hope you find this useful.

3 People Made This Project!

Recommendations

  • Woodworking Contest

    Woodworking Contest
  • Oil Contest

    Oil Contest
  • Clocks Contest

    Clocks Contest
user

We have a be nice policy.
Please be positive and constructive.

Tips

6 Questions

0

Hi to all ! I am still waiting to see the schematic diagram.

Could someone post it please ?

Thanks

iw2fvo@yahoo.com

hi, i found your diagram "well used" and thought i would redraw it before i started building, you are most welcome to use it but please check for errors, i can easily amend it for mods etc at anytime, thanks

0

Good work - you are clearly more patient than me! I said I would do something similar probably a year ago, but never got round to it. So sincere thanks for getting me off the hook! :-)

hi, this may seem a silly q but i cant find a 50r nearest 47 and 648r only 680 will these be ok and will i need to adjust something later, thanks, steve

0

Hi
Yep I'm sure these will be fine. I think I used 47Rs instead of 50Rs. This is not a high precision instrument, after all. Cheers...

Hi, for 1.9 MHz I read: 1.01, 1.22, 1.59, 1,97 instead of: 1, 2, 3, 4.
The instructions in the text above and the comment in the sketch (for swr_results array) maybe are different.
In the sketch I see 4 columns: the first two are empty (0),in the third a value (correction gradient), in the fourth an other value ( correction intercept). Maybe I have to replace 3rd and 4th values? In this case what is the formula for these two values? Thanks

0

Hi Paolo
I only just noticed your questions. You do have to replace the 3rd and 4th values as they appear in the relevant line of the array declaration. These are referred to as columns 2 and 3 in the text because the first column on Arduino IDE is column 0. Sorry for the confusion - I might clarify this. Anyway, it sounds like you sorted it all out in the end. Good work and I hope you find it useful...

1 more answer

0

I tryed and 3rd and 4th columns are ok. I've used logarithmic curve of tendency (calculated by Excel) and all now seems to make sense, It results a little difference (+- 0.10) but all is working. Nice project!!! Thanks

Hi, I'doeing this nice project. Micro USB B (in the list / step 1) or mini USB B. Mine nano has the mini type.

0

Oh yeah - sorry. You need the adaptor to go from the nano to the rear panel, so it's a mini plug. I'll correct the text.
Thanks
dr_phil

Hi, I found a Rotary Encoder KY-040 fro Arduino is ok or I need an other one? I've an Arduino Uno (not nano), can I use this? Thanks

0

Hi PaoloV22
I couldn't get this one (it's on a little PCB, correct?) to work reliably with the existing code, which annoyed me because it was cheap. Currently the code needs a two detent per step encoder, because I borrowed someone else's code to use it. Since then I've worked out how to get a standard encoder to work but haven't bothered changing the code. You should be able to hack it without too much trouble I think.
Cheers,

43 Comments

HF antenna analizer From robert_dima to dr_phil on 02.02.2018, 13:26:23
Hello Dr. Phill ;) can you help me pls with some litle modifications to the firmware of this project... i do not use 60m and 30m bands but i use the 6m band, i'v tried to modify your code but my understanding of code is limited and i did not succede. can you du it for me please. TNX from YO8SHU Robert.
Re: HF antenna analizer From dr_phil to robert_dima on 02.02.2018, 18:13:25
Hi Robert

Remember that the DDS module which generates the test signal isn't specified above 40 MHz (and probably rolls off way below that). If you can find a module that works at 50 MHz and uses the same communication protocol, then modding the firmware is easy. Find the line at the start of the sketch that looks like:

long hfbands [10][4]={
{160,1810000,2000000,64},
{80,3500000,3800000,100}, // wavelength,Fstart,Fstop,nsteps (nsteps chosen for ~3 kHz intervals)
{60,5258500,5406500,50},
{40,7000000,7200000,67},
{30,10100000,10150000,17},
{20,14000000,14350000,117},
{17,18068000,18168000,33},
{15,21000000,21450000,150},
{12,24890000,24990000,33},
{10,28000000,29700000,150} // nsteps for this one should really be 567, but that would take ages!
};

This sets up the array that stores all the frequency ranges for the bands. So perhaps replace one that you don't use (60 or 30) with the appropriate band in meters, start freq, stop freq (both in Hz) and number of steps. It's a piece of cake, as we say over here!

Something like : {6,50000000,52000000,100};
would probably work if you replaced one of the lines you didn't like. Let me know how you get on with the DDS module though. Please send future questions as comments, so everyone can read them and I can share the response.
Good luck
dr_phil

TNX for your response Phil. I have chinese DDS module at witch i have swaped the cheap IC with original TexaxInstrument AD8950. After tests the module can handle stabe output as high as 65mhz so i can use it on 6m band. i did modified the code wright where you told me that i have to, but then the firmware started to behave oddly. Now i have after 6m band one more band named band 0 and the freq shown is 550+mhz :)). and other oditty is that now the software skips 160m and 80m and sometimes 40m band. sometimes is scanning these band but only for about 20 or 30kz

1 reply

Hi Robert - interesting to hear that you've successfully modded a DDS module (have you published?). It's really hard for me to help remotely on this one, particularly without screenshots etc. The best I can suggest is that you attempt an all-band sweep and monitor the serial output. At least you can determine whether it's the display routine or the maths which is not working properly. Let me know how you get on...

Hello,

Very nice project!

Usefull in the ham shack to adjust HF antennas.

73 de Paulo, PY2PH

2 replies

Thanks Paulo. Sounds like you made it? If so I hope you find it useful (and worth the effort of building!).

I have just updated the firmware to include 160 m and 60 m (and all the bands still just about fit onto the OLED display). When I've done the calibration I'll upload V7. Watch this space...

Hi dr_phil,
No, didn´t make it.
Unfortunatelly some parts are a bit difficult to find here in Brazil.
Arduino is ok to find and resistors, capacitors, etc.
But I will beggin my one.
Please let me know if the schematics diagrams are correct to make a PCB for the analyser.
Paulo, PY2PH

Good work and thanks for letting me know! Did you reverse engineer my stripboard layout or do your own from the K6BEZ layout? I'm guessing that the arduino is hidden underneath the copper groundplane?

1 reply
user

I used your and K6BEZ layout to verify before I started wiring it up. Yes, the Arduino mini is carpet taped to the backside. I am now trying to get it mounded in a "field" ready box for Field Day. (by the way it pulls 130 mA - should run all day on a cheap 5V USB power pack). I thoroughly enjoyed your 'instructable', keep up the good work.

Thanks! Though I already have an antenna analyzer (a SARK Mini60 - $100 off eBay fully built with case and rechargeable batteries, works fine!), this looks like an interesting and fun project! (I love Arduino playing!)
.
As fun as they are, Arduinos can get frustrating as upgrades to the IDE, AVR Dude, libraries, etc. can conspire and things may suddenly stop working, or things that worked back when you were developing the project may not work when you want to make another one in the future. Also, many wanting to do these projects may not be experienced with Arduino and so getting up and going for them may be challenging. XLoader can really help there, it simply takes the guess work out of compiling the firmware (i.e. sort it out once and you're good to go from that point on (until you want to change something)).
.
XLoader is great for troubleshooting too - it can narrow the issue down between Arduino code just not being compiled correctly or a hardware issue very quickly.
.
It's great for quickly replicating the project (which in essence is what most visiting this page are wanting to do). When I finish a project I like to archive the Arduino sketch, a copy of the compiled hex file, and a note with all the hardware specs -> it's just much easier to load the hex than deal with making the sketch happy with the most recent development software updates. (always save the sketch though as you may not be able to get the same hardware in the future and may need to adapt the sketch to what is currently available)
.
For the experimenters/developers out there, learning to deal with the Arduino issues is no doubt the best route, but for those just wanting to build a project a specific parts list and hex file would be the easiest route.
.
The broadband amp may fix the need for calibration and it's $10 from US vendors and $5 or so from out of the country vendors, small price to pay, but for the thrifty a calibration routine could be built into the code and the values stored in the eeprom - that would avoid the need to edit the sketch for each individual unit built and thus would make simply loading a static hex file doable.
.
The biggest issue to using a static hex file is probably the display, the hex file is compiled from a sketch that's tailored for specific hardware. OLEDs are cheap these days and very attractive, but aren't standardized and can take some futzing about to find the right library. Developing a version that uses a standard character LCD display could address this though. Though not as attractive, they are still good looking and they are pretty generic and almost all are wired the same (I would avoid I2C - the device address would need to be in the code and the address varies between manufacturers. Standard wiring is cheap and easy to do and avoids code issues). I would suggest a four line, 20 character display as they're cheap and it seems you can never have enough display real estate. Mounting bezels are also available for the character displays, so the need for the 3D printed display mount would be avoided.
.
I already have a ton of projects backed up, but I'm adding this one to the list and ordering parts today! (I'll go cheap and order out of the country since I have a backlog of projects and won't get to it for a bit anyway)
.
I'm looking forward to playing with this!
.
DO give XLoader a try! I think once you use it, you'll see how handy it can be!
.
Also, as you're Arduino playing don't overlook the Teensy micros - more expensive, but more powerful and can do some interesting things (like interface to a PC through the USB port and emulate a keyboard like an Arduino Leonardo, but doesn't require a driver install like a Leonardo does). The Nanos, etc. are cheap, but pretty limited on capability. The most capable Arduino is the Mega. Many avoid the Mega because of it's size, but there's a mini version on eBay that's very small, so if you're project is outgrowing your Nano but you still want a tiny micro, search eBay for "Meduino Mega2560).
.
Take care, 73,
.
Steve, KA0NEB

1 reply

Hi Steve. You make some excellent points. I like the idea of an in-built cal routine (but I have to remind myself all the time that better is the enemy of good enough!). Anyway I've just found out how to extract the hex file and will email you one if you want (if it's not a breach of protocol and I can figure out how to attach stuff!).

I tend to put my projects together with cheap, compact Nanos and other import modules. Once the firmware is finalised I box it up and do nothing except change the battery occasionally. Your point about the OLED is a good one - in the driver file there is a huge range of options and you almost have to guess which display you have. It's worth it though, as these are crystal-clear, bright displays and even the graphing works well - I'm not sure how a classic 'lined' LCD would work. Much of my stuff ends up using every pin so I'm a bit of an I2C fan. This project has quite a few pins left over at the moment.

I'm keen to update this device to measure the magnitude of reactance, so I can plot minimum SWR and reactance null simultaneously. If it's easy it could happen quite quickly. If not, I'll move on to the next project in my brimming in-tray! Watch this space.

Best regards, dr_phil

Do you have a part number for the broadband amplifier?

1 reply

Type "30dB low-noise LNA Broadband Receiver Module RF Wideband Amplifier 0.1-2000MHz" into ebay and you should get a few hits. I couldn't find a part number.

I should stress that I make no recommendation as to the suitability of this device (as mine hasn't arrived yet). I think the problem of detector non-linearity will remain at low return signals. In my opinion the software-based calibration described in the instructable is the easiest and cheapest way to go. It is also fully supported in the sketch (version 6).

You should also post the hex file so others could use XLoader to load the already compiled hex and not have to deal with loading libraries, compiling, etc..
.

http://www.hobbytronics.co.uk/arduino-xloader

1 reply

I'm not familiar with this method of flashing the Arduino; it sounds very sensible for a production-type environment. In this instance I think the user community is best served by compiling from source, so they can calibrate the measurements, understand the code and customise the device if they wish.

Hi,

thanks for the reply on the veru useful analyzer project.

The applicable schematics is the one reported on page 7 of 8 on the follwing link:

https://www.instructables.com/you/backtalk/?action=reply&commentId=CSGLCWEJ0IEBCSC.

Is it correct ?

Where do I have to connect the encoder( 2 pins ) , the encoder push_button (1pin ) and the Oled_display (2 pins ) please ?

Does your program .ino send data to the LCD and to the USB for PC diplaying please ?

Thanks for the assistance.

iw2fvo,

Ambrogio

1 reply

Hi Ambroigo,

I've put additional information on Steps 2 & 3 which shows where to connect the screen and encoder to the Arduino. D2, D3, A4 & A5 must not be changed (because they provide hardware interrupts & I2C support). The other digital pins to interface with the DDS etc. are optional and can be changed in the sketch.

The sketch (.ino) automatically interfaces with the OLED and encoder. When performing a single or multi-band scan, frequency and VSWR values are sent out of the serial port on the back of the unit. The easiest way to get these is to connect up your USB Arduino Uno-style programming lead and start up a 9600 baud serial monitor via the Arduino IDE. Then copy and paste the results into a spreadsheet.

sorry there is a correction about the link:

http://www.hamstack.com/hs_projects/antenna_analyzer_docs.pdf

Bye

I will like to build up this good project soon.

Could you please post the schematics diagram ?

My e_mail is: iw2fvo@yahoo.com

Thanks

Regards

Could any body help me in sending the schematics diagram please ?

2 replies

Hi. You can find the schematic for the basic VSWR capability via the link on Step 3. Look on Page 7. This doesn't include the encoder and the screen.

I didn't expect this project to create such interest so I will have a look at creating a comprehensive schematic for the whole system. It will take a little while though...

er, sorry - Step 2!

Very nice job! I've been facing difficulties to compare your job to K6BEZ's. Mainly with respect of I2C and rotary encoder. Can't you show how you have connected them? I'm a beginner with Arduino.