Fsk Rtty Software For Mac
New RTTY user on Mac question #rtty#tinyfsk#mac#fldigi
Nov 26, 2019 RTTY tab, check FSK Keying Enable, the correct COM Port for keying (as above in CW) and tick the radio dial “Rigblaster PRO (TX, DTR), Icom (DTR) etc Use Center at 2210 in the Waterfall. Click the “C” in the Waterfall toolbar. Back on the Main window click on “Reverse”. This is the correct setting for operating RTTY FSK in DM780. Operating RTTY and especially RTTY contesting has quickly become my favourite facet of amateur radio. I started operating RTTY in 1984 using a Dragon 32 (6800 CPU) computer and G4BMK software and Terminal Unit. My interest then waned until 2002 when I discovered MMTTY and N1MM.
#476 I just bought a FSK MORTTY for RTTY use. It's loaded with TinyFSK. I don't currently have a RTTY setup, so I'm trying to understand what my options are. I have a Mac and an Icom IC-756PROIII. I'm OK with the hardware setup, it's the software that I'm trying to figure out. After reading a bunch of posts, here are the questions:
Thanks Rich, KD2CQ |
#477 Rich, You do need NanoIO for the current version, I have Fldigi 4.1.09.17. I could not get NanoIO with Fldigi it to work. I sent Dave a email and he sent me the .17 version and no go on that one also. I was able to put the TinyFSK sketch in MORTTY and was able use N1MM logger on RTTY. So the problem is with the NanoIO sketch. If N1MM logger is available on the Mac give it a try. I sent a post to the Fldigi and MORTTY group about 10 days ago and heard nothing until you replied. On Wed, Feb 12, 2020 at 10:03 AM Rich <rich@..> wrote: I just bought a FSK MORTTY for RTTY use. It's loaded with TinyFSK. |
#478 Just to test, I loaded nanoIO on the MORTTY and tried fldigi with it. It looked like it was working (it wasn't connected to the radio, but the red and green lights seemed to be correct). If you have a way to use a terminal emulator to connect to the MORTTY at 9600 baud, you can test it manually by issuing commands and see if the MORTTY reacts correctly. Rich On Wed, Feb 12, 2020 at 1:08 PM jerry deibel <jerrydnj@..> wrote:
|
#479 Rich, Fldigi with NanoIO was sending to MORTTY and the green light was blinking and red (PTT) solid, but it was only 1 rtty tone . My Icom 7610 was going into transmit and just putting out 1 tone of the rtty signal. Since the TinyFSK using N1MM was sending good Rtty to my Icom. To me the problem is with Fldigi. Not sure on how to use a terminal emulator to connect to the MORTTY at 9600 baud, what would that prove. Since I know the MORTTY is ok with running TinyFSK. On Wed, Feb 12, 2020 at 2:00 PM Rich <rich@..> wrote:
|
#480 >I sent a post to the Fldigi and MORTTY group about 10 days ago and heard nothing until you replied. OUCH! 'heard nothing?' I saw your posting on February 3rd and also saw the 8 responses to your post - including suggestions from Dave W1HKJ the fldigi/nanoIO developer. You last post on February 5th said you had reverted to the original sketch on your Mortty, TinyFSK, and that it was working and sending good FSK. -larry (K8UT) From: 'jerry deibel' <jerrydnj@..> Sent: 2020-02-12 13:08:29 Subject: Re: [Mortty] New RTTY user on Mac question #rtty #tinyfsk #mac #fldigi
|
#481 If the red LED is lighting in cadence with the Tx of each transmission, and the green LED is blinking rapidly during those transmissions to indicate FSK shifts, then it sounds like the software in your Mac and the hardware in your Mortty are working properly. If the radio goes into transmit when that red LED is lit, then you have PTT wired properly into your Icom 7610. Is the monitor audio is only a solid tone, then the FSK line into the radio is not wired properly _OR_ the radio is not set for FSK Digital operation. -larry (K8UT) From: 'jerry deibel' <jerrydnj@..> Sent: 2020-02-12 16:04:50 Subject: Re: [Mortty] New RTTY user on Mac question #rtty #tinyfsk #mac #fldigi
|
#482 I think the nanoIO support in fldigi is not stable at the moment. I just tried with fldigi-4.1.09.18 and it worked sometimes, but froze up frequently. The radio wasn't even connected. |
#483 Jerry, I have two Mortty’s, one for CW and the other for RTTY and I’ve seen this same problem on RTTY using TinyFSK. This usually occurs 5 minutes before a RTTY contest and is resolved 30 minutes after the contest begins. I assume you’re going through the ACC jack from the Mortty. Assuming you have Modems / TTY / nanoFSK set correctly in FLDigi and If you see the green LED flashing, then Mortty is doing its thing. Go into your Icom setting screen and make sure you have RTTY keying set for ACC. I think the default is USB on the IC 7300 but the menus are the same. 73 Gene KJ4M |
#484 Yea, David, W1HKJ, developer of Fldigi sent me a fix for it (4.1.09.17) to correct NanoIO, but it did not fix the problem. toggle quoted messageShow quoted textOn Wed, Feb 12, 2020 at 5:48 PM Rich <rich@..> wrote: I think the nanoIO support in fldigi is not stable at the moment. I just tried with fldigi-4.1.09.18 and it worked sometimes, but froze up frequently. The radio wasn't even connected. |
#485 Rich, toggle quoted messageShow quoted textI only had Flidig 4.1.09.17, so I just installed 4.1.09.18 and tried it. Same problem, when I hit connect the PTT led goes solid and green blinks on the MORTTY. The Icom 7610 goes into transmit and just a single tone. When I hit the Status button in flidig:Configure:Modem:TTY:nanoIO: I get ( ~? ) in Debug Output. When I hit the Connect button with Status button on i get ( reset ~F ~F ~F ~F ~F ~? ) in Debug Output. Jerry On Wed, Feb 12, 2020 at 6:12 PM Jerry Deibel <jerrydnj@..> wrote:
|
#487 Rich, This may not help you specifically, but may be useful to others with a Mac. I have just built a Mortty with the CW firmware. I have a Mac as well and have tested it with MacWinKeyer and FLDigi and it seems to work with those for CW emulating a WinKeyer. Not sure if you looked into CocoaModem on the mac. It also does RTTY, but I think it is sound card hardware based like a SignaLink or USB sound card in a radio. I don't see any settings that looks like it would trigger hardware..but then again I've never jumped on the RTTY band wagon. Aaron - N3MBH |
N1MM Logger+ > Setting up Gritty in a Receive-only Digital Interface window
Eminem discography mp3 torrent tpb torrent. (skit)03 - It's Ok04 - Tonite05 - 31306 - Maxine07 - Open Mic08 - Never 2 Far09 - Searchin'10 - Backstabber11 - Jealousy Woes(1997)Eminem - The Slim Shady EP01 - Intro (Slim Shady)02 - Low Down, Dirty03 - If I Had. (Original)04 - Just Dont Give A Fuck (Original)05 - Mommy06 - Just The Two Of Us (Original)07 - No One's Iller (feat. Eminem Discography(1988-2017)1Albums(1996)Eminem - Infinite01 - Infinite02 - W.E.G.O.
Gritty is a free RTTY decoding program written by Alex Shovkoplyas, VE3NEA. It is based on the technology developed for the RTTY Skimmer Server project. Although Gritty is designed to decode RTTY signals in 3 kHz of bandwidth, it also works well in narrower bandwidths such as those used in RTTY contesting. For that reason, it has become a popular “receive only” decoder since being incorporated into N1MM Logger+ in 2015. For more information on Gritty, visit the Gritty webpage at http://www.dxatlas.com/Gritty/.
These instructions will walk you through downloading and installing Gritty as well as interfacing Gritty with N1MM Logger+ to be used as a receive-only decoder. For the purpose of this tutorial, it is assumed that MMTTY is configured at DI-1, 2Tone is configured as DI1 RX Window 1 and Gritty will be configured as DI1 RX Window 2.
1. Download Gritty from Alex’s Download page at http://www.dxatlas.com/Download.asp. Look for the Gritty download link as shown in Figure 5-1.
Click the GRITTY link to download the file Gritty.zip to your hard drive.
[wpanchor id=”2″]2. Find Gritty.zip on your hard drive and extract the file Setup.exe. Run Setup.exe and Gritty will be installed on your PC at the default location C:Program Files (x86)AfreetGRITTY. (It is recommended you install Gritty in the default location because N1MM will look for it there). The actual executable program file is called Gritty.exe as shown in Figure 5-2.
Figure 5-2
3. Open N1MM Logger+. If it is not already opened, open the Digital Interface (DI-1) from the Window menu. If you have been following this Quickstart Guide and have already set up 2Tone in a receive-only window (DI1 RX Window 1), then it should be present in the Digital Interface as shown in Figure 5-3. The window with 11 in the left hand green bar is the 2Tone “DI1 RX Window 1” window, thus tagged 11 (Figure 5-3). If you have MMTTY set up as the main Digital Interface 1 (DI-1) and 2Tone set up as the Digital Interface 1 Receive Window 1 (DI1 RX Window 1), then Gritty will be configured as Digital Interface 1 Receive Window 2 (DI1 RX Window 2).
4. If you installed 2Tone at DI1 RX Window 1 and it is attached to DI-1, unattach it so that DI-1 has only one decoder showing in the DI window (Figure 5-5). (Do not close the 2Tone windows, just unattach them.) To unattach receive-only windows from the main DI window, go to the Setup menu, then to Add. RX Windows and uncheck Enable Attached RX Windows as shown in Figure 5-4. (NOTE: You must unattach receive-only windows in order to configure them. When the receive only windows are attached to the main DI window, the Setup menu is not visible for those receive windows and therefore is unavailable. Once you unattach them from the main DI window, the Setup menu then becomes available. Once you have configured your receive-only windows, you can them reattach them to the main DI window if you wish. Attaching receive-only windows reduces the amount of space taken up on your monitor.)
Figure 5-4
5. To open a receive-only window for Gritty, go to the Setup menu in the main DI window, then to Add. RX Windows and click on Open Add. RX Window (3 Avail.) as shown in Figure 5-6 below.
Figure 5-6
6. When you select to open the additional RX Window, a Setup screen should open as shown in Figure 5-7 (only the top half of the window is shown here). In the Window Type pull-down menu, select GRITTY.
7. When you choose GRITTY from the Window Type pull-down menu, you will notice at the bottom of the DI1 RX Window 2 setup screen that the path becomes populated to the location of Gritty.exe if you installed it in the default location as shown in Step 2. If you did not install it in the default location, use the Select button to navigate to the correct path to Gritty.exe. When finished, hit Save (Figure 5-8).
Figure 5-8
8. The Gritty engine and the DI1 RX Window 2 windows will open as well as another windows telling you that the windows need to be closed in order for the changes to take effect. Click OK. The Gritty engine and DI1 RX Window 2 will close, then reopen.
9. Resize and move the Gritty Engine and DI RX Window 2 so they do not overlap each other. (NOTE: Do not be alarmed at the size of the Gritty Engine window. When everything is configured, this window will be minimized because you will not need to see it during normal operations. Therefore it will not take up space on the monitor.)
Figure 5-10
10. The menu buttons across the top of the Gritty Engine are important. They are used to do things such as choose which sound card and which channel to use. One menu button is used to toggle AFC on and off. Instead of explaining each menu, I’m recommending you read the Help file to learn more about the menu options (see Figure 5-11).
11. Gritty works straight out of the box unless you run FSK with low tones or a tone pair other than 2125/2295 Hz. The only way to change the tone pair in Gritty is to edit the INI file. Here’s where it gets tricky. If you run Gritty as a stand-alone program and not within N1MM Logger+, then the INI file is called Gritty.ini. To find it, search your computer for Gritty.ini. However, when Gritty is used with N1MM Logger+, there could be several instances of Gritty (remember you can have up to 4 RX DI windows). Therefore whenever you create a DI RX Window, a new INI file gets created for that particular instance of Gritty.
In our example, we activated Gritty as the second receive-only window, or DI1 RX Window 2. Therefore the INI file for that particular instance of Gritty is named Config12.ini (DI1 RX Window 2) as shown highlighted in Figure 5-12. I purposely created a Gritty instance in DI1 RX Window 1 to show you that you could have multiple INI files depending on where you activate your receive-only Gritty windows. Notice the path to the INI files. It’s located in C:UsersUsernameAppDataRoamingAfreetProductsGRITTY.
Figure 5-12
12. To edit the Configuration INI file for your particular instance of Gritty, close Gritty if it is opened, then open the INI file in Notepad or some other text editor. If you use low tone frequencies of 1275 /1445 Hz, you will need to edit the INI file and change the entry DefaultHighTones=2295 to DefaultHighTones=1445. Then save the file. (NOTE: If you do not use low tones, there is probably no reason to edit the configuration INI files so you may skip this step and continue to step 13).
[wpanchor id=”13″]13. After you have Gritty configured, it’s time to attach all the DI windows so it makes a neater package. You could leave them unattached but it’s more efficient to attach them and makes for a more organized desktop. With the 2Tone and Gritty RX windows enabled, go to Settings menu in the main DI window (DI-1), select Add. RX Windows and click on Enable Attached RX Windows. The result is shown in Figure 5-14. The top window (11) is 2Tone, the middle window (12) is Gritty and the bottom window in the main window with MMTTY.
Figure 5-14
Now that you have all your RTTY windows configured, let’s create some messages to send during the contest. Continue on to Setup RTTY Messages.