Topics

: #V6 software issues help please #v6

Neil k8it
 




Begin forwarded message:

From: Neil Sablatzky <k8it@...>
Date: January 21, 2020 at 3:26:58 PM EST
To: farhanbox@...
Subject: #V6 software issues help please

Asher
With help from an experienced uBitX builder we just finished putting together a V6 complete kit. I am very disappointed.
I would appreciate your help to resolve these issues ASAP.

1. No 17M band
2. Lag time on CW it is almost impossible to operate CW with either a straight key or a iambic panel since it takes about 1.5 seconds to respond.

3. No side tone volume adjustment can this be added in software? Or what is the best way to add this?

4. Mounting of display standoffs shorted to metal case. We fixed this by ordering nylon standoffs. The dimensions of the case seems off.
5. Unknown calibration numbers for 10MHz, set frequently , set BFO values. Please add a function to read back the calibration values so they can be recorded.
6. why does the LSB button stay  lit when Cw button is pushed?
7. You had indicated that you would add Morse code feedback for selections and frequency . I am completely blind and had the help of two others in building this radio. When will this update be available? It was stated on the blind hams net that you would have this ready this month.

Thanks
73 Neil k8it








AndyH
 

I can't speak to the rest from the vantage point of my modded V3, but it appears that item 1 has been and/or is being worked.  Ashhar reported it on Christmas day, 2019.

https://groups.io/g/BITX20/message/74007


On Tue, Jan 21, 2020 at 02:33 PM, Neil k8it wrote:


 

Begin forwarded message:

From: Neil Sablatzky <k8it@...>
Date: January 21, 2020 at 3:26:58 PM EST
To: farhanbox@...
Subject: #V6 software issues help please

Asher
With help from an experienced uBitX builder we just finished putting together a V6 complete kit. I am very disappointed.
I would appreciate your help to resolve these issues ASAP.

1. No 17M band
2. Lag time on CW it is almost impossible to operate CW with either a straight key or a iambic panel since it takes about 1.5 seconds to respond.

3. No side tone volume adjustment can this be added in software? Or what is the best way to add this?

4. Mounting of display standoffs shorted to metal case. We fixed this by ordering nylon standoffs. The dimensions of the case seems off.
5. Unknown calibration numbers for 10MHz, set frequently , set BFO values. Please add a function to read back the calibration values so they can be recorded.
6. why does the LSB button stay  lit when Cw button is pushed?
7. You had indicated that you would add Morse code feedback for selections and frequency . I am completely blind and had the help of two others in building this radio. When will this update be available? It was stated on the blind hams net that you would have this ready this month.

Thanks
73 Neil k8it








Reed N
 

Hi Neil,

1) Pretty sure this has been fixed for a while
2) Others have reported this too. I hope to look into it in the not-too-distant future
3) The CW tone is generated by a PWM signal from the Arduino. There might be some tricks to turn the normal PWM output into a class D amp of sorts, but that could be a rabbit hole, and is not something I anticipate I'll be looking into soon
4) I slightly bent the pins on my screen to get it to sit flush against the case, but didn't have any issues with shorting (that I've noticed)
5) In my software version, you can view the current values by going to the respective menus - it doesn't revert them to default. I don't know if this helps you if you're blind.
6) The uBitx software switches USB/LSB separately from CW mode, so you could potentially run USB CW
7) It looks like Ashhar put a fair number of pieces in place to support menu navigation with Morse Code audio feedback, but never hooked them up. I just created a branch that hopefully does something useful in this regard: https://github.com/reedbn/ubitxv6/tree/morse-menu . I've also attached a hex file, if that's easier for you. In this build, the long press of the tuning knob no longer goes to the menu - instead, it will toggle the menu audio feedback. To get to the setup menu, you'll instead need to select the "MNU" button (or 'M' as the audio will play). NOTE: there's currently no way to skip the audio on an item. Once it starts playing, you have to listen to the whole text before you can select the next item. This can make it quite slow to navigate menus, however I hope that it's better than nothing. Feedback on this build is welcome, but I make no promises of support or further revisions.


Reed

Reed N
 

I've been working on this with Neil in PMs and figured others may also be interested in the accessibility aspect. I've made some additional changes to the UI since the file posted above (which can be found at https://github.com/reedbn/ubitxv6/tree/morse-menu), so here's the latest hex.


Reed

Reed N
 

Hi Neil and Bill,

Newer version attached. No major accessibility changes, but does fix the CW RX to TX issue that should help with straight key usage. Give it a try and let me know.


Reed

WB0WQS
 

Reed,  Congratulations..
I used your hex file attached to this email and loaded it into My V6
the CW is doing much better.  The lag is gone, in the transmit/ receive.  The hand key mode works well too.  What an improvement!  
If you would like some feedback, I would say that the characters sent with the paddle need some spacing in between them. I have
checked that in A and B mode.  I Don't know what the standard spacing would be.. but it is difficult to send characters like x.. dah dit dit dah...   K:  dah dit dah... without them running together and throwing an extra
dit in the there.    for example the letter K... might be dah dit dit dit dah ... easily by accident.  Thank you so much for your time and effort working on these codes.  I hope my input helps.Let me
know if you need any clarification..   73,  - WB0WQS

the menu status sent in CW is a nice touch too. That could be helpful in some situations.




On Tue, Jan 28, 2020 at 10:53 PM Reed N <greenkid336600+groupsio@...> wrote:
Hi Neil and Bill,

Newer version attached. No major accessibility changes, but does fix the CW RX to TX issue that should help with straight key usage. Give it a try and let me know.


Reed

Reed N
 

Hi WB0WQS,

Hopefully the attached hex fixes inter-element timing! It appears that it was only 1/10th the duration it was supposed to be.


Reed

WB0WQS
 

Good Job, Reed.  Keying using the built-in keyer is perfect!  After you adjusted the duration.  I will post a short video some time today on Facebook after my Iphone charges..  thank you!
I called cq on 14.060 and didn't get a call, but I was reported on the reverse beacon on 14.060 once I calibrated the frequency...  not bad for a 200 dollar rig.  73. 
P.S... I did make a ssb qso on one of the nets on 20, he said my audio was a bit bassy. but that is either that Baofoeng mic, or my BFO adjustments. 

On Thu, Jan 30, 2020 at 10:31 PM Reed N <greenkid336600+groupsio@...> wrote:
Hi WB0WQS,

Hopefully the attached hex fixes inter-element timing! It appears that it was only 1/10th the duration it was supposed to be.


Reed

Gordon Gibby
 

This all sounds great, lots and lots of people making fantastic improvements.   


On Jan 31, 2020, at 13:01, WB0WQS <WB0WQS@...> wrote:


Good Job, Reed.  Keying using the built-in keyer is perfect!  After you adjusted the duration.  I will post a short video some time today on Facebook after my Iphone charges..  thank you!
I called cq on 14.060 and didn't get a call, but I was reported on the reverse beacon on 14.060 once I calibrated the frequency...  not bad for a 200 dollar rig.  73. 
P.S... I did make a ssb qso on one of the nets on 20, he said my audio was a bit bassy. but that is either that Baofoeng mic, or my BFO adjustments. 

On Thu, Jan 30, 2020 at 10:31 PM Reed N <greenkid336600+groupsio@...> wrote:
Hi WB0WQS,

Hopefully the attached hex fixes inter-element timing! It appears that it was only 1/10th the duration it was supposed to be.


Reed

Evan Hand
 

WB0WQS,

The most likely adjustment for the "bassy" is the BFO.  The electret mic would not normally be bassy.

73
Evan
AC9TU

John T.
 

Thank you Reed! works great, excellent job!
--

John

73s de M0HSQ / SV1CWR

Reed N
 

Glad it's working for you, John! Let me know if any issues come up.


Reed