You have the same USB device for "Transmitter" and "Up converter" (/dev/ttyUSB0). Please choose an other device (/dev/serial0) for "Up converter".
Thank you for helping me. I changed Up converter to /dev/serial0, but still no success. Any other ideas? I am new to Linux so the problem could be something very basic.
73, Bill
Also after restarting the program?
Yes, I did restart, several times.
I think it must be a problem with the cable or the USB/TTL converter or the FT-817, not the software. I tried using SDR Console and the result was the same: FT-817 "not responding". I have checked the cable with an ohm meter several times, all seems correct. The converter has a red LED that stays on non-stop, is that normal? And on the FT-817, the ONLY thing that needs to be done is to set the CAT rate on menu 14, correct?
Thank you again, Frank, and 73,
Bill
Yes, at FT-817 only the CAT rate of 4800 is important.
Frank, I think I am close but I still need some help.
It looks like my original problem was the CT-62 cable. I tried a different one and it is working to control the FT817 with my laptop and SDR Console. However, I am still not able to control the FT817 with the Raspberry and your program. I assume I must have some incorrect setting, as we know the cable and FT817 are OK, since control is working with the laptop.
In the attached pictures, I see a red TX icon on the controller. On your screenshots, this icon is green and it says RX. Does that tell us anything? Otherwise, I think everything is set the way you instructed.
What am I doing wrong?
Thank you very much and 73,
Bill
TX and red means that the FT-817 is in transmit mode. Otherwise there ist a green RX icon. The PTT state is detected by PTT GND signal from FT-817.
Low state of CTS or DSR or DCD or RI from TTL/USB-Converter will be indicated as TX.
Thank you for the reply, Frank.
The FT817 was not in transmit mode when the photo was taken.
I just turned everything on, no changes from last night, but now the display is different. There is a green TX icon and the IF QRG box just has a "?", it no longer shows 432mhz. I clicked on Auto Tracking, no change.
What could be wrong?
73, Bill
Hi,
will it work if you tune the raspberry or the yaesu to the transponder frequency range (.489.500 - 490.000) ? Your photo shows both outside while uplink and downlink qrg do match. Maybe Frank inhibits TX if frequency is out of range? 73, Martin
Hi,
will it work if you tune the raspberry or the yaesu to the transponder frequency range (.489.500 - 490.000) ? Your photo shows both outside while uplink and downlink qrg do match. Maybe Frank inhibits TX if frequency is out of range? 73, Martin
Good idea, thank you, but it is not working even in the transponder range.
Working fine with SDR Console, maybe the CT-62 CAT cable is not Linux compatible?
73, Bill
Well,
you can check if raspberry recognizes the the cable by typing "lsusb | grep prolific" in a terminal. Your photo from an earlier post shows raspi can handle the cable. See entry "prolific 2303 on ttyUSB0" or so. Windows has driver problems with the prolific converters because of chinese fake chips and drivers refuse to work if the chip is fake, but linux doesn't care about that, it will work out of the box. So, no, your cable is not the culprit as far as the connection raspberry<>converter goes. Do you have an oscilloscope to check the other end of the converter that plugs into the yaesu? Are there signals detectable?
EDIT: You said, it works with sdr-console, so the hardware should be fine .
In a terminal, you can type "groups" to see if the user pi has permission to use tty , but if Frank put that wrong, this forum would be swamped with complaints.
You may want to install a serial ports emulator on your raspi, set it to /dev/ttyUSB0 and baud rate 4800 to see if your radio talks to it.
Feel free to ask for further help if that all is beyond your knowledge.
All that given you are in a hurry and want to get to the bottom of things. Otherwise , wait for the advices Frank will give you for sure.
73, Martin
the IF QRG box just has a "?", it no longer shows 432mhz.
"?" in the IF QRG field means that there is no communication to FT-817.
Hi,
in Post #200 , your converter is a silicon labs 2102, in post #206 it's a prolific. Are you sure you have checked the prolific with sdr-console or did you only verify that the silicon labs is working? Try the silicon labs under linux as well as the prolific under windows just to be sure.
Working fine with SDR Console, maybe the CT-62 CAT cable is not Linux compatible?
You use the Yaesu CT-62 USB CAT cable? In this case the PTT detection will not work because the TX GND signal is not connected internal.
So you have to use USB/TTL-converter with TX GND connected as described.
"?" in the IF QRG field means that there is no communication to FT-817.
Yes, that was my error, I had changed the baud rate. When I set it back to 4800 the 432mhz reappeared in the IF QRG field, and the icon changed back to red TX. But the FT817 was not actually in transmit mode.
Hi,
in Post #200 , your converter is a silicon labs 2102, in post #206 it's a prolific. Are you sure you have checked the prolific with sdr-console or did you only verify that the silicon labs is working? Try the silicon labs under linux as well as the prolific under windows just to be sure.
The converter in post #200 did not work with either the raspi or SDR Console on windows laptop. I changed cables, and the converter in post #206 works fine with SDR console but is not working with the raspi. There is apparently some type of communication, because I'm seeing 432mhz in the IF QRG field and a red TX icon. But the raspi is not changing the frequency on the FT817 and, even though the red TX icon means the FT817 is in transmit mode, it actually is in receive mode.
Yes, that was my error, I had changed the baud rate. When I set it back to 4800 the 432mhz reappeared in the IF QRG field, and the icon changed back to red TX. But the FT817 was not actually in transmit mode.
With the Yaesu CT-62 USB CAT cable? Then the TX detection will not work (see #214 obove).
You use the Yaesu CT-62 USB CAT cable? In this case the PTT detection will not work because the TX GND signal is not connected internal.
So you have to use USB/TTL-converter with TX GND connected as described.
Yes, I changed to a Yaesu CT-62 USB CAT cable. It just does not work with PTT? It should work to control the TX frequency on the FT817? It is not doing any control at all.
Previously, I used the USB/TTL converter in post #192, which also did not work.
During TX (if the TX icon is red) there will be no frequency updates.
That makes sense. Is there a way to stop the TX icon from going red? Maybe the pin that needs to be connected to TX GND is somehow permanently grounded, which would cause the raspi to think the FT817 is transmitting.
