Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
- BITX20
- Messages
Search
|
Re: S/N 0994 receiver internal noise
On Thu, Jan 2, 2025 at 01:25 AM, w9blw wrote:
HA3HZ,? That's exactly why. Because of the lack of shielding.
Since there is shielding between the pcb and the RPi and the monitor cable is also shielded, I can now increase the sensitivity to a much higher level without increasing the noise. Of course, increasing the sensitivity also increases the noise, but not as much as without shielding. --
Gyula HA3HZ |
|
Thank you for responding, you are the first to report the problem. Indeed, fixing this one line does not solve the problem, as I mentioned it together with the other settings. The monitor ribbon cable and the shielding between the RPi and the pcb greatly improve the quality of the incoming signal. What you did is the first step towards a good solution. I also went through these steps. The device in its delivered state cannot be used as described. What is described in the topic leads to the solution.
Indeed, I started using jtdx around 2017, following the childhood diseases of programming and using the radio, modem, PC I never encountered this message. I was surprised when I searched with google and people complained about similar messages with wsjt-x. Mostly caused by RFI, lack of shielding, tangled wires. In this case, everything is in one place, so a more careful solution was needed. --
Gyula HA3HZ |
On Jan 1, 2025, at 10:55, HA3HZ <gyula@...> wrote:I tried; this was not sufficient by itself, I’m still getting this error. I’ve been using wsjt-x, but I see various people report online that JTDX decodes more signals. I guess that’s why you use it? |
|
On Wed, Jan 1, 2025 at 02:43 PM, Mike Johnshoy wrote:
I'd like to give you 2 cents worth on the T/R switch, but I hate to get too many topics going. I'm assuming you are looking at the changes in the 64-bit repo? It might be a good example of code that evolved over time, and several iterations of hardware, that still carries the remnants of good (and less good?) problem workarounds ... My attempt to make things better (I especially like the idea that it seems to get all sbitx hardware back on the same T/R code) should ideally be reviewed and blessed by the original developers. Hi,
?
1.? No I have NOT been following anything at all about the 64-bit version because I have too many other responsibilities etc.? ?This Christmas break was the first chance I had to take a look at the CW responsiveness improvements.
2.? I have previously provided some code to avoid unnecessary clattering of relays in the DE version (but since I don't do GITHUB, that wheel gets reinvented over and over and hopefully finally implemented in the github versions.?
3.? Here is where I found what MIGHT be the sbitx.c in the 64-bit version: ?
?
I note that it is still using all the same (20 msec, 10 msec) delays as the original 32-bit code, in the transition from receive to transmit.? ?
?
4.? You had indicated you have basically removed ALL the delays, did I understand that correctly???? ? The code doesn't give engineering explanations of why the delays were instituted so I'm concerned about all of this.? ?I think our goal might be to reduce the delays (which you measured at about 30 msec I believe) to 12-15 mSec so that a "dot" at 25 wpm isn't shortened more than about 25%
?
Please correct any misconceptions that you see in the statements (1)(2)(3)(4) above!!? ?On Thursday I will probably try something with reducing the delays, but since my transmitter is currently dead in the water....won't really be able to test for some time....
?
Gordon KX4Z
?
? |
|
Re: wipe out - help
Terry,
?
If you're looking for the stock firmware(32bit) that ships with the sBitx, you can find it here :
?
If you are looking for the 64 bit firmware by JJ and team, you can find it here: ?
I hope you have a backup of the hardware settings as you will need to replace that on the new SD card.
I have had good luck with Sandisk and Samsung EVO cards in the past. I'd suggest a 64GB SDcard, but 32GB card will do just fine. Hope this helps. 73 and Happy New Year, Ragav VU3VWR |
|
Re: zBitx is here! Merry Christmas!!
开云体育From HFsignals:Power Supply: 6V to 9V. Receive Current consumption: 300 mATransmit Current consumption: 1.5 to 3A (depending on the Drive settings) There were discussions about modifying the unit to handle higher voltages, but as I recall Farhan made a conscious decision to this voltage range for several reasons, which he explained earlier. Ken, N2VIP On Jan 1, 2025, at 20:32, Chris Hoffman via groups.io <chris.wa2sem@...> wrote:
|
|
Re: zBitx is here! Merry Christmas!!
What is the acceptable range for voltage of the battery/power supply for the zBitx?
I understand that with higher voltages there is the issue with heat dissipation as the voltage is stepped down. Is there any advantage to higher voltage such as higher RF power output? ?
What is the minimum voltage? ?Is a 6 volt LiFePo adequate?? |
|
Re: S/N 0994 receiver internal noise
We've discussed this since the V2 days as both of the models suffer from the same issue. There is no shielding whatsoever inside this mass-produced radio which causes all sorts of issues. Mitigating internally generated noise can be accomplished by shielding the DSI cable, replacing the buck converter with a shielded one, making a shield cover for the RF input area, grounding unused pins, etc.
?
?
-JJ |
|
Re: S/N 0994 receiver internal noise
HA3HZ,? nice write up, your shielding looks really nice, much nicer than mine. :)? what was the purpose of shielding under the RPI?? Ryan,? i was thinking the same thing, need to shield the whole board.? I just reopened mine and i think we can 3D print a "mold" that we could then cover in shielding tape or paint ( the tape works better in my experience).? Looks really tight with the speaker in there but I'm going to take some measurements and see what i can come up with.? ?the output side will / would be much easier to 3d print a mold for.? thinking jut to keep the ribbons away from the filters if nothing else. w9blw |
|
Re: Zbitx boards only
Evan,
toggle quoted message
Show quoted text
Thanks, I personally have no interest in populated or bare PCBs, I'm happy to help Farhan achieve his social goals, providing meaningful work opportunities to members of his community. When RPi and Displays were hard to source, others and I encouraged Farhan to offer a version without the display or RPi, allowing those with their own display or RPi to supply their own - that was the limit of my interest in home-brewing or recreating his offerings! LOL Thanks for the reminder, I mis-remembered what Farhan does and does not share with the community. Ken, N2VIP On Jan 1, 2025, at 17:35, Evan Hand via groups.io <elhandjr@...> wrote: |
|
Re: Zbitx boards only
Yes. ?I would want a bare unpopulated board. ?I don’t intend to sell anything but have plenty of 1206 and 0805 parts and want to experiment here. ?I have already placed an order for a regular zbitx and my sbitx is modified quite a bit so rather than removing a bunch of parts from the zbitx id just start from scratch with another one. ?2 is fine?. ?If the gerber file is available I could buy some from china but would rather just purchase from Ashar. ?
Ryan
kk6dzb |
|
Gordon - Thanks for the feedback! The way your note started out I thought it was not going to be good! But it turned out nicely.
re: your results ... 1) Bencher paddle into Sbitx in "Iambic" mode -- seems to key perfectly, very responsive. [The polling rate for the paddle contacts is increased the same as the polling rate for straight key, so good to hear that] 2) Bencher paddle into "lil Bugger" ancient transistor/integrated circuit keyer (no longer on the market) -- with sBitx set to "straight key mode" and the "lil Bugger" doing all the electronic wizardry. This keyer COULD NOT PREVIOUSLY SEND GOOD CODE WITH THE SBITX -- IT JUST ACTED LIKE IT HAD BAD LENGTH CODE ELEMENTS -- I THOUGHT IT WAS NOT PROPERLY SHORTING OUT THE SBITX INPUTS OR SOMETHING AND HAD PLANS TO REBUILD THE OUTPUT CIRCUITRY -- Now, it is sending GREAT CODE! The sBitx is now responding quite well to the Lil Bugger's code. This suggests your fix is a huge improvement to the Straight Key input. [This has been the "acid test", using an electronic keyer to input arguably pefect code into the straigh key jack, and then seeing how bad it gets mangled ... ] 3) Switched to a homebrew Arduino emulator of a WINKEYER (K3NG code) that our group has laid out boards and built. Bencher paddle into Arduino emulator, output into "straight key" mode of sBitx. This is a confirmatory test of the straight key input -- I sent several sentences and the response of the sBitx was snappy and correct! [good, same as your second test] I'd like to give you 2 cents worth on the T/R switch, but I hate to get too many topics going. I'm assuming you are looking at the changes in the 64-bit repo? It might be a good example of code that evolved over time, and several iterations of hardware, that still carries the remnants of good (and less good?) problem workarounds ... My attempt to make things better (I especially like the idea that it seems to get all sbitx hardware back on the same T/R code) should ideally be reviewed and blessed by the original developers. -- Mike KB2ML |
|
Re: Zbitx boards only
Ryan and Ken,
?
PC board layout and STL files have always been the design pieces that have remained the property of HFSignals. However, there are always exceptions. For example, the original design before the inclusion of the small Pico-controlled screen may be available.
?
73/
Evan
AC9TU |
|
Re: Zbitx boards only
开云体育You want a "bare unpopulated" PCB?I'm sure you could convince Farhan to share the PCB design once it's finalized... I thought you wanted a PCB with the components installed... Ken, N2VIP On Jan 1, 2025, at 4:10?PM, Ryan Wesolowski via groups.io <cosmo1stgen@...> wrote:
|
|
Re: S/N 0994 receiver internal noise
Good on you for taking this on! ?I know many others will appreciate it also. ?We all just deal with it. ?I have a drok, twisted pair and a ferrite on the display power and a flat ferrite made for ribbon cables on the display cable. ?I have knocked down quite a bit, but the birdies are very annoying more visually than audible for me as you can move them out of the pass band on 4.2 64bit. ?I have a fan case on top of the pi5 that I may add the copper tape to act as a shield and am thinking of trying an aluminum shield between the rf board and display. ?This would cover a good portion of the board. ?
Ryan
kk6dzb |
|
OK!!? ?I have preliminary results to report.
?
First, the day started off badly.? ?While working to get going for morning CW practice listening to high speed ops on 80 meters, I got the amplifier going and didn't retune the little auto-tuner between the sBitx & the SB-200 amp.? ?The Sbitx was only at 68% drive (enough to drive the SB-200 to nearly 200 watts, about as much as I dare put into my homebrew 49:1 EFHW balun.)? ?I started to send just a very short identification --- and BAM! the sBitx went DARK.? ? A current meter that hadn't been working very well suddenly showed LOTS of current from the DC power supply (ghosts?) -- and the little DC power supply went into current limiting.? ?Quick, turn off sBitx.? ? Turn back on -- immediate replay of Bad Things -- power goes up, power goes DOWN, something is shorting out the power supply......
?
After getting over the emotions.....somehow I had to have shorted out one of the IRFZ24N's.? ?I have worked with? THREE sBitx's and done all kind of fool things, and NEVER blew out a power amp MOSFET!? ?So this was very, very surprising, when I had used nearly the same setup just a few days before.? ?
?
Later in the day, more composed, I managed to extricate the sBitx from my plywood go-box and the zillion plugs that are normally connected...got cracked open, looked over all the wiring and circuitry that I spent MONTHS diagnosing a shorted diode in the diode-switching systems, a bad MOSFET 7002? and such (MONTHS of work)....got the heatsink back off; my AlN insulators looked fine, but I failed to carefully check the tension on the bar -- but at least the first screw was indeed tight.? ?With some trial and error I found the IRFZ24N that was indeed shorted, and the other one looked fine, so for the moment I left it in there, got the entire thing back together and now it receives again.? ?Drive level set to 1%, can key CW with no output and no damage, so was able then to work with your code.
?
?
Managed after re-learning a bunch of stuff, to insert your very elegant code, recompiles and ran it -- runs.
?
Testing:? ?(this is 32-bit code, my "flatresponse version" from late in 2024
?
1)? Bencher paddle into Sbitx in "Iambic" mode -- seems to key perfectly, very responsive? ? ?The other day I had the feeling it just wasn't timing right and I made lots of errors in sending CW....but this time it seems very responsive at 21wpm internal electronic keying, and I'm not making errors for a change.
?
2)? Bencher paddle into "lil Bugger" ancient transistor/integrated circuit keyer (no longer on the market) -- with sBitx set to "straight key mode" and the "lil Bugger" doing all the electronic wizardry.? ?This keyer COULD NOT PREVIOUSLY SEND GOOD CODE WITH THE SBITX -- IT JUST ACTED LIKE IT HAD BAD LENGTH CODE ELEMENTS -- I THOUGHT IT WAS NOT PROPERLY SHORTING OUT THE SBITX INPUTS OR SOMETHING AND HAD PLANS TO REBUILD THE OUTPUT CIRCUITRY --? ?Now, it is sending GREAT CODE!? ?The sBitx is now responding quite well to the Lil Bugger's code.? ?This suggests your fix is a huge improvement to the Straight Key input.
?
3)? Switched to a homebrew Arduino emulator of a WINKEYER (K3NG code) that our group has laid out boards and built.? ?Bencher paddle into Arduino emulator, output into "straight key" mode of sBitx.? ? ?This is a confirmatory test of the striaght key input -- I sent several sentences and the response of the sBitx was snappy and correct!? ??
?
?
I have not tested the remaining impacts of the change; will have to watch it for a while.? ?Have not yet made the changes you suggest in the T/R code.? This is ONLY the addition to sbitx_gtk.c? you suggested.
?
// every 20 ticks call modem_poll to see if any modes need work done
if (ticks % 20 == 0) modem_poll(mode_id(get_field("r1:mode")->value)); else { // calling modem_poll every 20 ticks isn't enough to keep up with a fast // straight key, so now we go on _every_ tick in MODE_CW or MODE_CWR if ((mode_id(get_field("r1:mode")->value)) == MODE_CW || (mode_id(get_field("r1:mode")->value)) == MODE_CWR) modem_poll(mode_id(get_field("r1:mode")->value)); } This simple change seemingly gives a 20 x increase in polling rate for cw only. [added code is BOLDED] ?
Great going, Mike!!! This little part right here so far looks like a big win. It can't fix the non-real-time behavior of Linux....but it is fixing things that were much more of bother to a 20-25 wpm code operator. Based on the change, I would suspect it works past 30 wpm, making this a far far better CW rig already.
?
Next I'll get around to looking at the T/R delays and your suggestions there.
?
THANKS!!!!!
?
Gordon KX4Z
?
?
? |
|
Re: Zbitx boards only
I intend to repackage one of them. ?I have plenty of pi’s here and don’t need another one? even if I only save a few bucks. Shipping a bare unpopulated board in an envelope would be reasonable on cost. ?This is the exact reason I want a board only with no pi no screen and no case. ?Even if it’s just a bare unpopulated board I want to add my own case and possibly just a pi4 or 5.
?
Ryan
kk6dzb |
|
Re: Zbitx boards only
开云体育I'm not sure what a board only kit would look like, omitting the display and RPi 2 Zero W might cut the cost $30, and the case maybe another few dollars, but you're still looking at expensive shipping and paypal fees. You still need to add an RPi, erasing nearly half the savings.As I recall, the sBitx came in a few versions because RPi boards were scarce and selling at above retail price. I don't know that the volume is there to justify two versions of the radio - people that want to "re-package" the zBitx would likely be better off buying a finished zBitx and then removing it from the case. Just my opinion, but since you asked here, not asking HFSIGNALS directly, I assume you also were interested in list members thoughts on it... Ken, N2VIP On Jan 1, 2025, at 12:29, Ryan Wesolowski via groups.io <cosmo1stgen@...> wrote:
|
|
Re: sBitX V3 Microphone input
You can find the circuit diagram on github in the sbitx/src/docs folder. :
You need to measure 3.3V at the ptt point, which is connected to the RPi input. If you have problems with the microphone, you can find a solution on the , many people have implemented it and replaced the microphone insert. --
Gyula HA3HZ |
HA3HZ
to navigate to use esc to dismiss