Working on Pete's Simpleceiver + I need to build another VFO BFO. The SI5351 based boards have been my favorite for several years now. I have several different versions of boards that I have tried, but prefer the small module from Adafruit. It is very small, and comes built for around $8 plus shipping. One of the things I like about it is that the clock outputs are brought out to a header along with the SMA connectors. I have used this board in several projects and have designed different boards for each one. With this I plan on designing a board that can be used with many different projects.
The design considerations are, board size around 2" x 2",
Arduino Nano, rotary encoder, TFT display, a connector for the Adafruit SI5351 board. After an initial design and exchanging several e-mails with Pete I have expanded it to also provide a connector for a small I2C OLED display. Because there are several pinouts for these displays, some will plug in directly to the connector others will have to use a connector cable to the display. This connector could also be used to connect to a I2C version of a 1x16 or 2x16 line LCD display. With the correct software drivers you could use one of these LCD displays, a small OLED display, a 128x128 or 128x160 TFT display, or even a monochrome Nokia display. I also added a connector that brings the rotary encoder connections out to a separate connector so you can use either the bare encoder mounted on board, or one of the pre-wired encoder boards. I have not tried but you could probably use an optical encoder through this connector.
One thing I added was provisions for a voltage divider that can be used to measure input voltage if the board is used in a battery powered project. Finally I decided to bring some of the unused Arduino pins out to an auxiliary connector for use in other projects.
Since the board layout is similar to several others I have done, I was able to modify one of them fairly quickly. I did the board as a single sided board that can easily be made using the "toner transfer" method. Although I usually etch my own boards, in this case I decided to order some from one of the inexpensive Chinese board houses. If they turn out well, I will follow Pete's suggestion and make some available at a reasonable cost for those who are working on the Simpleceiver or other project that needs a VFO-BFO. I think I will start with one of these boards as the basis of a simple signal generator for routine use. This should be a easy way to test the different video drivers needed for the different display options available.
I ordered the boards on Sept 9 with DHL express delivery, and was pleasantly surprised when I received them on the 13th. I quickly wired one of them up to see how they will work. Changing some of my other sketches to reflect the correct pin configuration I tried the board with a small OLED display and a 128x128 TFT display. After getting a working display with each, I was sure that the board worked correctly.
I also took a picture of the Adafruit SI5351 board mounted on the back. Depending on how the header pins are installed in the board, it can also be flipped to have the edge with the SMA connectors extending past the board edge. I planned on the Nano and SI5351 board to be soldered to the board, but they could be socketed if you do not need to keep everything really compact. As it is with everything soldered the package with the OLED or 128x128 TFT is about 2"x 2"x 1". This should be small enough to fit in most project packages. Now to write some software to fully test each of these configurations
9/15/17
I had some time today, so I took Pete's Simpleceiver Plus DCR sketch and modified it to reflect the changes in the pin assignments on the new board. And after I had it working with the 160x128 TFT display I modified that to reflect the 128x128 display. There are several different versions of the 128x128 display that use different driver chips, so I had to also change the driver library and initialization code. With a little tweaking on position on the display I was able to get a very similar looking display screen. I had taken all of the additional code in the sketch that reflects U/L side band selection and several other things that Pete has in his code to make it more modular in design. When I get around to going to a superhet and then transceiver, these can be added in as separate .ino files in the main sketch directory. That way it should be possible that no other changes in the additional .ino files should be necessary whatever display you are using. Here are a couple pictures of the two displays. Hope to get around to writing some code for a couple other display types this weekend.
 |
| 128 x 128 display Rotary encoder on board |
 |
| 160 x 128 display External rotary encoder |
I spent a little over an hour this evening modifying one of the earlier sketches to support a small 0.96" OLED display. Most of that time was trying to fit everything on the screen, and make it look nice. It is much easier to work with a screen that has more real estate to work with. This is listed as a two color display, but all pixels are either white or black, the color comes from two different colored parts of the screen. In an earlier project, I used the smaller color area to put current settings.
One thing to be very careful about when using these small OLED displays is that looking at some of the pinouts for ones for sale on ebay, is that some have the VCC and GND pins reversed.
SO BE VERY CAREFUL and check before just plugging it in the socket. I still have one of the monochrome Nokia displays around, but with the problem I had trying to fit everything on the screen, I don't know if I will bother porting the code for that configuration.
Now that I know the boards work for multiple display types, I have decided that I will offer them for sale. Because of Pete's urging, I ordered 50 of them to start with. For now I only plan on shipping to US locations, but am working on getting the board layout as a shared project at the Chinese board house I used. This should make it easier for DX locations to order them directly. I had checked at oshpark.com, but the board size made them rather expensive. The board is single sided, so fairly easy to make with the "toner transfer method" if you want to make your own. I will have the "toner transfer" image along with other documentation at
https://www.dropbox.com/sh/2omkppe36797l15/AAD8BIuDPMa_-y6JxPI3XTHJa?dl=0
This dropbox will also have the Arduino sketches to use as a guide in using the board with different types of display. They are very rough right now, I just did enough work on them to get the display and rotary encoder to work correctly. I will be doing a lot of work as I progress with the Simpleceiver project and see what Pete has in store for us.
I am offering them at $5 each or $7.50 for two including shipping. If you are interested email me at duwayne@kv4qb.us and I will give put you on the list.
9/17/17
I have just uploaded the files for this board to the supplier I used to their shared projects area. You can download the gerber files from there or order directly. I have placed several orders with this supplier, and have been very happy with the results. Their pricing is very reasonable, and they offer several different shipping options that can be very reasonable. This will be the most economical way for DX builders to purchase boards. The project is at
https://www.pcbway.com/project/shareproject/W42368ASJ5_W42368ASJ4_si5351_vfo_bfo.html
And yes I do get a commission from boards sold. So if two people buy sets of 5 boards I save enough on my next order that I can stop at McDonalds and get a cup of coffee when it is on sale.
Finished up the modifications to Pete's Simpleceiver sketch for use with my PCB. I combined the direct conversion and super-het versions into one. There is a single flag variable dcr_mode that you can change to go from one to the other. I have it just before the start of the setup area in the sketch to make it easy to find. I have it tested as much as I can without having the complete hardware. Pete plans on building up one of the boards I sent him, and giving the software a test run. It is located in the folder Simpleceiver_Plus_DCR_SSB_160x128 at the dropbox link
11/15/17
Just got a e-mail from Nigel KG4ARS with a picture of his project using a 2 x 16 line display. Looking great !
Very nice DuWayne, I would be interested in one when it's offical.
ReplyDeleteDavid
KG7WFM
very nice ,also i want 2 pcb but pls tell me the price for shipping to Croatia,thanks in advance.
ReplyDeleteI decided to only ship to US locations, but in the latest update I have a link to the supplier I used. Boards can be ordered directly from them, and will be the cheapest way for non US builders to get boards
ReplyDeleteok thanks ,i m waiting ;)
ReplyDeleteHi Mike,
Deletedid you already order the PCB to Europe from PCBWAY.COM ?
72/3`s de sTef DM5TU / VY1QRP
Hi DuWayne, my name is sTef DM5TU / VY1QRP.
ReplyDeleteI was trying to compile the arduino sketch. The following errors are reported by my Arduino IDE 1.6.11 . Do you see any chance to give me a hint where to look at or what to do to get is solved. It is somewhere in the rotary section.... Tnx es 72/3 de sTef DM5TU
"----
C:\Users\DM5TU\AppData\Local\Temp\build8498a2cd1db95c79b63900dee4cf847f.tmp\libraries\Rotary-master\Rotary.cpp.o (symbol from plugin): In function `Rotary::Rotary(char, char)':
(.text+0x0): multiple definition of `Rotary::Rotary(char, char)'
C:\Users\DM5TU\AppData\Local\Temp\build8498a2cd1db95c79b63900dee4cf847f.tmp\sketch\Rotary.cpp.o (symbol from plugin):(.text+0x0): first defined here
C:\Users\DM5TU\AppData\Local\Temp\build8498a2cd1db95c79b63900dee4cf847f.tmp\libraries\Rotary-master\Rotary.cpp.o (symbol from plugin): In function `Rotary::Rotary(char, char)':
(.text+0x0): multiple definition of `Rotary::Rotary(char, char)'
C:\Users\DM5TU\AppData\Local\Temp\build8498a2cd1db95c79b63900dee4cf847f.tmp\sketch\Rotary.cpp.o (symbol from plugin):(.text+0x0): first defined here
C:\Users\DM5TU\AppData\Local\Temp\build8498a2cd1db95c79b63900dee4cf847f.tmp\libraries\Rotary-master\Rotary.cpp.o (symbol from plugin): In function `Rotary::Rotary(char, char)':
(.text+0x0): multiple definition of `Rotary::process()'
C:\Users\DM5TU\AppData\Local\Temp\build8498a2cd1db95c79b63900dee4cf847f.tmp\sketch\Rotary.cpp.o (symbol from plugin):(.text+0x0): first defined here
collect2.exe: error: ld returned 1 exit status
Bibliothek Rotary-master im Ordner: C:\Program Files (x86)\Arduino\libraries\Rotary-master (legacy) wird verwendet
Bibliothek SPI in Version 1.0 im Ordner: C:\Program Files (x86)\Arduino\hardware\arduino\avr\libraries\SPI wird verwendet
Bibliothek Adafruit-GFX-Library-master in Version 1.1.9 im Ordner: C:\Users\DM5TU\Documents\AFU und QRP\Arduino Projects\Projects\libraries\Adafruit-GFX-Library-master wird verwendet
Bibliothek Adafruit-ST7735-Library-master in Version 1.0.8 im Ordner: C:\Users\DM5TU\Documents\AFU und QRP\Arduino Projects\Projects\libraries\Adafruit-ST7735-Library-master wird verwendet
Bibliothek toneAC im Ordner: C:\Users\DM5TU\Documents\AFU und QRP\Arduino Projects\Projects\libraries\toneAC (legacy) wird verwendet
Bibliothek Wire in Version 1.0 im Ordner: C:\Program Files (x86)\Arduino\hardware\arduino\avr\libraries\Wire wird verwendet
exit status 1
Fehler beim Kompilieren für das Board Arduino Nano.
Looks like you probably have a different version of the Rotary library. I have a copy of the correct one in a dropbox folder at https://www.dropbox.com/sh/kw7c14euqqi28pn/AABc384tePRDZBoqo6s4YDCRa?dl=0 I will update the sketches with links to the correct library locations.
ReplyDeleteTnx fer your Link DuWayne. I am sorry to report the following error while using the advised rotary.zip file. All files (Rotary.ccp rotary.h Si5351.ccp and SI5351.h - these ones used from Pete`s blog) are in the same folder with the sketch. I tried the Simpleceiver VFO sketch as well as the SNA JR Sketch with my Arduino IDE 1.11.6. Here is the error report. Looks still the same. The Simpleceiver sketch from Pete (N6QW) is running well with his rotary and SI5351 files. Did someone else report problems?
ReplyDelete72/3`s sTef DM5TU
"------
ReplyDeleteLinking everything together...
"C:\Program Files (x86)\Arduino\hardware\tools\avr/bin/avr-gcc" -w -Os -flto -fuse-linker-plugin -Wl,--gc-sections -mmcu=atmega328p -o "C:\Users\DM5TU\AppData\Local\Temp\build1c1e57b0e1e27625cc05e7aac20428dd.tmp/sna-jr128X160-v2.ino.ino.elf" "C:\Users\DM5TU\AppData\Local\Temp\build1c1e57b0e1e27625cc05e7aac20428dd.tmp\sketch\rotary.cpp.o" "C:\Users\DM5TU\AppData\Local\Temp\build1c1e57b0e1e27625cc05e7aac20428dd.tmp\sketch\si5351.cpp.o" "C:\Users\DM5TU\AppData\Local\Temp\build1c1e57b0e1e27625cc05e7aac20428dd.tmp\sketch\sna-jr128X160-v2.ino.ino.cpp.o" "C:\Users\DM5TU\AppData\Local\Temp\build1c1e57b0e1e27625cc05e7aac20428dd.tmp\libraries\SPI\SPI.cpp.o" "C:\Users\DM5TU\AppData\Local\Temp\build1c1e57b0e1e27625cc05e7aac20428dd.tmp\libraries\Rotary\rotary.cpp.o" "C:\Users\DM5TU\AppData\Local\Temp\build1c1e57b0e1e27625cc05e7aac20428dd.tmp\libraries\Adafruit-GFX-Library-master\glcdfont.c.o" "C:\Users\DM5TU\AppData\Local\Temp\build1c1e57b0e1e27625cc05e7aac20428dd.tmp\libraries\Adafruit-GFX-Library-master\Adafruit_GFX.cpp.o" "C:\Users\DM5TU\AppData\Local\Temp\build1c1e57b0e1e27625cc05e7aac20428dd.tmp\libraries\Adafruit-ST7735-Library-master\Adafruit_ST7735.cpp.o" "C:\Users\DM5TU\AppData\Local\Temp\build1c1e57b0e1e27625cc05e7aac20428dd.tmp\libraries\Wire\Wire.cpp.o" "C:\Users\DM5TU\AppData\Local\Temp\build1c1e57b0e1e27625cc05e7aac20428dd.tmp\libraries\Wire\utility\twi.c.o" "C:\Users\DM5TU\AppData\Local\Temp\build1c1e57b0e1e27625cc05e7aac20428dd.tmp/core\core.a" "-LC:\Users\DM5TU\AppData\Local\Temp\build1c1e57b0e1e27625cc05e7aac20428dd.tmp" -lm
C:\Users\DM5TU\AppData\Local\Temp\build1c1e57b0e1e27625cc05e7aac20428dd.tmp\libraries\Rotary\rotary.cpp.o (symbol from plugin): In function `Rotary::Rotary(char, char)':
(.text+0x0): multiple definition of `Rotary::Rotary(char, char)'
C:\Users\DM5TU\AppData\Local\Temp\build1c1e57b0e1e27625cc05e7aac20428dd.tmp\sketch\rotary.cpp.o (symbol from plugin):(.text+0x0): first defined here
C:\Users\DM5TU\AppData\Local\Temp\build1c1e57b0e1e27625cc05e7aac20428dd.tmp\libraries\Rotary\rotary.cpp.o (symbol from plugin): In function `Rotary::Rotary(char, char)':
(.text+0x0): multiple definition of `Rotary::Rotary(char, char)'
C:\Users\DM5TU\AppData\Local\Temp\build1c1e57b0e1e27625cc05e7aac20428dd.tmp\sketch\rotary.cpp.o (symbol from plugin):(.text+0x0): first defined here
C:\Users\DM5TU\AppData\Local\Temp\build1c1e57b0e1e27625cc05e7aac20428dd.tmp\libraries\Rotary\rotary.cpp.o (symbol from plugin): In function `Rotary::Rotary(char, char)':
(.text+0x0): multiple definition of `Rotary::process()'
C:\Users\DM5TU\AppData\Local\Temp\build1c1e57b0e1e27625cc05e7aac20428dd.tmp\sketch\rotary.cpp.o (symbol from plugin):(.text+0x0): first defined here
collect2.exe: error: ld returned 1 exit status
Bibliothek SPI in Version 1.0 im Ordner: C:\Program Files (x86)\Arduino\hardware\arduino\avr\libraries\SPI wird verwendet
Bibliothek Rotary im Ordner: C:\Program Files (x86)\Arduino\libraries\Rotary (legacy) wird verwendet
Bibliothek Adafruit-GFX-Library-master in Version 1.1.9 im Ordner: C:\Users\DM5TU\Documents\AFU und QRP\Arduino Projects\Projects\libraries\Adafruit-GFX-Library-master wird verwendet
Bibliothek Adafruit-ST7735-Library-master in Version 1.0.8 im Ordner: C:\Users\DM5TU\Documents\AFU und QRP\Arduino Projects\Projects\libraries\Adafruit-ST7735-Library-master wird verwendet
Bibliothek Wire in Version 1.0 im Ordner: C:\Program Files (x86)\Arduino\hardware\arduino\avr\libraries\Wire wird verwendet
exit status 1
Fehler beim Kompilieren für das Board Arduino/Genuino Uno.
----"
One of the error messages seems to indicate that you have the rotary files in two places, and has found multiple files with the same name. If you have the rotary files in your sketch folder, try changing the include from include to include "Rotary.h>" That will tell the compiler to look in the sketch folder for the files instead of in the default library folder.
Deletequick correction the modified include should be #include "Rotary.h"
Deleteby the way... I totally accept your "BEER-WARE LICENSE" .... :-)
ReplyDeleteThis comment has been removed by the author.
ReplyDeleteThis comment has been removed by the author.
ReplyDeleteYou are so right!! I found it out too, but why. is it because the rotary files are in the same folder as the sketch itself?
ReplyDeleteThis was a real learning. Thanks DuWayne. It even helped me with some other Arduino issues. I now have to change my wiring from Pete`s to your sketch. Great stuff. Keep you updated. Its already late over here across the pond. Location is 1 hr south of Erfurt. Cheers sTef DM5TU
ReplyDeleteDo you inform Pete about the changes in the sketch concerning the #include rotary section () into ("/") ? He is also promoting to put the rotary files in the same folder as the sketch. Maybe some other hams run into the same topic. I dont know.
ReplyDeleteLast changes to be made.. so that the display is running, too:
ReplyDelete#define __CS 5 (should be 10)
#define __DC 7 (should be 9)
#define __RST 6 (should be 8)
These were inconsistent with the PIN definitions in the header section on the sketch... I hope I am doing right with this. Now the display is running.
I am waiting for my pcb from your gerber files being homemade by DH4YM... TNX es 72/3`s de sTef DM5TU / VY1QRP
Some of the errors look like you already had a different version of the rotary files in your default library folder. using the #include tells the compiler to first look in that folder to compile them. After that is done the comipiler compiles all the files in your sketch folder. That caused the errors with multiple definitions. By telling the comipiler to use the "filename" path it ignores the default library folder and just looks in the sketch folder. I think that if you do not have matching filename files in the library folder it will just use what it finds in the sketch folder. Problems with duplicate named libraries has been the biggest problem I have ran into when helping others with my sketches. Have a good evening in Kaulsdorf, I spent about 3 years in Karlsruhe in the 1970's my call there was DA1SC
ReplyDeletegOOd Morning DuWayne,
ReplyDeleteI now have 2 PCB`s on my workbench. TNX to Joh, in Freiburg for a suprise HAMSPIRIT letter containing a proto board. :-) DuWayne, I am relativley new to SMD. The spacing you used in your gerber file does that refer to SMD size 1206? As I am in the process of ordering the parts I just want to confirm that with you once again. Thanks for your feedback. 72/3`s de sTef DM5TU / VY1QRP
The board layout is for 1206, but 805 will fit as well. You could even use through hole capacitors with .1" lead spacing. For the resistors 1/4 watt bent in a hairpin shape will also fit.
ReplyDeleteThank you, DuWayne. Parts are ordered in size 1206. I need to practice SMD soldering. Did some soldering yesterday. To all newcomers to SMD/SMT soldering here is my hint. Read here: http://www.applied-mathematics.net/robotics/SMT-GuideV1-3.pdf Have fun and melt some solder.... 72/3`de sTef DM5TU / VY1QRP
ReplyDeleteGood Morning DuWayne,
ReplyDeleteI am on the move of completing the first PCB. I am just putting the SMD parts on the board. One question is rising about where to power up the board. I see the the marking 9-12 V (JP1) on the board but you are pointing out that the Rs 4k7 and 1k are optional for the battery read out. My thought was that I could power the board via JP1 from 9-12V. Please give me your advise how to power the board without burning it up in smoke. THANKS es 72/3`s de sTef DM5TU /VY1QRP
Power is applied at JP1. Anything from about 7 to 12 volts will be OK. I don't like to put more than 12 volts on the Arduino, its regulator gets quite warm above that. The board was designed so it could be used with batteries, or used in a line operated system. If it is powered by batteries, you can use the optional voltage divider to measure the battery level. If it is line operated, you do not need to add them to the circuit.
ReplyDeleteThanks DuWayne... Big time. We had to make some minor changes in the sketch concerning the PIN numbers. Over all a great project. More boards are ordered from China. Lets see. 72/3 de sTef DM5TU/VY1QRP
ReplyDeleteHi Wayne, its me again.
ReplyDeleteI have a question about some changes I need to make to your sketch and I do not get it done.
For my NorCal40a build I am planning to put in the DDS VFO.
As I am using a front panel encoder I have to use the encoder interface you put on your board. So far so good. I have all working but not thr use of PIN 4 (D3) encoder interface. My encoder SW uses A3 for the push switch.
This I do not get changed in your sketch.
Please tell me, what do I have to do to make the change because I would like to use the encoder interface 100%.
Thanks for your time, thoughts and help. 72 de sTef from your old "Base" arcoss the pond.
In the sketch find the definitions for the encoder pins
Delete// used by rotary encoder
#define ENCODER_B 2 // Encoder pin A
#define ENCODER_A 3 // Encoder pin B
#define ENCODER_BTN 4 // Emcoder push buttom
And then change the #define ENCODER_BTN 4 to
#define ENCODER_BTN A3 or whatever pin you are using.
This comment has been removed by the author.
DeleteIt was more than that.
ReplyDeleteI needed to dig in deeper into the sketch.
Your advise is normally not an issue for me.
And with this change I had no succsess. When I do the software change the encoder switch does not respond when connecting the cable to PIN 3 (advised the ENCODER_BTN to D4 (with 4)).
Even with the build on encoder that leads to no more functinal switch..
Seems like it stays advised to PIN A3.
So a deeper look into the sketch I found that part.
---------
}
buttonstate = digitalRead(A3);
if(buttonstate == LOW) {
---------------
Yes, when I here change (A3) to (4) than it works... Whitout this no chance.
Thanks for keep me going back into it to have a more deeper look at the software.
Any thoughts on that, DuWayne? If not OK. 72 de sTef DM5TU
Can you tell me which sketch you are using. I looked at all the ones I put in the dropbox folder and could not find where A3 was used. That was in Pete's original sketch and all references to A3 have been commented out or changed to reference the defined ENCODER_BTN.
ReplyDeleteGuten Abend DuWayne,
ReplyDeleteI emailed the sketch. Yes it is an original N6QW one.
72s sTef DM5TU
I am am getting a compiler function call error. Has the group seen this before and know how to fix? I am running Arduino IDE 1.8.5.
ReplyDelete-Michael KB4JHU
C:\Users\MIchael\Documents\Arduino\Simpleceiver_Plus_DCR_OLED\Simpleceiver_Plus_DCR_OLED.ino: In function 'void setup()':
Simpleceiver_Plus_DCR_OLED:171: error: no matching function for call to 'Si5351::init(int)'
si5351.init(SI5351_CRYSTAL_LOAD_8PF);
^
C:\Users\MIchael\Documents\Arduino\Simpleceiver_Plus_DCR_OLED\Simpleceiver_Plus_DCR_OLED.ino:171:38: note: candidate is:
In file included from C:\Users\MIchael\Documents\Arduino\Simpleceiver_Plus_DCR_OLED\Simpleceiver_Plus_DCR_OLED.ino:73:0:
C:\Users\MIchael\Documents\Arduino\libraries\Si5351Arduino/si5351.h:283:7: note: void Si5351::init(uint8_t, uint32_t, int32_t)
void init(uint8_t, uint32_t, int32_t);
^
C:\Users\MIchael\Documents\Arduino\libraries\Si5351Arduino/si5351.h:283:7: note: candidate expects 3 arguments, 1 provided
Simpleceiver_Plus_DCR_OLED:174: error: no matching function for call to 'Si5351::set_freq(int_fast32_t&, long long unsigned int, si5351_clock)'
si5351.set_freq(rx , SI5351_PLL_FIXED, SI5351_CLK0);
^
Michael, could you post the whole sketch or mail it to me? Maybe DuWayne teached me enough to help you out on that issue.
ReplyDelete72 de sTef DM5TU
Michael, did you put the SI5351.cpp / SI5351.h /ROTARY.CPP and the ROTARY.h files in the same folder as the main sketch?
ReplyDeleteI put them in the library. Let me move them to mail sketch area. tnx.
DeleteTef, I noted that Adafruit_SI5351 had teh Si5351 files called: Adafruit_SI5351.cpp and Adafruit_SI5351.h
DeleteShould I rename them to si5351.cpp and si5351.h ??
If you use the sketch of DuWayne, maybe it is better that you use Pets`s N6QW SI5351 and ROTRAY files. You find them here: http://www.n6qw.com/Simpleceiver_Plus.html They work well with DuWaynes main sketch.
DeleteEvery sketch gets its own folder by default when you start that sketch for the first time on your system.
ReplyDeletePut the rotray.h / .cpp and si5351.h / .cpp files in this specific sketch folder.... Enjoy and let me know when its running.... 72
Hum... strange error now..
DeleteSimpleceiver_Plus_DCR_OLED:75: error: 'Si5351' does not name a type
Si5351 si5351;
^
C:\Users\MIchael\Documents\Arduino\Simpleceiver_Plus_DCR_OLED\Simpleceiver_Plus_DCR_OLED.ino: In function 'void setup()':
Simpleceiver_Plus_DCR_OLED:171: error: 'si5351' was not declared in this scope
si5351.init(SI5351_CRYSTAL_LOAD_8PF);
^
C:\Users\MIchael\Documents\Arduino\Simpleceiver_Plus_DCR_OLED\Simpleceiver_Plus_DCR_OLED.ino: In function 'void loop()':
Simpleceiver_Plus_DCR_OLED:287: error: 'si5351' was not declared in this scope
si5351.set_freq(rx , SI5351_PLL_FIXED, VFO_CLK);
^
exit status 1
'Si5351' does not name a type
I did run the Adafruit example and it did program the Si5351. So the arduino and the Si5351 is working. Now just getting the code to work that DuWayne wrote.
DeleteThis comment has been removed by the author.
DeleteVersion 2 update. Will require changes to the .ino for the Si5351.
DeleteChanges from v1 to v2
The public interface to the v2 library is similar to the v1 library, but a few of the most-used methods have had their signatures changed, so your old programs won't compile right out-of-the-box after a library upgrade. Most importantly, the init() and set_freq() methods are different, so you'll at least need to change these calls in your old sketches.
The init() method now has three parameters: the crystal load capacitance, the reference frequency, and the frequency correction value (with this last parameter being a new addition). You'll need to add that third parameter to your old init() calls, but then you can delete any set_correction() calls after that (unless you explicitly are changing the frequency correction after the initialization).
The set_freq() method is now more streamlined and only requires two parameters: the desired output frequency (from 4 kHz to 225 MHz) and clock output. In your old code, you can delete the 2nd parameter in set_freq(), which was the PLL frequency. In case you want to do things manually, there is now a new method called set_freq_manual() (see below for details).
Those two changes should cover nearly all upgrade scenarios, unless you were doing some lower-level use of the Si5351.
DuWayne - Thank you for offering the Simpleceiver+ project.
DeletesTef DM5TU - for outstanding support and sending me the library files. Without your help I would have not figure this out. 1000 Thanks for your support!
Note: The board I got from FDIM (Four Days In May) Dayton Hemvention last week - the silkscreen of the Arduino Nano is backwards. Don't follow the silkscreen. Best way is to check the schematics and verify power before powering it all up.
73
- Michael KB4JHU QRP Operator
You have mail...
ReplyDeleteCan someone please point me to the latest sketch of the Simpleceiver with the OLED display. I have the one with the TFT display and want to try both versions. Thanks, Jack
ReplyDelete