Welcome to the new FlexRadio Community! Please review the new Community Rules and other important new Community information on the Message Board.
If you are having a problem, please check the Help Center for known solutions.
Need technical support from FlexRadio? It's as simple as Creating a HelpDesk ticket.
Need technical support from FlexRadio? It's as simple as Creating a HelpDesk ticket.
Need the latest SmartSDR and Power Genius Software?
SmartSDR v3.1.12 and the SmartSDR v3.1.12 Release Notes. | SmartSDR v2.6.2 and the SmartSDR v2.6.2 Release Notes.
SmartSDR v1.12.1 and the SmartSDR v1.12.1 Release Notes. | Power Genius XL Firmware v3.4.16. | Power Genius XL Utility v2.2.10.
SmartSDR v3.1.12 and the SmartSDR v3.1.12 Release Notes. | SmartSDR v2.6.2 and the SmartSDR v2.6.2 Release Notes.
SmartSDR v1.12.1 and the SmartSDR v1.12.1 Release Notes. | Power Genius XL Firmware v3.4.16. | Power Genius XL Utility v2.2.10.
SSDR v1.8.3 cw N1MM with emulated winkey
Douglas Maxwell
MrMember ✭✭
IARU HF Championships contest is in full swing at the moment and I thought I'd get the 6300 back out the box to see if I can contest with it yet.
Problems:
1) Cannot get SSDR Winkey to hold PTT on during transmit despite setting up a "P" port and assigning it in N1MM for slice A. I have to rely on breakin being selected and a delay of "300" @30wpm which means it's too slow to transition to rx for contesting.
2) If I'm called by gm0elp and I get "gm0" typed then hit enter then proceed to type "elp" whilst "gm0" is being sent by the winkey emulator, the sidetone audio cuts when I hit the remaining callsign keys. A real pest as I'm a slow typer and make most qsos this way. I cannot tell if it affects the tx, but loads of stns repeating their call after my garbled?? return.
3) I can see stns on the spectrum scope than I can't hear. I can see that weak stations are calling me, but cannot hear them. I find playing with the RIT as little as 20Hz helps some of the time.
This could be all finger trouble on my behalf, but I seem to remember the same problems with 1.6.21 and 1.7.3 ? Anyone have any advice?
Problems:
1) Cannot get SSDR Winkey to hold PTT on during transmit despite setting up a "P" port and assigning it in N1MM for slice A. I have to rely on breakin being selected and a delay of "300" @30wpm which means it's too slow to transition to rx for contesting.
2) If I'm called by gm0elp and I get "gm0" typed then hit enter then proceed to type "elp" whilst "gm0" is being sent by the winkey emulator, the sidetone audio cuts when I hit the remaining callsign keys. A real pest as I'm a slow typer and make most qsos this way. I cannot tell if it affects the tx, but loads of stns repeating their call after my garbled?? return.
3) I can see stns on the spectrum scope than I can't hear. I can see that weak stations are calling me, but cannot hear them. I find playing with the RIT as little as 20Hz helps some of the time.
This could be all finger trouble on my behalf, but I seem to remember the same problems with 1.6.21 and 1.7.3 ? Anyone have any advice?
0
Leave a Comment
Categories
- 70 Community Topics
- 1.9K New Ideas
- 120 The Flea Market
- 5.4K Software
- 4.9K SmartSDR for Windows
- 35 SmartSDR for Maestro and M models
- 87 SmartSDR for Mac
- 144 SmartSDR for iOS
- 150 SmartSDR CAT
- 69 DAX
- 279 SmartSDR API
- 7.1K Radios and Accessories
- 5.8K FLEX-6000 Signature Series
- 557 Maestro
- 14 FlexControl
- 723 FLEX Series (Legacy) Radios
- 153 Power Genius Products
- 119 Power Genius XL Amplifier
- 12 Power Genius Utility
- 22 Tuner Genius
- 41 Shack Infrastructure
- 22 Networking
- 89 Remote Operation (SmartLink)
- 50 Contesting
- 128 Peripherals & Station Integration
- 62 Amateur Radio Interests
- 405 Third-Party Software
Comments
Hi Doug, The flex programming team is in the process of working on some of these issues as we speak. another (the break in or MOX on ptt) is targeted for remediation in the nearish future One possible solution to get you through IARU would be to move to a hardware winkeyer I discovered that to work well but some issues remain with the lead character.
Feel free to contact me off list if you want further contest related guidance in this regard, I realize these can be frustrating issues. I should be back at my home QTH in W6 Monday.
Chris
N6WM -- ZF2CT
Sometimes it will just fail to send CW. N1MM+ will apparently get the keypress and no CW would come out. Could be a N1MM+ problem though.
Sometimes I stop CW mid-stream and try to send CW again only to get the tail end of what I was sending before.
Sometimes I will get a bust of 150wpm CW (sounds like it to me). I'm guessing this is a buffer emptying itself.
I might switch back to serial port CW, even with a real serial port interface. However I'm hoping Flex will figure it out so I can keep the cabling simple which is one of the things I love about the whole system.
Is there any configuration comparison we could do to maybe figure out what might be the issue?
Kev
Com7 is for WSJT-X. I always keep it monitoring a slice except when contesting.
Com8 and Com9 are for my regular log (Log4OM). This way if I work, say, a DX station in sweepstakes I can just dump them in the regular log since N1MM+ won't log them.
Com10 and Com11 are CAT ports for N1MM+
Com12 is WinKey
Com13 is OTRSP
Com14 I forgot what it was. Maybe I should get rid of it.
Com15 is PTT
Com5 and Com6 are physical ports to bandswitch my amp. They'll be going away with 1.10.
I followed the K9CT instructions to a T.
I do have an unrelated thought about connecting to Log4OM during a contest. From the N1MM+ docs: Maybe reducing some of the complexity may smooth things out. Good luck!
Kev
If this is not a bug, I have a feeling RF is getting in and mucking with something, but nothing else seems amiss. I have common mode chokes and all transmit antennas are at least 100ft away from the house. So it's pretty baffling. Maybe I'll run a few non-contest pileups on different bands and powers and see if I can reproduce it.
I'm not going to jump to the conclusion that Logger+ is to blame, but it's pretty clear it could either avoid the problem by use of a watchdog timer or provide a reset button. Now with that said, I'll also point out that I suspect RFI to be part of the problem. And if it is RFI related I also think the problem is very close to the Flex, not the computer running Logger+ or SmartSDR CAT. The reason I suspect this is that the problem happened much more often on 15m than any other band. But then again, I've also seen it happen when transmitting at only 1watt. I apologize for the conflicting information, but it's all I have.
A year or so ago and a few SmartSDR releases back I had nearly this CAT winkeyer hanging problem with HRD's DM780. It was far to easy to get it to cause the hang. But at that same time Logger+ was working flawlessly. For the record, I'm currently running SmartSDR 1.9.13.173.
Pressing 'ESCAPE' would sort this and I could then press function keys and transmit but it was pretty annoying and happened quite frequently (probably 1 in every 10 TXs)
In my mind this seems to have started only on the latest version of N1MM and I didn't notice it during previous CW contests with SSDR v1.9 but I may be wrong?
73 Phil M0VSE
When I call CQ using N1MM+ it would send the winkey command but SmartSDR would turn off the sidetone until the next keypress. That is not that big of a deal but it's somewhat mentally disruptive since I expect to hear the CQs.
I'm wondering if anyone has had that issue and what was done to resolve it.
I can send the .MC files if you want.
Kev
I'm on the latest beta here and the original problem that I reported 7 months ago is still stopping me using the 6300 for contesting. Here is a copy of the original post:
"1) Cannot get SSDR Winkey to hold PTT on during transmit despite setting up a "P" port and assigning it in N1MM for slice A. I have to rely on breakin being selected and a delay of "300" @30wpm which means it's too slow to transition to rx for contesting."
Try turning your key speed down and listen to the rx in between sent words (according your delay setting). This is called break-in. Why is it happening when N1MM+ is telling the 6300 to be in constant tx whilst sending a message?