afarhan / ubitxv6 Goto Github PK

Creating this issue as I didn't find any contact information.

We are planning to build a satellite system for the financial industry and looking for someone to assist us with that.

Your profile looks good - let us know if you're interested to take this forward. Thanks.

Hi. My name is Joseph Stephen, vk7js. I am a totally blind software engineer as well as an advanced amateur radio licence holder from VK. I have been reviewing your firmware for v6 and noted that you have a morse field for each button. I am wondering if this is to eventually provide CW feedback for the touch screen controls? I'd love to contribute to this project to either make the UBitX v6 totally accessible via CW or via speech output. I do not have a kit as yet. Please write to me off list at [email protected] if you would be interested in me helping you make this project accessible for blind hams of which there are many. It would be wonderful if we could produce an accessible multiband transceiver for under $250 USD. Most blind hams are not financial. I am of course willing to donate my programming time. I would however apreciate a kit that I can test changes on.

I am currently building a uBitx clone and found that when I hooked up the display it would only go white. it would only function properly if i disconnected one of the SPI lines from the touch controls.
Turns out the reason is that in nano_gui.cpp, you don't disable the touch SPI during boot up, which leaves the CS line low.
I was able to fix this issue by moving the xpt2046_Init() to the top of displayInit(void){}

It is a good idea to make sure all CS pins are pulled high before sending any SPI communications so as to ensure that you are only communicating with one SPI device at a time.

When tuning below 1MHz, the displayed frequency doesn't match the tuned frequency

Reported twice, independently:
https://groups.io/g/BITX20/message/74006
https://groups.io/g/BITX20/message/74703

Ray K7OME reported at https://groups.io/g/BITX20/message/74595 that the "F" coding is wrong. I think I agree, and it should be changed to 0xE2.

To start, I am running Linux Mint 20.1 with the Cinnamon 4.4.8 GUI.

When using the Arduino IDE (1.8.15 or 2.0 beta 9), I can load sketch 6.3.1 and it compiles without any errors.
However, I can't upload to the Nano with either IDE. Now, I know others have uploaded so maybe my issue is that I'm using a Nano clone? Here are the errors I'm getting;

Arduino: 1.8.15 (Linux), Board: "Arduino Nano, ATmega328P"

Sketch uses 28748 bytes (93%) of program storage space. Maximum is 30720 bytes.
Global variables use 1151 bytes (56%) of dynamic memory, leaving 897 bytes for local variables. Maximum is 2048 bytes.
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 1 of 10: not in sync: resp=0x00
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 2 of 10: not in sync: resp=0x00
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 3 of 10: not in sync: resp=0x00
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 4 of 10: not in sync: resp=0x00
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 5 of 10: not in sync: resp=0x00
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 6 of 10: not in sync: resp=0x00
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 7 of 10: not in sync: resp=0x00
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 8 of 10: not in sync: resp=0x00
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 9 of 10: not in sync: resp=0x00
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 10 of 10: not in sync: resp=0x00
Problem uploading to board. See https://support.arduino.cc/hc/en-us/sections/360003198300 for suggestions.

This report would have more information with
"Show verbose output during compilation"
option enabled in File -> Preferences.

It would be very helpful if the variables selected for BFO and Freq when calibrating the V6 were re-displayed when the user returns to that screen. As it is now they default to factory initial values so trying to zero beat means starting from scratch when you find that you missed by some small margin on a previous attempt.

Updated uBiTX 6 with this sketch. upload was complete.... success. volume is very very feeble now.