Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
- Winfldigi
- Messages
Search
Re: Xiegu G-90 + FLDigi; waterfall issues
Sorry I missed that you were mainly operating CW, decoding in fldigi. So I have done lots of CW decoding in SSB in the -D mode on G-90, but have not done transmission so I cannot be sure the signal out is correct in that mode but I do expect so. Andrew Farris <lordmorgul@...> On Fri, Aug 23, 2024 at 11:13 Bill KD9TWA via <kd9twa=[email protected]> wrote:
|
FLDigi, N3FJP, and contesting
I'm?trying?to get prepared for the Hawaii QSP party tonight, but this question applies to any contest.
?
I believe I have FLDigi and N3FJP hooked up correctly and talking to each other. CAT works and CW decodes/encodes well, (enough). QSOs log properly into both N3FJP?and FLDigi.
?
The behavior I'm curious about is that the frequency pane in FLDigi doesn't follow the frequency selected, either by spinning the VFO knob or by clicking on a station in the N3FJP band map.
?
Any thoughts.?
?
Icom IC-7300
WinKeyer USB
Windows 10
All software updates are current
?
?
Bill KD9TWA |
Re: Xiegu G-90 + FLDigi; waterfall issues
Thanks for the info Andrew.
?
I was hesitant to use the dash U or dash L because many folks seem adamant about using the CW mode. Maybe since I'm using WinKeyer for the code generation, it isn't as big a deal as I?assumed.
?
I'll give it a try and report my results.
?
Bill KD9TWA |
Re: Xiegu G-90 + FLDigi; waterfall issues
The G-90 needs to be in USB-D or LSB-D, with the input source set to Line.? FLRIG does not know about these settings so will be in USB or LSB after it performs init, manually change it after. My waterfall with G-90 is set to 10 and 80.? But yes the audio power level could vary and need to be different than someone else.? The audio level in and out in the radio settings on my three different G-90 radios are all set differently as they have enough variance to need that. Andrew Farris <lordmorgul@...> On Thu, Aug 22, 2024 at 22:30 Bill KD9TWA via <kd9twa=[email protected]> wrote:
|
Xiegu G-90 + FLDigi; waterfall issues
I'm trying to use FLDigi as an encoder/decoder with the Xiegu G90. I think I'm?close.
?
The problem is I can't get the FLDigi waterfall to show activity.
?
Adjusting the?two selections at the bottom of the waterfall, only changes the background from black to blue. The trace for the incoming signals, usually yellow and red, is non existent.?
?
The?Signal diamond?is black 99% of the time. Every once in a while it will tick yellow or green.?
?
?
If I put the VFO on a spot on the G-90's onboard waterfall with no activity, the decoder is still producing text. The decode function of FLDigi seems like it's trying to work, but it's gibberish. If I tune into ARRL's W1AW practice code station it is decoded, (just okay), but still no activity on the waterfall.
?
Rig: G90
Sound card: DigiRig
Rig control (CAT): FLRig. Works perfectly BTW
Squelch: Off
Computer: Evolve Win10 mini laptop
Antenna: Diamond CP5H, 5 band vertical
Keyer: WinKeyer USB
Software: latest versions of FLRig, FLDigi, and G90 firmware
Environment: Urban, high noise floor
G90 gain: I've tried between 43% and 100% and it has no effect has no effect.
Other digital modes: FT8 and FT4 work flawlessly. Winlink works okay too.
?
I feel like the incoming sound level isn't right. I've mucked-around with the computer sound settings, but that didn't resolve the issue.
?
Note; in the shack, when I substitute an Icom IC7300 for the G90, everything works. When I use FLDigi, the IC7300, and desktop PC, it functions?perfectly?pretty well.
?
?
? |
Re: FLrig and VSPE
On Fri, Aug 23, 2024 at 11:49 AM, Arvind Mallya wrote:
No problem here with Flrig 1.4.7 and VSPe with icom radio. What radio are you trying to connect with the split ports. Yes that's right version 1.4.7 works fine with VSPE. My issue was with the later versions. Guess as youbI will stay with 1.4.7.
--
DE Bruce VK2RT |
Re: FLrig and VSPE
No problem here with Flrig 1.4.7 and VSPe with icom radio. What radio are you trying to connect with the split ports. -Arvind On Thu, Aug 22, 2024, 3:59?PM Bruce VK2RT via <bruce=[email protected]> wrote:
|
Re: FLrig and VSPE
On Fri, Aug 23, 2024 at 08:01 AM, Mike Black wrote:
I use VSPE so that I can integrate Ham Radio Deluxe Logbook and all my digital progeams like WSJT-X/JTAlert, JS8Call, SSTV and VarAC.
?
I use FLrig to access all my SSB net frequencies which all works fine with port sharing with FLrig Ver 1.4.7.
?
My problem is with the later versions of FLrig, I gave to disconnect everything from VSPE and then shut it down before running FLrig.
?
Just a pain Mike.
?
They must have made some change in the later versions of FLrig compared to V1.4.7 that has caused this.
?
The new version of FLrig will hook into the spared port but then the frequency wanders around and it is not stable.
?
DE Bruce VK2RT |
Re: FLrig and VSPE
Mike Black
Please explain exactly what you are trying to do....there's likely a better solution. Splitting a COM port like that is prone to failure. Mike W9MDB
On Thursday, August 22, 2024 at 04:54:25 PM CDT, Bruce VK2RT <bruce@...> wrote:
On Fri, Aug 23, 2024 at 07:42 AM, Mike Black wrote:
Yes Mike, I am using Splitter for the Device type.
?
DE Bruce
VK2RT |
Re: FLrig and VSPE
Mike Black
How are you using VSPE?? You trying to split the port? Mike W9MDB
On Thursday, August 22, 2024 at 04:39:01 PM CDT, Bruce VK2RT <bruce@...> wrote:
Anyone successfully using the latest FLrig with VSPE?
?
I am stuck on FLrig Ver 1.4.7, latest version fails when using it with VSPE.
?
DE Bruce
VK2RT |
Re: FLRIG 2.0.04 + TS590SG, Meters Display no SWR or ALC
toggle quoted message
Show quoted text
|
Re: FLRIG 2.0.04 + TS590SG, Meters Display no SWR or ALC
I have gotten the SWR meter working and it has a reasonably-accurate scaling with a lookup table based on the rig scaling vs the scaling of the meter in flrig. Here's the code for the get_swr function that goes into TS590SG.cxx int RIG_TS590SG::get_swr(void) { ? ? ? ? int mtr = 0; ? ? ? ? cmd = "RM;"; ? ? ? ? sendCommand(cmd); ? ? ? ? if (wait_char(';', 8, 100, "get SWR", ASC) < 8) return 0; ? ? ? ? sscanf(replystr.c_str(), "RM1%d", &mtr); ? ? ? ? if (( 1 <= mtr ) && ( mtr <= 6 )) ? ? ? ? { ? ? ? ? ? mtr = (mtr * 12) / 6; ? ? ? ? } ? ? ? ? else if (( 7 <= mtr ) && ( mtr <= 11 )) ? ? ? ? { ? ? ? ? ? mtr = (mtr * 25) / 11; ? ? ? ? } ? ? ? ? else if (( 12 <= mtr ) && ( mtr <= 15 )) ? ? ? ? { ? ? ? ? ? mtr = 25 + ((mtr - 12)*7); ? ? ? ? } ? ? ? ? else if ( mtr >= 16 ) ? ? ? ? { ? ? ? ? ? mtr = (mtr * 100) / 30; ? ? ? ? } ? ? ? ? if (mtr > 100) mtr = 100; ? ? ? ? return mtr; } And the result: My get_alc doesn't seem to work, and I think it has to do with the 590SG always returning all three meter readings on a single response line. SWR is the first of the three, which is why I think it works with this function. I'm not sure how to scan for the third response. ? ? ? ? sscanf(replystr.c_str(), "RM3%d", &alc_val); doesn't seem to pull it out. Cheers Eric On Tue, 20 Aug 2024 at 10:09, Wayne Carpenter KN2Z @minicowman via <mwcarpe=[email protected]> wrote:
|
Re: FLDIGI & FT-991A Settings
¿ªÔÆÌåÓýYa! That did it. Thanks! Sent via the Samsung Galaxy S8+, an AT&T 5G Evolution capable smartphone -------- Original message -------- From: "Dave via groups.io" <w1hkj@...> Date: 8/19/24 03:11 (GMT-08:00) Subject: Re: [winfldigi] FLDIGI & FT-991A Settings David On 8/19/24 01:00, Howard wrote:
|
Re: Fldigi call previous lookup in Log4omV2
If you link fldigi correctly to log4om? fldigi contact will appear in lig4om so you can see the b4. Before you try ho work again sent by ve3wej on samsung s21+ On Tue, Aug 20, 2024, 11:51?a.m. Bill Hodgson - W1WRH via <w1wrh=[email protected]> wrote:
|
Re: FLAMP Question: block fills from old queue ID?
Version 2.2.12.04 and 2.2.13.0x (not published, and the only difference is in OPT.M4 file) are slated to become 2.2.14 once Dave has the time to publish one of these 2 Alpha versions. I don't have a time frame as to when this will happen. I see no issues using 2.2.12.04 until that time arrives.
Sadly even 2.2.12 has some issues and the reason for 2.2.13 release, because of miscommunications with myself and Dave the wrong pu/xx branch was published (for 2.2.13). 2.2.12.04/2.2.13.0x is the correct/working version. Robert |
to navigate to use esc to dismiss