开云体育

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