Re: sBitx v3 - problem with nonstandard callsigns
Yes, that’s what I was testing today, and just wrote about.
toggle quoted message
Show quoted text
On Mar 7, 2025, at 16:39, HA3HZ <gyula@...> wrote:
Hi Shawn,
Those who seek will find. I looked into the linked website and Georgy published his modifications two months ago.
For coders, this can be a call to attention for modifications, since sbitx is also based on kgoba coding.
Please write about your experiences so that someone on JJ discord will pay attention to the topic.
|
Re: zBitx - Progress Update
Hello,
Now that I've purchased some flat top 18650s, I'm thinking that one could easily mix up polarity on these.? What happens if someone inserts both batteries backwards?? I'm assuming that full reversal of the EMF would cause damage and that having one cell reversed will simply decrease the voltage potential below the threshold required so no damage there.
?
If it's possible to cause damage, are there recommendations for adding elements to prevent it?
Thanks
?
Hopefully the question is not a duplicate.
|
Hi Vule,
?
Raj has more experience with the uBitx than I do. However, the symptoms you describe indicate a stuck K1; here, the Nano is commanding the relay to be off, but the TX is still on and not indicated on the display.
?
You can try tapping K1 to see if that clears the TX before power cycling the radio.
?
73
Evan
AC9TU
|
Re: sBitx v3 - problem with nonstandard callsigns
Hi Shawn,
Those who seek will find. I looked into the linked website and Georgy published his modifications two months ago.
For coders, this can be a call to attention for modifications, since sbitx is also based on kgoba coding.
Please write about your experiences so that someone on JJ discord will pay attention to the topic.
--
Gyula HA3HZ
|
Vule,
Just replace the front panel mic socket. It may be a problem, just a thought!
Raj
toggle quoted message
Show quoted text
On 07/03/2025 8:41 PM, e78cb@... via groups.io wrote: Tomasz, things are like this:
1) I have original screen and TX is disapearing normaly but PTT stays ON and there is no modulation going out.
2) I did not happend on SSB, only on digital, in the biginnig only after longer session or contest, but now even after short sessions..
3) When I power down and power up uBITX TX is still ON. It is only going to off if I enter Microphone jack in the socket and push/release PTT button.
No changes in Power Voltage or different antenna or even a different PC? or cable in between makes difference.. Also, it all works fine in first 5-10 minutes an then start akting like this.
Is this indicate mostly to these two issues possible? PTT relay or Mic/PTT socket? If it is so, I will concentrate in that way..
73
Vule, E78CB
|
Tomasz, things are like this:
1) I have original screen and TX is disapearing normaly but PTT stays ON and there is no modulation going out.
2) I did not happend on SSB, only on digital, in the biginnig only after longer session or contest, but now even after short sessions..
3) When I power down and power up uBITX TX is still ON. It is only going to off if I enter Microphone jack in the socket and push/release PTT button.
No changes in Power Voltage or different antenna or even a different PC? or cable in between makes difference.. Also, it all works fine in first 5-10 minutes an then start akting like this.
?
Is this indicate mostly to these two issues possible? PTT relay or Mic/PTT socket? If it is so, I will concentrate in that way..
?
73
?
Vule, E78CB
?
?
|
Just to add to Evans first para. If a diode has failed or mostly
bad solder then the RX would have dropped sensitivity.
Good Luck with a fix!
Raj, vu2zap
On 07/03/2025 6:59 PM, Evan Hand via
groups.io wrote:
toggle quoted message
Show quoted text
Hi Ted,
?
The short answer is that both the calibration (master and
BFO) settings can cause the filter to be misaligned with the
signal.? Also, it can be a failure in the modulator in that
one-half of the BAT54FL diode could have failed or other
problems with the modulator.? If the issue is recent, it is
most likely a failure rather than a bad calibration.
?
I saw on your QRZ page that the v5 is running the KD8CEC
software with a Nextion screen.? That makes it easy to do some
checks and possible adjustments after saving the current
configuration.? Can you pull up the software settings page and
note the BO value?? It should be close to 11.056 kilohertz.? If
not, I suggest using the Memory Manager software to save the
current values and perform a complete recalibration.??
?
I have always struggled using WWV as the calibration source
as the sidetones get in the way of determining beat frequency.?
I have a 10MHz standard that I use through an attenuator for the
calibration source.? I also use a signal generator calibrated
using the standard to verify accuracy.? The higher the
calibration frequency, the better the accuracy.? If in a pinch,
you can tune down to the commercial AM band and use a known
station as the standard.? I have found this easy to do (other
than all the turns of the tuning dial to get down to the
station) but less accurate.
?
If the calibration values seem correct, then the only test I
know for the modulator is to pull the diode and replace it with
a known-good one.? That does require SMD rework skills.? I
suggest not using discrete diodes for this replacement, as they
may not have the matched characteristics.
?
Before you start tearing apart your radio, I have a question:
The video clip shows USB as the communication mode.? Were you
running a USB on 40 meters?
?
73
Evan
AC9TU
|
Hi Ted,
?
The short answer is that both the calibration (master and BFO) settings can cause the filter to be misaligned with the signal.? Also, it can be a failure in the modulator in that one-half of the BAT54FL diode could have failed or other problems with the modulator.? If the issue is recent, it is most likely a failure rather than a bad calibration.
?
I saw on your QRZ page that the v5 is running the KD8CEC software with a Nextion screen.? That makes it easy to do some checks and possible adjustments after saving the current configuration.? Can you pull up the software settings page and note the BO value?? It should be close to 11.056 kilohertz.? If not, I suggest using the Memory Manager software to save the current values and perform a complete recalibration.??
?
I have always struggled using WWV as the calibration source as the sidetones get in the way of determining beat frequency.? I have a 10MHz standard that I use through an attenuator for the calibration source.? I also use a signal generator calibrated using the standard to verify accuracy.? The higher the calibration frequency, the better the accuracy.? If in a pinch, you can tune down to the commercial AM band and use a known station as the standard.? I have found this easy to do (other than all the turns of the tuning dial to get down to the station) but less accurate.
?
If the calibration values seem correct, then the only test I know for the modulator is to pull the diode and replace it with a known-good one.? That does require SMD rework skills.? I suggest not using discrete diodes for this replacement, as they may not have the matched characteristics.
?
Before you start tearing apart your radio, I have a question: The video clip shows USB as the communication mode.? Were you running a USB on 40 meters?
?
73
Evan
AC9TU
|
Re: sBitx v3 - problem with nonstandard callsigns
On Mar 7, 2025, at 07:28, Shawn Rutledge K7IHZ / LB2JK <social@...> wrote:
But I see the issue got another patch, so I can test that soon: ?
I just tried gdyuldin’s fork: ? It looks promising: I can receive longer callsigns, can send with a suffix (LB2JK/QRP), and on pskreporter I can see that my packets get received successfully (at least sending my callsign with a suffix seems ok). ?But so far I didn’t get a successful QSO with a prefixed or suffixed callsign. ?
I just had to retune the dipole after trying that and seeing somewhat high SWR; not sure why the resonant frequency went up from where it was in the recent past, so had to add a couple cm to both ends by making some quick-connect “extensions” that I can plug on when necessary:
Got SWR down to 1.2 on 20m now, and that makes a difference in transmit power too: it goes up to about 15W max, instead of only 11 or 12. ?I’m not quite sure how to tell when I’m overdriving audio; the built-in FT8 mode generates a yellow “scope trace” that goes outside the pane (so it looks flat on top and wavy on the bottom), and if I have resized the window, then it leaves “droppings” after the transmission is done. I guess it’s supposed to be ok, since that’s how it shipped (and I still don’t understand where is that setting: the volume on some particular ALSA device or what. ?Can’t continue with trying pat until I figure out how to control ardop's crazy-large audio output. ?With that modem, the waveform gets so big that it just about fills the window.)
Anyway: I got some QSOs with normal callsigns (to prove the library isn’t totally broken). ?But just now I was monitoring FT8 with a nearby kiwisdr (since I don’t have a second rig to monitor my own transmissions), and I saw
LB2J <OH2NP/60> +14
The last letter of my callsign is truncated, while I was trying to call another callsign with a suffix (60th anniversary of a Finnish club apparently). So maybe there is at least one bug in that fork; on the other hand, guess which library the kiwisdr software is using? ?;-) ?yep, ft8_lib… so I can’t necessarily trust a kiwi to decode such callsigns anyway. ?(Or is there another fork for that? I do see some suffixed callsigns in the kiwi's log. ?How did they do that?) ?So I should probably be testing encoding and decoding wav files, instead of transmitting with a bad callsign. ?Or when the zbitx gets here, if Farhan releases the software right away, I can recompile it with the alternate ft8_lib, and use dummy loads, which ought to radiate enough for local testing, without getting out far.?
So there is hope, it just needs more work.
Screenshots:
|
I was doing POTA yesterday with the V.5 shown in my avatar, when a caller asked me if I was [intentionally] running double sideband.? He was really cool about it and volunteered to send a short video capture of my signal. I've included a still from that.
?
I haven't adjusted anything for at least 2 years and it's spot on frequency,? so I'm loathe to change anything too quickly.? I also have forgotten or am unaware that any if the VFO or tuning parameters alter the transmit side of things.? Again, it's been a while and I shall be re-reading the tuning methodology today.
?
That said, i apparently misinterpreted or missed something before, unless it's a part failure. Would anyone whose good on the earlier models be able to suggest a good methodology for placing all of my RF energy into just one 3kc channel?? I'm doing about 20 watts on 40m, so getting the full benefit - and not occupying more space than I need - would be an improvement.
?
Tnx,
?
K3RTA
?
?
?
|
Re: sBitx v3 - problem with nonstandard callsigns
I use WSJT-X on the sBitx. The screen scaler leaves me with text that is too small to read and you can't see the bottom of the WSJT-X window unless you use the X-Large setting.
Fortunately the screen resizer scrolling window still works perfectly with WSJT-X.
--
73
??? Bob? KD8CGH
|
Hi Vule,
To start narrowing the issue we would like to know if "TX" is still hanging on the screen while PTT is OFF.
?
regards
Tomasz
|
Re: sBitx v3 - problem with nonstandard callsigns
This problem is due to the ft8 library used in the sBitx software. This was already brought up by Shawn, K7IHZ, in this thread:
?
You can migrate to the 64bit version from JJ and team, and to use WSJTX/JTDX application for FT8 and use the screen scaler tool in the toolbox to resize the screen to fit the 7inch display.
Hope this helps
?
73,
Ragav
|
Re: sBitx v3 - problem with nonstandard callsigns
Yep it’s a known problem with ft8_lib. ?I was trying to hack on that a few months ago:?? It wasn’t complete enough to work yet; so I guess I should get back to it soon, or maybe someone else will.
But I see the issue got another patch, so I can test that soon: ?https://github.com/kgoba/ft8_lib/issues/44
I will have the same problem, wanting to use either the sbitx or zbitx when traveling, so I’d also like to have it fixed in time for summer.
You can use wsjt-x rather than the built-in FT8 mode in the meantime, if you don’t want to help with the changes.
toggle quoted message
Show quoted text
On Mar 7, 2025, at 02:38, WZab - SP5DAA via groups.io <wzab01@...> wrote:
I've been using my sBitx v3 for one and a half months and am pretty happy with it. However, I noticed strange behavior.
When I try to start QSO with a station that uses nonstandard callsign (e.g., longer than usual or prefixed or suffixed with something), its callsign is displayed as <...>. The same "<...>" is output to the log. This form seems to be used even in responses, so the recipient does not accept them, and the QSO gets broken.
Up to now, I'm simply limiting my QSOs to the stations with standard callsigns.?
However, spring and summer approach, and I hope to use my site v3 in SOTA and POTA activities or use it during my holidays abroad.
In those cases, my callsign will need to be suffixed (e.g., with "/P") or prefixed (e.g., with "OE/" when in ?sterreich).
Is my sBitx v3 going to handle that situation properly, or I won't be able to make any QSO?
How can I fix that issue?
?
73,
Wojtek SP5DAA
|
sBitx v3 - problem with nonstandard callsigns
I've been using my sBitx v3 for one and a half months and am pretty happy with it. However, I noticed strange behavior.
When I try to start QSO with a station that uses nonstandard callsign (e.g., longer than usual or prefixed or suffixed with something), its callsign is displayed as <...>. The same "<...>" is output to the log. This form seems to be used even in responses, so the recipient does not accept them, and the QSO gets broken.
Up to now, I'm simply limiting my QSOs to the stations with standard callsigns.?
However, spring and summer approach, and I hope to use my site v3 in SOTA and POTA activities or use it during my holidays abroad.
In those cases, my callsign will need to be suffixed (e.g., with "/P") or prefixed (e.g., with "OE/" when in ?sterreich).
Is my sBitx v3 going to handle that situation properly, or I won't be able to make any QSO?
How can I fix that issue?
?
73,
Wojtek SP5DAA
?
?
|
Re: zBITX: Is there a built-in charging circuit for the 18650 batteries?
Thanks David for the clarification.
73 Jon, VU2JO
On Thu, Mar 6, 2025 at 9:51?PM David T-- VE3TOS via <digiital= [email protected]> wrote: No there isn't.?
I bought this device in the hopes it works :)?
Is there a built-in charging circuit for the 18650 batteries in zBITX?
This question was asked by one of my ham friends. I told him that I will post on this group and get back to him if I get a response.
73 Jon, VU2JO
|
Re: SBitx SDR v3 for sale
toggle quoted message
Show quoted text
HI Everybody I have a?sBitx v3 SDR For sale Price is 375.00 plus shipping It comes with 2 mics (was told the?original sounded off) and it has power poles on the DC leads A wireless?keyboard/mouse I printed manual My thought’s changed, It has NOT been on the air, just listen. The battery is not in the deal
Denton Larson
WB0ZUR
Delavan, MN
|
HI Everybody I have a?sBitx v3 SDR For sale Price is 375.00 plus shipping It comes with 2 mics (was told the?original sounded off) and it has power poles on the DC leads A wireless?keyboard/mouse I printed manual My thought’s changed, It has NOT been on the air, just listen. The battery is not in the deal
Denton Larson
WB0ZUR
Delavan, MN
|
Re: zBitx - Progress Update
When can we expect an updated accurate schematic?
?
Joel
N6ALT
|
I use same dipole that was in use before.. It is without balun but good trimmed and it works same for many years also on other devices, even on the very same uBITX and for same purpose, nothing has changed concerning the antenna... Just thinking, could it be that the relay has worned or weakened out in a year of doing RTTY and PSK contestings..?
?
73
?
Vule, E78CB
|
Kevin
HA3HZ
Raj vu2zap
Ted
Bob Benedict, KD8CGH
tomekdm sp7etd
James Riley kb9tzq
Joel Caulkins/N6ALT