Here is the trace file created when using -vvvvv if it's of any help.
F:\hamlib-win32-1.2.9-stdcall\hamlib-1.2.9-stdcall\bin>rigmem -vvvv -r ../lib/COM4 -m 122 save test
rigmem, Hamlib version 1.2.9
Report bugs to <hamlib-developer@lists.sourceforge.net>
rig:rig_init called
rig: loading backend yaesu
yaesu: initrigs2_yaesu called
rig_register (121)
rig_register (127)
rig_register (110)
rig_register (105)
rig_register (106)
rig_register (107)
rig_register (109)
rig_register (120)
rig_register (101)
rig_register (122)
rig_register (123)
rig_register (111)
rig_register (115)
rig_register (113)
rig_register (114)
rig_register (128)
rig_register (116)
rig_register (103)
rig_register (124)
rig_register (104)
rig_register (125)
rig_register (129)
rig_register (130)
rig_register (117)
rig_register (119)
rig_register (118)
rig_register (126)
ft857:ft857_init called
rig:rig_open called
ft857:ft857_open called
Opened rig model 122, 'FT-857'
Backend version: 0.3, Status: Beta
rig:rig_close called
ft857:ft857_close called
rig:rig_cleanup called
ft857:ft857_cleanup called
Looking at the ft857.c backend code, the memory functions have not been written. What's bothersome is that rigmem did not provide an error to the console to that effect.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
So far I've not tackled the memory functions for my backends (FT890/900 and FT920), however, what works on one should be reasonably close for the other Yaesu models. I guess that's something I should look into.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I think I need help
I can talk to my 857d no problems using a command shell in vista, I can use rigctl without a hitch.
My problems start when I attempt to use the rigmem command, I input a command like
"rigmem -r com4 -m 122 save test.txt" and get a blank 0 byte file.
Is there any online info for the "save" and "load" command switches for rigmem ?
What am I doing wrong ?? Any help would be much appreciated.
Here is the trace file created when using -vvvvv if it's of any help.
F:\hamlib-win32-1.2.9-stdcall\hamlib-1.2.9-stdcall\bin>rigmem -vvvv -r ../lib/COM4 -m 122 save test
rigmem, Hamlib version 1.2.9
Report bugs to <hamlib-developer@lists.sourceforge.net>
rig:rig_init called
rig: loading backend yaesu
yaesu: initrigs2_yaesu called
rig_register (121)
rig_register (127)
rig_register (110)
rig_register (105)
rig_register (106)
rig_register (107)
rig_register (109)
rig_register (120)
rig_register (101)
rig_register (122)
rig_register (123)
rig_register (111)
rig_register (115)
rig_register (113)
rig_register (114)
rig_register (128)
rig_register (116)
rig_register (103)
rig_register (124)
rig_register (104)
rig_register (125)
rig_register (129)
rig_register (130)
rig_register (117)
rig_register (119)
rig_register (118)
rig_register (126)
ft857:ft857_init called
rig:rig_open called
ft857:ft857_open called
Opened rig model 122, 'FT-857'
Backend version: 0.3, Status: Beta
rig:rig_close called
ft857:ft857_close called
rig:rig_cleanup called
ft857:ft857_cleanup called
F:\hamlib-win32-1.2.9-stdcall\hamlib-1.2.9-stdcall\bin>
Looking at the ft857.c backend code, the memory functions have not been written. What's bothersome is that rigmem did not provide an error to the console to that effect.
OK then if the code has not been written then the memory function cant read..
I wont ask if / when it will be implemented as this project must take up a lot of time adding features for all the radios it supports.
Great job so far, I'll keep checking for updates..
Many thanks.
So far I've not tackled the memory functions for my backends (FT890/900 and FT920), however, what works on one should be reasonably close for the other Yaesu models. I guess that's something I should look into.