Hi Ashhar,

With the latest (stock) code from GitHub, I lose the first dit consistently when sending with a straight key.? If I attempt to keyboard send, the rig goes into a tx/rx endless loop without sending any RF.? I have to exit from the app to stop the tx/rx looping.

On a side note, I did just verify my ui_tick mod isn’t a factor in the button text updating issue I’m experiencing with my code fork.? I’m going to go back through all my updates and figure out what broke it.?

73

Goody

K3NG

On Aug 24, 2022, at 07:38, Ashhar Farhan <farhanbox@...> wrote:

Neils,

When call cq on ft8, as multiple people can respond back, you have to click on one qso to reply back to.

I would suggest? you pull the latest changes. The latest build fixes many of the problems you pointed pit.

Are you refering to volume of the receiver or the sidetone? The rx volume can be accessed as AUDIO control. You can also tap on the function knob to move the focus to AUDIO control.

I have been using CW regularly. With a straight key as well as the keyboard. Both work well.?

On Wed, Aug 24, 2022, 4:51 PM Niels Jalling <niels@...> wrote:

After a short vacation I am back in the shack.?

I changed the IRFZ24's with a new set, adjusted bias and was ready to test.

CW first with a dummy load. Output looked good on the scope. Output 25W on 20m with 2tone signal. Began flattopping with more power. Maybe my powersupply is too small.

Then I tried sending some letters from the keyboard. The very first dot or dash was never sent. So A became T, K became A, etc.?

The K3NG mod seems to fix the keyboard cw-problem.

Then I connected a paddle. There is a timing problem too with a paddle. A short press on the can result in a very short dit or dash. Again the polling frequency is the problem. (There is something called interrupts)

Then I switched to FT8.

First issue: there is no way to turn the volume down. The T41-SDT book placed over the speaker solved this :-)

In the FT8-demo video Ashar showed how easy a qso can be. But the current software does not work that way. I tried several times and when someone answered my CQ the next steps for a QSO didn't happen.

Then for calling CQ you have to press the CQ-button (F5) for every period instead of calling CQ several times and waiting for an answer.?

de oz9ny, niels

PS The only positive: The IRFZ24 survived

After a short vacation I am back in the shack.

I changed the IRFZ24's with a new set, adjusted bias and was ready to test.

CW first with a dummy load. Output looked good on the scope. Output 25W on 20m with 2tone signal. Began flattopping with more power. Maybe my powersupply is too small.

Then I tried sending some letters from the keyboard. The very first dot or dash was never sent. So A became T, K became A, etc.

The K3NG mod seems to fix the keyboard cw-problem.

Then I connected a paddle. There is a timing problem too with a paddle. A short press on the can result in a very short dit or dash. Again the polling frequency is the problem. (There is something called interrupts)

Then I switched to FT8.

First issue: there is no way to turn the volume down. The T41-SDT book placed over the speaker solved this :-)

In the FT8-demo video Ashar showed how easy a qso can be. But the current software does not work that way. I tried several times and when someone answered my CQ the next steps for a QSO didn't happen.

Then for calling CQ you have to press the CQ-button (F5) for every period instead of calling CQ several times and waiting for an answer.

de oz9ny, niels

PS The only positive: The IRFZ24 survived

After a short vacation I am back in the shack.

I changed the IRFZ24's with a new set, adjusted bias and was ready to test.

CW first with a dummy load. Output looked good on the scope. Output 25W on 20m with 2tone signal. Began flattopping with more power. Maybe my powersupply is too small.

Then I tried sending some letters from the keyboard. The very first dot or dash was never sent. So A became T, K became A, etc.

The K3NG mod seems to fix the keyboard cw-problem.

Then I connected a paddle. There is a timing problem too with a paddle. A short press on the can result in a very short dit or dash. Again the polling frequency is the problem. (There is something called interrupts)

Then I switched to FT8.

First issue: there is no way to turn the volume down. The T41-SDT book placed over the speaker solved this :-)

In the FT8-demo video Ashar showed how easy a qso can be. But the current software does not work that way. I tried several times and when someone answered my CQ the next steps for a QSO didn't happen.

Then for calling CQ you have to press the CQ-button (F5) for every period instead of calling CQ several times and waiting for an answer.

de oz9ny, niels

PS The only positive: The IRFZ24 survived

Can someone tell me why a brass screw is used vs an iron or steel screw? I am sure this was explained years ago when these were first used but I don’t have that information.? I would think you would need iron to interact with the coil, but no science to back my thinking up.

Thanks in advance.

Dave K8WPE

David J. Wilcox’s iPad

> On Aug 23, 2022, at 8:16 AM, Craig Wadsworth <w9ctw@...> wrote:
>
> ?Getting closer.? Maybe need longer brass screw.? Thinner walls for toroid.? Outer toroid proportions look off, somehow.? Still, this is progress.?
>
>
>
>
>

.profile and .bashrc? are where you'd put commands that you want to run upon >>user login<<.??

xinput is an executable file (program) that modifies the established X windowing environment.

rather than wait until after the X environment is set up (for all users), then modifying it via xinput (just for the user pi), you could simply specify the desired configuration in the X windowing initialization process.? (these rules are usually stored in the /usr/share/X11/xorg.conf.d/ directory).

On 8/23/22 19:12, JerryP wrote:

The files, .profile and .bashrc,? are "hidden" files because they are preceded?by a '.' and usually won't be displayed in a terminal unless you use the command "ls -la". A gui file manager don't show them either unless you turn on view hidden files. You can edit the files from a terminal command prompt using "nano .bashrc". Use ctrl-x to exit after your edits to save and exit nano. I don't remember if the file manager in PI-OS shows hidden files.

On Tue, Aug 23, 2022 at 5:45 PM Scott KE8KYP <scott_massey@...> wrote:

Hi Jerry,

I'll have to find the appropriate files and add the command.? I'm really kind of green when it comes to Linux.? It sort of "feels" like DOS but different.? I never had the need to really learn it but now I need to learn a bit more.? Ol' dogs and tricks, right?

Thanks, Scott

--

Jerry, AC9NM

手中的鸟在灌木丛中值两个

Finally got a good set of PAs and a regulator. My Sbitx is up and working. Looking forward to getting the upgrade parts. Farhan Thanks
art N2AJO

Hi Jerry,

I'll have to find the appropriate files and add the command.? I'm really kind of green when it comes to Linux.? It sort of "feels" like DOS but different.? I never had the need to really learn it but now I need to learn a bit more.? Ol' dogs and tricks, right?

Thanks, Scott

Hey Ashhar (or anyone else),

I am uncertain where it would be best to add this mouse mapping to the RPI/sBitx boot sequence.? Can you make a recommendation?

Thanks, Scott