¿ªÔÆÌåÓý

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

Re: #flrig flrig not working with my FT-890 FTDI Programming Cable #flrig

 

The S meter reads lower than the rig's meter.


Re: #flrig flrig not working with my FT-890 FTDI Programming Cable #flrig

 

After recompiling with the updated FT890.cxx
Init works now. The rig is recognized. Both the red and green receive/send lights flash periodically.
Modulation mode works, where it was disabled before, but does not read the rig's mode.
Still does not read the rig's VFO freq, but it still writes to the rig.
In Operating Controls: Freq and Mode are checked.

Buttons for vfoA vfoB and A/B work, but changing vfoB in FLRIG does not change the rig's (vfo b) freq.
S-meter works when enabled.
PTT puts the rig in transmit.

Changing the timing parameters had no effect.
Changing the comm parameters did not help.

I have attached a trace log that starts with the init.


Re: #flrig flrig not working with my FT-890 FTDI Programming Cable #flrig

 

¿ªÔÆÌåÓý

Read through the FT-890 pdf manual, and it looks like flrig is expecting to receive the wrong number of bytes.? Please substitute the attached file for the one with the same name in src/rigs/yaesu/.? Report if this corrects the issue.

David

On 4/15/24 00:26, Steve, KB5AW wrote:

Using a Raspberry Pi 4 on DietPi Debian Bookworm OS.
In the FLRIG configuration, I selected the Yaesu FT-890 rig and for the port I used /dev/ttyUSB0 for a USB to serial converter.
Port /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_ABSCDZTJ-if00-port0 works the same.

Both the red and green lights on the USB to serial converter flash when Init is pressed, which means that FLRIG sent data and the rig replied.
However, FLRIG says "Transceiver not responding!".
Changing the frequency in FLRIG changes the frequency on the rig. The green light on the USB converter flashes. PTT puts the rig in transmit.
Changing the frequency on the rig does not update FLRIG.

It's like FLRIG is sending the correct data, but it does not receive anything from the rig even though it is sending data back when Init is pressed.

CAT works perfectly with applications that use hamlib like FLDIGI, WSJT-X and grig.

I am using this cable:


Trace with all items checked

05:16:57.893 : closeRig()
05:16:57.893 : close serial port
05:16:57.893 : ClosePort(): fd = 10
05:16:57.896 : serial port closed
05:16:57.897 : clear frequency list
05:16:57.897 : initialize title bar
05:16:57.897 : start tranceiver serial port
05:16:57.900 : /dev/ttyUSB0 opened: fd = 10
05:16:57.908 : D: startXcvrSerial:
Serial port:
??? Port???? : /dev/ttyUSB0
??? Baud???? : 4
??? Stopbits : 2
??? Retries? : 2
??? Timeout? : 50
??? Loop???? : 500
??? RTSCTS?? : 0
??? CATptt?? : 1
??? RTSptt?? : 0
??? DTRptt?? : 0
??? RTS+???? : 0
??? DTR+???? : 1


05:16:57.908 : initialize transceiver
05:16:57.910 : selrig->initialize()
05:16:57.910 : init_rig()
05:16:57.910 : selrig->check()
05:16:57.910 : WriteBuffer:? 00 00 00 03 10
05:16:58.011 : ReadBuffer [50.660000 msec]: 01 01 21 10 00 00 03 04 05 09 0A AE 60 00 00 00 04 00
05:16:58.011 : E: ReadBuffer: ReadBuffer FAILED [50.941000 msec] wanted 28 chars, read 18 chars

05:16:58.012 : ReadBuffer FAILED [50.941000 msec] wanted 28 chars, read 18 chars
05:16:58.063 : ReadBuffer [50.610000 msec]:
05:16:58.063 : E: ReadBuffer: ReadBuffer FAILED [50.743000 msec] wanted 10 chars, read 0 chars

05:16:58.064 : ReadBuffer FAILED [50.743000 msec] wanted 10 chars, read 0 chars
05:16:58.065 : FAILED
05:18:23.361 : WriteBuffer:? 00 41 07 00 0A
05:18:25.073 : WriteBuffer:? 00 40 07 00 0A
05:18:26.130 : WriteBuffer:? 00 41 07 00 0A
05:18:26.961 : WriteBuffer:? 00 42 07 00 0A
05:18:27.073 : WriteBuffer:? 00 43 07 00 0A
05:18:27.233 : WriteBuffer:? 00 44 07 00 0A
05:18:29.313 : WriteBuffer:? 00 43 07 00 0A
05:18:29.377 : WriteBuffer:? 00 42 07 00 0A
05:18:29.441 : WriteBuffer:? 00 41 07 00 0A
05:18:29.521 : WriteBuffer:? 00 40 07 00 0A
05:18:36.466 : WriteBuffer:? 00 40 07 00 0A
05:18:38.723 : WriteBuffer:? 00 40 07 00 0A
05:18:40.659 : WriteBuffer:? 01 40 07 00 0A
05:18:43.043 : WriteBuffer:? 00 40 07 00 0A
05:18:44.451 : WriteBuffer:? 00 40 07 00 0A
05:18:45.059 : WriteBuffer:? 00 40 07 00 0A
05:18:45.539 : WriteBuffer:? 00 40 07 00 0A
05:18:45.603 : WriteBuffer:? 00 40 07 00 0A
05:18:45.653 : WriteBuffer:? 00 40 07 00 0A
05:18:45.704 : WriteBuffer:? 00 40 07 00 0A
05:18:45.763 : WriteBuffer:? 00 40 07 00 0A
05:18:46.323 : WriteBuffer:? 00 40 07 00 0A
05:18:46.387 : WriteBuffer:? 00 40 07 00 0A
05:18:46.772 : WriteBuffer:? 01 40 07 00 0A
05:18:48.692 : WriteBuffer:? 00 40 07 00 0A


Re: #flrig flrig not working with my FT-890 FTDI Programming Cable #flrig

 

¿ªÔÆÌåÓý

Have you experimented with these settings?



David


#flrig flrig not working with my FT-890 FTDI Programming Cable #flrig

 

Using a Raspberry Pi 4 on DietPi Debian Bookworm OS.
In the FLRIG configuration, I selected the Yaesu FT-890 rig and for the port I used /dev/ttyUSB0 for a USB to serial converter.
Port /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_ABSCDZTJ-if00-port0 works the same.

Both the red and green lights on the USB to serial converter flash when Init is pressed, which means that FLRIG sent data and the rig replied.
However, FLRIG says "Transceiver not responding!".
Changing the frequency in FLRIG changes the frequency on the rig. The green light on the USB converter flashes. PTT puts the rig in transmit.
Changing the frequency on the rig does not update FLRIG.

It's like FLRIG is sending the correct data, but it does not receive anything from the rig even though it is sending data back when Init is pressed.

CAT works perfectly with applications that use hamlib like FLDIGI, WSJT-X and grig.

I am using this cable:


Trace with all items checked

05:16:57.893 : closeRig()
05:16:57.893 : close serial port
05:16:57.893 : ClosePort(): fd = 10
05:16:57.896 : serial port closed
05:16:57.897 : clear frequency list
05:16:57.897 : initialize title bar
05:16:57.897 : start tranceiver serial port
05:16:57.900 : /dev/ttyUSB0 opened: fd = 10
05:16:57.908 : D: startXcvrSerial:
Serial port:
??? Port???? : /dev/ttyUSB0
??? Baud???? : 4
??? Stopbits : 2
??? Retries? : 2
??? Timeout? : 50
??? Loop???? : 500
??? RTSCTS?? : 0
??? CATptt?? : 1
??? RTSptt?? : 0
??? DTRptt?? : 0
??? RTS+???? : 0
??? DTR+???? : 1


05:16:57.908 : initialize transceiver
05:16:57.910 : selrig->initialize()
05:16:57.910 : init_rig()
05:16:57.910 : selrig->check()
05:16:57.910 : WriteBuffer:? 00 00 00 03 10
05:16:58.011 : ReadBuffer [50.660000 msec]: 01 01 21 10 00 00 03 04 05 09 0A AE 60 00 00 00 04 00
05:16:58.011 : E: ReadBuffer: ReadBuffer FAILED [50.941000 msec] wanted 28 chars, read 18 chars

05:16:58.012 : ReadBuffer FAILED [50.941000 msec] wanted 28 chars, read 18 chars
05:16:58.063 : ReadBuffer [50.610000 msec]:
05:16:58.063 : E: ReadBuffer: ReadBuffer FAILED [50.743000 msec] wanted 10 chars, read 0 chars

05:16:58.064 : ReadBuffer FAILED [50.743000 msec] wanted 10 chars, read 0 chars
05:16:58.065 : FAILED
05:18:23.361 : WriteBuffer:? 00 41 07 00 0A
05:18:25.073 : WriteBuffer:? 00 40 07 00 0A
05:18:26.130 : WriteBuffer:? 00 41 07 00 0A
05:18:26.961 : WriteBuffer:? 00 42 07 00 0A
05:18:27.073 : WriteBuffer:? 00 43 07 00 0A
05:18:27.233 : WriteBuffer:? 00 44 07 00 0A
05:18:29.313 : WriteBuffer:? 00 43 07 00 0A
05:18:29.377 : WriteBuffer:? 00 42 07 00 0A
05:18:29.441 : WriteBuffer:? 00 41 07 00 0A
05:18:29.521 : WriteBuffer:? 00 40 07 00 0A
05:18:36.466 : WriteBuffer:? 00 40 07 00 0A
05:18:38.723 : WriteBuffer:? 00 40 07 00 0A
05:18:40.659 : WriteBuffer:? 01 40 07 00 0A
05:18:43.043 : WriteBuffer:? 00 40 07 00 0A
05:18:44.451 : WriteBuffer:? 00 40 07 00 0A
05:18:45.059 : WriteBuffer:? 00 40 07 00 0A
05:18:45.539 : WriteBuffer:? 00 40 07 00 0A
05:18:45.603 : WriteBuffer:? 00 40 07 00 0A
05:18:45.653 : WriteBuffer:? 00 40 07 00 0A
05:18:45.704 : WriteBuffer:? 00 40 07 00 0A
05:18:45.763 : WriteBuffer:? 00 40 07 00 0A
05:18:46.323 : WriteBuffer:? 00 40 07 00 0A
05:18:46.387 : WriteBuffer:? 00 40 07 00 0A
05:18:46.772 : WriteBuffer:? 01 40 07 00 0A
05:18:48.692 : WriteBuffer:? 00 40 07 00 0A


Re: QRZ.com application of Android

 

¿ªÔÆÌåÓý

Here¡¯s the one I use for my (iOS) iPhone and it uses QRZ.com ! It¡¯s called QRZ - Call Search ! Works super !

IMG_5371

73 de Dave

Cell: 519.241.9206
ve3nn@...
www.ve3nn.ca
15 Pro Max

On Apr 14, 2024, at 13:24, Paul - W1BIU <paul.w1biu@...> wrote:

?
It¡¯s available for iOS, it¡¯s called Callsign Search.

Paul - W1BIU
Paul.w1biu@...


From: [email protected] <[email protected]> on behalf of Harry Bloomberg, W3YJ via groups.io <hbloomb@...>
Sent: Sunday, April 14, 2024 10:59:41 AM
To: [email protected] <[email protected]>
Subject: Re: [linuxham] QRZ.com application of Android
?
There is an IOS app named "Ham Callsigns" that uses QRZ to lookup callsigns.? I use it all the time and it works great.

73,
Harry Bloomberg W3YJ

On Sun, Apr 14, 2024 at 10:56?AM SkipF, NT1G via <skip.flem=[email protected]> wrote:
As the group new member moderator,? I frequently use to verify new applicant requests. Just became aware that it is now offered as an app for android phones. I can't speak about Apple,? however I imagine that it will soon become available for that platform.?
73 de Skip, NT1G?


flamp 2.2.12 poosted at

 

¿ªÔÆÌåÓý

??? Version 2.2.12
?? ?
????? * maintenance release
?? ?
???????? . kk5vd? <kk5vd@...>
?????????? 6754d04: Compatibility/Modem Switch
?????????? 24e1837: Document/GUI/Header Modem/Default Modems
?????????? afb90bd: Tabs/Relay Options/GUI/Fluid
?? ?
???????? . dave-w1hkj? <w1hkj@...>
?????????? 73db3b6: font browser

See readme.txt for complete list of changes.

73, David, W1HKJ
??? Robert, KK5VD


Re: QRZ.com application of Android

 

On 14/04/2024 22:55, Dave, G?WBX via groups.io wrote:
Not everyone uses QRZ.com, or any of the alternatives, just as many won't touch f'book etc.
Ding! Ding! Ding! We have a winner.

QRZ is not an official source of ham QTH information and relying on it for any kind of ID confirmation is not wise.


Re: QRZ.com application of Android

 

Not everyone uses QRZ.com, or any of the alternatives, just as many won't touch f'book etc.

Take care.

Dave 'KBV


Re: QRZ.com application of Android

 

I have an Android and I have QRZ (3) apps but I only see QRZ XML now

73

Don Poaps
New Westminster, BC
VA7DGP DATA
VA7QU ? VOICE


Winlink:?va7dgp@...
Subject://wl2k ? ? ? ? ?

ALLSTAR ?530780
Hamshack Hotline
5971
Mid-Island Phone Mesh
2210
2232

? ? ? ? ? ? ? ? ? ?


On Sun, Apr 14, 2024 at 9:46?AM Keith/KI5US via <geek4096=[email protected]> wrote:

Playstore doesn't seem to be able to locate an app called "".? RepeaterBook, QTH Locator toolkit, Ham Radio - CQ logs, HAMRS logger, etc, but not .? Is it called something different?

QRZ.com is really great - I use it almost exclusively.? Having an app (vs the website) on my phone would be very nice.

73
Keith/KI5US


On 4/14/24 10:56, SkipF, NT1G via wrote:
As the group new member moderator,? I frequently use to verify new applicant requests. Just became aware that it is now offered as an app for android phones. I can't speak about Apple,? however I imagine that it will soon become available for that platform.?
73 de Skip, NT1G?



--
Don Poaps
VA7DGP: data
VA7QU:? ?voice


Re: QRZ.com application of Android

 

Andy.

I think all UK calls were added years ago as place holders. Since data protection came in it's up to you to add your call and any others you manage.

Phil GM3ZZA.

On 14 April 2024, at 20:17, Andy <andy.mm0fmf@...> wrote:

On 14/04/2024 19:53, SkipF, NT1G via groups.io wrote:
I've never had any issue with non-US callsigns using qrz.com
None of my 4 calls (personal and club calls) are listed. There again I
know of several fictitious ham calls in there.


Re: QRZ.com application of Android

 

On 14/04/2024 19:53, SkipF, NT1G via groups.io wrote:
I've never had any issue with non-US callsigns using qrz.com
None of my 4 calls (personal and club calls) are listed. There again I know of several fictitious ham calls in there.


Re: QRZ.com application of Android

 

I've never had any issue with non-US callsigns using .
Skip, NT1G?

On Sun, Apr 14, 2024, 2:15 PM Andy via <andy.mm0fmf=[email protected]> wrote:
On 14/04/2024 15:56, SkipF, NT1G via wrote:
> I frequently use to verify new applicant requests.

QRZ maybe valid for US calls but it's not reliable for non-US calls.

Andy







Re: QRZ.com application of Android

 

On 14 April 2024, at 19:15, Andy <andy.mm0fmf@...> wrote:

>On 14/04/2024 15:56, SkipF, NT1G via groups.io wrote:
>> I frequently use qrz.com to verify new applicant requests.
>QRZ maybe valid for US calls but it's not reliable for non-US calls.

It's reliable only if the call owner allows it to be. Under data protection it's all it can be. I'm in charge of my entries and others' who've let me.

>Andy

Phil GM3ZZA
>


Re: QRZ.com application of Android

 

On 14/04/2024 15:56, SkipF, NT1G via groups.io wrote:
I frequently use qrz.com to verify new applicant requests.
QRZ maybe valid for US calls but it's not reliable for non-US calls.

Andy


Re: QRZ.com application of Android

 

¿ªÔÆÌåÓý

It¡¯s available for iOS, it¡¯s called Callsign Search.

Paul - W1BIU
Paul.w1biu@...


From: [email protected] <[email protected]> on behalf of Harry Bloomberg, W3YJ via groups.io <hbloomb@...>
Sent: Sunday, April 14, 2024 10:59:41 AM
To: [email protected] <[email protected]>
Subject: Re: [linuxham] QRZ.com application of Android
?
There is an IOS app named "Ham Callsigns" that uses QRZ to lookup callsigns.? I use it all the time and it works great.

73,
Harry Bloomberg W3YJ

On Sun, Apr 14, 2024 at 10:56?AM SkipF, NT1G via <skip.flem=[email protected]> wrote:
As the group new member moderator,? I frequently use to verify new applicant requests. Just became aware that it is now offered as an app for android phones. I can't speak about Apple,? however I imagine that it will soon become available for that platform.?
73 de Skip, NT1G?


Re: Problemm running fldigi on Raspberry Pi

 

Steve, thanks for your reply, but I'm using bullseye, X11 is default.


Re: QRZ.com application of Android

 

"To opt-in to the Beta Test program, please go to:?

This release works on all Android phones having the Ice Cream Sandwich (Android 4.1) and later. This covers more than 97% of all Android phones out there.

We're still working on the program's help and other documentation, but for now the App is ready to explore. Here are a few screen shots of the new app."

On Sun, Apr 14, 2024, 12:46 PM Keith/KI5US via <geek4096=[email protected]> wrote:

Playstore doesn't seem to be able to locate an app called "".? RepeaterBook, QTH Locator toolkit, Ham Radio - CQ logs, HAMRS logger, etc, but not .? Is it called something different?

QRZ.com is really great - I use it almost exclusively.? Having an app (vs the website) on my phone would be very nice.

73
Keith/KI5US


On 4/14/24 10:56, SkipF, NT1G via wrote:
As the group new member moderator,? I frequently use to verify new applicant requests. Just became aware that it is now offered as an app for android phones. I can't speak about Apple,? however I imagine that it will soon become available for that platform.?
73 de Skip, NT1G?



Re: QRZ.com application of Android

 

¿ªÔÆÌåÓý


Playstore doesn't seem to be able to locate an app called "qrz.com".? RepeaterBook, QTH Locator toolkit, Ham Radio - CQ logs, HAMRS logger, etc, but not qrz.com.? Is it called something different?

QRZ.com is really great - I use it almost exclusively.? Having an app (vs the website) on my phone would be very nice.

73
Keith/KI5US


On 4/14/24 10:56, SkipF, NT1G via groups.io wrote:

As the group new member moderator,? I frequently use qrz.com to verify new applicant requests. Just became aware that it is now offered as an app for android phones. I can't speak about Apple,? however I imagine that it will soon become available for that platform.?
73 de Skip, NT1G?



Re: Problemm running fldigi on Raspberry Pi

 

I found that with the new Raspberry Pi OS that uses Wayland, FLDIGI runs extremely slow. Even the mouse cursor is slow.
My solution is to switch back to openbox.

sudo raspi-config
Select Advanced Options
Select Wayland
Select X11? Openbox window manager with X11 backend
Tab to <OK> and press enter.
Press the ESC key
Tab to <Finish> and press Enter.
<reboot>

I hope this fixes it for you.