Date   
Re: uBITX Software error messages #ubitx-help

bengt-ingvar.andersson@...
 

Ok Armin.

I count to 9 files under uBITX_20, one of them is uBITX_20.ino. ( the biggest )

I click on it and IDE start up with an sketch file.

I compile and here are the error list:

Arduino:1.8.5 (Windows Store 1.8.10.0) (Windows 10), Kort:"Arduino Nano, ATmega328P"
 
C:\Users\mop\AppData\Local\Temp\Temp1_ubitx-master (5).zip\ubitx-master\ubitx_20\ubitx_20.ino: In function 'void setNextHamBandFreq(long unsigned int, char)':
 
ubitx_20:396: error: 'byteToMode' was not declared in this scope
 
   byteToMode(loadMode, 1);
 
                         ^
 
C:\Users\mop\AppData\Local\Temp\Temp1_ubitx-master (5).zip\ubitx-master\ubitx_20\ubitx_20.ino: In function 'byte delay_background(unsigned int, byte)':
 
ubitx_20:420: error: 'getPaddle' was not declared in this scope
 
       if (getPaddle() != 0) //Interrupt : Stop cw Auto mode by Paddle -> Change Auto to Manual
 
                     ^
 
ubitx_20:424: error: 'autoSendPTTCheck' was not declared in this scope
 
       autoSendPTTCheck();
 
                        ^
 
ubitx_20:426: error: 'Check_Cat' was not declared in this scope
 
       Check_Cat(3);
 
                  ^
 
ubitx_20:431: error: 'Check_Cat' was not declared in this scope
 
       Check_Cat(fromType);
 
                         ^
 
C:\Users\mop\AppData\Local\Temp\Temp1_ubitx-master (5).zip\ubitx-master\ubitx_20\ubitx_20.ino: In function 'void setFrequency(long unsigned int)':
 
ubitx_20:500: error: 'si5351bx_setfreq' was not declared in this scope
 
       si5351bx_setfreq(2, SECOND_OSC_USB - usbCarrier + f  + (isIFShift ? ifShiftValue : 0));
 
                                                                                            ^
 
ubitx_20:504: error: 'si5351bx_setfreq' was not declared in this scope
 
       si5351bx_setfreq(2, SECOND_OSC_LSB + usbCarrier + f + (isIFShift ? ifShiftValue : 0));
 
                                                                                           ^
 
ubitx_20:511: error: 'si5351bx_setfreq' was not declared in this scope
 
       si5351bx_setfreq(2, SECOND_OSC_LSB + cwmCarrier + f + (isIFShift ? ifShiftValue : 0));
 
                                                                                           ^
 
ubitx_20:515: error: 'si5351bx_setfreq' was not declared in this scope
 
       si5351bx_setfreq(2, SECOND_OSC_USB - cwmCarrier + f + (isIFShift ? ifShiftValue : 0));
 
                                                                                           ^
 
C:\Users\mop\AppData\Local\Temp\Temp1_ubitx-master (5).zip\ubitx-master\ubitx_20\ubitx_20.ino: In function 'void startTx(byte, byte)':
 
ubitx_20:549: error: 'byteToMode' was not declared in this scope
 
         byteToMode(vfoA_mode, 0);
 
                                ^
 
ubitx_20:554: error: 'byteToMode' was not declared in this scope
 
         byteToMode(vfoB_mode, 0);
 
                                ^
 
ubitx_20:563: error: 'si5351bx_setfreq' was not declared in this scope
 
     si5351bx_setfreq(0, 0);
 
                          ^
 
ubitx_20:589: error: 'updateDisplay' was not declared in this scope
 
     updateDisplay();
 
                   ^
 
C:\Users\mop\AppData\Local\Temp\Temp1_ubitx-master (5).zip\ubitx-master\ubitx_20\ubitx_20.ino: In function 'void stopTx()':
 
ubitx_20:598: error: 'si5351bx_setfreq' was not declared in this scope
 
     si5351bx_setfreq(0, usbCarrier + (isIFShift ? ifShiftValue : 0));  //set back the carrier oscillator anyway, cw tx switches it off
 
                                                                    ^
 
ubitx_20:600: error: 'si5351bx_setfreq' was not declared in this scope
 
     si5351bx_setfreq(0, cwmCarrier + (isIFShift ? ifShiftValue : 0));  //set back the carrier oscillator anyway, cw tx switches it off
 
                                                                    ^
 
ubitx_20:609: error: 'byteToMode' was not declared in this scope
 
         byteToMode(vfoA_mode, 0);
 
                                ^
 
ubitx_20:614: error: 'byteToMode' was not declared in this scope
 
         byteToMode(vfoB_mode, 0);
 
                                ^
 
ubitx_20:621: error: 'updateDisplay' was not declared in this scope
 
   updateDisplay();
 
                 ^
 
C:\Users\mop\AppData\Local\Temp\Temp1_ubitx-master (5).zip\ubitx-master\ubitx_20\ubitx_20.ino: In function 'void ritDisable()':
 
ubitx_20:640: error: 'updateDisplay' was not declared in this scope
 
     updateDisplay();
 
                   ^
 
C:\Users\mop\AppData\Local\Temp\Temp1_ubitx-master (5).zip\ubitx-master\ubitx_20\ubitx_20.ino: In function 'void checkButton()':
 
ubitx_20:670: error: 'btnDown' was not declared in this scope
 
   if (!btnDown())
 
                ^
 
ubitx_20:673: error: 'btnDown' was not declared in this scope
 
   if (!btnDown()) //debounce
 
                ^
 
ubitx_20:676: error: 'doMenu' was not declared in this scope
 
   doMenu();
 
          ^
 
ubitx_20:679: error: 'btnDown' was not declared in this scope
 
   while(btnDown()) {
 
                 ^
 
ubitx_20:681: error: 'Check_Cat' was not declared in this scope
 
     Check_Cat(0);
 
                ^
 
C:\Users\mop\AppData\Local\Temp\Temp1_ubitx-master (5).zip\ubitx-master\ubitx_20\ubitx_20.ino: In function 'void doTuningWithThresHold()':
 
ubitx_20:710: error: 'enc_read' was not declared in this scope
 
     s = enc_read();
 
                  ^
 
ubitx_20:749: error: 'updateDisplay' was not declared in this scope
 
   updateDisplay();
 
                 ^
 
C:\Users\mop\AppData\Local\Temp\Temp1_ubitx-master (5).zip\ubitx-master\ubitx_20\ubitx_20.ino: In function 'void doRIT()':
 
ubitx_20:756: error: 'enc_read' was not declared in this scope
 
   int knob = enc_read();
 
                       ^
 
ubitx_20:766: error: 'updateDisplay' was not declared in this scope
 
     updateDisplay();
 
                   ^
 
C:\Users\mop\AppData\Local\Temp\Temp1_ubitx-master (5).zip\ubitx-master\ubitx_20\ubitx_20.ino: In function 'void initSettings()':
 
ubitx_20:846: error: 'printLineF' was not declared in this scope
 
     printLineF(1, F("Init EEProm...")); 
 
                                      ^
 
C:\Users\mop\AppData\Local\Temp\Temp1_ubitx-master (5).zip\ubitx-master\ubitx_20\ubitx_20.ino: In function 'void setup()':
 
ubitx_20:1112: error: 'printLineF' was not declared in this scope
 
   printLineF(1, F("CECBT v1.04")); 
 
                                 ^
 
ubitx_20:1114: error: 'Init_Cat' was not declared in this scope
 
   Init_Cat(38400, SERIAL_8N1);
 
                             ^
 
ubitx_20:1115: error: 'initMeter' was not declared in this scope
 
   initMeter(); //not used in this build
 
             ^
 
ubitx_20:1120: error: 'printLineFromEEPRom' was not declared in this scope
 
     printLineFromEEPRom(0, 0, 0, userCallsignLength -1); //eeprom to lcd use offset (USER_CALLSIGN_DAT)
 
                                                       ^
 
ubitx_20:1126: error: 'clearLine2' was not declared in this scope
 
     clearLine2();
 
                ^
 
ubitx_20:1131: error: 'byteToMode' was not declared in this scope
 
   byteToMode(vfoA_mode, 0);
 
                          ^
 
ubitx_20:1132: error: 'initOscillators' was not declared in this scope
 
   initOscillators();
 
                   ^
 
ubitx_20:1137: error: 'updateDisplay' was not declared in this scope
 
   updateDisplay();
 
                 ^
 
ubitx_20:1139: error: 'btnDown' was not declared in this scope
 
   if (btnDown())
 
               ^
 
ubitx_20:1140: error: 'factory_alignment' was not declared in this scope
 
     factory_alignment();
 
                       ^
 
C:\Users\mop\AppData\Local\Temp\Temp1_ubitx-master (5).zip\ubitx-master\ubitx_20\ubitx_20.ino: In function 'void checkAutoSaveFreqMode()':
 
ubitx_20:1161: error: 'FrequencyToVFO' was not declared in this scope
 
       FrequencyToVFO(1);
 
                       ^
 
C:\Users\mop\AppData\Local\Temp\Temp1_ubitx-master (5).zip\ubitx-master\ubitx_20\ubitx_20.ino: In function 'void loop()':
 
ubitx_20:1174: error: 'controlAutoCW' was not declared in this scope
 
     controlAutoCW();
 
                   ^
 
ubitx_20:1176: error: 'cwKeyer' was not declared in this scope
 
   cwKeyer(); 
 
           ^
 
ubitx_20:1188: error: 'idle_process' was not declared in this scope
 
       idle_process();
 
                    ^
 
ubitx_20:1195: error: 'Check_Cat' was not declared in this scope
 
   Check_Cat(inTx? 1 : 0);
 
                        ^
 
exit status 1
'byteToMode' was not declared in this scope
 
This report would have more information with
"Show verbose output during compilation"
option enabled in File -> Preferences.
 


Re: uBITX Software error messages #ubitx-help

Jack Purdum
 

This will likely make no difference, but the error messages that result might. Try creating a directory with this structure:

    C:\uBITXSoftware\ubitx_20\ubitx_20.ino   // plus the other 8 files

then compile and report the first 3 or 4 errors you get using this directory structure.

Jack, W8TEE





From: "bengt-ingvar.andersson@..." <bengt-ingvar.andersson@...>
To: BITX20@groups.io
Sent: Tuesday, March 13, 2018 3:12 PM
Subject: Re: [BITX20] uBITX Software error messages #ubitx-help

Ok Armin.

I count to 9 files under uBITX_20, one of them is uBITX_20.ino. ( the biggest )

I click on it and IDE start up with an sketch file.

I compile and here are the error list:

Arduino:1.8.5 (Windows Store 1.8.10.0) (Windows 10), Kort:"Arduino Nano, ATmega328P"
 
C:\Users\mop\AppData\Local\Temp\Temp1_ubitx-master (5).zip\ubitx-master\ubitx_20\ubitx_20.ino: In function 'void setNextHamBandFreq(long unsigned int, char)':
 
ubitx_20:396: error: 'byteToMode' was not declared in this scope
 
   byteToMode(loadMode, 1);
 
                         ^
 
C:\Users\mop\AppData\Local\Temp\Temp1_ubitx-master (5).zip\ubitx-master\ubitx_20\ubitx_20.ino: In function 'byte delay_background(unsigned int, byte)':
 
ubitx_20:420: error: 'getPaddle' was not declared in this scope
 
       if (getPaddle() != 0) //Interrupt : Stop cw Auto mode by Paddle -> Change Auto to Manual
 
                     ^
 
ubitx_20:424: error: 'autoSendPTTCheck' was not declared in this scope
 
       autoSendPTTCheck();
 
                        ^
 
ubitx_20:426: error: 'Check_Cat' was not declared in this scope
 
       Check_Cat(3);
 
                  ^
 
ubitx_20:431: error: 'Check_Cat' was not declared in this scope
 
       Check_Cat(fromType);
 
                         ^
 
C:\Users\mop\AppData\Local\Temp\Temp1_ubitx-master (5).zip\ubitx-master\ubitx_20\ubitx_20.ino: In function 'void setFrequency(long unsigned int)':
 
ubitx_20:500: error: 'si5351bx_setfreq' was not declared in this scope
 
       si5351bx_setfreq(2, SECOND_OSC_USB - usbCarrier + f  + (isIFShift ? ifShiftValue : 0));
 
                                                                                            ^
 
ubitx_20:504: error: 'si5351bx_setfreq' was not declared in this scope
 
       si5351bx_setfreq(2, SECOND_OSC_LSB + usbCarrier + f + (isIFShift ? ifShiftValue : 0));
 
                                                                                           ^
 
ubitx_20:511: error: 'si5351bx_setfreq' was not declared in this scope
 
       si5351bx_setfreq(2, SECOND_OSC_LSB + cwmCarrier + f + (isIFShift ? ifShiftValue : 0));
 
                                                                                           ^
 
ubitx_20:515: error: 'si5351bx_setfreq' was not declared in this scope
 
       si5351bx_setfreq(2, SECOND_OSC_USB - cwmCarrier + f + (isIFShift ? ifShiftValue : 0));
 
                                                                                           ^
 
C:\Users\mop\AppData\Local\Temp\Temp1_ubitx-master (5).zip\ubitx-master\ubitx_20\ubitx_20.ino: In function 'void startTx(byte, byte)':
 
ubitx_20:549: error: 'byteToMode' was not declared in this scope
 
         byteToMode(vfoA_mode, 0);
 
                                ^
 
ubitx_20:554: error: 'byteToMode' was not declared in this scope
 
         byteToMode(vfoB_mode, 0);
 
                                ^
 
ubitx_20:563: error: 'si5351bx_setfreq' was not declared in this scope
 
     si5351bx_setfreq(0, 0);
 
                          ^
 
ubitx_20:589: error: 'updateDisplay' was not declared in this scope
 
     updateDisplay();
 
                   ^
 
C:\Users\mop\AppData\Local\Temp\Temp1_ubitx-master (5).zip\ubitx-master\ubitx_20\ubitx_20.ino: In function 'void stopTx()':
 
ubitx_20:598: error: 'si5351bx_setfreq' was not declared in this scope
 
     si5351bx_setfreq(0, usbCarrier + (isIFShift ? ifShiftValue : 0));  //set back the carrier oscillator anyway, cw tx switches it off
 
                                                                    ^
 
ubitx_20:600: error: 'si5351bx_setfreq' was not declared in this scope
 
     si5351bx_setfreq(0, cwmCarrier + (isIFShift ? ifShiftValue : 0));  //set back the carrier oscillator anyway, cw tx switches it off
 
                                                                    ^
 
ubitx_20:609: error: 'byteToMode' was not declared in this scope
 
         byteToMode(vfoA_mode, 0);
 
                                ^
 
ubitx_20:614: error: 'byteToMode' was not declared in this scope
 
         byteToMode(vfoB_mode, 0);
 
                                ^
 
ubitx_20:621: error: 'updateDisplay' was not declared in this scope
 
   updateDisplay();
 
                 ^
 
C:\Users\mop\AppData\Local\Temp\Temp1_ubitx-master (5).zip\ubitx-master\ubitx_20\ubitx_20.ino: In function 'void ritDisable()':
 
ubitx_20:640: error: 'updateDisplay' was not declared in this scope
 
     updateDisplay();
 
                   ^
 
C:\Users\mop\AppData\Local\Temp\Temp1_ubitx-master (5).zip\ubitx-master\ubitx_20\ubitx_20.ino: In function 'void checkButton()':
 
ubitx_20:670: error: 'btnDown' was not declared in this scope
 
   if (!btnDown())
 
                ^
 
ubitx_20:673: error: 'btnDown' was not declared in this scope
 
   if (!btnDown()) //debounce
 
                ^
 
ubitx_20:676: error: 'doMenu' was not declared in this scope
 
   doMenu();
 
          ^
 
ubitx_20:679: error: 'btnDown' was not declared in this scope
 
   while(btnDown()) {
 
                 ^
 
ubitx_20:681: error: 'Check_Cat' was not declared in this scope
 
     Check_Cat(0);
 
                ^
 
C:\Users\mop\AppData\Local\Temp\Temp1_ubitx-master (5).zip\ubitx-master\ubitx_20\ubitx_20.ino: In function 'void doTuningWithThresHold()':
 
ubitx_20:710: error: 'enc_read' was not declared in this scope
 
     s = enc_read();
 
                  ^
 
ubitx_20:749: error: 'updateDisplay' was not declared in this scope
 
   updateDisplay();
 
                 ^
 
C:\Users\mop\AppData\Local\Temp\Temp1_ubitx-master (5).zip\ubitx-master\ubitx_20\ubitx_20.ino: In function 'void doRIT()':
 
ubitx_20:756: error: 'enc_read' was not declared in this scope
 
   int knob = enc_read();
 
                       ^
 
ubitx_20:766: error: 'updateDisplay' was not declared in this scope
 
     updateDisplay();
 
                   ^
 
C:\Users\mop\AppData\Local\Temp\Temp1_ubitx-master (5).zip\ubitx-master\ubitx_20\ubitx_20.ino: In function 'void initSettings()':
 
ubitx_20:846: error: 'printLineF' was not declared in this scope
 
     printLineF(1, F("Init EEProm...")); 
 
                                      ^
 
C:\Users\mop\AppData\Local\Temp\Temp1_ubitx-master (5).zip\ubitx-master\ubitx_20\ubitx_20.ino: In function 'void setup()':
 
ubitx_20:1112: error: 'printLineF' was not declared in this scope
 
   printLineF(1, F("CECBT v1.04")); 
 
                                 ^
 
ubitx_20:1114: error: 'Init_Cat' was not declared in this scope
 
   Init_Cat(38400, SERIAL_8N1);
 
                             ^
 
ubitx_20:1115: error: 'initMeter' was not declared in this scope
 
   initMeter(); //not used in this build
 
             ^
 
ubitx_20:1120: error: 'printLineFromEEPRom' was not declared in this scope
 
     printLineFromEEPRom(0, 0, 0, userCallsignLength -1); //eeprom to lcd use offset (USER_CALLSIGN_DAT)
 
                                                       ^
 
ubitx_20:1126: error: 'clearLine2' was not declared in this scope
 
     clearLine2();
 
                ^
 
ubitx_20:1131: error: 'byteToMode' was not declared in this scope
 
   byteToMode(vfoA_mode, 0);
 
                          ^
 
ubitx_20:1132: error: 'initOscillators' was not declared in this scope
 
   initOscillators();
 
                   ^
 
ubitx_20:1137: error: 'updateDisplay' was not declared in this scope
 
   updateDisplay();
 
                 ^
 
ubitx_20:1139: error: 'btnDown' was not declared in this scope
 
   if (btnDown())
 
               ^
 
ubitx_20:1140: error: 'factory_alignment' was not declared in this scope
 
     factory_alignment();
 
                       ^
 
C:\Users\mop\AppData\Local\Temp\Temp1_ubitx-master (5).zip\ubitx-master\ubitx_20\ubitx_20.ino: In function 'void checkAutoSaveFreqMode()':
 
ubitx_20:1161: error: 'FrequencyToVFO' was not declared in this scope
 
       FrequencyToVFO(1);
 
                       ^
 
C:\Users\mop\AppData\Local\Temp\Temp1_ubitx-master (5).zip\ubitx-master\ubitx_20\ubitx_20.ino: In function 'void loop()':
 
ubitx_20:1174: error: 'controlAutoCW' was not declared in this scope
 
     controlAutoCW();
 
                   ^
 
ubitx_20:1176: error: 'cwKeyer' was not declared in this scope
 
   cwKeyer(); 
 
           ^
 
ubitx_20:1188: error: 'idle_process' was not declared in this scope
 
       idle_process();
 
                    ^
 
ubitx_20:1195: error: 'Check_Cat' was not declared in this scope
 
   Check_Cat(inTx? 1 : 0);
 
                        ^
 
exit status 1
'byteToMode' was not declared in this scope
 
This report would have more information with
"Show verbose output during compilation"
option enabled in File -> Preferences.
 




60m USB??

nt6s@...
 

The ubitx looks like a neat project to build for a portable field rig, but before I get one, does anyone know if it is capable of operating on USB below 10MHz?  I would like to use it on the 60m band, where USB is the sideband mode used. 

NT6S

Teensy 3.5/3.6 upgrade for uBITX

n5ib_2
 

Here's what our little Skunkworks has been up to.

A wee PC board that accepts a Teensy 3.5 or 3.6 processor, then plugs into the space that would have been occupied by a NANO.
Corresponding I/O lines are routed to maintain compatibility with uBITX.
Since the Teensy has a RTC (real time clock) there's a spot for its backup battery.

In principle, the adapter could be used to plug in a Teensy anywhere a NANO used to live.
On a stock Raduino (have to remove the NANO and socket the space), an enhanced Raduino, our own RadI2Cino, or what else may come along.
Scads more memory, more I/O including lots of analog, an on-card microSD slot, and of course the RTC
The Teensy 3.5 runs on 3-6 volts, with 3.3V logic, but 5 V tolerant digital inputs. The Teensy 3.6 also runs on 3-6 V, but its logic is 3.3V ONLY, and is faster and has more memory than the 3.5

Prototype boards are in hand are about to get to beta test within the next few days. Firmware portability is of course the thing that must be confirmed,
We'll keep y'all posted.

Jim, N5IB
with W0EB and W2CTX

Re: 60m USB??

M Garza <mgarza896@...>
 

NT6S,
Yes, USB under 10MHZ is supported.  You just have to go through the menu and select USB.

Marco - KG5PRT

On Tue, Mar 13, 2018 at 2:25 PM, <nt6s@...> wrote:
The ubitx looks like a neat project to build for a portable field rig, but before I get one, does anyone know if it is capable of operating on USB below 10MHz?  I would like to use it on the 60m band, where USB is the sideband mode used. 

NT6S


Re: Teensy 3.5/3.6 upgrade for uBITX

n5ib_2
 

Forgot the photo,,,

Re: 60m USB??

Jerry Gaffke
 

Yes, below 10mhz on USB works fine, USB can be selected within the menu system,

Could easily write firmware for the Arduino Nano to channelize as per US usage
and select USB automatically, whenever a frequency within that band is selected.

Jerry, KE7ER


On Tue, Mar 13, 2018 at 12:25 pm, <nt6s@...> wrote:
The ubitx looks like a neat project to build for a portable field rig, but before I get one, does anyone know if it is capable of operating on USB below 10MHz?  I would like to use it on the 60m band, where USB is the sideband mode used. 

Re: Teensy 3.5/3.6 upgrade for uBITX

Jerry Gaffke
 

Would be interesting to try a high side BFO with your Teensy,
see if it has any issue with battling oscillators:
    https://groups.io/g/BITX20/topic/14533495


On Tue, Mar 13, 2018 at 12:26 pm, n5ib_2 wrote:
A wee PC board that accepts a Teensy 3.5 or 3.6 processor, then plugs into the space that would have been occupied by a NANO.

Re: TFT TOUCH CONTROL AND DISPLAY CODE -2.9u

Walter
 

On Mon, Mar 12, 2018 at 05:47 pm, Joe wrote:
Walter,
 
There are various ways to make the project.
 
I have chosen to mount the display directly on the Atmega . 
 
Since it is a TFT Touch control, external buttons are optional... just a vol control is required 
 
The 2.8 inch TFT Elegoo display  I use plugs directly into the Atmega. I use display   from amazon- very high quality and sensitive touch control.   Other displays work as well 
 
Plugging the display directly into  the Atmega eliminates any wiring for the display to the Atmega connectivity.  It also helps keep noise down.
 
From the Atmega you need to connect wires to the Digital Connector on the Ubitx board.
From the Atmega you also need to connect the sda and scl pins of the atmega to the sda and scl pins on the DDS si5351(I use the adafruit)
 
From the DDS si5351 you need to connect the 3 output clocks to the digital connector on the Ubitx mainboard.  I use shielded wire
 
On the atmega on the rear side I added some socks so i can acess the pins i require for control.
Since the display is mounted to the atmega directly, I cant access the front atmega contol pins. Adding the socks on the back is easy and solves that problem.
 
 
 
Not Required but its what I do to ensure there is no digital noise and vfo clicks etc.
I use a small Chinese buck voltage regulator with a hash filter on the output --- 12 volt( INPUT or whatever your main input voltage is) in adjusted to 5.01v OUTPUT for the DDS.
This ensures  isolation and kills digital noise 
 
I use  another identical regulator and feed the input with the same 12 volts and adjust the output for 9.5v this goes to the atmega voltage in connector.  This isolates, and keeps the atmega running cool. As well the hash filters kills the noise.
 
As for how much space from the back of my front panel... 1 inch plus the rear sockets i added, probably around 1.5 inches total
 
Attached is a picture of the wiring diagram - 
 
The setup is quite simple. 
 
Joe 
VE1BWV
 

On Mon, Mar 12, 2018 at 9:21 PM, Walter <W9KJO@...> wrote:
On Mon, Mar 12, 2018 at 12:50 pm, Joe wrote:
Good Afternoon,

The latest version 2.9u - of the TFT Colour touch control for the UBitx has just been released.

The new version has Cat control and Split mode for Tx / RX

I have attached the code and wiring diagram.

The code can also be found at vu2spf.blogspot.ca




73
VE1BWV AND VU2SPF
Would you happen to have complete instructions for adding such a display.

Also how much room in required in the case and does the display mount on the main board as the old display or does it need to be cable connected?

I am very interested in this but need much more information.

Thanks
 
--
73, W9KJO
Walter

 

 

Joe,

I like what you have done with this full color touch screen.  Really nice work.  However, I will not be able to implement your project because you are talking over my head.

I am an electronics technician but I am far from an EE.  I would need much more detailed instructions and parts lists.  I would also need step by step instructions for loading software.  For instance you mention a resistor to reduce hash.  Where does the resistor fit into the system?

So I will say, very nice full color display.  Great Work.  Thanks for showing it to us and sharing some of your information with us.
 
--
73, W9KJO
Walter

Re: F R A G M E N T A T I O N !

Charles D. Smith
 

Well said Arv.
72/73 de Chas ai4ot

Re: TFT TOUCH CONTROL AND DISPLAY CODE -2.9u

Joe
 

Wa

On Tue, Mar 13, 2018, 4:58 PM Walter <W9KJO@...> wrote:
On Mon, Mar 12, 2018 at 05:47 pm, Joe wrote:
Walter,
It seems like a big task but it is manageable.

1. Software - you do need to compile it and upload to the atmega micro controller.
There are several tutorials available.
It sounds more difficult than it actually is.

2. Hardware -  On ubitx.net there is a listing of the hardware required and where to source it.  I think if you search for ve1bwv it will pop up.

3. I think. I need to do a build video on youtube. I have several, but they are for operations an features.

4.  The hash filters are used by many. Vk3eye has a video on using them.
Basically, a I use a 1000mfd to 2200mfd cap on input and output. On the output, I add a 2 to 10 ohm resistor in series with the positive lead ouput lead.
Resistor Wattage depends on load but mostly a few watts are fine. It is amazing how effectively the kill noise.

Joe
VE1BWV
 
There are various ways to make the project.
 
I have chosen to mount the display directly on the Atmega . 
 
Since it is a TFT Touch control, external buttons are optional... just a vol control is required 
 
The 2.8 inch TFT Elegoo display  I use plugs directly into the Atmega. I use display   from amazon- very high quality and sensitive touch control.   Other displays work as well 
 
Plugging the display directly into  the Atmega eliminates any wiring for the display to the Atmega connectivity.  It also helps keep noise down.
 
From the Atmega you need to connect wires to the Digital Connector on the Ubitx board.
From the Atmega you also need to connect the sda and scl pins of the atmega to the sda and scl pins on the DDS si5351(I use the adafruit)
 
From the DDS si5351 you need to connect the 3 output clocks to the digital connector on the Ubitx mainboard.  I use shielded wire
 
On the atmega on the rear side I added some socks so i can acess the pins i require for control.
Since the display is mounted to the atmega directly, I cant access the front atmega contol pins. Adding the socks on the back is easy and solves that problem.
 
 
 
Not Required but its what I do to ensure there is no digital noise and vfo clicks etc.
I use a small Chinese buck voltage regulator with a hash filter on the output --- 12 volt( INPUT or whatever your main input voltage is) in adjusted to 5.01v OUTPUT for the DDS.
This ensures  isolation and kills digital noise 
 
I use  another identical regulator and feed the input with the same 12 volts and adjust the output for 9.5v this goes to the atmega voltage in connector.  This isolates, and keeps the atmega running cool. As well the hash filters kills the noise.
 
As for how much space from the back of my front panel... 1 inch plus the rear sockets i added, probably around 1.5 inches total
 
Attached is a picture of the wiring diagram - 
 
The setup is quite simple. 
 
Joe 
VE1BWV
 

On Mon, Mar 12, 2018 at 9:21 PM, Walter <W9KJO@...> wrote:
On Mon, Mar 12, 2018 at 12:50 pm, Joe wrote:
Good Afternoon,

The latest version 2.9u - of the TFT Colour touch control for the UBitx has just been released.

The new version has Cat control and Split mode for Tx / RX

I have attached the code and wiring diagram.

The code can also be found at vu2spf.blogspot.ca




73
VE1BWV AND VU2SPF
Would you happen to have complete instructions for adding such a display.

Also how much room in required in the case and does the display mount on the main board as the old display or does it need to be cable connected?

I am very interested in this but need much more information.

Thanks
 
--
73, W9KJO
Walter

 

 

Joe,

I like what you have done with this full color touch screen.  Really nice work.  However, I will not be able to implement your project because you are talking over my head.

I am an electronics technician but I am far from an EE.  I would need much more detailed instructions and parts lists.  I would also need step by step instructions for loading software.  For instance you mention a resistor to reduce hash.  Where does the resistor fit into the system?

So I will say, very nice full color display.  Great Work.  Thanks for showing it to us and sharing some of your information with us.
 
--
73, W9KJO
Walter

Re: #uBITX Firmware KD8CEC - IF-Shift etc. #ubitx

Guy N7BIR <sgbridge@...>
 

Jerry, 
Following your suggestions I started running some tests on my uBitX. 
You asked whether it was plugged into an antenna. Funny you should ask that because I had just plugged it into a brand new 40 meter monoGap; just enough to check SWR....no reading. 
I am showing 12 volts in transmit coming off the K1 relay. 
I checked Q90 and got 0 volts on both the base and emitter in transmit. 
Cant pick up my signal in a nearby receiver  in either SSB or CW. Toroids are all good. 
So at the very least I think i’ll be replacing Q90. 
73,
Guy

Re: #uBITX Firmware KD8CEC - IF-Shift etc. #ubitx

Jerry Gaffke
 

How about the Q90 collector?
If it's 12v, then Q90 is probably blown, though look over R81.
If it's not 12v, then R84 or T8 are bad.


On Tue, Mar 13, 2018 at 02:01 pm, Guy N7BIR wrote:
I checked Q90 and got 0 volts on both the base and emitter in transmit. 

Re: 13.8 v power supplies safe for bitx?

Tom VE3THR
 

Bill ... 13.8VDC would be the absolute max for the main boards ( BITX40 and uBITX). I would suspect this level is stressing the raduino, relay coils etc. over time, and stuffing the gear in an enclosure would raise the internal temp very quickly as well.
FUSE your PA and BOARD appropriately! I use a 12v sealed battery portable or a switch mode wall wart repurposed for the BITX. Output is 12.1 VDC at 2.5 Amps. There is no stress on my motherboard and in the unfortunate event of a IRF510 current runaway (high swr) or failure, the most current drawn will be limited to a couple of amps. My main shack supply would supply 30 amps plus and a lot more smoke. I have run the BITX40 for over a year now making over a hundred contacts across 3 continents with no problems, often having the rig on for the whole day. Using original heatsink on the PA but I did put another sink on the 5V regulator for the raduino just in case. Went through a few wall warts before I found a "quiet" one. Stable clean DC power is paramount. 
I plan on using same power for the new uBITX but will do the 5V reg mod on my TDA2822M chip just in case. I use a built in small speakers and/or external DSP audio filter/amp/spkr - no headphones. Will be mounting  the PA's to a metal backpanel with mica insulators on this build and a sink on the raduino 5V regulator  too.
73 Tom VE3THR

uBITx: Interesting new firmware for the uBITx from BG1REN (China)

Mike Woods
 

Bob GM4CID placed a comment on my article “Ubitx modders are hard at work”  about another very interesting Raduino solution from BG1REN.  

The firmware can be found here:  https://github.com/qiwenmin/ubitx-fsm  There is a link to the documentation which when translated using Google Translate is pretty readable.

See the news item on ubitx.net about this new firmware that is based on a new mini Operating System (called FSMOS) for the arduino:

http://ubitx.net/2018/03/13/1291/

I suspect this new firmware will create a bit of interest in the uBITx community.  It is based heavily on KD8CEC's feature set, but has some features of its own.

73 Mike ZL1AXG

--
Mike Woods
mhwoods@...

Re: RD16HHF1 power curve flattening...some

Glenn
 

Hi John, no not yet. Plan is do that asap, duplicate the final stage with RD16HHF1's and hook up to my driver section..

Depending on how it all works of course, then mod my uBITX.

glenn

Re: F R A G M E N T A T I O N !

Jerry Gaffke
 

We often have the related problem of sidetracking a perfectly good thread title
For example, we might have a thread going with "uBitx:  loud spurious audio tones"
and somebody pipes up with a new thread:  "uBitx:  loud spurious audio tones, my solution"

Makes it almost impossible to follow a conversation when digging through the archives.
With a hijacked thread, I can skip over the off topic posts.

Jerry


On Tue, Mar 13, 2018 at 09:41 am, Arv Evans wrote:
Yes, hijacking of threads has always been a problem on this and other similar groups.

Re: uBITX Software error messages #ubitx-help

DJ2AG
 

I was able to reproduce this. If after downloading the zip file from github I assume you just double clicked the downloaded zip file and opened ubitx_20.ino by double clicking it too. Windows just extracted this file into a temp directory. In your case into:

C:\Users\mop\AppData\Local\Temp\Temp1_ubitx-master (5).zip\ubitx-master\ubitx_20

But only this file and not the other ones. To fix the problem just go to the Download directory where Windows saved the zip file and unzip or extract whatever command you have available with a right click on the zip file. From here you can move it to a more convenient place, but you could also try from the newly created directory in your download Folder.
When you now double click ubitx_20.ino, the Arduino IDE should now show  all ino files in separate tabs and compile should work.

Good luck!
Armin, DJ2AG

Re: Complaint Department

Mike Woods
 

Obviously I would be happy to curate an Errata page.  However, it may be better to have this on the HF Signals website in terms of giving confidence to new constructors.

I would be happy to curate such a page and Ashhar Farhan could always amend if he didn't agree with me!

Mike ZL1AXG ubitx.net


On 14/03/18 7:13 AM, Jerry Gaffke via Groups.Io wrote:
Could be to the wiki.
But if so, then all 10000 members of this forum could be editing it.

I think a curated errata page on ubitx.net would be preferable for new builders.
But by all means, we can have a wiki errata page, where we all pile in with our own perhaps conflicting suggestions.

Jerry


On Tue, Mar 13, 2018 at 10:42 am, Vince Vielhaber wrote:
If there's going to be a link to errata, it could be a link to the wiki page on errata. Doesn't have to be one pointing to the first page of it making anyone dig around for anything. For all that matter, a link on the first page of the wiki to errata would help as well for someone who just went straight there.


--
Mike Woods
mhwoods@...

Re: RD16HHF1 power curve flattening...some

Nick VK4PP
 

Nice work Glen.

I am still to solve my oscillation issue on 20m+, but I have also decided to upgrade the LPF toroids to T50-6, I am concerned that the T30 will be overwhelmed at 20W output... Maybe need to do all the emitter 220 caps... and play with the feedback loop on the RD16.

I did order a bunch of the MPSH10 too. They have a different pinout to the 3904s? so have to go in the place twisted, like the RD16.... ?

73 Nick,