Over the weekend I dabbled in the RTTY Roundup with my Flex 6700. I really like the RTTY mode. I locked my decoder software at 2210 Hz and tuned the SSDR Panafall with the Flex Control knob. I just ran 50 watts to a vertical antenna, and I quickly figured out how strong a station had to be on the waterfall for them to hear me.
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.
73,
Mark
P.S. over the entire weekend, I never had any loss or other issues with CAT or DAX, and I am running Windows 10.
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.
73,
Mark
P.S. over the entire weekend, I never had any loss or other issues with CAT or DAX, and I am running Windows 10.
Posted 3 years ago
Good suggestions. I also jumped in and made some contacts. No issues at all here either. Operating my 6700 was very enjoyable.
Butch, contesting, say it AIN'T so. :)
Lew
N4CO
Lew
N4CO
Alex - DH2ID, Elmer
Mark, re your suggestions:
1) can't be done IMHO as FSK is hardware, but maybe the FPGA-programmers can do
something there?
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
1) can't be done IMHO as FSK is hardware, but maybe the FPGA-programmers can do
something there?
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
Regarding FSK, I would have thought that they could implement EXTFSK 'relatively' easily as an addition to CAT? EXTFSK is supported by MMTTY and DM780 (among others) for FSK RTTY operation.
Al K0VM, Elmer
FSK is clearly spelled out in the Flex hardware book - section 7.4.4. If that had said FSK will never be implemented - AFSK only, I would have never purchased the radio.
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 . . .
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 . . .
(Edited)
In my defense Walt, I was asking as an engineer vis-a-vis the original posting, what is limiting about the current implementation. This is not 1963 and not about my Collins KWM-2 where AFSK can certainly be problematic. If there is no observable difference between FSK and the current RTTY mode, then my question holds. Assume you have a black box and not privy to what occurs within. What is wrong or limiting about the mode as it is?
I agree, that if you are using an RTTY terminal and level-shifted appropriately, that an FSK implementation would be the simplest of approaches for you. For most, I believe it would not be. Many hams desire to experience AM and simply turn the knob and talk with horrendous results. They are not monitoring their signal and modulation. There was quite the flurry here over $300 headphones, and yet, you can buy an oscilloscope for much less. You mentioned Part 97, and hopefully mention of a clean signal and good engineering practices are held within.
cheers ...
W7NGA dan
San Juan Island, Wa.
I agree, that if you are using an RTTY terminal and level-shifted appropriately, that an FSK implementation would be the simplest of approaches for you. For most, I believe it would not be. Many hams desire to experience AM and simply turn the knob and talk with horrendous results. They are not monitoring their signal and modulation. There was quite the flurry here over $300 headphones, and yet, you can buy an oscilloscope for much less. You mentioned Part 97, and hopefully mention of a clean signal and good engineering practices are held within.
cheers ...
W7NGA dan
San Juan Island, Wa.
(Edited)
This discussion, for me, brings up an interesting aside. Should you desire pure FSK (even if only philosophically), what would you be using as the Baudot character source? Yes, a Teletype Model 15 or Robot 800 keyboard qualifies .. but what else? An Apple II I suppose running out of the RS-232 port and level-shifted (appropriately transmogrified from ASCII to Baudot). I've done that in the past, running to my HAL ST-6 and properly level-shifted to my Icom or Drake T4XC PTO. No timing worries and great fun .. but I didn't have a Flex 6000 series transceiver sitting on the desk or SSDR running on my PC!
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.
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.
(Edited)
Ken - NM9P, Elmer
It wouldn't need to use the external port FSK line.
They could just take the data from a virtual serial port accessed from inside a RTTY program configured for true FSK. The FSK mode in the rig would translate the data to tones using the waveform API.
They might need to define a dedicated port option for FSK in the same way that they do PTT. Or it could just be part of the CAT functions or the Ethernet data stream, configured as a virtual serial port. No external hardware needed...
Ken - NM9P
They could just take the data from a virtual serial port accessed from inside a RTTY program configured for true FSK. The FSK mode in the rig would translate the data to tones using the waveform API.
They might need to define a dedicated port option for FSK in the same way that they do PTT. Or it could just be part of the CAT functions or the Ethernet data stream, configured as a virtual serial port. No external hardware needed...
Ken - NM9P
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.
Ken - NM9P, Elmer
Yes... The same as using DSTAR or FreeDV as an API doesn't need a Dax channel to be defined. That would be a nice feature of a waveform API version of RTTY, or many other modes, too.
