Steve?

Thanks! ?Brain is a little foggy today or would have pounded on the code to do my own testing.?

BTW: ?for you Nextion users out there, commenting out the tiny software serial library is not an option. CEC uses a couple of the digital pins (believe d8 and d9) for serial connection to the Nextion since the normal nano uart is locked to the usb connection. The solution is to convert to the real software serial library and that is not as easy as Dr Lee suggested in the comments in the tinysoftwareserial.cpp file….?

So although I am hope to be proved wrong, trying to replace a nano with a nano every is far from a drop in replacement if you are using Nextion.?

73
Mark
AJ6CU

Hi

i have been porting KD8CEC to non-nano platforms and rewriting the uBITX memory manager. Although definitely a “work in progress” it I had reached a pretty functional level. This work is hosted at gitgub.com.?

My initial hardware targets were the next gen Arduino Nanos including Nano Every, Nano IOT, Nano BLE and Nano RP Connect (raspberry pi pico in an Arduino nano package) Thought they would be the easiest targets.?

But in doing these ports, I suspect supporting other hardware should be trivial. For example, although never put into an uBITX, it compiles cleanly for teensy 4.0. I suspect that it would also run on real Raspberry Pi Picos with only a little work.?

so was planning on adding the teensy and pico when I do my next board spin. Any other suggestions?

73
Mark
AJ6CU

开云体育

Mark - sorry, I have not used the memory manager.

Steve,

Tried your suggestions, but ran into other compile issues.? More curiosity than anything else. So if you could, can you let me know whether you have successfully used the uBITX Memory Manager??

73
Mark
AJ6CU

Thanks for the information regarding how to fix my sBitx. I'm still puzzled as to why TX oscillations would have caused this, as I have yet to transmit through the radio! It looks like I will have to perform a major strip-down and component-level repair to get it working again - a bit of a disappointment for something I've hardly used, and only had for a few weeks, but I suppose that's what you get being an 'early adopter'. I'll wait to see what HF Signals come up with to fix these issues. Fingers crossed.

Regards,

Ian
G4ZJH.

--
Jack, W8TEE

--
Jack, W8TEE

开云体育

Working !!!!??? Hooray
Thank you

73
ZS5GI

Steve,

Just one more thing, you are talking about the original CEC v1.2 code (the directory is uBTIX 2.0 so that can cause confusion...)? Just wanted to make sure you were *not* running my modified CEC code that I am working on to support non-Nano platforms (with external I2C EEPROM chips)

73
Mark
AJ6CU

Steve,

CEC stores a lot of stuff in EEPROM > 256.? For example call sign, custom named freq, cw messages, wspr, CW ADC settings, band frequencies, CW key type, tuning steps, CW CAL, etc.? CEC does make reasonable defaults here on boot if it finds "0' (assume that is what happens when you try to access eeprom that doesnt exist, I don't recall seeing CEC checking for errors on EEPROM fetches). But if you are not in Region 2, that would be a problem...

Have you tried using uBITX Memory Manager? It does a fetch of the 1024 EEPROM when you load from uBITX and gets upset if it doesnt get all the bytes. But again perhaps the lack of error checking is playing in our favor and you just get a lot of 0's.But anything that is normally saved in that >256 area should not be...

Appreciate the insights here!?

73
Mark
AJ6CU

开云体育

Hi Mark

Thank you for your responce
I have uncommented the selected the "Recommended for Nextion, TJC LCD 88%"
The sketch now compiles :)

I will upload to the Ardunio nano and test and let you know how it goes

73
Gary
ZS5GI

The Nano Every only has 256 bytes of eeprom.? I believe that KD8CEC assumes a Nano that has 1024 bytes.

Can someone confirm that you can really run KD8CEC on a Nano Every? I never tried it because of that EEPROM issue. I will give it a try later, willing to be surprised here....

73
Mark
AJ6CU

Gary,

Look in ubitx.h and search for "Recommended for Nextion, TJC LCD 88%"? Make sure that set of defines is uncommented and any other sets are commented out.? ?You can also look at the individuals setting and commend some out (the size occupied by each option is in a comment on right.? ?"1" means enabled, "0" means disabled.

Another option is to go search youtube for "expanding nano flash" or something similar. If you update to the latest bootloader and do the expansion, your nano will have some 32k memory.? But i am pretty sure the issue is that the srouce code doesn't naturally assume a nextion screen and you need to adjust the defines.

73
Mark
AJ6CU

开云体育

Be aware of one minor difference with the Every - the ADC reference default mode is different between the Every and the Nano. With the way the uBitx radios handle reading the keyer line when sending CW, this can trip you up.

The Nano Every? is one way out. 48K and faster!.? I have a few on order.

Most of the time for this stuff?I'd start with checking the code for bulky
libraries and fluff.? I've managed in the past to easily remove excess
code or refactor it so it compiles far more compactly.

Allison
------------------
Please use the forum, offline and private will go to bit bucket.

Hi Art,

The SSB inversion is often due to a BFO on the wrong side of the SSB filter.? To correct you should adjust the BFO to be closer to 11.056MHz.? The SSB filter center is close to 11.058MHz and can vary for each filter.? These values are for the v5 and v6 uBitx built with 11.059 crystals for the SSB filter.

I would suggest that you use the Memory Manager software to save the current values.

73
Evan
AC9TU

开云体育