|
I am working on the next release of the sbitx software. Some bugs will be fixed, there is a massive rewrite pending to make the code friendlier to those writing on top of the sbitx core (like JJ's excellent apps). I want to take a straw poll of what all to finish, my own list includes: 1. A better and more accurate Power meter 2. Fix the keyboard bug: it crashes when there isn't enough?space to accommodate?it on the screen. 3. A newer web UI, I saw one that was very robust, done by Lars, OZ7BX. Upgrade to this one. 4. Move to be compatible with 64-bits, use the kernel I2C driver (this will involve changing the config.txt). 5. Fix the FT8 logging to kick in later at RRR, R73 or 73. It automatically detects DUPs anyway. 6. Add AM and NBFM (will try, it is still unstable). Anything else? ) This apart, we are also considering the next revision of the radio, the software development is entirely independent of the hardware and it is backwards compatible with all previous versions of the radio. For the next revision, we are considering: 1. 10.1 screen, this pulls up the power from 0.5A to 0.8A. It will impact the field ops. Should we or shouldn't we? 2. A PTT out to key the linear. 3. The 5v Regulator and the RTC to be bolted down. 4.? Higher power. How much higher should we go? At 100 watts, the entire engineering of heat dissipation will change. It may need a fan. Between 100 watts and 50 watts, it will be virtually impossible to know the difference. Between 25 watts and 100 watts, it is a one S unit difference. 5. Redesign the box to be slimmer.? 6. Higher power 5V regulator to support Raspberry 5 (for those who insist) Anything else? - f
|
As far as power goes, i like the original 40 watt design... but perhaps keep the basic 15 to 20 watt, but have an economical outboard amp that fastens to the back for those times when higher power is desired. Perhaps at the 50 watt level.
Scotty WD4PYT
On Thu, Jun 13, 2024, 12:55 PM Ashhar Farhan via <farhanbox= [email protected]> wrote: I am working on the next release of the sbitx software. Some bugs will be fixed, there is a massive rewrite pending to make the code friendlier to those writing on top of the sbitx core (like JJ's excellent apps). I want to take a straw poll of what all to finish, my own list includes: 1. A better and more accurate Power meter 2. Fix the keyboard bug: it crashes when there isn't enough?space to accommodate?it on the screen. 3. A newer web UI, I saw one that was very robust, done by Lars, OZ7BX. Upgrade to this one. 4. Move to be compatible with 64-bits, use the kernel I2C driver (this will involve changing the config.txt). 5. Fix the FT8 logging to kick in later at RRR, R73 or 73. It automatically detects DUPs anyway. 6. Add AM and NBFM (will try, it is still unstable). Anything else? ) This apart, we are also considering the next revision of the radio, the software development is entirely independent of the hardware and it is backwards compatible with all previous versions of the radio. For the next revision, we are considering: 1. 10.1 screen, this pulls up the power from 0.5A to 0.8A. It will impact the field ops. Should we or shouldn't we? 2. A PTT out to key the linear. 3. The 5v Regulator and the RTC to be bolted down. 4.? Higher power. How much higher should we go? At 100 watts, the entire engineering of heat dissipation will change. It may need a fan. Between 100 watts and 50 watts, it will be virtually impossible to know the difference. Between 25 watts and 100 watts, it is a one S unit difference. 5. Redesign the box to be slimmer.? 6. Higher power 5V regulator to support Raspberry 5 (for those who insist) Anything else? - f
|
Great news.?? The sBitX is fantastic Ashhar.? Thank you for creating it and for the continued development.???
For the next revision, we are considering:
1. 10.1 screen, this pulls up the power from 0.5A to 0.8A. It will impact the field ops. Should we or shouldn't we?
??? You did an amazing job of maximizing content and usability on the 7" screen.? Moving to 10" is a tough call.
2. A PTT out to key the linear.
??? Yes, this would be a very worthwhile addition.??
3. The 5v Regulator and the RTC to be bolted down.
??? I have not had trouble as is, however you know best here.
4. ?Higher power. How much higher should we go? At 100 watts, the entire engineering of heat dissipation will change. It may need a fan. Between 100 watts and 50 watts, it will be virtually impossible to know the difference. Between 25 watts and 100 watts, it is a one S unit difference.
??? I have found 20 to 25 watts is typically enough. ? However, output on 10m is only about 7w on mine, if the power output could be evened out then 25w across the bands should be plenty. ?? Maybe a 7" 25 watt model and a 100w 10" model is worth thinking about.??
5. Redesign the box to be slimmer.?
?? I think the box size is ok.?? It would however benefit from built in tilt legs.
6. Higher power 5V regulator to support Raspberry 5 (for those who insist)
? Hard to say on this one.?? You have managed to keep the cost very reasonable, every upgrade adds to it.
Anything else?
An on screen keyboard for using apps aside from the sbitx app.??? That would be nice for using with the chrome browser when checking pskreporter, reverse beacon network, etc..
|
To go much above 20W the mechanical, thermal, and RF layout
is a significant effort..? Also an amp that is fairly flat and has a
reasonable IMD might be worth it and also resilient (blast proof).
Also above 20W diode switching may require revisit for better
devices.? ?Higher power means more space for more robust LPFs.
I just put an oled screen on a project at 11.3 inches and less
than .5A at 5V.? Not a touch screen but usually they do not
require more power for that subcircuit.
--
Allison
------------------
Please use the forum, offline and private will go to bit bucket.
|
Screen thoughts:
I am very satisfied with the screen size. The only things I would recommend are associated with a different gui. If the screen window sizes could be resized and tiled, that would be handy. For example, if a proficient cw or phone op didn't want the visual waterfall or decoder windows, the space could be used for other things. Maybe some might even like s- meter or larger frequency readout. Programmable frequency colors based on modes or license privileges would be cool.
To go much above 20W the mechanical, thermal, and RF layout
is a significant effort..? Also an amp that is fairly flat and has a
reasonable IMD might be worth it and also resilient (blast proof).
Also above 20W diode switching may require revisit for better
devices.? ?Higher power means more space for more robust LPFs.
I just put an oled screen on a project at 11.3 inches and less
than .5A at 5V.? Not a touch screen but usually they do not
require more power for that subcircuit.
--
Allison
------------------
Please use the forum, offline and private will go to bit bucket.
|
So Far I have been liking the little rig.
From the exploring and reviewing of the different Mods and
updates I've found, I think the following may be of note:
- Add some RF shielding between the different sections of the
main board
- Or at least provide points on the board where they can be
added
- Raise the RPIx computer up from the main-board so there is
space so heat sinks / fans can be used to aid cooling that I and
others have done
- This would help stabilize the computer and increase the
performance overall - especially if the RPi 5 is used
On 6/13/2024 11:55 AM, Ashhar Farhan
via groups.io wrote:
toggle quoted message
Show quoted text
I am working on the next release of the sbitx
software. Some bugs will be fixed, there is a massive rewrite
pending to make the code friendlier to those writing on top of
the sbitx core (like JJ's excellent apps). I want to take a
straw poll of what all to finish, my own list includes:
1. A better and more accurate Power meter
2. Fix the keyboard bug: it crashes when there isn't
enough?space to accommodate?it on the screen.
3. A newer web UI, I saw one that was very robust, done by
Lars, OZ7BX. Upgrade to this one.
4. Move to be compatible with 64-bits, use the kernel I2C
driver (this will involve changing the config.txt).
5. Fix the FT8 logging to kick in later at RRR, R73 or 73.
It automatically detects DUPs anyway.
6. Add AM and NBFM (will try, it is still unstable).
Anything else?
)
This apart, we are also considering the next revision of
the radio, the software development is entirely independent of
the hardware and it is backwards compatible with all previous
versions of the radio.
For the next revision, we are considering:
1. 10.1 screen, this pulls up the power from 0.5A to 0.8A.
It will impact the field ops. Should we or shouldn't we?
2. A PTT out to key the linear.
3. The 5v Regulator and the RTC to be bolted down.
4.? Higher power. How much higher should we go? At 100
watts, the entire engineering of heat dissipation will change.
It may need a fan. Between 100 watts and 50 watts, it will be
virtually impossible to know the difference. Between 25 watts
and 100 watts, it is a one S unit difference.
5. Redesign the box to be slimmer.?
6. Higher power 5V regulator to support Raspberry 5 (for
those who insist)
Anything else?
- f
|
Being the owner of a V3, my opinion: only software changes, 64 bits, compatible with JJ's programs, delete, resize the image on the display
73 thank you
|
I would suggest adding some test points at strategic places and a convenient place to connect a clip to circuit ground (for oscilloscope probes for example). This platform is ideal for tinkering and learning, and this would make it much easier. I can envision someone creating documentation with voltages and waveforms at each test point to aid in troubleshooting and repair, or just to allow one to follow along as they learn how each section works. That would make an outstanding teaching tool. Thanks for the continued development of this platform (both at HFSignals and in the community)! 73 de W0ZF?
Being the owner of a V3, my opinion: only software changes, 64 bits, compatible with JJ's programs, delete, resize the image on the display
73 thank you
|
I have 2 V2s which I have not used yet.? Neither was new from
HFS.? One is "as shipped" hardware, the other has an 8 GB Pi in
it.? I think the software is 3.02 in both.? I plan to change the
"as shipped" to an 8 GB Pi.? I will likely bring the uSD up to 128
GB, or perhaps even 256.? I won't be using the on-screen keyboard
as I have an official Pi keyboard & mouse.
Given the ability of those lithium polymer batteries to deliver
very high currents, some fusing would likely be a good idea.? It
might not save the finals, but might avoid a burned circuit board.
Most of my operating is likely to be either CW or SSB voice.? Not
sure if I will use the other digital modes like FT8.
Apparently JJ has done a lot of software development.? Perhaps
that should be included as a regular part of any future software
releases.
The power capability of the V2 is adequate.? Would like to see it
stay there.? The capability of working with an external high power
amplifier might be used by some of us - I won't be one of them.
Definitely want to switch to a 64bit OS.
Why is Chrome apparently the browser.? Why not Firefox?
I have a Xiegu X6200 (in transit at the moment).? It has memory
keyer capabilities - voice & CW.? Might be nice additions
Call me an "appliance operator" if you like - I'm getting too
long in the whiskers to be able to hack hardware & software.
Gerry Sherman
Sent by the Windows 11 Thunderbird
On 2024-06-13 12:14, John Cooper wrote:
toggle quoted message
Show quoted text
Great news.?? The sBitX is fantastic Ashhar.? Thank you for
creating it and for the continued development.???
For the next revision, we are considering:
1. 10.1 screen, this pulls up the power from 0.5A to 0.8A. It will
impact the field ops. Should we or shouldn't we?
??? You did an amazing job of maximizing content and
usability on the 7" screen.? Moving to 10" is a tough call.
2. A PTT out to key the linear.
??? Yes, this would be a very worthwhile addition.??
3. The 5v Regulator and the RTC to be bolted down.
??? I have not had trouble as is, however you know best
here.
4. ?Higher power. How much higher should we go? At 100 watts, the
entire engineering of heat dissipation will change. It may need a
fan. Between 100 watts and 50 watts, it will be virtually
impossible to know the difference. Between 25 watts and 100 watts,
it is a one S unit difference.
??? I have found 20 to 25 watts is typically enough. ?
However, output on 10m is only about 7w on mine, if the power
output could be evened out then 25w across the bands should be
plenty. ?? Maybe a 7" 25 watt model and a 100w 10" model is
worth thinking about.??
5. Redesign the box to be slimmer.?
?? I think the box size is ok.?? It would however benefit
from built in tilt legs.
6. Higher power 5V regulator to support Raspberry 5 (for those who
insist)
? Hard to say on this one.?? You have managed to keep the
cost very reasonable, every upgrade adds to it.
Anything else?
An on screen keyboard for using apps aside from the sbitx
app.??? That would be nice for using with the chrome browser
when checking pskreporter, reverse beacon network, etc..
|
Ashhar,
I dont own the SBITX yet but several ubitxs and bitx 40s.So what im suggesting might bounce off the walls HI HI.
I tend to agree with allison on the display issue
OLED -Less power consumed.
Touch screen? maybe but if you re coded you could add a menu button and rotate the tuning knob for the submenus .
or : 0.1",10" inch TFT LCD Display w/ HDMI Controller/Driver Board for Raspberry PI
selling for$53.37 Probably can find these cheaper if buying in bundles and such.
reading all the posts, maybe leave the SBITX at 20 watts, maybe allowing for external control knobs for rf drive, mic gain and such ? giving the SBITX the Classic feel even though its still rippling with digital muscle.maybe an accessory to be plugged in like a OLED SWR meter designed specifically for the SBITX line.?
I agree with the PTT to activate an amp. alot of rigs have these.
And here is a big one which will probably get some laughs:
detachable front end. ? probably too much for costs.
Thats my ideas. Ashhar, one idea which isnt for the SBITX, bring back the bitx40 with a 3 to 5 inch screen .monobander, all mode.
Love your radios. Thank you for bringing your ideas to reality!!!!The Ham community is better with designers such as you.
73 David ac9xh
On Thursday, June 13, 2024 at 03:00:19 PM EDT, Brian - N9NAZ <n9naz2@...> wrote:
So Far I have been liking the little rig.
From the exploring and reviewing of the different Mods and
updates I've found, I think the following may be of note:
- Add some RF shielding between the different sections of the
main board
- Or at least provide points on the board where they can be
added
- Raise the RPIx computer up from the main-board so there is
space so heat sinks / fans can be used to aid cooling that I and
others have done
- This would help stabilize the computer and increase the
performance overall - especially if the RPi 5 is used
On 6/13/2024 11:55 AM, Ashhar Farhan
via groups.io wrote:
I am working on the next release of the sbitx
software. Some bugs will be fixed, there is a massive rewrite
pending to make the code friendlier to those writing on top of
the sbitx core (like JJ's excellent apps). I want to take a
straw poll of what all to finish, my own list includes:
1. A better and more accurate Power meter
2. Fix the keyboard bug: it crashes when there isn't
enough?space to accommodate?it on the screen.
3. A newer web UI, I saw one that was very robust, done by
Lars, OZ7BX. Upgrade to this one.
4. Move to be compatible with 64-bits, use the kernel I2C
driver (this will involve changing the config.txt).
5. Fix the FT8 logging to kick in later at RRR, R73 or 73.
It automatically detects DUPs anyway.
6. Add AM and NBFM (will try, it is still unstable).
Anything else?
)
This apart, we are also considering the next revision of
the radio, the software development is entirely independent of
the hardware and it is backwards compatible with all previous
versions of the radio.
For the next revision, we are considering:
1. 10.1 screen, this pulls up the power from 0.5A to 0.8A.
It will impact the field ops. Should we or shouldn't we?
2. A PTT out to key the linear.
3. The 5v Regulator and the RTC to be bolted down.
4.? Higher power. How much higher should we go? At 100
watts, the entire engineering of heat dissipation will change.
It may need a fan. Between 100 watts and 50 watts, it will be
virtually impossible to know the difference. Between 25 watts
and 100 watts, it is a one S unit difference.
5. Redesign the box to be slimmer.?
6. Higher power 5V regulator to support Raspberry 5 (for
those who insist)
Anything else?
- f
|
Did I miss something? I see the SWR and power out on the screen every time I key transmit. Why would it need an external OLED SWR meter?
I'd love a built-in tuner. I use my V3 all the time with my Comet CHA-250b vertical because I don't have to worry about tuning. The Comet is pre-tuned via the transformer at the base. It's a compromise antenna, sure, but not needing a tuner on it is a big benefit. But my other wire on my house is a W3EDP EFHW. That one always needs a tuner, by design. But it's a great antenna. I use my KX3 on it, and the built in tuner on either the radio OR the 100w amp tunes it in a couple of seconds.
A jack for keying the amp would be a welcome addition. I have only one issue with the current screen and its touch capability. The touch is inaccurate as all get out. I can almost NEVER actually hit what I want to hit, even with a stylus. Even with a mouse, it's a bit hit?or miss. That's because you can never tell WHAT PART of the cursor will select what you click on. Is it the tip of the arrow? Is it the center of the icon? IF it's the arrow tip, is it off to the upper left like the arrow? Where do you click, on the middle of what you want? I've tried all of these, and even with a good mouse, the detection is inconsistent. I'll frequently get the call ABOVE the one I want in FT8, and have to halt TX and redo it.
-=-=-=-=-=-=-=-=- 73, Gwen, NG3P
Ashhar,
I dont own the SBITX yet but several ubitxs and bitx 40s.So what im suggesting might bounce off the walls HI HI.
I tend to agree with allison on the display issue
OLED -Less power consumed.
Touch screen? maybe but if you re coded you could add a menu button and rotate the tuning knob for the submenus .
or : 0.1",10" inch TFT LCD Display w/ HDMI Controller/Driver Board for Raspberry PI
selling for$53.37 Probably can find these cheaper if buying in bundles and such.
reading all the posts, maybe leave the SBITX at 20 watts, maybe allowing for external control knobs for rf drive, mic gain and such ? giving the SBITX the Classic feel even though its still rippling with digital muscle.maybe an accessory to be plugged in like a OLED SWR meter designed specifically for the SBITX line.?
I agree with the PTT to activate an amp. alot of rigs have these.
And here is a big one which will probably get some laughs:
detachable front end. ? probably too much for costs.
Thats my ideas. Ashhar, one idea which isnt for the SBITX, bring back the bitx40 with a 3 to 5 inch screen .monobander, all mode.
Love your radios. Thank you for bringing your ideas to reality!!!!The Ham community is better with designers such as you.
73 David ac9xh
On Thursday, June 13, 2024 at 03:00:19 PM EDT, Brian - N9NAZ < n9naz2@...> wrote:
So Far I have been liking the little rig.
From the exploring and reviewing of the different Mods and
updates I've found, I think the following may be of note:
- Add some RF shielding between the different sections of the
main board
- Or at least provide points on the board where they can be
added
- Raise the RPIx computer up from the main-board so there is
space so heat sinks / fans can be used to aid cooling that I and
others have done
- This would help stabilize the computer and increase the
performance overall - especially if the RPi 5 is used
On 6/13/2024 11:55 AM, Ashhar Farhan
via wrote:
I am working on the next release of the sbitx
software. Some bugs will be fixed, there is a massive rewrite
pending to make the code friendlier to those writing on top of
the sbitx core (like JJ's excellent apps). I want to take a
straw poll of what all to finish, my own list includes:
1. A better and more accurate Power meter
2. Fix the keyboard bug: it crashes when there isn't
enough?space to accommodate?it on the screen.
3. A newer web UI, I saw one that was very robust, done by
Lars, OZ7BX. Upgrade to this one.
4. Move to be compatible with 64-bits, use the kernel I2C
driver (this will involve changing the config.txt).
5. Fix the FT8 logging to kick in later at RRR, R73 or 73.
It automatically detects DUPs anyway.
6. Add AM and NBFM (will try, it is still unstable).
Anything else?
)
This apart, we are also considering the next revision of
the radio, the software development is entirely independent of
the hardware and it is backwards compatible with all previous
versions of the radio.
For the next revision, we are considering:
1. 10.1 screen, this pulls up the power from 0.5A to 0.8A.
It will impact the field ops. Should we or shouldn't we?
2. A PTT out to key the linear.
3. The 5v Regulator and the RTC to be bolted down.
4.? Higher power. How much higher should we go? At 100
watts, the entire engineering of heat dissipation will change.
It may need a fan. Between 100 watts and 50 watts, it will be
virtually impossible to know the difference. Between 25 watts
and 100 watts, it is a one S unit difference.
5. Redesign the box to be slimmer.?
6. Higher power 5V regulator to support Raspberry 5 (for
those who insist)
Anything else?
- f
|
At last check a non touch screen works just fine off the HDMI output
with a mouse plugged in just fine.? Same for the native touch screen.?
Less troubles with fat fingers.? Also its rather unique.
On a specialized system I made (non ham) a trackball was used in
place of a mouse.? it only took 50mm square area on the panel.
Later we found a force stick that fit the same spot.
Also a small 5 key pad up,down, right, left, and enter works well.
Many ways have been developed to deal with pointing devices
and touch screen is not the only one.
Some of the linux GUIs allow for multiple workspace screens rather
than cram it all into one space.? I did that on my nominal ham
computer so that WSJT-z is on one workspace, FLdigi and CWtype
is on a second? and for voice/cw ops Xlog on the third.? Takes only
one click to jump from one to another.
--
Allison
------------------
Please use the forum, offline and private will go to bit bucket.
|
GWEN with touch screen there is a registration issue ]
As in where you point or touch is not where the object is.
larger screen helps as there are more pixels in the object.
That makes defining the active area easier.
Usually the tip of the arrow on the object center or text
under it is the "hotspot".
FYI I suggested that a larger non-touch OLED display can
be far lower power.? I have a 11.1" HDMI interfaced unit
that uses typically about .4A out of a USB port (5V) for
about 2-3W.? I put that on a built up Mini-ITX as the combo
is power efficient (7.3W average at 12V (CPU, Display,
Mouse, keyboard) for FD use (QRP) logging and WSJT-x
where everything must run on battery/solar for 24+ hours
(for the alternate energy bonus).? Without resorting to a
100Ah battery that is.? A 20Ah lifepo4 does the job
alone without solar help.
I tried a RPi400, RPI-5 and they were power hungry compared
to the? Asrock J4125B (intel quad core) and while they ran
what I wanted they were a bit sloggy..??
I can't think of a reason to add another display for power/SWR
when its on the main screen.
--
Allison
------------------
Please use the forum, offline and private will go to bit bucket.
|
On Thu, Jun 13, 2024 at 11:55 AM, Ashhar Farhan wrote:
I am working on the next release of the sbitx software. Some bugs will be fixed, there is a massive rewrite pending to make the code friendlier to those writing on top of the sbitx core (like JJ's excellent apps). I want to take a straw poll of what all to finish, my own list includes:
1. A better and more accurate Power meter
2. Fix the keyboard bug: it crashes when there isn't enough?space to accommodate?it on the screen.
3. A newer web UI, I saw one that was very robust, done by Lars, OZ7BX. Upgrade to this one.
4. Move to be compatible with 64-bits, use the kernel I2C driver (this will involve changing the config.txt).
5. Fix the FT8 logging to kick in later at RRR, R73 or 73. It automatically detects DUPs anyway.
6. Add AM and NBFM (will try, it is still unstable).
Anything else?
)
This apart, we are also considering the next revision of the radio, the software development is entirely independent of the hardware and it is backwards compatible with all previous versions of the radio.
For the next revision, we are considering:
1. 10.1 screen, this pulls up the power from 0.5A to 0.8A. It will impact the field ops. Should we or shouldn't we?
2. A PTT out to key the linear.
3. The 5v Regulator and the RTC to be bolted down.
4.? Higher power. How much higher should we go? At 100 watts, the entire engineering of heat dissipation will change. It may need a fan. Between 100 watts and 50 watts, it will be virtually impossible to know the difference. Between 25 watts and 100 watts, it is a one S unit difference.
5. Redesign the box to be slimmer.?
6. Higher power 5V regulator to support Raspberry 5 (for those who insist)
Anything else?
- f
As a constant tinkerer in this platform (thanks Ashhar), here is a list of items that I'd like to see in future software/hardware updates.
?
1. Fix the telnet connection handling for client disconnect crashes in remote.c.. See my fix at ? 2. Add functionality to the hamlib control set such as mode and band. Fix the responsiveness and client disconnect crash. 3. Add a TUNE button to set the rig to 5-10 watts, change mode to CW temporarily, and put the rig into TX for a user defined amount of time in seconds. 4. Rewrite the local gui to support industry standard development tools and allow modification from an external config file to change colors, scheme, boxes, etc. 5. Add reverse polarity protection at power input. 6. Add a S-METER!!!!
7. Add the 60 meter band 8. Add shielding between TX and RX stage and add shielding on 5V regulator and Pi. 9. Add additional filtering like a notch filter, noise reduction, shift, noise blanker, etc10. Add AM mode RX/TX capability 11. Add a "sub-menu for shortwave band listening since it is a general coverage receiver.
12 . A better and more accurate Power meter
13. Fix the keyboard bug: it crashes when there isn't enough space to accommodate it on the screen.?
14. A newer web UI, I saw one that was very robust, done by Lars, OZ7BX. Upgrade to this one.
15. Move to be compatible with 64-bits, use the kernel I2C driver (this will involve changing the config.txt).
16. Fix the FT8 logging to kick in later at RRR, R73 or 73. It automatically detects DUPs anyway.
17. Fix the naming convention for the log "export" function - it currently says import.
18. Fix the log refresh function for viewing the log in the radio GUI (shows duplicate 123123123. etc)
19. Remove RTTY and PSK31 modes since they don't work
20. Add TX compression and mic audio filtering/gain
21. Add a choice of a hand mic or USB mic in the gui (see my app for details)
22. Add Web TX capability from browser (I have this working and can share details)
23. Add a voice keyer (see my app in Toolbox)
A good starting point is to look at my sBitx Toolbox apps and add some of these functions into the software natively.
Thanks for your consideration,
JJ
|
I think a useful feature would be to add a low level output to be used with vhf/uhf transverters. ?Both ICOM and Yaesu had low level output for transverters on some models. ?It could also be tied into the software with a preset offset to account for a 26 to 30 mhz to 144 or 432 conversion and give correct frequency reading on screen. ?
|
Thanks all, Allison has confirmed my own view that 25 watts is a plenty, esp with decent speech compression.
JJ, Beckman,? Lars, Raphael and others work will be rolled in as well as the move to 64 bits.
The tough part is to simultaneously debug this on 32 bit and 64 bit.
I am using JJ's 64 bit image as the startinf point, to which I will add Lars' web UI and proceed from there. We will leave out the 10.1 inch screen for the time.
Btw, David, there is a transverter output on the board (not on the panel). We left it out as it was messing with the passive FET mixer's performance.
On Fri, Jun 14, 2024, 5:01 AM David Mitchell via <mitchedb1970= [email protected]> wrote: I think a useful feature would be to add a low level output to be used with vhf/uhf transverters.? Both ICOM and Yaesu had low level output for transverters on some models.? It could also be tied into the software with a preset offset to account for a 26 to 30 mhz to 144 or 432 conversion and give correct frequency reading on screen. ?
|
I will also add my own wish list to this. The clock syncing is one such thing. It would be easier to just ping an ntp server when online and write that time to the RTC. The linux ntp daemon is crappy
Thanks all, Allison has confirmed my own view that 25 watts is a plenty, esp with decent speech compression.
JJ, Beckman,? Lars, Raphael and others work will be rolled in as well as the move to 64 bits.
The tough part is to simultaneously debug this on 32 bit and 64 bit.
I am using JJ's 64 bit image as the startinf point, to which I will add Lars' web UI and proceed from there. We will leave out the 10.1 inch screen for the time.
Btw, David, there is a transverter output on the board (not on the panel). We left it out as it was messing with the passive FET mixer's performance.
On Fri, Jun 14, 2024, 5:01 AM David Mitchell via <mitchedb1970= [email protected]> wrote: I think a useful feature would be to add a low level output to be used with vhf/uhf transverters.? Both ICOM and Yaesu had low level output for transverters on some models.? It could also be tied into the software with a preset offset to account for a 26 to 30 mhz to 144 or 432 conversion and give correct frequency reading on screen. ?
|
Gwen, Allison,
I dont own the SBITX, but, I usually use a proven external swr/power meter to compare to the radios internal swr/power meter for awhile until i can prove the internal meter is accurate.Its also nice to reference it during new antenna installs. Just bad habits i guess.
Personally ive seen even new radios fry because the owner thought the swr/power meter was accurate.
Just my habits. Even if you Mod something like changing finals ,etc, you should always match the readings of an internal meter to an external one to see if everything is pretty close to match.
I personally seen internal meters in Some new rigs be completely astronomically off compared to a proven calibrated external one. Just thought i would suggest this tip to help save those who mod their SBITXS and other radios from a trip to the service shop.I personally enjoy using an external one. to match up with the internal one. removing it only after ive tried the radio on all bands and all modes on the antennas i use at home. Maybe Ashhar could make an external one to hook up to not only the SBITX but the UBTIXs too.That way the meter would be a matching set with the radio.
I agree with the both of you on the touch screens. I personally dont like them or the stylus that are offered by manufacturers. I prefer a knob or slide control or a push button that brings up a menu .I also have fingers that dont operate like they should.
Gwen i read you stated u have the elekraft kx3. My friend owns one and he says he bought the 2 meter module option. have u tried it on this band or 6 meters?
73 David ac9xh
On Thursday, June 13, 2024 at 06:13:37 PM EDT, JJ - W9JES <w9jes@...> wrote:
On Thu, Jun 13, 2024 at 11:55 AM, Ashhar Farhan wrote:
I am working on the next release of the sbitx software. Some bugs will be fixed, there is a massive rewrite pending to make the code friendlier to those writing on top of the sbitx core (like JJ's excellent apps). I want to take a straw poll of what all to finish, my own list includes:
1. A better and more accurate Power meter
2. Fix the keyboard bug: it crashes when there isn't enough?space to accommodate?it on the screen.
3. A newer web UI, I saw one that was very robust, done by Lars, OZ7BX. Upgrade to this one.
4. Move to be compatible with 64-bits, use the kernel I2C driver (this will involve changing the config.txt).
5. Fix the FT8 logging to kick in later at RRR, R73 or 73. It automatically detects DUPs anyway.
6. Add AM and NBFM (will try, it is still unstable).
Anything else?
)
This apart, we are also considering the next revision of the radio, the software development is entirely independent of the hardware and it is backwards compatible with all previous versions of the radio.
For the next revision, we are considering:
1. 10.1 screen, this pulls up the power from 0.5A to 0.8A. It will impact the field ops. Should we or shouldn't we?
2. A PTT out to key the linear.
3. The 5v Regulator and the RTC to be bolted down.
4.? Higher power. How much higher should we go? At 100 watts, the entire engineering of heat dissipation will change. It may need a fan. Between 100 watts and 50 watts, it will be virtually impossible to know the difference. Between 25 watts and 100 watts, it is a one S unit difference.
5. Redesign the box to be slimmer.?
6. Higher power 5V regulator to support Raspberry 5 (for those who insist)
Anything else?
- f
As a constant tinkerer in this platform (thanks Ashhar), here is a list of items that I'd like to see in future software/hardware updates.
?
1. Fix the telnet connection handling for client disconnect crashes in remote.c.. See my fix at ? 2. Add functionality to the hamlib control set such as mode and band. Fix the responsiveness and client disconnect crash. 3. Add a TUNE button to set the rig to 5-10 watts, change mode to CW temporarily, and put the rig into TX for a user defined amount of time in seconds. 4. Rewrite the local gui to support industry standard development tools and allow modification from an external config file to change colors, scheme, boxes, etc. 5. Add reverse polarity protection at power input. 6. Add a S-METER!!!!
7. Add the 60 meter band 8. Add shielding between TX and RX stage and add shielding on 5V regulator and Pi. 9. Add additional filtering like a notch filter, noise reduction, shift, noise blanker, etc10. Add AM mode RX/TX capability 11. Add a "sub-menu for shortwave band listening since it is a general coverage receiver.
12 . A better and more accurate Power meter
13. Fix the keyboard bug: it crashes when there isn't enough space to accommodate it on the screen.?
14. A newer web UI, I saw one that was very robust, done by Lars, OZ7BX. Upgrade to this one.
15. Move to be compatible with 64-bits, use the kernel I2C driver (this will involve changing the config.txt).
16. Fix the FT8 logging to kick in later at RRR, R73 or 73. It automatically detects DUPs anyway.
17. Fix the naming convention for the log "export" function - it currently says import.
18. Fix the log refresh function for viewing the log in the radio GUI (shows duplicate 123123123. etc)
19. Remove RTTY and PSK31 modes since they don't work
20. Add TX compression and mic audio filtering/gain
21. Add a choice of a hand mic or USB mic in the gui (see my app for details)
22. Add Web TX capability from browser (I have this working and can share details)
23. Add a voice keyer (see my app in Toolbox)
A good starting point is to look at my sBitx Toolbox apps and add some of these functions into the software natively.
Thanks for your consideration,
JJ
|
Hello Farhan,
I can see a few things from using it to do POTA parks that I would like. FT8 stuff: 1. Resize?the waterfall to only show the bandwidth of the FT8 segment?when using FT8 in the native mode, the whole portion below say 14.074 is wasted space that we could spread out the water fall somewhat?on and be better able to find openings to setup?for CQ on. 2. I like the on screen keyboard but it is almost a non-issue for me. I barely ever use it since you can just touch the callsign you want to call next. 3. A simple export button to open an export screen that would allow that day's log to be exported as an adif file would be pretty sweet. 4. original 40 watts forward power would be nice too, I am using IRF520 transistors and I have played with them and they are working fine at fairly high power (55 watts into the dummyload?on 80 meters is not a problem) but I don't?know how much power the traces and circuit board?can handle... But yes, the option for 40 watts again would be nice on the days the bands are noisy... 5. A cabinet mounted fuse...doesn't?matter what kind, but it needs to be there. I build cords and put them in the cords but a cabinet mounted fuse should be in the REV4 with?a much larger reverse polarity diode so it blows the fuse instead of killing the diode... That is what I did to mine. 6. Since this is a linux machine, how hard would it be to roll in the code from the nanoVNA stuff (they use linux too) to be able to say run simple antenna analysis?stuff to check it for SWR before getting on the air? Shoot, it could be a different program you launch first then, when done, close it and run the sbitx program...just a thought. 7. The menu choice for different CW memories is only on the WEB GUI and not the GTK (I think that is what it is called) so I have to open the web gui then change the CW message?memory?to my POTA one, then close the webGUI to operate because I like the native one better. 8. Program the push button on the volume knob to open a menu that shows all the buttons on screen so you can: push the volume knob, then spin the knob to scroll down to the item, then push it again to select the item to adjust it. I don't?worry too much about the volume control when operating, but I do use the scroll feature on that knob to adjust everything I?will touch a?function and use the knob to adjust it then push the knob to return to volume or touch the volume to cancel?it so that?I don't?make accidental adjustments. That feature works so well and I love it. 9. Make the CW decoder something that can be turned off for people that dont use it. I never look at it and would rather have a wider water fall?with more data instead or the logbook in place of it. 10. Is it possible to link the AGC to the mode you are using at the time? Like set it to "off"?if you are on FT8 and "medium" on CW? I would love that if possible. Maybe it could just remember the last setting in each mode if possible? Also could we get the bandstack portion that lands on the FT8 frequency to not be USB but FT8 when it is selected? That would save a ton of time for me.
I could get really nitpicky but to be honest, these are the top 10 items I can think of after using it for many months and making a ton of contacts at local parks and in the shack with it.
Thank you for asking for input! David - WK4DS
On Thu, Jun 13, 2024 at 12:55?PM Ashhar Farhan via <farhanbox= [email protected]> wrote: I am working on the next release of the sbitx software. Some bugs will be fixed, there is a massive rewrite pending to make the code friendlier to those writing on top of the sbitx core (like JJ's excellent apps). I want to take a straw poll of what all to finish, my own list includes: 1. A better and more accurate Power meter 2. Fix the keyboard bug: it crashes when there isn't enough?space to accommodate?it on the screen. 3. A newer web UI, I saw one that was very robust, done by Lars, OZ7BX. Upgrade to this one. 4. Move to be compatible with 64-bits, use the kernel I2C driver (this will involve changing the config.txt). 5. Fix the FT8 logging to kick in later at RRR, R73 or 73. It automatically detects DUPs anyway. 6. Add AM and NBFM (will try, it is still unstable). Anything else? ) This apart, we are also considering the next revision of the radio, the software development is entirely independent of the hardware and it is backwards compatible with all previous versions of the radio. For the next revision, we are considering: 1. 10.1 screen, this pulls up the power from 0.5A to 0.8A. It will impact the field ops. Should we or shouldn't we? 2. A PTT out to key the linear. 3. The 5v Regulator and the RTC to be bolted down. 4.? Higher power. How much higher should we go? At 100 watts, the entire engineering of heat dissipation will change. It may need a fan. Between 100 watts and 50 watts, it will be virtually impossible to know the difference. Between 25 watts and 100 watts, it is a one S unit difference. 5. Redesign the box to be slimmer.? 6. Higher power 5V regulator to support Raspberry 5 (for those who insist) Anything else? - f
|
Any progress?or plans to provide ssb remote.. It works now except?for no TX audio..
VE1BWV Joe
Hello Farhan,
I can see a few things from using it to do POTA parks that I would like. FT8 stuff: 1. Resize?the waterfall to only show the bandwidth of the FT8 segment?when using FT8 in the native mode, the whole portion below say 14.074 is wasted space that we could spread out the water fall somewhat?on and be better able to find openings to setup?for CQ on. 2. I like the on screen keyboard but it is almost a non-issue for me. I barely ever use it since you can just touch the callsign you want to call next. 3. A simple export button to open an export screen that would allow that day's log to be exported as an adif file would be pretty sweet. 4. original 40 watts forward power would be nice too, I am using IRF520 transistors and I have played with them and they are working fine at fairly high power (55 watts into the dummyload?on 80 meters is not a problem) but I don't?know how much power the traces and circuit board?can handle... But yes, the option for 40 watts again would be nice on the days the bands are noisy... 5. A cabinet mounted fuse...doesn't?matter what kind, but it needs to be there. I build cords and put them in the cords but a cabinet mounted fuse should be in the REV4 with?a much larger reverse polarity diode so it blows the fuse instead of killing the diode... That is what I did to mine. 6. Since this is a linux machine, how hard would it be to roll in the code from the nanoVNA stuff (they use linux too) to be able to say run simple antenna analysis?stuff to check it for SWR before getting on the air? Shoot, it could be a different program you launch first then, when done, close it and run the sbitx program...just a thought. 7. The menu choice for different CW memories is only on the WEB GUI and not the GTK (I think that is what it is called) so I have to open the web gui then change the CW message?memory?to my POTA one, then close the webGUI to operate because I like the native one better. 8. Program the push button on the volume knob to open a menu that shows all the buttons on screen so you can: push the volume knob, then spin the knob to scroll down to the item, then push it again to select the item to adjust it. I don't?worry too much about the volume control when operating, but I do use the scroll feature on that knob to adjust everything I?will touch a?function and use the knob to adjust it then push the knob to return to volume or touch the volume to cancel?it so that?I don't?make accidental adjustments. That feature works so well and I love it. 9. Make the CW decoder something that can be turned off for people that dont use it. I never look at it and would rather have a wider water fall?with more data instead or the logbook in place of it. 10. Is it possible to link the AGC to the mode you are using at the time? Like set it to "off"?if you are on FT8 and "medium" on CW? I would love that if possible. Maybe it could just remember the last setting in each mode if possible? Also could we get the bandstack portion that lands on the FT8 frequency to not be USB but FT8 when it is selected? That would save a ton of time for me.
I could get really nitpicky but to be honest, these are the top 10 items I can think of after using it for many months and making a ton of contacts at local parks and in the shack with it.
Thank you for asking for input! David - WK4DS
On Thu, Jun 13, 2024 at 12:55?PM Ashhar Farhan via <farhanbox= [email protected]> wrote: I am working on the next release of the sbitx software. Some bugs will be fixed, there is a massive rewrite pending to make the code friendlier to those writing on top of the sbitx core (like JJ's excellent apps). I want to take a straw poll of what all to finish, my own list includes: 1. A better and more accurate Power meter 2. Fix the keyboard bug: it crashes when there isn't enough?space to accommodate?it on the screen. 3. A newer web UI, I saw one that was very robust, done by Lars, OZ7BX. Upgrade to this one. 4. Move to be compatible with 64-bits, use the kernel I2C driver (this will involve changing the config.txt). 5. Fix the FT8 logging to kick in later at RRR, R73 or 73. It automatically detects DUPs anyway. 6. Add AM and NBFM (will try, it is still unstable). Anything else? ) This apart, we are also considering the next revision of the radio, the software development is entirely independent of the hardware and it is backwards compatible with all previous versions of the radio. For the next revision, we are considering: 1. 10.1 screen, this pulls up the power from 0.5A to 0.8A. It will impact the field ops. Should we or shouldn't we? 2. A PTT out to key the linear. 3. The 5v Regulator and the RTC to be bolted down. 4.? Higher power. How much higher should we go? At 100 watts, the entire engineering of heat dissipation will change. It may need a fan. Between 100 watts and 50 watts, it will be virtually impossible to know the difference. Between 25 watts and 100 watts, it is a one S unit difference. 5. Redesign the box to be slimmer.? 6. Higher power 5V regulator to support Raspberry 5 (for those who insist) Anything else? - f
|
Scotty R
Brian - N9NAZ
Gwen Patton
WK4DS