Newbie try to define a RIG

Gpredict
1

Thanks that I am allowed to be here.

I installed Gpredict and looked into - seems no problems…
But now like to define a RIG
Have here the FT-857 - Runs also sucessful FLDigi with these Parameters:
PTT - > CAT, DTR → +, Baudrate → 4800, device /dev/ttyUSB0
Based on them, FLDigi, JS8Call, WSJTX, JTDX all runs fine

With the hamlib parameters I am fighting
rigctl --model=122 -rig-file=/dev/ttyUSB0 --serial-speed=4800
Always get this error:
rig_open: error = IO error

Any Idea/Help for me ?

2

Not sure if I can help, no FT-857 on my side!
Try to add some debug output adding -vvvvv to the command line and paste your logs using a code-fence in your reply and I will have a look!

3

Ok do it
Mach das
Danke schon mal…

4

Here pse:

hb9fih@hb9fih-HP-EliteBook-840-G1:~$ rigctl --model=122 -rig-file=/dev/ttyUSB0 --serial-speed=4800 -vvvvv
rigctl, Hamlib 3.3
Report bugs to hamlib-developer@lists.sourceforge.net

rig_init called
yaesu: initrigs3_yaesu called
rig_register called
rig_register: rig_register (121)
rig_register called
rig_register: rig_register (127)
rig_register called
rig_register: rig_register (110)
rig_register called
rig_register: rig_register (105)
rig_register called
rig_register: rig_register (106)
rig_register called
rig_register: rig_register (107)
rig_register called
rig_register: rig_register (109)
rig_register called
rig_register: rig_register (120)
rig_register called
rig_register: rig_register (101)
rig_register called
rig_register: rig_register (122)
rig_register called
rig_register: rig_register (123)
rig_register called
rig_register: rig_register (111)
rig_register called
rig_register: rig_register (115)
rig_register called
rig_register: rig_register (113)
rig_register called
rig_register: rig_register (114)
rig_register called
rig_register: rig_register (128)
rig_register called
rig_register: rig_register (131)
rig_register called
rig_register: rig_register (116)
rig_register called
rig_register: rig_register (103)
rig_register called
rig_register: rig_register (124)
rig_register called
rig_register: rig_register (104)
rig_register called
rig_register: rig_register (125)
rig_register called
rig_register: rig_register (129)
rig_register called
rig_register: rig_register (132)
rig_register called
rig_register: rig_register (130)
rig_register called
rig_register: rig_register (117)
rig_register called
rig_register: rig_register (119)
rig_register called
rig_register: rig_register (118)
rig_register called
rig_register: rig_register (126)
rig_register called
rig_register: rig_register (133)
rig_register called
rig_register: rig_register (134)
rig_register called
rig_register: rig_register (135)
rig_register called
rig_register: rig_register (136)
ft857:ft857_init called
rig_open called
port_open called
serial_open called
serial_open: Unable to open ig-file=/dev/ttyUSB0 - No such file or directory
rig_open: error = IO error

Remark: the /dev/ttyUSB0 exactly written like in FLrig
See: Bold - the command is -rig-file but in Debug is replied as -ig-file

5

Aha… doch mein Fehler das second - forgot !
Seems ok now ?

hb9fih@hb9fih-HP-EliteBook-840-G1:~$ rigctl --model=122 –rig-file=/dev/ttyUSB0 --serial-speed=4800 -vvvvv
rigctl, Hamlib 3.3
Report bugs to hamlib-developer@lists.sourceforge.net

rig_init called
yaesu: initrigs3_yaesu called
rig_register called
rig_register: rig_register (121)
rig_register called
rig_register: rig_register (127)
rig_register called
rig_register: rig_register (110)
rig_register called
rig_register: rig_register (105)
rig_register called
rig_register: rig_register (106)
rig_register called
rig_register: rig_register (107)
rig_register called
rig_register: rig_register (109)
rig_register called
rig_register: rig_register (120)
rig_register called
rig_register: rig_register (101)
rig_register called
rig_register: rig_register (122)
rig_register called
rig_register: rig_register (123)
rig_register called
rig_register: rig_register (111)
rig_register called
rig_register: rig_register (115)
rig_register called
rig_register: rig_register (113)
rig_register called
rig_register: rig_register (114)
rig_register called
rig_register: rig_register (128)
rig_register called
rig_register: rig_register (131)
rig_register called
rig_register: rig_register (116)
rig_register called
rig_register: rig_register (103)
rig_register called
rig_register: rig_register (124)
rig_register called
rig_register: rig_register (104)
rig_register called
rig_register: rig_register (125)
rig_register called
rig_register: rig_register (129)
rig_register called
rig_register: rig_register (132)
rig_register called
rig_register: rig_register (130)
rig_register called
rig_register: rig_register (117)
rig_register called
rig_register: rig_register (119)
rig_register called
rig_register: rig_register (118)
rig_register called
rig_register: rig_register (126)
rig_register called
rig_register: rig_register (133)
rig_register called
rig_register: rig_register (134)
rig_register called
rig_register: rig_register (135)
rig_register called
rig_register: rig_register (136)
ft857:ft857_init called
rig_open called
port_open called
serial_open called
serial_setup called
ft857:ft857_open called
rig_get_vfo called
Opened rig model 122, ‘FT-857’
rig_strstatus called
Backend version: 0.5, Status: Beta

Rig command: q
rig_close called
ft857:ft857_close called
port_close called
ser_close called
rig_cleanup called
ft857:ft857_cleanup called

1 Like
6

SRI for German…

das rigctl in der Konsole darf ich dann nicht beenden nehme ich an - sonst wird die Verbindung freigegeben.
Der nächste ist der AO-85 in 33 Minuten - mal sehen

Info:
Ich bin in meinem Segelschiff auf Samos west KM37ir22 und habe Zeit, weil ich auf jemanden warte der meine Papiere hat und der Wind ungünstig ist. Vermutlich nächsten Montag kann ich dann starten - nach Nord nach Chios-Lesbos.

1 Like
7

Whow - now it runs - automatic QRG set in FT-857.

I did not know rigctrd - the deamon must be run…

The final “kick” gave the description especially for FT-857 from an OV Wolfsburg
Thanks…for the learning curfe !73

1 Like