Page 3 of 3

Re: testing the CW program

PostPosted: Mon Feb 09, 2015 5:48 pm
by AE9RB
kb3cuf wrote:After a few things opened, the PC crashed (no BSOD shows now, it just rebooted itself)


This is a hardware or kernel mode problem.
https://msdn.microsoft.com/en-us/librar ... 54836.aspx

Re: testing the CW program

PostPosted: Wed Feb 11, 2015 12:17 am
by camqrp
Regarding the "fuzzy" audio reported by KZ1X, I believe it's a function of the SI570, not the software. I first encountered this problem with one of my Peaberries while running HDSDR. It was a function of the spacing between the LO frequency and the Tune frequency. The farther Tune was from LO, the fuzzier the signals sounded. The closer Tune is to LO, the better the audio. Try using a signal generator and varying the spacing between the two to check it.

My solution is the cycle the power to the Peaberry off and then back on after a few seconds. Sometimes it takes a few tries at re-cycling, but it always clears up the fuzzies. I can only guess that the SI570 starts in some unstable state which can be corrected.

David - can the Element, Character and Word spacings be only used one at a time? My fist needs element and character spacing help.

Cam N6GA

Re: testing the CW program

PostPosted: Fri Feb 13, 2015 5:25 pm
by W4MMP
David,
The latest release resolved my issue of Peaberry CW not finding the Peaberry audio device(s). However I did need to alter the devices to exclusive mode. No big deal as only one application may access the Peaberry audio devices at any given time. The latency appears to be zero or near zero. I could not discern any latency by ear but this is at CW speeds of mere mortals :oops:

My wish list:
1) Alternate audio output device. My 60 yr old ears need a bit more volume and driving the default audio device to a volume I like would drive my wife nuts and end my ham radio career. This is simply a convenience as I could set the Windows default audio device to my head set that is attached to a different audio device. But switching the default device back and forth between the speaker and the headset is to be perfectly honest, a pain.
2) Remember window size between iterations.
3) RIT. This has been mentioned elsewhere.
4) Straight key option that uses the TIP (Key_0) and/or RING (Key_1). This is so that I can drive the Peaberry CW application with other applications such as CW-TYPE or an outboard electronic keyer. My particular setting up includes CW-TYPE communicating with a comm port attached to a hard keyer attached to the Peaberry key port - TIP (Key_0). This is paralleled with my electronic keyer. This arrangement allows me to use the CW-TYPE macros for sending CQ and such and then switching to the paddle for the QSO.
(If have noticed, my CW Peaberry firmware activates the TX line if either Key_0 or Key_1 goes key down.)
5) Multiple Peaberry support. I believe you have mentioned this may be coming in a future release.

Re: testing the CW program

PostPosted: Fri Feb 13, 2015 6:31 pm
by AE9RB
W4MMP wrote:4) Straight key option that uses the TIP (Key_0) ... so that I can drive the Peaberry CW application with ... an outboard electronic keyer.

Slide the keyer speed to 0(Off).

W4MMP wrote:The latency appears to be zero or near zero. I could not discern any latency by ear

Yep. With most sound cards I write directly to the DMA memory. Completely bypasses all processing by Windows. No other SDR application has latency this low.

Re: testing the CW program

PostPosted: Fri Feb 13, 2015 7:27 pm
by W4MMP
AE9RB wrote:
W4MMP wrote:4) Straight key option that uses the TIP (Key_0) ... so that I can drive the Peaberry CW application with ... an outboard electronic keyer.

Slide the keyer speed to 0(Off).

Yep. With most sound cards I write directly to the DMA memory. Completely bypasses all processing by Windows. No other SDR application has latency this low.


David,
Thanks. yes setting the keyer speed to zero (0) did the trick.

As for sound output, when Peaberry CW is set to use the internal onboard sound device (VIA) things are fine (audio quality, latency and such). When the default sound device is set to an admittedly cheap USB audio device (C-Media, I don't know the chip number), latency remains fine, but the audio wigs out after a minute or two. The best I can describe it is as a buzzing hum which is always present overlaid on the real signal which also sounds like a buzz. This is with either receive or transmit audio. The C-Media device is using the default Windows (Win 7) device driver(s) and they are up to date.

Re: testing the CW program

PostPosted: Fri Feb 13, 2015 7:35 pm
by AE9RB
W4MMP wrote:When the default sound device is set to an admittedly cheap USB audio device...

Did you try eventSpeaker=false as described in the README?

Re: testing the CW program

PostPosted: Fri Feb 13, 2015 8:03 pm
by W4MMP
AE9RB wrote:Did you try eventSpeaker=false as described in the README?


Oops, yep that did the trick.

Re: testing the CW program

PostPosted: Sat Feb 14, 2015 12:05 am
by kz1x
Wow, terrific improvements. Amazing.

Worked first time here on the i5 box.

Next needs are:

1. RX audio fix, distortion is added to the RX note as the tuning is varied from the offset frequency, along with the pitch change. Why is that?
it's an improved RX note when tuned on frequency! (Still sounds a bit weird to me, though. I AB back and forth with another radio to be sure.)
2. Place marker line in the spectrum passband --in 'zoom' mode-- according to the radio offset
3. Create a check-box option in the radio tab to make "offset equal to keyer sidetone" which then grays out the radio offset value
4. Make the 1s of Hz only selectable manually; in other words, spectrum click-to-tune varies 10s of Hz.
5. VFO focus should be a default; do not move focus off it when you change filter settings, etc.
6. Right-click in spectrum graph to enable and set VFO B
7. Toggle-click volume bar 'handle' to mute, but do not mute sidetone
8. Create 'spot' button (note, in addition to the zero beat function; some of us like to drive)

Re: testing the CW program

PostPosted: Sat Feb 14, 2015 2:14 pm
by kz1x
Oh, and, you mentioned you'd enable the TX in the next revision.
For that:

1. put a TX INHibit check box someplace (sidetone works but no RF energy)
2. put a field someplace that allows one to set the delay between the start of the RF envelope after the amp key line is toggled
3. the sidetone volume needs to be independently adjustable
4. you need a 'tune' button, which transmits a carrier (toggle button; 5 second auto timeout)
5. there needs to be an overall TX timeout function, if either the dit or dah contact closure is stuck on for more than, say, 20 seconds

Re: testing the CW program

PostPosted: Fri Oct 02, 2015 10:22 pm
by Paul NT7U
Is the Peaberry v2 and PeaberryCW 0.6 working reliably with OS X Yosemite (v10.10)?

I failed to get a bandscope using two different Macs in our house. Luckily the third Mac I tried worked (all are fast, modern, and running 10.10.5; the latest). However, sometimes it still fails and requires that I power down the Peaberry and/or disconnect the USB before being able to fire up PeaberryCW and have a live bandscope + audio out. To be honest, I've been cycling power and doing the USB plug both whenever it failed (kitchen sink approach). When it fails, the only functionality that I get is being able to change settings, frequency, and hearing the bandswitching relay upon frequency scrolling across bands. Yes, when the bandscope and audio fail, I still always am able to verify the functionality of the frequency adjustment on the hardware. Oh, and the s/w iambic keyer works too.

I thought that perhaps there was an issue with initializing the audio I/Q interface on the Mac, however, regardless of if it fails or works, when I re-open the "system report" from the "About this Mac" menu, under Audio I see that there is a "Peaberry Radio" device under the Audio "Devices" (2 input channels, 2 output channels, Mfg.: http://www.obdev.at, SampleRate 96000, transport USB). And under USB I see the expected Peaberry SDR device as well. Again, regardless of failure or success, those appear to show up the same and as expected.

When it does fail it will do so many times in a row where power and/or USB cycling doesn't fix it. I thought that perhaps unplugging the power supply from the wall and then plugging it in so that the rise time of power was slower might have given better success but I'm still not sure. Then it will start working and do so for many times in a row. Quite frustrating to try figure out. Perhaps even the power cycling isn't related and it just starts working.!? Hardware has the latest firmware installed (Apr 30 2013?) and works well with HDSDR on Windows (always fires right up)!

Btw, nice job on the program, David. So grateful for it and also happy to see that you used the fabulous QT framework. Kudos. Hopefully as more and more old-timers become SKs there will be as many who are picking up CW and cherishing it. I will say that as a 49 year old, it is gratifying to be able to do something that the young whipper-snappers aren't just picking up in a day one and able to make do more than one thought possible. So it has been since the beginning of time, I suppose, with young brains and newfangled things being "trivial" for them to master.

73, Paul NT7U