massleft.blogg.se

1. #Fldigi and signalink setup windows 10 mod#
2. #Fldigi and signalink setup windows 10 serial#
3. #Fldigi and signalink setup windows 10 drivers#
4. #Fldigi and signalink setup windows 10 software#

If you get it too high, Vara FM will tell you to turn it down. If you are failing and know you have a good signal path to the destination station, try increasing the Signalink TX control and repeat the test. So, the initial drive level must be high enough for the destination station to decode. When you click the "plug" button: A data block is sent to the destination station indicating an Autotune is in progress, using the current drive settings The drive level is then set low and a test block is sent The drive level is increased and another test block is sent This process repeats 8 more times The destination station then replies with the level that had the best S/N reading at the destination station If the first block is sent with a level that is too low, the destination station doesn't know a Autotune is in progress and ignores the rest of the blocks. Report forthcoming when I get more data, and hopefully, report that I am fully functional on HF and VHF.On Sat, at 3:49 PM Scott Currie wrote: OK, so the way Autotune works is as follows. I really just wanted to send some digital messages. I remember reading about 'phantom USB ports' in an FTDX-3000 post a few years ago. I was going to wait until I got Fldigi working on HF before tackling the VHF again, but it appears that it is all the same problem. I tried the SignaLink on another computer and the ports showed up in seconds. I tried to get my SignaLink installed again, but nothing happens when I disconnect it, change ports on the computer, scan for hardware.

Things looked more normal this time with Port3 and Port6.

#Fldigi and signalink setup windows 10 drivers#

I found the drivers that I used when my FTDX3000 was installed and tried again. MMSSTV, MMTTY, FLdigi, Ham Radio Deluxe / Digital Master 780, MultiPSK, MRP40, VARA Modem. Sound card program setup for the SignaLink USB. All was not normal, and my SignaLink ports that I use with my VHF radio were gone. In general, we have found that most communication programs that are designed to work in Windows XP also work just fine in all newer versions of Windows, including Windows 11. However, the other port was under something like WDS and required drilling down to get to the port. Under Fldigi and the computer sound settings, one port showed normally. When the radio was reconnected and powered on, the ports appeared as COM3 and COM6. The radio was disconnected during the installation.

#Fldigi and signalink setup windows 10 software#

I reinstalled the software using the file downloaded from the Yaesu site under the FTDX-10 section. I decided that I did not want to deal with extra ports and removed the drivers and the ports. I don't remember the numbers for all of the ports, but the FTDX-3000 was using Port 3 and Port4.

#Fldigi and signalink setup windows 10 serial#

When I powered on the radio, two new serial ports were created. When I setup the radio initially, I removed my FTDX-3000 and connected the FTDX-10. I know that I have the correct ports selected because I only have two of them. Something is not right with the serial ports. Fldigi is processing the message because I see it on the screen.

Last night I decided to check the PO level. I was switching to ALC to monitor my sound levels when sending and did not have any movement scale. I adjusted my Fldigi settings to match the information that Gary provided and still could not get an answer to a CQ, or get reply from a station calling CQ that I answered.

I finally realized that I have a problem worse than incorrect settings. That way you can just click the digital signal and everything aligns.

I generally like a wider bandwidth while tuning around, so the DATA-U suits me better. You still have to select RTTY in the OpMode, though. If you select RTTY using the box in the upper left corner of FLDigi, the rig will switch to RTTY mode, i.e., narrow BW with the M-S (mark/space) tuning window. Change to Data-L or RTTY-R (reverse) FYI, the RTTY decoder in the rig doesn't hold a candle to FLDigi. I found RTTY on LSB today, which is really the way it should be. FLDigi operation Packet USB = Data USB and your rig will change to that.

#Fldigi and signalink setup windows 10 mod#

Rig settings Set Radio Settings, Mode PSK/Data - Data mod source = rear Rear Select = USB AMC = 25-30 Set TX power = 100 watts Click the "Tune" button on Fldigi Adjust Windows volume, i.e., Speakers(USB Audio Codec) for 30-35 watts output. It will pick up your frequency and mode automatically. I changed mine to 38,400 Restart FLDigi to be sure. I got FLDigi up and running today as follows: Rig Control = Hamlib Use the Yaesu FT-991 rig from the list Checkmark "Use Hamlib" Checkmark "PTT via Hamlib command" Uncheck everything else Set your baud rate to the rig setting.