开云体育

So my Yeasu FT-890 is connected using a CAT to USB-FTDI cord my Baund is set at 4800 when I click Init I get this error:

Transceiver not responding!?
Check serial (COM) port connection?
Open menu Config/Setup/Transceiver
Press 'Ser Port' button, reselect port
Press 'Init' button

I though it was a cord issue that I bought on Amazon, so I purchased a new cord from the UK that was supposed to be the fix, but I'm still getting this issue. Any help would be appreciated.?

Are U using a PC, MAC or Linux machine.
I also have some issues with FLrig and Fldigi but its more related to the sound, but what I can tell you is that all the baud rates and Com port settings have to be the same, e.g. the buad rate set on your rig (sometimes set on 9600 or 34500 or even 115k). It have to be the same as your hardware port (virtual port as the FTDi is creating a virtual com port) and the port speed of the FLrig. If the port speeds is not set the same, its interpreted as a bunch of garbage. Also have a look at the stop bits. I know that the Yaesu love to use two stop bits in stead of one. It must correspond everywhere. This is especially a problem with regard to virtual ports (e.g. FTDI, Prolific etc) created by USB to serial devices as this serial communications can be much faster than the original serial port speed of 9600 or 4800 baud. Had a similar problem with all my software and hardware, also jumping from the ESP32 chip to the arduino chip etc.
--
73 de Eugene / ZR4EM

It may be advantageous also to use a lower port speed than the maximum rate of your devices. My experience is that 9600 is the better rate as my FT-897 was previously set on 38k and it worked fine on windows, but not that well on the Raspberry Pi. Using 9600 (but I had to set the CAT speed of the rig to 9600) and my apps worked the best, and is fast enough.

73

I see on the user manual of your rig its very similar to my FT-840.
On p31 in the manual it explains the data flow, with one start bit, 8 data bits and two stop bits, no parity or flow control.
I also see on p34 in the paragraph sending a command it mentions that the data rate is set to 4800 baud so your Virtual serial port should also be on 4800 baud, otherwise the data comms may be to fast. Check again the stop bit is set to 2 and not 1.
--
73 de Eugene / ZR4EM

@ZR4EM I am running a Raspberry Pi 4/4gig with buster and the build-a-pi script. I have looked at the baund rate in the 890 manual it says 4800, but I cannot find the other settings you mentioned. Thank you for helping me troubleshoot this.?

?

I'm very new to this could you explain, "data flow, with one start bit, 8 data bits and two stop bits, no parity or flow control" what this looks like in the settings? I set to 4800 baud, and 2 stop bit same error.

Okay, I got it going. I am putting the settings for flrig below incase anyone else needs them. RTS + 12v and DTR + 12v needed to be on at the same time. @ZR4EM thank you for helping me figure this mess out!

My RTS and DTR radio buttons is not on because its not connected with my homebrew cable, but it works
Pardon for the late reply, was out of office
--
73 de Eugene / ZR4EM

It worked like a charm all day yesterday, got up this morning and it won't connect. Might be a hardware issue with the radio. I'm reinstalling Build-a-Pi now.

I don't know if anyone can take a look at this error report from flrig and advise? I'm not sure what I'm looking at. I was able to connect to the radio all day yesterday and can't connect for anything today, I'm starting to wonder if I have an issue with the radio??

Also, JS8CALL works perfect connects the first try every try. I don't get it?

On Thu, Jul 2, 2020 at 09:44 PM, KN4VXP | Chad wrote:

I don't know if anyone can take a look at this error report from flrig and advise? I'm not sure what I'm looking at. I was able to connect to the radio all day yesterday and can't connect for anything today, I'm starting to wonder if I have an issue with the radio?

The guys that build/maintain FLRIG might be able to give you specifics on the errors you are seeing. /g/linuxham/topics

?
--

Nope it seems to be a USB hickup with the Linux core. So no, its maybe a collection of stuff and its frustrating. The other stuff is when the baud rate (not in your case) is fine for an instant but for continued use maybe a problem. When I program an ESP32 on 115k its fine, but if I want the continuous serial monitoring it drops the connection so slower is maybe better. I do not know anymore if USB and The RasPi is a good idea. Maybe using plain UART comms would be better but you have just so much UART TTL ports. I am now talking BS like my bosses in circles and confusing everyone. Its seems there is no short resolution for the problem that updating the core and firmware. And by that time we have a raspberry pi 10
--
73 de Eugene / ZR4EM

@ KN4VXP
Maybe its the port you are connecting to. Perhaps you should try another available port. Look for a similar description or try entering the command lsusb in terminal to see the port. It is usually something with either ttyUSB[and either 1 or 0 or some number)?or something similar. The directory you are linking with is constantly changing. It also seems from??that according to a post by?? on?? that?

post 10??suggests that the ftdi drivers are not ARM compatible which the driver page??does back up, if that is the case then this is going nowhere until we have new drivers?

So its a problem again with the Linux core and USB
Also see??with the mention that

/dev/ttyS0?and?/dev/ttyAMA0?are inbuilt UARTS?/dev/ttyprintk?MAY be yours.

NOT all USB devices/drivers are "tty".

Unplug the device, list?/dev?then plug in and see what has changed.

--
73 de Eugene / ZR4EM