On Fri, Dec 16, 2022 at 05:56 PM, Ashhar Farhan wrote:
Raspberry Pis are being sold one off at the moment to individuals. They are also selling it to approved commercial buyers. We applied but received stony silence from them.
On Dec 16, 2022, at 18:55, Ashhar Farhan <farhanbox@...> wrote:
Raspberry Pis are being sold one off at the moment to individuals. They are also selling it to approved commercial buyers. We applied but received stony silence from them.
On Sat, Dec 17, 2022, 12:07 AM AndyH <awhecker@...> wrote:
The latest update from the Raspberry Pi folks looks good.
Reportedly there are about 100,000 units of Pi are flowing into approved resellers now, including 2 and 4 Gig Pi 4s.
73 Andy, KG5RKP/MM
Re: Raspberry Pi (no longer the value proposition)
Raspberry Pis are being sold one off at the moment to individuals. They are also selling it to approved commercial buyers. We applied but received stony silence from them.
Glad you got it working. When I've seen errors in the upload status messages, the previous version is left loaded.
I'm not sure there aren't other issues with the CAT interface. ?I just found that if I change the baud to 115200, the radio works with WSJT-X, but not with FLRig. But at 38400, it seems pretty stable.? -- 73, Mark, N8ME
I reloaded the firmware and it seems to be working. I remember the first upload status message came back with an error message even though the screen works. This time around there wasn't any error message.
Where do I find this setting? It isn't in Config Setup or UI.
Mike N2MS
On 12/16/2022 2:01 PM Mark Erbaugh <mark.election@...> wrote:
Also, under ports on the FLRig configuration, I see two versions of the same port: /dev/tty.usbserial-#### and /dev/cu.usbserial-#### (with the same number in ####). I don't know the differences, try switching between them. -- 73, Mark, N8ME
On 12/16/2022 2:01 PM Mark Erbaugh <mark.election@...> wrote:
Also, under ports on the FLRig configuration, I see two versions of the same port: /dev/tty.usbserial-#### and /dev/cu.usbserial-#### (with the same number in ####). I don't know the differences, try switching between them. -- 73, Mark, N8ME
The USE_CAT_ACTIVITY is also commented out. That explains why I don't see it.
Here are my settings:
#pragma once
// use the defines below to enable or disable features // --------------------------------------------------- #define USE_CAT // CAT, subset of Yaesu FT817ND - works with WSJT-X and FLDigi hamlib #define USE_HAM_BAND // band selection screen (ham bands)
// MEE add-ons // #define USE_BC_BAND // band selection screen (broadcast bands) #define USE_MEMORY // M1 .. M5 buttons // #define USE_RF_SHIFT // RF shift - provides an adjustable RF shift #define USE_RF_SHIFT_STEP // RF shift - provides stepped settings of 0, -10dB, -20dB, -30dB #define USE_ATTN // RF Attenuator - based on reducing drive level of 1st IF #define USE_LOCK // frequency lock #define USE_IF_SHIFT // IF shift - tone control #define USE_SPOT // CW spotting tone #define USE_TUNE // Tune output #define USE_PDL_POL // paddle polarity #define USE_TX_DIS // Tx disable button #define USE_HB_DISP // Flashing HB indicator // #define USE_CAT_ACTIVITY // Flashing CAT activity indicator // #define USE_MAN_SAVE // manually save VFOs #define USE_AUTO_SAVE // Periodic auto-save VFOs #define USE_WINKEY // Winkeyer (CW - tip, PTT - ring) option on paddle jack // #define USE_RX_ONLY // disable all TX functions // #define USE_SCREEN_DUMP // add screen dump feature #define USE_CFG_FREQ // add option for frequency calibration #define USE_CFG_BFO // add option for BFO calibration // #define USE_CFG_TOUCH // add option for touch calibration
On 12/16/2022 1:59 PM Mark Erbaugh <mark.election@...> wrote:
The correct setting is 38,400 N,8,2. It is set in main.cpp. I will have to update the documentation.
Please check the defines.h file. Is USE_SCREEN_DUMP enabled (not commented out with leading '//')? That changes the baud rate from 38400 to get faster screen dumps. Unless you are generating screen dumps for documentation, USE_SCREEN_DUMP should be commented out.
The blue CAT activity is only visible if the USE_CAT_ACTIVITY line (in defines.h) is enabled. ?
Here are some other things to try:
Try reloading the firmware.
Cycle the power on the uBitx. With the stock uBitx, that will require unplugging the USB cable as well as turning the radio off with the volume knob as the Arduino gets power from both sources.
On the FLRig Xcvr configuration screen, verify the settings and click the INIT button.
Also, under ports on the FLRig configuration, I see two versions of the same port: /dev/tty.usbserial-#### and /dev/cu.usbserial-#### (with the same number in ####). I don't know the differences, try switching between them. -- 73, Mark, N8ME
The correct setting is 38,400 N,8,2. It is set in main.cpp. I will have to update the documentation.
Please check the defines.h file. Is USE_SCREEN_DUMP enabled (not commented out with leading '//')? That changes the baud rate from 38400 to get faster screen dumps. Unless you are generating screen dumps for documentation, USE_SCREEN_DUMP should be commented out.
The blue CAT activity is only visible if the USE_CAT_ACTIVITY line (in defines.h) is enabled. ?
Here are some other things to try:
Try reloading the firmware.
Cycle the power on the uBitx. With the stock uBitx, that will require unplugging the USB cable as well as turning the radio off with the volume knob as the Arduino gets power from both sources. ?
On the FLRig Xcvr configuration screen, verify the settings and click the INIT button.
Mark
-- 73, Mark, N8ME
Re: Raspberry Pi (no longer the value proposition)
I am testing with FLRIG version 1.4.5. I set up as per your FLRIG CAT setup diagram in the user manual. I verified my CCOM port settings via device manager.
FLRIG Setup recognizes the CAT port but when I initialize the uBitX screen flashes off/on and the LOCK mode is enabled. The radio does not respond to FLRIG. If I depress the LOCK button in will enable it self again. I don't see the blue box under the heartbeat.
All diagrams show settings of 38,400 N,8,2 but your writeup says N,8,1 . I normally use N,8,2 but I tried both settings.
On 12/15/2022 2:19 PM Mark Erbaugh <mark.election@...> wrote:
I found that CAT support of the original uBitx firmware was not reliable. I worked on the CAT implementation in my N8ME firmware (which was included in the VU3GAO mod) to make sure it works with both WSJT-X and FLRig (part of the FLDigi suite). Here are the settings I use on my M1 Mac Mini. They seem to work well. FWIW, use Utilities/Audio MIDI Setup to adjust the audio levels.
I have a new sBitx that has never been powered up or opened. I am asking $500 including shipping (USA only), and I'll forward the modification kit when I receive it. The reason I want to sell is that I don't have time to work on it.? If interested, kindly email me at w4wb@....?? -- Barry W4WB Huntsville, Alabama USA
Thanks for the explanation. Your code is a vast improvement on the original code. I'm spending more time on the uBitX than with my $$$ radios these days.
On 12/15/2022 2:04 PM Mark Erbaugh <mark.election@...> wrote:
Mike,
I do my development using VSCode & PlatformIO. I wanted to make the firmware available for people using the Arduino IDE. The src.ino name was the only way I could figure out that would working with both VSCode and the Arduino IDE. AFAIK, VSCode requires the files to be in the "src" directory. Arduino IDE requires that the directory have the same name as the .ino file, file hence the name src.ino. An empty src.ino keeps the Arduino IDE happy, VSCode ignores that file and finds the real main entry point in main.cpp.
That said, if you want to archive the files with your naming, just rename the .ino file and directory to your "N8ME-uBitx6-V0.2-master."
Alternatively, you can download the .ZIP file from github.com. It is titled "N8ME-uBitx-master.zip." It contains both versions 0.1 and 0.2, you can use the tags v1_release (v 0.1) or v2_release (v 0.2) to check out the desired version. Note that the v1_release will need an added src.ino (which is empty) to work with the Arduino IDE.