¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io
Date

Re: Slows down, then freezes

 

Try ferrite¡¯s on usb cable and or a higher quality USB cable.?


Re: Slows down, then freezes

 

You using a mouse or touch pad?
--

73
Karl
KI4ZUQ


Re: Slows down, then freezes

Mike Black
 

Does it behave if you lower power all the way down?

Mike W9MDB

On Monday, September 16, 2024 at 05:25:49 PM CDT, Jay W6CJ via groups.io <lastradioman@...> wrote:





Group-
IC-7300 & Win-11 PC.
FLRIG is controlling the 7300 & FLDIGI.
25 watts, or lower output.
Single USB connection between 7300 & PC.

I start an Olivia CQ, and part way into the CQ the waterfall slows down then freezes and the PTT stays on, although no RF is going out.

My audio levels are OK on test tone and all modes.??
My IC-7300 is set the way I want - for FLDIGI, JS8 and other modes.

Can someone suggest FLRIG and FLDIGI settings to try?

Thanks & 73
Jay
W6CJ


Slows down, then freezes

 

Group-
IC-7300 & Win-11 PC.
FLRIG is controlling the 7300 & FLDIGI.
25 watts, or lower output.
Single USB connection between 7300 & PC.

I start an Olivia CQ, and part way into the CQ the waterfall slows down then freezes and the PTT stays on, although no RF is going out.

My audio levels are OK on test tone and all modes.??
My IC-7300 is set the way I want - for FLDIGI, JS8 and other modes.

Can someone suggest FLRIG and FLDIGI settings to try?

Thanks & 73
Jay
W6CJ



Re: flrig 2.0.05.75 alpha release

 

On Mon, Sep 16, 2024 at 03:18 PM, Mike Black wrote:
Click the Activate button and increase the timeout to 500ms
Ooh, I think that may have fixed it. No errors so far. I'll keep playing with it.
?
Thanks Mike!
?
Steve K4RVA


Re: flrig 2.0.05.75 alpha release

Mike Black
 

Click the Activate button and increase the timeout to 500ms


Mike W9MDB

On Monday, September 16, 2024 at 04:13:04 PM CDT, Steve K4RVA via groups.io <k4rva@...> wrote:





Hey David,

?

I've been trying 2.0.05.75 for a few hours, and I'm still getting read errors. Seems to happen when I'm not touching the flrig controls, when I adjust the frequency with the mouse wheel, and also when I send Kenwood commands either via one of the 'Command' buttons or from the 'Send' dialog. Example: FA00028400000;MD2;NB0;

?

Windows 10 Home 22H2 19045.4894 (just updated itself last night)

Prolific USB-to-serial adapter (allegedly authentic)

Kenwood TS-570DG

?

Attaching photos of the errors and of my flrig config. groups.io didn't like me adding inline photos a moment ago.

?

Cheers,

Steve K4RVA


Re: flrig 2.0.05.75 alpha release

 

Hey David,
?
I've been trying 2.0.05.75 for a few hours, and I'm still getting read errors. Seems to happen when I'm not touching the flrig controls, when I adjust the frequency with the mouse wheel, and also when I send Kenwood commands either via one of the 'Command' buttons or from the 'Send' dialog. Example: FA00028400000;MD2;NB0;
?
Windows 10 Home 22H2 19045.4894 (just updated itself last night)
Prolific USB-to-serial adapter (allegedly authentic)
Kenwood TS-570DG
?
Attaching photos of the errors and of my flrig config. groups.io didn't like me adding inline photos a moment ago.
?
Cheers,
Steve K4RVA


Re: flrig v2.0.05 has a problem setting 2 stop bits

Nico
 

I tried flrig 2.0.05.75 on linux and I selected FT-747GX. When I try to initialize it freezes the radio. I have to turn it off and on again to unfreeze it. I also checked fldigi and this doesn?t happend with FT-747GX selected. Is there any way to hardcode the 2 stop bits on the windows version to check it? maybe I could use a microcontroller to capture the UART frames and re transmit them with 2 stop bits.


flamp version 2.2.14 posted at

 

¿ªÔÆÌåÓý


Index of /files/flamp

See readme.txt for list of changes.

73, David, W1HKJ
??? Robert, KK5VD



Re: flrig v2.0.05 has a problem setting 2 stop bits

Nico
 

Same result, it still isn?t sending the 2 stop bits. I noticed it says "DCB.StopBits 0" I guess it should say "DCB.StopBits 2". Also, it says "expected 28 bytes" but the radio sends 345 bytes.
Here is the trace log:
?
16:19:17.589 : closeRig()
16:19:17.589 : close serial port
16:19:17.589 : clear frequency list
16:19:17.589 : initialize title bar
16:19:17.589 : start tranceiver serial port
16:19:17.968 : I: OpenPort: Open Comm port //./COM7 ; hComm = 1160

16:19:17.968 : Open Comm port //./COM7 ; hComm = 1160
16:19:17.968 : Open Comm port //./COM7 ; hComm = 1160
16:19:17.983 : I: ConfigurePortA:?
Set Comm State:
DCB.DCBlength ? ? ? 28
DCB.Baudrate ? ? ? ?4800
DCB.ByteSize ? ? ? ?8
DCB.Parity ? ? ? ? ?0
DCB.StopBits ? ? ? ?0
DCB.Binary ? ? ? ? ?1
DCB.fDtrControl ? ? 1
DCB.fRtsControl ? ? 1
DCB.fDsrSensitivity 0
DCB.fParity ? ? ? ? 0
DCB.fOutX ? ? ? ? ? 0
DCB.fInX ? ? ? ? ? ?0
DCB.fNull ? ? ? ? ? 0
DCB.XonChar ? ? ? ? 17
DCB.XoffChar ? ? ? ?19
DCB.fAbortOnError ? 0
DCB.fOutxCtsFlow ? ?0
DCB.fOutxDsrFlow ? ?0

16:19:17.983 :?
Set Comm State:
DCB.DCBlength ? ? ? 28
DCB.Baudrate ? ? ? ?4800
DCB.ByteSize ? ? ? ?8
DCB.Parity ? ? ? ? ?0
DCB.StopBits ? ? ? ?0
DCB.Binary ? ? ? ? ?1
DCB.fDtrControl ? ? 1
DCB.fRtsControl ? ? 1
DCB.fDsrSensitivity 0
DCB.fParity ? ? ? ? 0
DCB.fOutX ? ? ? ? ? 0
DCB.fInX ? ? ? ? ? ?0
DCB.fNull ? ? ? ? ? 0
DCB.XonChar ? ? ? ? 17
DCB.XoffChar ? ? ? ?19
DCB.fAbortOnError ? 0
DCB.fOutxCtsFlow ? ?0
DCB.fOutxDsrFlow ? ?0
16:19:17.983 : I: SetCommunicationTimeouts:?
============ ? ? COMM TIMEOUTS ? ? ================
Saved Read Interval Timeout............... -1
Saved Read Total Timeout Multiplier....... 0
Saved Read Total Timeout Constant Timeout. 0
Saved Write Total Timeout Constant........ 0
Saved Write Total Timeout Multiplier...... 0
===================================================
Set Read Interval Timeout................. -1
Set Read Total Timeout Multiplier......... -1
Set Read Total Timeout Constant Timeout... 1
Set Write Total Timeout Constant.......... 0
Set Write Total Timeout Multiplier........ 0
===================================================
16:19:17.983 :?
============ ? ? COMM TIMEOUTS ? ? ================
Saved Read Interval Timeout............... -1
Saved Read Total Timeout Multiplier....... 0
Saved Read Total Timeout Constant Timeout. 0
Saved Write Total Timeout Constant........ 0
Saved Write Total Timeout Multiplier...... 0
===================================================
Set Read Interval Timeout................. -1
Set Read Total Timeout Multiplier......... -1
Set Read Total Timeout Constant Timeout... 1
Set Write Total Timeout Constant.......... 0
Set Write Total Timeout Multiplier........ 0
===================================================
16:19:18.005 : D: startXcvrSerial:?
Serial port:
? ? Port ? ? : COM7
? ? Baud ? ? : 4
? ? Stopbits : 2
? ? Retries ?: 2
? ? Timeout ?: 50
? ? Loop ? ? : 500
? ? RTSCTS ? : 1
? ? CATptt ? : 0
? ? RTSptt ? : 0
? ? DTRptt ? : 0
? ? RTS+ ? ? : 0
? ? DTR+ ? ? : 1

16:19:18.005 : initialize transceiver
16:19:18.037 : selrig->initialize()
16:19:18.037 : init_rig()
16:19:18.037 : selrig->check()
16:19:18.037 : WriteBuffer: ?00 00 00 00 10
16:19:18.121 : 1: ReadBuffer3 [69.08 msec] (0):?
16:19:18.121 : E: ReadBuffer: ReadBuffer4 FAILED [69.08 msec], read 0 bytes, expected 28 bytes
16:19:18.121 : 2: ReadBuffer4 FAILED [69.08 msec], read 0 bytes, expected 28 bytes
16:19:18.137 : FAILED


Re: flrig v2.0.05 has a problem setting 2 stop bits

Mike Black
 

Try this version...there was a change that removed the 0xFA



Mike W9MDB

On Monday, September 16, 2024 at 09:53:53 AM CDT, nico-florio@... <nico-florio@...> wrote:





Yes, I did click on the save button. There is definitely an issue with the windows version of FLRIG 2.0.05. FLDIGI does work with the FT747. It changes frequencies but it also fails with the init button. I think it fails to initialize because it sends a wrong opcode to the radio. It sends 0xFA and that opcode does not exist. I?m guessing what it?s trying to do is to send 0x10 which is to get the status of the radio. But I?m not sure.


Re: flrig v2.0.05 has a problem setting 2 stop bits

 

¿ªÔÆÌåÓý

suggest you try the latest development release which was posted this morning at



Note this is NOT a secure URL.? If you allow your browser to force https you will be transported to another world.

David

On 9/16/24 09:53, nico-florio@... wrote:

Yes, I did click on the save button. There is definitely an issue with the windows version of FLRIG 2.0.05. FLDIGI does work with the FT747. It changes frequencies but it also fails with the init button. I think it fails to initialize because it sends a wrong opcode to the radio. It sends 0xFA and that opcode does not exist. I?m guessing what it?s trying to do is to send 0x10 which is to get the status of the radio. But I?m not sure.


Re: flrig v2.0.05 has a problem setting 2 stop bits

 

Yes, I did click on the save button. There is definitely an issue with the windows version of FLRIG 2.0.05. FLDIGI does work with the FT747. It changes frequencies but it also fails with the init button. I think it fails to initialize because it sends a wrong opcode to the radio. It sends 0xFA and that opcode does not exist. I?m guessing what it?s trying to do is to send 0x10 which is to get the status of the radio. But I?m not sure.


Re: Double-clicking setup.exe does nothing

 

I use 7-zip all the time...but my action of choice is to
right click the file in the Windows file manager
from the context menu...with options created by installing 7-zip...
...I choose...
Extract to "name_of_zip_file"
That is the fastest for me. Then I rename the resulting dir if I want it renamed...and in this case, I suspect you do.
The other recommendations about fldigi config directory and files is ~exactly~ why I never install any fl_suite program, but always unzip. I have spent far too much time with hams trying to debug the mess they created by installing, removing, etc., unaware that they were contributing to their problems. Then follow the other suggestions of Tobias.

~R~


Re: Double-clicking setup.exe does nothing

 


Bill,

Just like Rich wrote, if setup doesn't run as expected (and provided you have downloaded the correct FLdigi setup file!) it may make more sense to extract (unzip) it directly into the new folder of your choice.


Then you can:

1. First verify that the setup file is complete.

2. See exactly what you put where.

3. Then run the fldigi.exe from your (new) folder and see what happens. Normally, you should be OK now.


Please take a look at the attached screenshot:

If you don't have/use it already, I highly recommend to download the lightweight, versatile and free 7zip archive manager from 'www.7-zip.org'.

With it, you can open the setup file just like an ordinary zip file, which is what I show in the attached screenshot.

Either drag the 'fldigi...setup.exe' onto '7zFM.exe' (see below) or, if you have setup 7zip this way, use the context menu (or right click) in the Explorer and then, with your FLdigi setup file selected, choose 7zip > Open archive.

In 7zip, once you have the setup file opened, first click the 'test' icon to see whether the archive as such is OK. This is *not* a malw./vir. check (!), it simply tests the archive data integrity. 7zip may or may not check and find issues in the file while opening it, so this extra check is useful.

The 7zip File Manager (7zFM.exe) can be setup to display 2 windows side-by-side, as shown here.

There simply select all the program files and folders contained in the setup file and (if you have entered the path of the target folder on the right side, as shown here), click the 'Copy' icon and the files are extracted into your chosen folder. Alternatively, you may also drag the selection into the right window or into a separate explorer window showing the target folder.

Then run FLdigi as usual and all should work as expected. From this point onward, the 7zip window is no longer needed.


Notes:

1. If all looked OK so far but the FLdigi program window still does not open, consult the Windows 'Task Manager' (Ctrl+Shift+Esc) and look for fldigi.exe in the 'Process' tab. If it is visible there (possibly multiple times: sort the list it by name clicking the respective header!), close all these previous instances and run FLdigi from your new folder again.

2. If FLdigi still won't open, you may try and locate existing data and settings from an (old) installation, usually in 'C:\Users\<UserName>\fldigi.files'. If this folder exists, close all fldigi instances (as described in 1.) and rename the 'fldigi.files' folder into something else, e.g. '_BACKUP_fldigi.files' (you may wish to keep it in case you still have useful data there). Then run Fldigi again - now there's no reason why it should fail. FLdigi will recreate the 'fldigi.files' folder with default values. Then copy what you still need from the _BACKUP_ into the new fldigi.files folder and you're all set. Once complete, you can remove the _BACKUP_ folder. If this method did not work either, I'm afraid I don't have an explanation or advice.

3. Should you wonder, no, not every app ('exe') can be opened this way as an archive. But the fldigi setup for Windows is compatible with this operation.


Hope this helps. Good luck!

And please let us know whether (and if so, how) you were successful.


73s
Tobias
.-.-.
Am Montag, 16. September 2024 um 05:14:29 MESZ hat Bill Wiltschko <bill@...> Folgendes geschrieben:


I set up a folder on my C:\ drive called FL_APP, saved the fldigi-4.2.05_setup.exe file to that folder, and double-clicked it.? I get a window asking me to login as Administrator, which I do, after which nothing happens.? No dialogs at all, no files saved anywhere.? The same thing happens when I right-click the setup.exe file and "Run as Administrator".?? I haven't seen this (non) behavior with any other setup.exe file I have ever run.? I checked the manual and online messages.? Can anyone help?
Bill, KJ6PN


Re: flrig v2.0.05 has a problem setting 2 stop bits

Mike Black
 

Can you test WSJT-X-Improved to see if it works with the FT747?



Then we can compare debug logs.

Or if you contact me off-list maybe we can hook up using AnyDesk and do some debugging.

Mike W9MDB

On Monday, September 16, 2024 at 05:13:41 AM CDT, nico-florio@... <nico-florio@...> wrote:





Hi, yes. Changing them makes no difference. I also noticed that it does not detect the FT-747 because it sends an instruction that the radio does not recognize. The instruction is 0xFA.


Re: flrig v2.0.05 has a problem setting 2 stop bits

 

Last night I re-installed FLRIG 2.0.05 freshly downloaded from Sourceforge. It installed and controls FLDIGI correctly, to operate an IC7300.

I don't think that the "problem" resides in the two programs themselves. Be sure that -after setting the stop bit 2- you go to the bottom of that screen and choose SAVE or INITIATE.

Also, on the FLDIGI Configure tab there is an option to SAVE SETUP.

73
Bill K2TNO?

On Sun, Sep 15, 2024, 11:14?PM nico-florio via <nico-florio=[email protected]> wrote:
Hi,
?
I?m using flrig v2.0.05 with a Yaesu FT-747 and it doesnt work. Upon further debuggin with a logic analyzer I found out that it does not set 2 stop bits. How can I solve this issue? I?ll attach a trace debug generated by flrig. Thanks!
?
12:50:23.300 : closeRig()
12:50:23.300 : close serial port
12:50:23.378 : clear frequency list
12:50:23.378 : initialize title bar
12:50:23.378 : start tranceiver serial port
12:50:23.532 : I: OpenPort: Open Comm port //./COM7 ; hComm = 988
?
?
12:50:23.532 : Open Comm port //./COM7 ; hComm = 988
?
12:50:23.532 : Open Comm port //./COM7 ; hComm = 988
?
12:50:23.547 : I: ConfigurePortA:?
Set Comm State:
DCB.DCBlength ? ? ? 28
DCB.Baudrate ? ? ? ?4800
DCB.ByteSize ? ? ? ?8
DCB.Parity ? ? ? ? ?0
DCB.StopBits ? ? ? ?0
DCB.Binary ? ? ? ? ?1
DCB.fDtrControl ? ? 1
DCB.fRtsControl ? ? 1
DCB.fDsrSensitivity 0
DCB.fParity ? ? ? ? 0
DCB.fOutX ? ? ? ? ? 0
DCB.fInX ? ? ? ? ? ?0
DCB.fNull ? ? ? ? ? 0
DCB.XonChar ? ? ? ? 17
DCB.XoffChar ? ? ? ?19
DCB.fAbortOnError ? 0
DCB.fOutxCtsFlow ? ?0
DCB.fOutxDsrFlow ? ?0
?
?
12:50:23.547 :?
Set Comm State:
DCB.DCBlength ? ? ? 28
DCB.Baudrate ? ? ? ?4800
DCB.ByteSize ? ? ? ?8
DCB.Parity ? ? ? ? ?0
DCB.StopBits ? ? ? ?0
DCB.Binary ? ? ? ? ?1
DCB.fDtrControl ? ? 1
DCB.fRtsControl ? ? 1
DCB.fDsrSensitivity 0
DCB.fParity ? ? ? ? 0
DCB.fOutX ? ? ? ? ? 0
DCB.fInX ? ? ? ? ? ?0
DCB.fNull ? ? ? ? ? 0
DCB.XonChar ? ? ? ? 17
DCB.XoffChar ? ? ? ?19
DCB.fAbortOnError ? 0
DCB.fOutxCtsFlow ? ?0
DCB.fOutxDsrFlow ? ?0
?
12:50:23.547 : I: SetCommunicationTimeouts:?
============ ? ? COMM TIMEOUTS ? ? ================
Saved Read Interval Timeout............... -1
Saved Read Total Timeout Multiplier....... 0
Saved Read Total Timeout Constant Timeout. 0
Saved Write Total Timeout Constant........ 0
Saved Write Total Timeout Multiplier...... 0
===================================================
Set Read Interval Timeout................. -1
Set Read Total Timeout Multiplier......... -1
Set Read Total Timeout Constant Timeout... 1
Set Write Total Timeout Constant.......... 0
Set Write Total Timeout Multiplier........ 0
===================================================
?
12:50:23.547 :?
============ ? ? COMM TIMEOUTS ? ? ================
Saved Read Interval Timeout............... -1
Saved Read Total Timeout Multiplier....... 0
Saved Read Total Timeout Constant Timeout. 0
Saved Write Total Timeout Constant........ 0
Saved Write Total Timeout Multiplier...... 0
===================================================
Set Read Interval Timeout................. -1
Set Read Total Timeout Multiplier......... -1
Set Read Total Timeout Constant Timeout... 1
Set Write Total Timeout Constant.......... 0
Set Write Total Timeout Multiplier........ 0
===================================================
12:50:23.563 : D: startXcvrSerial:?
Serial port:
? ? Port ? ? : COM7
? ? Baud ? ? : 4
? ? Stopbits : 2
? ? Retries ?: 2
? ? Timeout ?: 50
? ? Loop ? ? : 500
? ? RTSCTS ? : 1
? ? CATptt ? : 0
? ? RTSptt ? : 0
? ? DTRptt ? : 0
? ? RTS+ ? ? : 0
? ? DTR+ ? ? : 1
?
?
12:50:23.563 : initialize transceiver
12:50:23.563 : selrig->initialize()
12:50:23.563 : init_rig()
12:50:23.579 : selrig->check()
12:50:23.579 : WriteBuffer: ?00 00 00 01 FA
12:50:23.663 : 1: ReadBuffer [69.07 msec] (0):?
12:50:23.663 : E: ReadBuffer: ReadBuffer FAILED [69.07 msec], read 0 bytes
?
12:50:23.663 : 2: ReadBuffer FAILED [69.07 msec], read 0 bytes
12:50:23.679 : FAILED


Re: flrig v2.0.05 has a problem setting 2 stop bits

 

I can do the testing for the Yaesu FT-80C or the FT-747 because they are almost the same and I have the 80C. I forgot to mention that the issue of the stop bits happens only in the windows version. I have tested the linux version and it does not have that issue. But both versions have the issue that they do not recognize the radio. Do I have to send Dave a message or will he read this messages? Thanks!


Re: flrig v2.0.05 has a problem setting 2 stop bits

Cliff
 

¿ªÔÆÌåÓý

Ok, well hopefully Dave will be able to check the code and find the issue. One of the big challenges is that he does not have any way of actually testing on many of the rigs to verify the code.

73,
Cliff, AE5ZA



On Sep 16, 2024, at 05:13, nico-florio via <nico-florio@...> wrote:

Hi, yes. Changing them makes no difference. I also noticed that it does not detect the FT-747 because it sends an instruction that the radio does not recognize. The instruction is 0xFA.


Re: Double-clicking setup.exe does nothing

 

I never install it, because of the way I use it. Installations always result in conflicts with the constant changes I make to my systems. I unzip, and run from there.
I wondered at the choice of FL_APP, because that suggests you are thinking of FL_APPS....for the portable installation.
Sorry to say I don't have a clue about why 4.2.05 would do this.
You should not have to log in as admin.
Did you download from

*** Note http, NOT https !
What Windows version?
I imagine that even if, as I have seen on occasion, the install window winds up behind some other window or minimized, it would still be on the taskbar.
Sorry not much help.
~R~

On 2024-09-15 14:00:, Bill Wiltschko wrote:
I set up a folder on my C:\ drive called FL_APP, saved the fldigi-4.2.05_setup.exe file to that folder, and double-clicked it. I get a window asking me to login as Administrator, which I do, after which nothing happens. No dialogs at all, no files saved anywhere. The same thing happens when I right-click the setup.exe file and "Run as Administrator". I haven't seen this (non) behavior with any other setup.exe file I have ever run. I checked the manual and online messages. Can anyone help?
Bill, KJ6PN