|
Re: Mike Black W9MDB SK
Hello Rick,
?
There are two versions of the Nano's boot loader: one for original miniUSB-connected devices and the other for USB-C devices. This is a generalization, so there can be exceptions.
?
The secret is to change the processor in the tools menu:
?
?
If one does not work, try the other.? All of the USB-C Nanos use the ATmega328 processor.
?
The other potential issue is the size of the bootloader file.? If the KD8CEC program will not fit, some options are selected in the ubitx.h file:
?
//==============================================================================
// User Select feather list
//==============================================================================
/*
//Enable all features
#define FN_BAND ? ? ? ? 1 //592
#define FN_VFO_TOGGLE ? 1 //78
#define FN_MODE ? ? ? ? 1 //20
#define FN_RIT ? ? ? ? ?1 //58
#define FN_SPLIT ? ? ? ?1 //62
#define FN_IFSHIFT ? ? ?1 //238
#define FN_ATT ? ? ? ? ?1 //128
#define FN_CW_SPEED ? ? 1 //152
#define FN_VFOTOMEM ? ? 1 //254
#define FN_MEMTOVFO ? ? 1 //188
#define FN_MEMORYKEYER ?1 //156
#define FN_WSPR ? ? ? ? 1 //1044
#define FN_SDRMODE ? ? ?1 //68
#define FN_CALIBRATION ?1 //666
#define FN_CARRIER ? ? ?1 //382
#define FN_CWCARRIER ? ?1 //346
#define FN_CWTONE ? ? ? 1 //148
#define FN_CWDELAY ? ? ?1 //98
#define FN_TXCWDELAY ? ?1 //94
#define FN_KEYTYPE ? ? ?1 //168
#define FN_ADCMONITOR ? 1 //516
#define FN_TXONOFF ? ? ?1 //58
*/
?
Not selecting the FN_WSPR frees up the most memory. The display plays a role as well. There are two suggested feature lists:
?
/*
//Recommended Character LCD Developer ?87%
#define FN_BAND ? ? ? ? 1 //592
#define FN_VFO_TOGGLE ? 1 //78
#define FN_MODE ? ? ? ? 1 //20
#define FN_RIT ? ? ? ? ?1 //58
#define FN_SPLIT ? ? ? ?1 //62
#define FN_IFSHIFT ? ? ?1 //238
#define FN_ATT ? ? ? ? ?0 //128
#define FN_CW_SPEED ? ? 0 //152 //using MM
#define FN_VFOTOMEM ? ? 1 //254
#define FN_MEMTOVFO ? ? 1 //188
#define FN_MEMORYKEYER ?1 //156
#define FN_WSPR ? ? ? ? 1 //1044
#define FN_SDRMODE ? ? ?1 //68
#define FN_CALIBRATION ?0 //667 //using MM
#define FN_CARRIER ? ? ?0 //382 //using MM
#define FN_CWCARRIER ? ?0 //346 //using MM
#define FN_CWTONE ? ? ? 0 //148 //using MM
#define FN_CWDELAY ? ? ?0 //98 //using MM
#define FN_TXCWDELAY ? ?0 //94 //using MM
#define FN_KEYTYPE ? ? ?0 //168 //using MM
#define FN_ADCMONITOR ? 0 //516 //using MM
#define FN_TXONOFF ? ? ?1 //58
*/
//Recommended for Nextion, TJC LCD 88%
#define FN_BAND ? ? ? ? 1 //600
#define FN_VFO_TOGGLE ? 1 //90
#define FN_MODE ? ? ? ? 1 //318
#define FN_RIT ? ? ? ? ?1 //62
#define FN_SPLIT ? ? ? ?1 //2
#define FN_IFSHIFT ? ? ?1 //358
#define FN_ATT ? ? ? ? ?1 //250
#define FN_CW_SPEED ? ? 0 //286
#define FN_VFOTOMEM ? ? 0 //276
#define FN_MEMTOVFO ? ? 0 //234
#define FN_MEMORYKEYER ?1 //168
#define FN_WSPR ? ? ? ? 1 //1130
#define FN_SDRMODE ? ? ?1 //70
#define FN_CALIBRATION ?0 //790
#define FN_CARRIER ? ? ?0 //500
#define FN_CWCARRIER ? ?0 //464
#define FN_CWTONE ? ? ? 0 //158
#define FN_CWDELAY ? ? ?0 //108
#define FN_TXCWDELAY ? ?0 //106
#define FN_KEYTYPE ? ? ?0 //294
#define FN_ADCMONITOR ? 0 //526 //not available with Nextion or Serial UI
#define FN_TXONOFF ? ? ?1 //70
//==============================================================================
// End of User Select Mode and Compil options
?
?
Setting define to 0 removes that feature from the program.
?
I hope the above helps.
?
73
Evan
AC9TU
?
?
?
|
|
Re: WSJT-X/Rigctl Configuration Issues - Need Info
Try this. I have seen this happen.? Select the mode and don't keep clicking it with the stylus. But highlight the mode and then use the knob to go up or down to select the mode. Should bring up the correct ft 8 screen? On Sat, Apr 5, 2025, 7:44?AM matjaz via <matjaz_zejn=[email protected]> wrote:
|
|
Re: zbitx - No Tx on WSJTX?
On Sat, Apr 5, 2025 at 05:39 PM, Leo Aniol, AI5II wrote:
Already did this. Still does not transmit? I'm sorry, but I don't know much about the sbitx application used by zbitx. Why didn't it become zbitx?
Among the questions is sbitx v3, which cannot update v3.051. The name is unfortunate. If you don't read the forum regularly, you will think that v3.051 is a new sbitx version, while this is the firmware version number used by the zbitx hardware. While the manufacturer is shifting the responsibility of providing help to the forum. We are also just users and customers with different knowledge and expertise. --
Gyula HA3HZ |
|
Re: zbitx - No Tx on WSJTX?
Already did this. Still does not transmit? Leo, AI5II On Sat, Apr 5, 2025, 10:52 HA3HZ via <gyula=[email protected]> wrote:
|
|
Re: Sbitx v2 to v3 update problem
#sbitx_v2
I just wrote to a questioner where you can get more knowledge and read the topic: New sBitx V3 to me
--
Gyula HA3HZ |
|
Re: sBitx update to 3.051?
Steve,
if I understand correctly, you have sBitx v3 hardware. I recommend upgrading to 64-bit, the forum discussion for which can be found here: New sBitx V3 to me --
Gyula HA3HZ |
|
CW decode
¿ªÔÆÌåÓýGot my zbitx updated.
Cells charged.
FT8 working but no qso as yet.
Tring cw mode. Can't make any sense of decodes a stream of T & E which I suppose is to be expected. Tried different wpm to no avail. Not a CW operator but got the zbitx to encourage me to learn the craft.
And real newbie question. There are two CW model in the zbitx manual. But only one in the manual.
73 de 2E0IIY?
Andrew
Sent from
|
HA3HZ
Andrew Wade UK