Three things I would like to see added, but the setup works well as is.
1) FSK operation
2) Extend the lines marking the RTTY tone pair into the waterfall display. Often I was tuning to where a station last transmitted and there was no activity on the spectrum display.
3) Add the ability for the operating frequency to stay centered on the screen with the display moving, or
Add the ability to shift the screen so that the operating frequency is near one edge. Here's how I see that working: I started out at the low end of the stations calling CQ. I would tune up to the next station and work them, then tune up to the next station. Once I neared the right side of the display, I would grab the spectrum display and slide it so the operating frequency was near the left side of the screen so I could see the stations above me.
P.S. over the entire weekend, I never had any loss or other issues with CAT or DAX, and I am running Windows 10.
1) can't be done IMHO as FSK is hardware, but maybe the FPGA-programmers can do
2) Very good idea, should be easy to program into SmartSDR.
3) My words ;-) Shoud be made optional and would greatly improve working with digimodes...
73, Alex DH2ID
So I vote to implement the FSK pin as per the hardware specs..
I do not see why I cannot have Flex live up to the radios specs and shift the transmit carrier 170 Hertz. I mean, geeze . . 170 Hertz is all I am asking for,
And please make sure that those who love AFSK are still allowed to send tones through DAX to get a signal on the air. Their preferences should be protected also. It does not have to be either / or.
I think the implied comment about what skills a "modern-day-ham" has is quite inappropriate to this forum. Everyone on here has a right to operate the radio in whatever fashion they wish under part 97.
All I ask for is that Flex honor the published specs for FSK within some software version of the future. If Flex thinks I am asking for too much, they can so state on here or send me a private email and I will not bring this up again.
And for what it is worth, I would use my RTTY terminal and send ASCII characters to it and have it produce the actual FSK. I would not use comport RTS/DTR pins due to timing issues.
Cheers - I think . . .
I used Writelog with the MMTTY plug-in. I don't know if many are aware of it but the Author of Writelog created a Driver to replace the CAT and mostly DAX. In addition you can run split without going in an changing any audio device settings. You can also run SO2V.
WlFlexDriver1201L3.exe (2015/12/26) This is a WriteLog rig driver for the FlexRadio 6000 series rigs. With this rig driver WriteLog reads and controls Flex 6000 series rigs without need for the Flex SmartSDR CAT control and virtual COM ports and Kenwood TS-2000 rig emulation, etc. This rig driver is compatible with all WriteLog versions since 11.01. But WriteLog 11.27 and later recognize additional interfaces in this rig driver that simplify WriteLog’s display of the Flex rig discovery results as well as certain error conditions.
I don't want to hear that N1MM does this or that. I am only talking about Writelog. N1MM is a very good program but this is not the place to do a "mine is better than yours".
I suspect most people will run SSDR and their RTTY software on the same computer. It doesn't make a whole lot of sense to have to run a cable from the computer to the FSK input on the Flex. I can see where doing FSK via a virtual serial port may have some timing issues.
I like the idea of sending characters to the radio, rather than tones. I see this as similar to CWX, except for RTTY. FWIW, the only radio I know of that can send RTTY based on a character input are the K3 and KX3.
The next question is if they do implement a RTTY encoder in the radio, should there also be a RTTY decoder? Would a decoder running in the SDR processes in the radio be more accurate or sensitive than something running on audio tones (or DAX versions of them)?
Thank FRS :-)
Mark, re for tuning RTTY, I did wonder about extending those tone markers, but I did find during the Round-Up that using the mouse I could double click fairly accurately on the center of the high tone remnants on the waterfall, where ever it may be and be close enough for FLDIGI to decode. I usually have the spectrum width set so that the two tone markers are about 6 or 7mm apart, works for my myopic eye sight on a 21inch monitor.
Mark .. I believe you have misunderstood the issue. There would be no encoder (or decoder hopefully) as you mentioned, but the FSK pin on the ACC connector that shifts between two frequencies based on a logic-level at the FSK pin. You would have to provide the Baudot serial data-stream to that pin, carefully level-shifted to 3.3v (whatever is spec'd) logic levels.
Things may have changed but in AFSK using DAX you have to bother with going into the DAX control panel to designate which slice to use for TX. Now lets say you have multiple slices open on different bands.....you want to jump to another slice to work a multiplier.....you have to change your DAX TX setting.....then go work him....change it back...go back to the run band.
With FSK the TX slice would not have to deal with the DAX TX setting. You would just transmit FSK on whatever slice has the TX flag active. Dax would only be in play on RX. Much easier and much less cumbersome.
I think the same applies to working split on the same band.
My only suggestion is to be able to set that the slice stay fixed and slide the panafall under it (selectable).
BTW - Did anyone else notice that FLDIGI is now 'Open Source'? Sounds like another Waveform API application, to me.
If FRS could make the FSK interface (Or maybe a way to sample RF / IF data inside the Waveform API, we could really have some fun).
Just my $0.02
73's de Mike