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?
- 99 Posts
- 18 Reply Likes
Posted 3 years ago
- 99 Posts
- 18 Reply Likes
Chris Tate - N6WM, Elmer
- 812 Posts
- 219 Reply Likes
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
- 99 Posts
- 18 Reply Likes
Chris Tate - N6WM, Elmer
- 812 Posts
- 219 Reply Likes
- 99 Posts
- 18 Reply Likes
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?
Chris Tate - N6WM, Elmer
- 812 Posts
- 219 Reply Likes
Chris Tate - N6WM, Elmer
- 812 Posts
- 219 Reply Likes
Ria - N2RJ, Elmer
- 2276 Posts
- 917 Reply Likes
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.
- 814 Posts
- 191 Reply Likes
Is there any configuration comparison we could do to maybe figure out what might be the issue?
Kev
Ria - N2RJ, Elmer
- 2276 Posts
- 917 Reply Likes
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.
- 814 Posts
- 191 Reply Likes
I do have an unrelated thought about connecting to Log4OM during a contest. From the N1MM+ docs:
Force logging - The program tries to help you by validating what you copy as the Exchange, but if it is balking and you don;'t want to stop to figure it out, you can force logging with Ctrl+Alt+Enter. A small Note window will pop up, pre-filled with the words "Forced QSO". You can type over to remind yourself later what you copied, or simply hit Enter to log the default note.Maybe reducing some of the complexity may smooth things out. Good luck!
Kev
Ria - N2RJ, Elmer
- 2276 Posts
- 917 Reply Likes
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.
- 475 Posts
- 77 Reply Likes
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.
Tim - W4TME, Customer Experience Manager
- 9153 Posts
- 3495 Reply Likes
- 475 Posts
- 77 Reply Likes
- 814 Posts
- 191 Reply Likes
Chris Tate - N6WM, Elmer
- 812 Posts
- 219 Reply Likes
- 814 Posts
- 191 Reply Likes
Kev
Chris Tate - N6WM, Elmer
- 812 Posts
- 219 Reply Likes
- 205 Posts
- 38 Reply Likes
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
- 475 Posts
- 77 Reply Likes
Ria - N2RJ, Elmer
- 2276 Posts
- 917 Reply Likes
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.
Chris Tate - N6WM, Elmer
- 812 Posts
- 219 Reply Likes
Chris Tate - N6WM, Elmer
- 812 Posts
- 219 Reply Likes
Ria - N2RJ, Elmer
- 2276 Posts
- 917 Reply Likes
- 193 Posts
- 50 Reply Likes
Steve gw0gei / gw9j
Related Categories
-
SmartSDR for Windows
- 4858 Conversations
- 1451 Followers
Tim - W4TME, Customer Experience Manager
Douglas Maxwell
Tim - W4TME, Customer Experience Manager