It controls and readout data from the up converter (power, temperature, voltage etc.). In the actual version you can control Kuhne MKU2424 and AMSAT UpCon6W converters.
Posts by DL3DCW
-
-
I have now tested several variants. Almost everything was unusable. The delay is too long. Both via a sound card input and via USB. Because you need an undelayed audible tone in order to give cleanly. And that only works if the morse keyer generates it directly. If this sidetone is generated on the PC, the delay is too long.
-
The only thing that changes when the raspi detects that the FT817 is transmitting is that the speaker is muted or the volume is lowered, correct?
Yes, thats correct.
-
TX red = PTT active = FT-817 in TX mode
TX green = PTT not active = FT-817 in RX mode
If you press PTT on FT-817 color of TX icon changes from green to red.
-
During TX (if the TX icon is red) there will be no frequency updates.
-
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).
-
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.
-
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.
-
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.
-
Yes, at FT-817 only the CAT rate of 4800 is important.
-
Also after restarting the program?
-
You have the same USB device for "Transmitter" and "Up converter" (/dev/ttyUSB0). Please choose an other device (/dev/serial0) for "Up converter".
In the actual version for Raspberry Pi 4B you can set "Up converter" to "none" if you dont need this function.
-
The software uses 4800 baud default CAT rate. The USB port you can set under Setup/Hardware/Transmitter.
-
In this version you can also use CTS. But it is a very very old version. I recommend to use Raspberry Pi 4B with last satcontrol software. There are many changes and improvements.
-
DCD was used in the old software versions. CTS is used in actual versions.
-
If it is possible then you can connect CTS to TX GND. But it is not absolutely necessary. The PTT signal from FT817 is also available via CAT command (you can enable this in the software). But via CAT the PTT detection is a little bit slower.
-
I am sure it would work, but since my PC in the shack is already connected to the FT-817 and gqrx is perfectly working, I would like to avoid setting up a separate hardware only for SAT control.
The Python program you can download here: http://www.satcontrol.de/files/satcontrol.zip
Maybe that on your system some additional packages need to be installed. On the complete Raspberry image everything is already prepared.
-
Maybe this will work for you: SAT Controller SDR Nano
-
Ok thanks. I will try this.
-
My Pluto is connected via USB/LAN adapter to my network. With SDR console it works fine via network access.
But with the „software DVB-S demodulator“ i have no success. What settings are needed in this software to connect my Pluto via LAN?
