You can subscribe to this list here.
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
(2) |
May
(1) |
Jun
(1) |
Jul
|
Aug
(1) |
Sep
(1) |
Oct
(1) |
Nov
|
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2003 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2004 |
Jan
|
Feb
(1) |
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2005 |
Jan
(2) |
Feb
(1) |
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
(2) |
Aug
|
Sep
(1) |
Oct
|
Nov
(1) |
Dec
(2) |
| 2006 |
Jan
|
Feb
|
Mar
(6) |
Apr
|
May
|
Jun
(5) |
Jul
(2) |
Aug
|
Sep
(4) |
Oct
(2) |
Nov
(1) |
Dec
(2) |
| 2007 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
|
Jun
(5) |
Jul
(3) |
Aug
|
Sep
(3) |
Oct
|
Nov
(2) |
Dec
(4) |
| 2008 |
Jan
(2) |
Feb
(3) |
Mar
(2) |
Apr
(5) |
May
(3) |
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
(1) |
Nov
|
Dec
(2) |
| 2009 |
Jan
|
Feb
|
Mar
|
Apr
(2) |
May
(3) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2010 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(5) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(2) |
Nov
|
Dec
|
| 2012 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2015 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(4) |
| 2016 |
Jan
|
Feb
|
Mar
|
Apr
(5) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2017 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2020 |
Jan
|
Feb
(1) |
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2023 |
Jan
(1) |
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Brian W. <br...@wi...> - 2023-03-25 21:51:17
|
Do you know of any projects to do a program in Python?
To me, we still need a full featured GUI to control rigs supported by Hamlib,
but IMO programmed in Python would be a better choice.
73
--
Stephane - F8CFE
73 de Brian W6GKD
|
|
From: Stephane F. <f8...@fr...> - 2023-01-04 20:14:39
|
Good News every one! Finally here comes grig 0.9.0. This is mainly a maintenance release in order to align with Hamlib-4.x, plus some cosmetic fixes. Thanks to all the contributors and pull requests. Download it at: https://github.com/fillods/grig/releases/tag/GRIG-0_9_0 I might give a try at releasing a win32 version, but this will be on a low effort mode. Please note that grig moved from sourceforge to https://github.com/fillods/grig/ Remember, Alexandru Csete, OZ9AEC, the original designer and developer of grig is looking for people to take over and maintain the project. The current release has been made on interim. No further development of feature is planned. However pull requests are welcome of course. To me, we still need a full featured GUI to control rigs supported by Hamlib, but IMO programmed in Python would be a better choice. 73 -- Stephane - F8CFE |
|
From: Cam <cam...@bi...> - 2020-12-18 18:03:41
|
Rig: Yaesu FTdx1200 OS: Ubuntu 20.04.1 LTS PC: Lenovo T430 laptop grig: 0.8.2 Accessing the rig from a terminal emulator works fine. Accessing the rig from rigctl works fine. But when I attempt to run grig using: grig -m 134 -r /dev/ttyUSB0 -s 4800 I get a series of message, shown below, which suggests that grig is having issues accessing the rig. Any suggestions? Thanks Cam Output captured from stderr: Gtk-Message: 12:00:42.101: Failed to load module "canberra-gtk-module" 2020/12/18 12:00:42;;GRIG;;4;;grig_debug_init: Debug handler initialised. 2020/12/18 12:00:42;;GRIG;;4;;Checking GRIG configuration. 2020/12/18 12:00:42;;GRIG;;4;;..Configuration directory: OK 2020/12/18 12:00:42;;GRIG;;4;;..Radio config files: 2020/12/18 12:00:42;;GRIG;;5;;rig_daemon_start entered 2020/12/18 12:00:42;;GRIG;;5;;rig_daemon_start: Initializing rig (id=134) 2020/12/18 12:00:42;;HAMLIB;;4;;rig_init called 2020/12/18 12:00:42;;HAMLIB;;4;;yaesu: initrigs3_yaesu called 2020/12/18 12:00:42;;HAMLIB;;4;;rig_register called 2020/12/18 12:00:42;;HAMLIB;;4;;rig_register: rig_register (121) 2020/12/18 12:00:42;;HAMLIB;;4;;rig_register called 2020/12/18 12:00:42;;HAMLIB;;4;;rig_register: rig_register (127) 2020/12/18 12:00:42;;HAMLIB;;4;;rig_register called 2020/12/18 12:00:42;;HAMLIB;;4;;rig_register: rig_register (110) 2020/12/18 12:00:42;;HAMLIB;;4;;rig_register called 2020/12/18 12:00:42;;HAMLIB;;4;;rig_register: rig_register (105) 2020/12/18 12:00:42;;HAMLIB;;4;;rig_register called 2020/12/18 12:00:42;;HAMLIB;;4;;rig_register: rig_register (106) 2020/12/18 12:00:42;;HAMLIB;;4;;rig_register called 2020/12/18 12:00:42;;HAMLIB;;4;;rig_register: rig_register (107) 2020/12/18 12:00:42;;HAMLIB;;4;;rig_register called 2020/12/18 12:00:42;;HAMLIB;;4;;rig_register: rig_register (109) 2020/12/18 12:00:42;;HAMLIB;;4;;rig_register called 2020/12/18 12:00:42;;HAMLIB;;4;;rig_register: rig_register (120) 2020/12/18 12:00:42;;HAMLIB;;4;;rig_register called 2020/12/18 12:00:42;;HAMLIB;;4;;rig_register: rig_register (101) 2020/12/18 12:00:42;;HAMLIB;;4;;rig_register called 2020/12/18 12:00:42;;HAMLIB;;4;;rig_register: rig_register (122) 2020/12/18 12:00:42;;HAMLIB;;4;;rig_register called 2020/12/18 12:00:42;;HAMLIB;;4;;rig_register: rig_register (123) 2020/12/18 12:00:42;;HAMLIB;;4;;rig_register called 2020/12/18 12:00:42;;HAMLIB;;4;;rig_register: rig_register (111) 2020/12/18 12:00:42;;HAMLIB;;4;;rig_register called 2020/12/18 12:00:42;;HAMLIB;;4;;rig_register: rig_register (115) 2020/12/18 12:00:42;;HAMLIB;;4;;rig_register called 2020/12/18 12:00:42;;HAMLIB;;4;;rig_register: rig_register (113) 2020/12/18 12:00:42;;HAMLIB;;4;;rig_register called 2020/12/18 12:00:42;;HAMLIB;;4;;rig_register: rig_register (114) 2020/12/18 12:00:42;;HAMLIB;;4;;rig_register called 2020/12/18 12:00:42;;HAMLIB;;4;;rig_register: rig_register (128) 2020/12/18 12:00:42;;HAMLIB;;4;;rig_register called 2020/12/18 12:00:42;;HAMLIB;;4;;rig_register: rig_register (131) 2020/12/18 12:00:42;;HAMLIB;;4;;rig_register called 2020/12/18 12:00:42;;HAMLIB;;4;;rig_register: rig_register (116) 2020/12/18 12:00:42;;HAMLIB;;4;;rig_register called 2020/12/18 12:00:42;;HAMLIB;;4;;rig_register: rig_register (103) 2020/12/18 12:00:42;;HAMLIB;;4;;rig_register called 2020/12/18 12:00:42;;HAMLIB;;4;;rig_register: rig_register (124) 2020/12/18 12:00:42;;HAMLIB;;4;;rig_register called 2020/12/18 12:00:42;;HAMLIB;;4;;rig_register: rig_register (104) 2020/12/18 12:00:42;;HAMLIB;;4;;rig_register called 2020/12/18 12:00:42;;HAMLIB;;4;;rig_register: rig_register (125) 2020/12/18 12:00:42;;HAMLIB;;4;;rig_register called 2020/12/18 12:00:42;;HAMLIB;;4;;rig_register: rig_register (129) 2020/12/18 12:00:42;;HAMLIB;;4;;rig_register called 2020/12/18 12:00:42;;HAMLIB;;4;;rig_register: rig_register (132) 2020/12/18 12:00:42;;HAMLIB;;4;;rig_register called 2020/12/18 12:00:42;;HAMLIB;;4;;rig_register: rig_register (130) 2020/12/18 12:00:42;;HAMLIB;;4;;rig_register called 2020/12/18 12:00:42;;HAMLIB;;4;;rig_register: rig_register (117) 2020/12/18 12:00:42;;HAMLIB;;4;;rig_register called 2020/12/18 12:00:42;;HAMLIB;;4;;rig_register: rig_register (119) 2020/12/18 12:00:42;;HAMLIB;;4;;rig_register called 2020/12/18 12:00:42;;HAMLIB;;4;;rig_register: rig_register (118) 2020/12/18 12:00:42;;HAMLIB;;4;;rig_register called 2020/12/18 12:00:42;;HAMLIB;;4;;rig_register: rig_register (126) 2020/12/18 12:00:42;;HAMLIB;;4;;rig_register called 2020/12/18 12:00:42;;HAMLIB;;4;;rig_register: rig_register (133) 2020/12/18 12:00:42;;HAMLIB;;4;;rig_register called 2020/12/18 12:00:42;;HAMLIB;;4;;rig_register: rig_register (134) 2020/12/18 12:00:42;;HAMLIB;;4;;rig_register called 2020/12/18 12:00:42;;HAMLIB;;4;;rig_register: rig_register (135) 2020/12/18 12:00:42;;HAMLIB;;4;;rig_register called 2020/12/18 12:00:42;;HAMLIB;;4;;rig_register: rig_register (136) 2020/12/18 12:00:42;;HAMLIB;;4;;newcat_init called 2020/12/18 12:00:42;;HAMLIB;;4;;rig_open called 2020/12/18 12:00:42;;HAMLIB;;4;;port_open called 2020/12/18 12:00:42;;HAMLIB;;4;;serial_open called 2020/12/18 12:00:42;;HAMLIB;;4;;serial_setup called 2020/12/18 12:00:42;;HAMLIB;;4;;newcat_open called 2020/12/18 12:00:42;;HAMLIB;;5;;newcat_open: write_delay = 0 msec 2020/12/18 12:00:42;;HAMLIB;;5;;newcat_open: post_write_delay = 5 msec 2020/12/18 12:00:42;;HAMLIB;;4;;newcat_get_trn called 2020/12/18 12:00:42;;HAMLIB;;4;;newcat_valid_command called 2020/12/18 12:00:42;;HAMLIB;;5;;newcat_valid_command AI 2020/12/18 12:00:42;;HAMLIB;;5;;cmd_str = AI; 2020/12/18 12:00:42;;HAMLIB;;4;;write_block called 2020/12/18 12:00:42;;HAMLIB;;5;;write_block(): TX 3 bytes 2020/12/18 12:00:42;;HAMLIB;;5;;0000 41 49 3b AI; 2020/12/18 12:00:42;;HAMLIB;;4;;read_string called 2020/12/18 12:00:44;;HAMLIB;;5;;read_string(): RX 5 characters 2020/12/18 12:00:44;;HAMLIB;;5;;0000 80 00 80 80 00 ..... 2020/12/18 12:00:44;;HAMLIB;;5;;newcat_get_cmd: read count = 5, ret_data = 2020/12/18 12:00:44;;HAMLIB;;2;;newcat_get_cmd: Command is not correctly terminated '' 2020/12/18 12:00:44;;HAMLIB;;4;;read_string called 2020/12/18 12:00:46;;HAMLIB;;3;;read_string(): Timed out 2.2055 seconds after 0 chars 2020/12/18 12:00:46;;HAMLIB;;5;;cmd_str = AI; 2020/12/18 12:00:46;;HAMLIB;;4;;write_block called 2020/12/18 12:00:46;;HAMLIB;;5;;write_block(): TX 3 bytes 2020/12/18 12:00:46;;HAMLIB;;5;;0000 41 49 3b AI; 2020/12/18 12:00:46;;HAMLIB;;4;;read_string called 2020/12/18 12:00:48;;HAMLIB;;5;;read_string(): RX 5 characters 2020/12/18 12:00:48;;HAMLIB;;5;;0000 80 00 80 80 00 ..... 2020/12/18 12:00:48;;HAMLIB;;5;;newcat_get_cmd: read count = 5, ret_data = 2020/12/18 12:00:48;;HAMLIB;;2;;newcat_get_cmd: Command is not correctly terminated '' 2020/12/18 12:00:48;;HAMLIB;;4;;read_string called 2020/12/18 12:00:50;;HAMLIB;;3;;read_string(): Timed out 2.2076 seconds after 0 chars 2020/12/18 12:00:50;;HAMLIB;;4;;newcat_set_trn called 2020/12/18 12:00:50;;HAMLIB;;4;;newcat_valid_command called 2020/12/18 12:00:50;;HAMLIB;;5;;newcat_valid_command AI 2020/12/18 12:00:50;;HAMLIB;;5;;cmd_str = AI0; 2020/12/18 12:00:50;;HAMLIB;;4;;serial_flush called 2020/12/18 12:00:50;;HAMLIB;;5;;cmd_str = AI0; 2020/12/18 12:00:50;;HAMLIB;;4;;write_block called 2020/12/18 12:00:50;;HAMLIB;;5;;write_block(): TX 4 bytes 2020/12/18 12:00:50;;HAMLIB;;5;;0000 41 49 30 3b AI0; 2020/12/18 12:00:50;;HAMLIB;;5;;cmd_str = ID; 2020/12/18 12:00:50;;HAMLIB;;4;;write_block called 2020/12/18 12:00:50;;HAMLIB;;5;;write_block(): TX 3 bytes 2020/12/18 12:00:50;;HAMLIB;;5;;0000 49 44 3b ID; 2020/12/18 12:00:50;;HAMLIB;;4;;read_string called 2020/12/18 12:00:52;;HAMLIB;;5;;read_string(): RX 5 characters 2020/12/18 12:00:52;;HAMLIB;;5;;0000 80 00 80 80 00 ..... 2020/12/18 12:00:52;;HAMLIB;;5;;newcat_set_cmd: read count = 5, ret_data = 2020/12/18 12:00:52;;HAMLIB;;2;;newcat_set_cmd: Unexpected verify command response '' 2020/12/18 12:00:52;;HAMLIB;;4;;serial_flush called 2020/12/18 12:00:52;;HAMLIB;;5;;cmd_str = AI0; 2020/12/18 12:00:52;;HAMLIB;;4;;write_block called 2020/12/18 12:00:52;;HAMLIB;;5;;write_block(): TX 4 bytes 2020/12/18 12:00:52;;HAMLIB;;5;;0000 41 49 30 3b AI0; 2020/12/18 12:00:52;;HAMLIB;;5;;cmd_str = ID; 2020/12/18 12:00:52;;HAMLIB;;4;;write_block called 2020/12/18 12:00:52;;HAMLIB;;5;;write_block(): TX 3 bytes 2020/12/18 12:00:52;;HAMLIB;;5;;0000 49 44 3b ID; 2020/12/18 12:00:52;;HAMLIB;;4;;read_string called 2020/12/18 12:00:54;;HAMLIB;;5;;read_string(): RX 5 characters 2020/12/18 12:00:54;;HAMLIB;;5;;0000 80 00 80 80 00 ..... 2020/12/18 12:00:54;;HAMLIB;;5;;newcat_set_cmd: read count = 5, ret_data = 2020/12/18 12:00:54;;HAMLIB;;2;;newcat_set_cmd: Unexpected verify command response '' 2020/12/18 12:00:54;;HAMLIB;;4;;serial_flush called 2020/12/18 12:00:54;;HAMLIB;;5;;cmd_str = AI0; 2020/12/18 12:00:54;;HAMLIB;;4;;write_block called 2020/12/18 12:00:54;;HAMLIB;;5;;write_block(): TX 4 bytes 2020/12/18 12:00:54;;HAMLIB;;5;;0000 41 49 30 3b AI0; 2020/12/18 12:00:54;;HAMLIB;;5;;cmd_str = ID; 2020/12/18 12:00:54;;HAMLIB;;4;;write_block called 2020/12/18 12:00:54;;HAMLIB;;5;;write_block(): TX 3 bytes 2020/12/18 12:00:54;;HAMLIB;;5;;0000 49 44 3b ID; 2020/12/18 12:00:54;;HAMLIB;;4;;read_string called |
|
From: Don P. <rad...@gm...> - 2020-04-07 01:59:31
|
Hello I switched from my desktop (ubuntu 18.04) to my laptop, also 18.04.. Now, grig has to be ran as root..On the desktop I just clicked on grig after choosing the correct hamlib. Wondering why sudo is now required? Donald Porter Jr, D.Min. <http://arrl.org/Groups/view/indiana> w9...@w9... rad...@gm... |
|
From: Barry J. <zen...@ze...> - 2020-02-02 13:15:09
|
Hi it seems that: state.rx_range_list[i].start state.rx_range_list[i].end Used in rig-daemon-check.c are no longer valid in hamlib. I am the grig package maintainer for Mageia Linux and have moved all our other hamlib based packages to hamlib-4.0~git as there has been no full release of hamlib for some time despite over 900 commits to the project. Only grig does not build. Will grig be updated to work again? Thanks, Barry |
|
From: Pete S. <wb...@gm...> - 2017-01-13 02:53:32
|
Hi folks, I'm using Grig 0.8.1 on an HP Envy laptop running Xubuntu 16.10. I've set up Grig so it can share communications with Xlog via their localhost settings. Oddly, I can see the frequency readout on the logging program, as expected in this configuration. But frequency doesn't display on Grig. When I try to enter it manually, the frequency display goes blank and the rig (FT817ND) keeps its old frequency. Nor can I change operating modes with Grig in this configuration. I can, however, power up the rig and shut it down with Grig's power button. And the S meter responds normally. I don't get this behavior in Grig when I go directly through /dev/ttyUSB0. But if I try to use Grig and Xlog through /dev/ttyUSBO, the readout of each briefly goes bonkers every 10 or 15 seconds. Polling conflict? Finally, if I try to run Grig from a terminal via localhost, I see the following line in the startup echoes: 2017/01/12 19:44:34;;GRIG;;1;;rig_daemon_check_mode: Can not find frequency range for this mode (2)! Bug in backend? Any thoughts on how I can get Grig to play nicely through localhost? With best regards, Pete -- Peter N. Spotts -- WB5BUP http://www.wb5bup.net Email: wb...@ar... | Skype: pspotts QCWA #34679 | SKCC #4853S | QRP-ARCI #4174 NEQRP #714 | NAQCC #2446 | G-QRP #13202 | Polar Bear #348 "Amateur radio is a contact sport. Get on the air and make a contact!" -- Lyle Amundson, K0LFV |
|
From: Antonio M <ant...@gm...> - 2016-04-25 14:31:58
|
After a long time I reconnected my rig to my Pc using a 4-port communication interface CI-V and a serial/USB converter (see DMESG) [ 367.139148] usb 4-1: New USB device found, idVendor=0403, idProduct=6001 [ 367.139154] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 367.139158] usb 4-1: Product: USB Serial Converter [ 367.139161] usb 4-1: Manufacturer: FTDI [ 367.139164] usb 4-1: SerialNumber: FTDVRKNS [ 367.145135] ftdi_sio 4-1:1.0: FTDI USB Serial Device converter detected [ 367.145227] usb 4-1: Detected FT232RL [ 367.149152] usb 4-1: FTDI USB Serial Device converter now attached to ttyUSB0 when I start Grig (as root) I get [antonio@pcdesktop1 ~]$ su Password: [root@pcdesktop1 antonio]# grig -m 334 -r /dev/ttyUSB0 2016/04/03 11:38:40;;GRIG;;4;;grig_debug_init: Debug handler initialised. 2016/04/03 11:38:40;;GRIG;;4;;Checking GRIG configuration. 2016/04/03 11:38:40;;GRIG;;4;;..Configuration directory: OK 2016/04/03 11:38:40;;GRIG;;4;;..Radio config files: 2016/04/03 11:38:40;;GRIG;;5;;rig_daemon_start entered 2016/04/03 11:38:40;;GRIG;;5;;rig_daemon_start: Initializing rig (id=334) 2016/04/03 11:38:40;;HAMLIB;;4;;rig:rig_init called 2016/04/03 11:38:40;;HAMLIB;;4;;icom: _init called 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (355) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (309) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (310) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (311) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (313) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (314) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (315) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (319) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (320) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (321) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (322) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (367) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (323) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (346) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (324) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (328) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (330) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (326) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (327) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (347) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (357) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (363) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (329) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (362) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (345) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (356) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (360) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (370) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (361) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (331) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (312) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (316) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (332) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (334) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (344) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (368) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (335) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (369) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (336) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (358) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (337) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (338) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (339) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (340) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (341) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (342) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (343) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (366) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (303) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (304) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (306) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (307) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (302) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (352) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (353) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (351) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (364) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (365) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (354) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (371) 2016/04/03 11:38:40;;HAMLIB;;4;;rig:rig_open called 2016/04/03 11:38:40;;GRIG;;5;;rig_daemon_start: Init successfull, executing post-init 2016/04/03 11:38:40;;HAMLIB;;5;;write_block(): TX 6 bytes 2016/04/03 11:38:40;;HAMLIB;;5;;0000 fe fe 4c e0 04 fd ..L... 2016/04/03 11:38:40;;HAMLIB;;5;;read_string(): RX 6 characters 2016/04/03 11:38:40;;HAMLIB;;5;;0000 fe fe 4c e0 04 fd ..L... 2016/04/03 11:38:40;;HAMLIB;;5;;read_string(): RX 8 characters 2016/04/03 11:38:40;;HAMLIB;;5;;0000 fe fe e0 4c 04 05 01 fd ...L.... 2016/04/03 11:38:40;;HAMLIB;;5;;write_block(): TX 7 bytes 2016/04/03 11:38:40;;HAMLIB;;5;;0000 fe fe 4c e0 1a 03 fd ..L.... 2016/04/03 11:38:40;;HAMLIB;;5;;read_string(): RX 7 characters 2016/04/03 11:38:40;;HAMLIB;;5;;0000 fe fe 4c e0 1a 03 fd ..L.... 2016/04/03 11:38:40;;HAMLIB;;5;;read_string(): RX 6 characters 2016/04/03 11:38:40;;HAMLIB;;5;;0000 fe fe e0 4c fa fd ...L.. 2016/04/03 11:38:40;;GRIG;;1;;rig_daemon_check_mode: Can not find frequency range for this mode (32)! Bug in backend? 2016/04/03 11:38:40;;GRIG;;5;;rig_daemon_post_init: GET bits: 0000000000000000 2016/04/03 11:38:40;;GRIG;;5;;rig_daemon_post_init: SET bits: 0000000000000XXX 2016/04/03 11:38:40;;GRIG;;5;;rig_daemon_start: Starting rig daemon 2016/04/03 11:38:40;;GRIG;;4;;rig_daemon_start: Daemon thread started 2016/04/03 11:38:40;;GRIG;;4;;Initialising key press handler and I don't see any freqquency on the Grig window. But: using rigctl for hamlib debugging I think that it is working fine. So where is my mistake is tarting Grig?? Rig command: h Channel: 1 write_block(): TX 6 bytes 0000 fe fe 4c e0 08 fd ..L... read_string(): RX 6 characters 0000 fe fe 4c e0 08 fd ..L... read_string(): RX 6 characters 0000 fe fe e0 4c fb fd ...L.. write_block(): TX 7 bytes 0000 fe fe 4c e0 08 01 fd ..L.... read_string(): RX 7 characters 0000 fe fe 4c e0 08 01 fd ..L.... read_string(): RX 6 characters 0000 fe fe e0 4c fb fd ...L.. write_block(): TX 6 bytes 0000 fe fe 4c e0 03 fd ..L... read_string(): RX 6 characters 0000 fe fe 4c e0 03 fd ..L... read_string(): RX 11 characters 0000 fe fe e0 4c 03 00 50 57 45 01 fd ...L..PWE.. icom_get_freq: freq len (5) differs from expected write_block(): TX 6 bytes 0000 fe fe 4c e0 04 fd ..L... read_string(): RX 6 characters 0000 fe fe 4c e0 04 fd ..L... read_string(): RX 8 characters 0000 fe fe e0 4c 04 05 01 fd ...L.... write_block(): TX 7 bytes 0000 fe fe 4c e0 1a 03 fd ..L.... read_string(): RX 7 characters 0000 fe fe 4c e0 1a 03 fd ..L.... read_string(): RX 6 characters 0000 fe fe e0 4c fa fd ...L.. Channel: 1, Name: '' VFO: MEM, Antenna: 0, Split: OFF Freq: 145.575 MHz Mode: FM Width: 15 kHz txFreq: 145.575 MHz txMode: FM txWidth: 15 kHz Shift: None, Offset: 0 Hz, Step: 0 Hz, RIT: 0 Hz, XIT: 0 Hz CTCSS: 0.0Hz, CTCSSsql: 0.0Hz, DCS: 0.0, DCSsql: 0.0 Functions: Levels: Rig command: h Channel: 2 write_block(): TX 6 bytes 0000 fe fe 4c e0 08 fd ..L... read_string(): RX 6 characters 0000 fe fe 4c e0 08 fd ..L... read_string(): RX 6 characters 0000 fe fe e0 4c fb fd ...L.. write_block(): TX 7 bytes 0000 fe fe 4c e0 08 02 fd ..L.... read_string(): RX 7 characters 0000 fe fe 4c e0 08 02 fd ..L.... read_string(): RX 6 characters 0000 fe fe e0 4c fb fd ...L.. write_block(): TX 6 bytes 0000 fe fe 4c e0 03 fd ..L... read_string(): RX 6 characters 0000 fe fe 4c e0 03 fd ..L... read_string(): RX 11 characters 0000 fe fe e0 4c 03 00 00 80 45 01 fd ...L....E.. icom_get_freq: freq len (5) differs from expected write_block(): TX 6 bytes 0000 fe fe 4c e0 04 fd ..L... read_string(): RX 6 characters 0000 fe fe 4c e0 04 fd ..L... read_string(): RX 8 characters 0000 fe fe e0 4c 04 05 01 fd ...L.... write_block(): TX 7 bytes 0000 fe fe 4c e0 1a 03 fd ..L.... read_string(): RX 7 characters 0000 fe fe 4c e0 1a 03 fd ..L.... read_string(): RX 6 characters 0000 fe fe e0 4c fa fd ...L.. Channel: 2, Name: '' VFO: MEM, Antenna: 0, Split: OFF Freq: 145.8 MHz Mode: FM Width: 15 kHz txFreq: 145.8 MHz txMode: FM txWidth: 15 kHz Shift: None, Offset: 0 Hz, Step: 0 Hz, RIT: 0 Hz, XIT: 0 Hz CTCSS: 0.0Hz, CTCSSsql: 0.0Hz, DCS: 0.0, DCSsql: 0.0 -- Antonio Montagnani Skype : amontag52 Linux Fedora 23 (Workstation) inviato da Gmail |
|
From: Antonio M <ant...@gm...> - 2016-04-04 17:26:18
|
---------- Messaggio inoltrato ---------- Da: "Antonio M" <ant...@gm...> Data: 04/Apr/2016 19:25 Oggetto: Re: [Groundstation-user] How to use Grig with Icom 821H A: <jcz...@co...> Cc: My rig can talk With My computer as i tested hamlib and i can get frequency so i assume That grig command is wrong Il 03/Apr/2016 22:56, <jcz...@co...> ha scritto: > Antonio, > I could not get grig to work with Fedora 23. I switched to a PC running > Ubuntu 15.10 and it came right up. My problem was that the radio could not > communicate with the PC. > John > > > Sent from XFINITY Connect Mobile App > > > -----Original Message----- > > From: ant...@gm... > To: gro...@li... > Cc: > Sent: 2016-04-03 13:36:46 GMT > Subject: Re: [Groundstation-user] How to use Grig with Icom 821H > > using rigctl for hamlib debugging I think that it is working fine. So > where is my mistake is tarting Grig?? > Rig command: h > Channel: 1 > write_block(): TX 6 bytes > 0000 fe fe 4c e0 08 fd > ..L... > read_string(): RX 6 characters > 0000 fe fe 4c e0 08 fd > ..L... > read_string(): RX 6 characters > 0000 fe fe e0 4c fb fd > ...L.. > write_block(): TX 7 bytes > 0000 fe fe 4c e0 08 01 fd > ..L.... > read_string(): RX 7 characters > 0000 fe fe 4c e0 08 01 fd > ..L.... > read_string(): RX 6 characters > 0000 fe fe e0 4c fb fd > ...L.. > write_block(): TX 6 bytes > 0000 fe fe 4c e0 03 fd > ..L... > read_string(): RX 6 characters > 0000 fe fe 4c e0 03 fd > ..L... > read_string(): RX 11 characters > 0000 fe fe e0 4c 03 00 50 57 45 01 fd > ...L..PWE.. > icom_get_freq: freq len (5) differs from expected > write_block(): TX 6 bytes > 0000 fe fe 4c e0 04 fd > ..L... > read_string(): RX 6 characters > 0000 fe fe 4c e0 04 fd > ..L... > read_string(): RX 8 characters > 0000 fe fe e0 4c 04 05 01 fd > ...L.... > write_block(): TX 7 bytes > 0000 fe fe 4c e0 1a 03 fd > ..L.... > read_string(): RX 7 characters > 0000 fe fe 4c e0 1a 03 fd > ..L.... > read_string(): RX 6 characters > 0000 fe fe e0 4c fa fd > ...L.. > Channel: 1, Name: '' > VFO: MEM, Antenna: 0, Split: OFF > Freq: 145.575 MHz Mode: FM Width: 15 kHz > txFreq: 145.575 MHz txMode: FM txWidth: 15 kHz > Shift: None, Offset: 0 Hz, Step: 0 Hz, RIT: 0 Hz, XIT: 0 Hz > CTCSS: 0.0Hz, CTCSSsql: 0.0Hz, DCS: 0.0, DCSsql: 0.0 > Functions: > Levels: > > Rig command: h > Channel: 2 > write_block(): TX 6 bytes > 0000 fe fe 4c e0 08 fd > ..L... > read_string(): RX 6 characters > 0000 fe fe 4c e0 08 fd > ..L... > read_string(): RX 6 characters > 0000 fe fe e0 4c fb fd > ...L.. > write_block(): TX 7 bytes > 0000 fe fe 4c e0 08 02 fd > ..L.... > read_string(): RX 7 characters > 0000 fe fe 4c e0 08 02 fd > ..L.... > read_string(): RX 6 characters > 0000 fe fe e0 4c fb fd > ...L.. > write_block(): TX 6 bytes > 0000 fe fe 4c e0 03 fd > ..L... > read_string(): RX 6 characters > 0000 fe fe 4c e0 03 fd > ..L... > read_string(): RX 11 characters > 0000 fe fe e0 4c 03 00 00 80 45 01 fd > ...L....E.. > icom_get_freq: freq len (5) differs from expected > write_block(): TX 6 bytes > 0000 fe fe 4c e0 04 fd > ..L... > read_string(): RX 6 characters > 0000 fe fe 4c e0 04 fd > ..L... > read_string(): RX 8 characters > 0000 fe fe e0 4c 04 05 01 fd > ...L.... > write_block(): TX 7 bytes > 0000 fe fe 4c e0 1a 03 fd > ..L.... > read_string(): RX 7 characters > 0000 fe fe 4c e0 1a 03 fd > ..L.... > read_string(): RX 6 characters > 0000 fe fe e0 4c fa fd > ...L.. > Channel: 2, Name: '' > VFO: MEM, Antenna: 0, Split: OFF > Freq: 145.8 MHz Mode: FM Width: 15 kHz > txFreq: 145.8 MHz txMode: FM txWidth: 15 kHz > Shift: None, Offset: 0 Hz, Step: 0 Hz, RIT: 0 Hz, XIT: 0 Hz > CTCSS: 0.0Hz, CTCSSsql: 0.0Hz, DCS: 0.0, DCSsql: 0.0 > > 2016-04-03 16:07 GMT+02:00 Antonio M <ant...@gm...>: > >> >> >> >> After a long time I reconnected my rig to my Pc using a 4-port >> communication interface CI-V and a serial/USB converter (see DMESG) >> >> [ 367.139148] usb 4-1: New USB device found, idVendor=0403, >> idProduct=6001 >> [ 367.139154] usb 4-1: New USB device strings: Mfr=1, Product=2, >> SerialNumber=3 >> [ 367.139158] usb 4-1: Product: USB Serial Converter >> [ 367.139161] usb 4-1: Manufacturer: FTDI >> [ 367.139164] usb 4-1: SerialNumber: FTDVRKNS >> [ 367.145135] ftdi_sio 4-1:1.0: FTDI USB Serial Device converter >> detected >> [ 367.145227] usb 4-1: Detected FT232RL >> [ 367.149152] usb 4-1: FTDI USB Serial Device converter now attached to >> ttyUSB0 >> >> when I start Grig (as root) I get >> >> [antonio@pcdesktop1 ~]$ su >> Password: >> [root@pcdesktop1 antonio]# grig -m 334 -r /dev/ttyUSB0 >> 2016/04/03 11:38:40;;GRIG;;4;;grig_debug_init: Debug handler initialised. >> 2016/04/03 11:38:40;;GRIG;;4;;Checking GRIG configuration. >> 2016/04/03 11:38:40;;GRIG;;4;;..Configuration directory: OK >> 2016/04/03 11:38:40;;GRIG;;4;;..Radio config files: >> 2016/04/03 11:38:40;;GRIG;;5;;rig_daemon_start entered >> 2016/04/03 11:38:40;;GRIG;;5;;rig_daemon_start: Initializing rig (id=334) >> 2016/04/03 11:38:40;;HAMLIB;;4;;rig:rig_init called >> 2016/04/03 11:38:40;;HAMLIB;;4;;icom: _init called >> 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (355) >> 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (309) >> 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (310) >> 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (311) >> 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (313) >> 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (314) >> 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (315) >> 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (319) >> 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (320) >> 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (321) >> 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (322) >> 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (367) >> 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (323) >> 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (346) >> 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (324) >> 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (328) >> 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (330) >> 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (326) >> 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (327) >> 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (347) >> 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (357) >> 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (363) >> 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (329) >> 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (362) >> 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (345) >> 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (356) >> 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (360) >> 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (370) >> 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (361) >> 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (331) >> 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (312) >> 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (316) >> 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (332) >> 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (334) >> 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (344) >> 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (368) >> 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (335) >> 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (369) >> 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (336) >> 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (358) >> 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (337) >> 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (338) >> 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (339) >> 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (340) >> 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (341) >> 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (342) >> 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (343) >> 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (366) >> 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (303) >> 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (304) >> 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (306) >> 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (307) >> 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (302) >> 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (352) >> 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (353) >> 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (351) >> 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (364) >> 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (365) >> 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (354) >> 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (371) >> 2016/04/03 11:38:40;;HAMLIB;;4;;rig:rig_open called >> 2016/04/03 11:38:40;;GRIG;;5;;rig_daemon_start: Init successfull, >> executing post-init >> 2016/04/03 11:38:40;;HAMLIB;;5;;write_block(): TX 6 bytes >> 2016/04/03 11:38:40;;HAMLIB;;5;;0000 fe fe 4c e0 04 >> fd ..L... >> 2016/04/03 11:38:40;;HAMLIB;;5;;read_string(): RX 6 characters >> 2016/04/03 11:38:40;;HAMLIB;;5;;0000 fe fe 4c e0 04 >> fd ..L... >> 2016/04/03 11:38:40;;HAMLIB;;5;;read_string(): RX 8 characters >> 2016/04/03 11:38:40;;HAMLIB;;5;;0000 fe fe e0 4c 04 05 01 >> fd ...L.... >> 2016/04/03 11:38:40;;HAMLIB;;5;;write_block(): TX 7 bytes >> 2016/04/03 11:38:40;;HAMLIB;;5;;0000 fe fe 4c e0 1a 03 >> fd ..L.... >> 2016/04/03 11:38:40;;HAMLIB;;5;;read_string(): RX 7 characters >> 2016/04/03 11:38:40;;HAMLIB;;5;;0000 fe fe 4c e0 1a 03 >> fd ..L.... >> 2016/04/03 11:38:40;;HAMLIB;;5;;read_string(): RX 6 characters >> 2016/04/03 11:38:40;;HAMLIB;;5;;0000 fe fe e0 4c fa >> fd ...L.. >> 2016/04/03 11:38:40;;GRIG;;1;;rig_daemon_check_mode: Can not find >> frequency range for this mode (32)! Bug in backend? >> 2016/04/03 11:38:40;;GRIG;;5;;rig_daemon_post_init: GET bits: >> 0000000000000000 >> 2016/04/03 11:38:40;;GRIG;;5;;rig_daemon_post_init: SET bits: >> 0000000000000XXX >> 2016/04/03 11:38:40;;GRIG;;5;;rig_daemon_start: Starting rig daemon >> 2016/04/03 11:38:40;;GRIG;;4;;rig_daemon_start: Daemon thread started >> 2016/04/03 11:38:40;;GRIG;;4;;Initialising key press handler >> >> and I don't see any freqquency on the Grig window. >> >> What is wrong in my understanding?? >> >> >> >> -- >> Antonio Montagnani >> Skype : amontag52 >> >> Linux Fedora 23 (Workstation) >> inviato da Gmail >> > > > > -- > Antonio Montagnani > Skype : amontag52 > > Linux Fedora 23 (Workstation) > inviato da Gmail > ------------------------------------------------------------------------------ > Transform Data into Opportunity. Accelerate data analysis in your > applications with Intel Data Analytics Acceleration Library. Click to learn > more. http://pubads.g.doubleclick.net/gampad/clk?id=278785471&iu=/4140 > > _______________________________________________ Groundstation-user mailing > list Gro...@li... > https://lists.sourceforge.net/lists/listinfo/groundstation-user > > > > |
|
From: <jcz...@co...> - 2016-04-03 20:57:04
|
Antonio,<br>I could not get grig to work with Fedora 23. I switched to a PC running Ubuntu 15.10 and it came right up. My problem was that the radio could not communicate with the PC.<br>John<br><br><br>Sent from XFINITY Connect Mobile App<br><br><br>-----Original Message-----<br><br>From: ant...@gm...<br>To: gro...@li...<br>Cc: <br>Sent: 2016-04-03 13:36:46 GMT<br>Subject: Re: [Groundstation-user] How to use Grig with Icom 821H<br><br><html><div dir="ltr">using rigctl for hamlib debugging I think that it is working fine. So where is my mistake is tarting Grig??<br>Rig command: h<br>Channel: 1<br>write_block(): TX 6 bytes<br>0000 fe fe 4c e0 08 fd ..L... <br>read_string(): RX 6 characters<br>0000 fe fe 4c e0 08 fd ..L... <br>read_string(): RX 6 characters<br>0000 fe fe e0 4c fb fd ...L.. <br>write_block(): TX 7 bytes<br>0000 fe fe 4c e0 08 01 fd ..L.... <br>read_string(): RX 7 characters<br>0000 fe fe 4c e0 08 01 fd ..L.... <br>read_string(): RX 6 characters<br>0000 fe fe e0 4c fb fd ...L.. <br>write_block(): TX 6 bytes<br>0000 fe fe 4c e0 03 fd ..L... <br>read_string(): RX 6 characters<br>0000 fe fe 4c e0 03 fd ..L... <br>read_string(): RX 11 characters<br>0000 fe fe e0 4c 03 00 50 57 45 01 fd ...L..PWE.. <br>icom_get_freq: freq len (5) differs from expected<br>write_block(): TX 6 bytes<br>0000 fe fe 4c e0 04 fd ..L... <br>read_string(): RX 6 characters<br>0000 fe fe 4c e0 04 fd ..L... <br>read_string(): RX 8 characters<br>0000 fe fe e0 4c 04 05 01 fd ...L.... <br>write_block(): TX 7 bytes<br>0000 fe fe 4c e0 1a 03 fd ..L.... <br>read_string(): RX 7 characters<br>0000 fe fe 4c e0 1a 03 fd ..L.... <br>read_string(): RX 6 characters<br>0000 fe fe e0 4c fa fd ...L.. <br>Channel: 1, Name: ''<br>VFO: MEM, Antenna: 0, Split: OFF<br>Freq: 145.575 MHz Mode: FM Width: 15 kHz<br>txFreq: 145.575 MHz txMode: FM txWidth: 15 kHz<br>Shift: None, Offset: 0 Hz, Step: 0 Hz, RIT: 0 Hz, XIT: 0 Hz<br>CTCSS: 0.0Hz, CTCSSsql: 0.0Hz, DCS: 0.0, DCSsql: 0.0<br>Functions: <br>Levels:<br><br>Rig command: h<br>Channel: 2<br>write_block(): TX 6 bytes<br>0000 fe fe 4c e0 08 fd ..L... <br>read_string(): RX 6 characters<br>0000 fe fe 4c e0 08 fd ..L... <br>read_string(): RX 6 characters<br>0000 fe fe e0 4c fb fd ...L.. <br>write_block(): TX 7 bytes<br>0000 fe fe 4c e0 08 02 fd ..L.... <br>read_string(): RX 7 characters<br>0000 fe fe 4c e0 08 02 fd ..L.... <br>read_string(): RX 6 characters<br>0000 fe fe e0 4c fb fd ...L.. <br>write_block(): TX 6 bytes<br>0000 fe fe 4c e0 03 fd ..L... <br>read_string(): RX 6 characters<br>0000 fe fe 4c e0 03 fd ..L... <br>read_string(): RX 11 characters<br>0000 fe fe e0 4c 03 00 00 80 45 01 fd ...L....E.. <br>icom_get_freq: freq len (5) differs from expected<br>write_block(): TX 6 bytes<br>0000 fe fe 4c e0 04 fd ..L... <br>read_string(): RX 6 characters<br>0000 fe fe 4c e0 04 fd ..L... <br>read_string(): RX 8 characters<br>0000 fe fe e0 4c 04 05 01 fd ...L.... <br>write_block(): TX 7 bytes<br>0000 fe fe 4c e0 1a 03 fd ..L.... <br>read_string(): RX 7 characters<br>0000 fe fe 4c e0 1a 03 fd ..L.... <br>read_string(): RX 6 characters<br>0000 fe fe e0 4c fa fd ...L.. <br>Channel: 2, Name: ''<br>VFO: MEM, Antenna: 0, Split: OFF<br>Freq: 145.8 MHz Mode: FM Width: 15 kHz<br>txFreq: 145.8 MHz txMode: FM txWidth: 15 kHz<br>Shift: None, Offset: 0 Hz, Step: 0 Hz, RIT: 0 Hz, XIT: 0 Hz<br>CTCSS: 0.0Hz, CTCSSsql: 0.0Hz, DCS: 0.0, DCSsql: 0.0<br></div><div class="gmail_extra"><br><div class="gmail_quote">2016-04-03 16:07 GMT+02:00 Antonio M <span dir="ltr"><<a href="mailto:ant...@gm..." >ant...@gm...</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5"><div dir="ltr"><br><div class="gmail_quote"><br><br><div dir="ltr"><div>After a long time I reconnected my rig to my Pc using a 4-port communication interface CI-V and a serial/USB converter (see DMESG)<br><br> <a href="tel:%5B%C2%A0%20367.139148" >[ 367.139148</a>] usb 4-1: New USB device found, idVendor=0403, idProduct=6001<br><a href="tel:%5B%C2%A0%20367.139154" >[ 367.139154</a>] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3<br><a href="tel:%5B%C2%A0%20367.139158" >[ 367.139158</a>] usb 4-1: Product: USB Serial Converter<br><a href="tel:%5B%C2%A0%20367.139161" >[ 367.139161</a>] usb 4-1: Manufacturer: FTDI<br><a href="tel:%5B%C2%A0%20367.139164" >[ 367.139164</a>] usb 4-1: SerialNumber: FTDVRKNS<br><a href="tel:%5B%C2%A0%20367.145135" >[ 367.145135</a>] ftdi_sio 4-1:1.0: FTDI USB Serial Device converter detected<br><a href="tel:%5B%C2%A0%20367.145227" >[ 367.145227</a>] usb 4-1: Detected FT232RL<br><a href="tel:%5B%C2%A0%20367.149152" >[ 367.149152</a>] usb 4-1: FTDI USB Serial Device converter now attached to ttyUSB0<br><br></div>when I start Grig (as root) I get<br clear="all"><br><div><div>[antonio@pcdesktop1 ~]$ su<br>Password: <br>[root@pcdesktop1 antonio]# grig -m 334 -r /dev/ttyUSB0 <br>2016/04/03 11:38:40;;GRIG;;4;;grig_debug_init: Debug handler initialised.<br>2016/04/03 11:38:40;;GRIG;;4;;Checking GRIG configuration.<br>2016/04/03 11:38:40;;GRIG;;4;;..Configuration directory: OK<br>2016/04/03 11:38:40;;GRIG;;4;;..Radio config files:<br>2016/04/03 11:38:40;;GRIG;;5;;rig_daemon_start entered<br>2016/04/03 11:38:40;;GRIG;;5;;rig_daemon_start: Initializing rig (id=334)<br>2016/04/03 11:38:40;;HAMLIB;;4;;rig:rig_init called<br>2016/04/03 11:38:40;;HAMLIB;;4;;icom: _init called<br>2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (355)<br>2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (309)<br>2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (310)<br>2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (311)<br>2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (313)<br>2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (314)<br>2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (315)<br>2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (319)<br>2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (320)<br>2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (321)<br>2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (322)<br>2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (367)<br>2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (323)<br>2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (346)<br>2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (324)<br>2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (328)<br>2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (330)<br>2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (326)<br>2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (327)<br>2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (347)<br>2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (357)<br>2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (363)<br>2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (329)<br>2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (362)<br>2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (345)<br>2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (356)<br>2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (360)<br>2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (370)<br>2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (361)<br>2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (331)<br>2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (312)<br>2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (316)<br>2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (332)<br>2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (334)<br>2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (344)<br>2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (368)<br>2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (335)<br>2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (369)<br>2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (336)<br>2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (358)<br>2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (337)<br>2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (338)<br>2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (339)<br>2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (340)<br>2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (341)<br>2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (342)<br>2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (343)<br>2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (366)<br>2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (303)<br>2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (304)<br>2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (306)<br>2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (307)<br>2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (302)<br>2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (352)<br>2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (353)<br>2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (351)<br>2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (364)<br>2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (365)<br>2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (354)<br>2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (371)<br>2016/04/03 11:38:40;;HAMLIB;;4;;rig:rig_open called<br>2016/04/03 11:38:40;;GRIG;;5;;rig_daemon_start: Init successfull, executing post-init<br>2016/04/03 11:38:40;;HAMLIB;;5;;write_block(): TX 6 bytes<br>2016/04/03 11:38:40;;HAMLIB;;5;;0000 fe fe 4c e0 04 fd ..L...<br>2016/04/03 11:38:40;;HAMLIB;;5;;read_string(): RX 6 characters<br>2016/04/03 11:38:40;;HAMLIB;;5;;0000 fe fe 4c e0 04 fd ..L...<br>2016/04/03 11:38:40;;HAMLIB;;5;;read_string(): RX 8 characters<br>2016/04/03 11:38:40;;HAMLIB;;5;;0000 fe fe e0 4c 04 05 01 fd ...L....<br>2016/04/03 11:38:40;;HAMLIB;;5;;write_block(): TX 7 bytes<br>2016/04/03 11:38:40;;HAMLIB;;5;;0000 fe fe 4c e0 1a 03 fd ..L....<br>2016/04/03 11:38:40;;HAMLIB;;5;;read_string(): RX 7 characters<br>2016/04/03 11:38:40;;HAMLIB;;5;;0000 fe fe 4c e0 1a 03 fd ..L....<br>2016/04/03 11:38:40;;HAMLIB;;5;;read_string(): RX 6 characters<br>2016/04/03 11:38:40;;HAMLIB;;5;;0000 fe fe e0 4c fa fd ...L..<br>2016/04/03 11:38:40;;GRIG;;1;;rig_daemon_check_mode: Can not find frequency range for this mode (32)! Bug in backend?<br>2016/04/03 11:38:40;;GRIG;;5;;rig_daemon_post_init: GET bits: 0000000000000000<br>2016/04/03 11:38:40;;GRIG;;5;;rig_daemon_post_init: SET bits: 0000000000000XXX<br>2016/04/03 11:38:40;;GRIG;;5;;rig_daemon_start: Starting rig daemon<br>2016/04/03 11:38:40;;GRIG;;4;;rig_daemon_start: Daemon thread started<br>2016/04/03 11:38:40;;GRIG;;4;;Initialising key press handler<br><br></div><div>and I don't see any freqquency on the Grig window.<br><br></div><div>What is wrong in my understanding??<span><font color="#888888"><br></font></span></div><span></span><br></div></div></div><br clear="all"><br>-- <br><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div>Antonio Montagnani<br>Skype : amontag52<br><br>Linux Fedora 23 (Workstation)<br>inviato da Gmail</div></div></div></div></div></div></div> </div> </div></div></blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div>Antonio Montagnani<br>Skype : amontag52<br><br>Linux Fedora 23 (Workstation)<br>inviato da Gmail</div></div></div></div></div></div></div> </div> <html><body>------------------------------------------------------------------------------ Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://pubads.g.doubleclick.net/gampad/clk?id=278785471&iu=/4140<br><br></body></html><html><body>_______________________________________________ Groundstation-user mailing list Gro...@li... https://lists.sourceforge.net/lists/listinfo/groundstation-user <br><br></body></html></html><br><br> |
|
From: Antonio M <ant...@gm...> - 2016-04-03 18:36:17
|
using rigctl for hamlib debugging I think that it is working fine. So where is my mistake is tarting Grig?? Rig command: h Channel: 1 write_block(): TX 6 bytes 0000 fe fe 4c e0 08 fd ..L... read_string(): RX 6 characters 0000 fe fe 4c e0 08 fd ..L... read_string(): RX 6 characters 0000 fe fe e0 4c fb fd ...L.. write_block(): TX 7 bytes 0000 fe fe 4c e0 08 01 fd ..L.... read_string(): RX 7 characters 0000 fe fe 4c e0 08 01 fd ..L.... read_string(): RX 6 characters 0000 fe fe e0 4c fb fd ...L.. write_block(): TX 6 bytes 0000 fe fe 4c e0 03 fd ..L... read_string(): RX 6 characters 0000 fe fe 4c e0 03 fd ..L... read_string(): RX 11 characters 0000 fe fe e0 4c 03 00 50 57 45 01 fd ...L..PWE.. icom_get_freq: freq len (5) differs from expected write_block(): TX 6 bytes 0000 fe fe 4c e0 04 fd ..L... read_string(): RX 6 characters 0000 fe fe 4c e0 04 fd ..L... read_string(): RX 8 characters 0000 fe fe e0 4c 04 05 01 fd ...L.... write_block(): TX 7 bytes 0000 fe fe 4c e0 1a 03 fd ..L.... read_string(): RX 7 characters 0000 fe fe 4c e0 1a 03 fd ..L.... read_string(): RX 6 characters 0000 fe fe e0 4c fa fd ...L.. Channel: 1, Name: '' VFO: MEM, Antenna: 0, Split: OFF Freq: 145.575 MHz Mode: FM Width: 15 kHz txFreq: 145.575 MHz txMode: FM txWidth: 15 kHz Shift: None, Offset: 0 Hz, Step: 0 Hz, RIT: 0 Hz, XIT: 0 Hz CTCSS: 0.0Hz, CTCSSsql: 0.0Hz, DCS: 0.0, DCSsql: 0.0 Functions: Levels: Rig command: h Channel: 2 write_block(): TX 6 bytes 0000 fe fe 4c e0 08 fd ..L... read_string(): RX 6 characters 0000 fe fe 4c e0 08 fd ..L... read_string(): RX 6 characters 0000 fe fe e0 4c fb fd ...L.. write_block(): TX 7 bytes 0000 fe fe 4c e0 08 02 fd ..L.... read_string(): RX 7 characters 0000 fe fe 4c e0 08 02 fd ..L.... read_string(): RX 6 characters 0000 fe fe e0 4c fb fd ...L.. write_block(): TX 6 bytes 0000 fe fe 4c e0 03 fd ..L... read_string(): RX 6 characters 0000 fe fe 4c e0 03 fd ..L... read_string(): RX 11 characters 0000 fe fe e0 4c 03 00 00 80 45 01 fd ...L....E.. icom_get_freq: freq len (5) differs from expected write_block(): TX 6 bytes 0000 fe fe 4c e0 04 fd ..L... read_string(): RX 6 characters 0000 fe fe 4c e0 04 fd ..L... read_string(): RX 8 characters 0000 fe fe e0 4c 04 05 01 fd ...L.... write_block(): TX 7 bytes 0000 fe fe 4c e0 1a 03 fd ..L.... read_string(): RX 7 characters 0000 fe fe 4c e0 1a 03 fd ..L.... read_string(): RX 6 characters 0000 fe fe e0 4c fa fd ...L.. Channel: 2, Name: '' VFO: MEM, Antenna: 0, Split: OFF Freq: 145.8 MHz Mode: FM Width: 15 kHz txFreq: 145.8 MHz txMode: FM txWidth: 15 kHz Shift: None, Offset: 0 Hz, Step: 0 Hz, RIT: 0 Hz, XIT: 0 Hz CTCSS: 0.0Hz, CTCSSsql: 0.0Hz, DCS: 0.0, DCSsql: 0.0 2016-04-03 16:07 GMT+02:00 Antonio M <ant...@gm...>: > > > > After a long time I reconnected my rig to my Pc using a 4-port > communication interface CI-V and a serial/USB converter (see DMESG) > > [ 367.139148] usb 4-1: New USB device found, idVendor=0403, > idProduct=6001 > [ 367.139154] usb 4-1: New USB device strings: Mfr=1, Product=2, > SerialNumber=3 > [ 367.139158] usb 4-1: Product: USB Serial Converter > [ 367.139161] usb 4-1: Manufacturer: FTDI > [ 367.139164] usb 4-1: SerialNumber: FTDVRKNS > [ 367.145135] ftdi_sio 4-1:1.0: FTDI USB Serial Device converter detected > [ 367.145227] usb 4-1: Detected FT232RL > [ 367.149152] usb 4-1: FTDI USB Serial Device converter now attached to > ttyUSB0 > > when I start Grig (as root) I get > > [antonio@pcdesktop1 ~]$ su > Password: > [root@pcdesktop1 antonio]# grig -m 334 -r /dev/ttyUSB0 > 2016/04/03 11:38:40;;GRIG;;4;;grig_debug_init: Debug handler initialised. > 2016/04/03 11:38:40;;GRIG;;4;;Checking GRIG configuration. > 2016/04/03 11:38:40;;GRIG;;4;;..Configuration directory: OK > 2016/04/03 11:38:40;;GRIG;;4;;..Radio config files: > 2016/04/03 11:38:40;;GRIG;;5;;rig_daemon_start entered > 2016/04/03 11:38:40;;GRIG;;5;;rig_daemon_start: Initializing rig (id=334) > 2016/04/03 11:38:40;;HAMLIB;;4;;rig:rig_init called > 2016/04/03 11:38:40;;HAMLIB;;4;;icom: _init called > 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (355) > 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (309) > 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (310) > 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (311) > 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (313) > 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (314) > 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (315) > 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (319) > 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (320) > 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (321) > 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (322) > 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (367) > 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (323) > 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (346) > 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (324) > 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (328) > 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (330) > 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (326) > 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (327) > 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (347) > 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (357) > 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (363) > 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (329) > 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (362) > 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (345) > 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (356) > 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (360) > 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (370) > 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (361) > 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (331) > 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (312) > 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (316) > 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (332) > 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (334) > 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (344) > 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (368) > 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (335) > 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (369) > 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (336) > 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (358) > 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (337) > 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (338) > 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (339) > 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (340) > 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (341) > 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (342) > 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (343) > 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (366) > 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (303) > 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (304) > 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (306) > 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (307) > 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (302) > 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (352) > 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (353) > 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (351) > 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (364) > 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (365) > 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (354) > 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (371) > 2016/04/03 11:38:40;;HAMLIB;;4;;rig:rig_open called > 2016/04/03 11:38:40;;GRIG;;5;;rig_daemon_start: Init successfull, > executing post-init > 2016/04/03 11:38:40;;HAMLIB;;5;;write_block(): TX 6 bytes > 2016/04/03 11:38:40;;HAMLIB;;5;;0000 fe fe 4c e0 04 > fd ..L... > 2016/04/03 11:38:40;;HAMLIB;;5;;read_string(): RX 6 characters > 2016/04/03 11:38:40;;HAMLIB;;5;;0000 fe fe 4c e0 04 > fd ..L... > 2016/04/03 11:38:40;;HAMLIB;;5;;read_string(): RX 8 characters > 2016/04/03 11:38:40;;HAMLIB;;5;;0000 fe fe e0 4c 04 05 01 > fd ...L.... > 2016/04/03 11:38:40;;HAMLIB;;5;;write_block(): TX 7 bytes > 2016/04/03 11:38:40;;HAMLIB;;5;;0000 fe fe 4c e0 1a 03 > fd ..L.... > 2016/04/03 11:38:40;;HAMLIB;;5;;read_string(): RX 7 characters > 2016/04/03 11:38:40;;HAMLIB;;5;;0000 fe fe 4c e0 1a 03 > fd ..L.... > 2016/04/03 11:38:40;;HAMLIB;;5;;read_string(): RX 6 characters > 2016/04/03 11:38:40;;HAMLIB;;5;;0000 fe fe e0 4c fa > fd ...L.. > 2016/04/03 11:38:40;;GRIG;;1;;rig_daemon_check_mode: Can not find > frequency range for this mode (32)! Bug in backend? > 2016/04/03 11:38:40;;GRIG;;5;;rig_daemon_post_init: GET bits: > 0000000000000000 > 2016/04/03 11:38:40;;GRIG;;5;;rig_daemon_post_init: SET bits: > 0000000000000XXX > 2016/04/03 11:38:40;;GRIG;;5;;rig_daemon_start: Starting rig daemon > 2016/04/03 11:38:40;;GRIG;;4;;rig_daemon_start: Daemon thread started > 2016/04/03 11:38:40;;GRIG;;4;;Initialising key press handler > > and I don't see any freqquency on the Grig window. > > What is wrong in my understanding?? > > > > -- > Antonio Montagnani > Skype : amontag52 > > Linux Fedora 23 (Workstation) > inviato da Gmail > -- Antonio Montagnani Skype : amontag52 Linux Fedora 23 (Workstation) inviato da Gmail |
|
From: Antonio M <ant...@gm...> - 2016-04-03 14:08:04
|
After a long time I reconnected my rig to my Pc using a 4-port communication interface CI-V and a serial/USB converter (see DMESG) [ 367.139148] usb 4-1: New USB device found, idVendor=0403, idProduct=6001 [ 367.139154] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 367.139158] usb 4-1: Product: USB Serial Converter [ 367.139161] usb 4-1: Manufacturer: FTDI [ 367.139164] usb 4-1: SerialNumber: FTDVRKNS [ 367.145135] ftdi_sio 4-1:1.0: FTDI USB Serial Device converter detected [ 367.145227] usb 4-1: Detected FT232RL [ 367.149152] usb 4-1: FTDI USB Serial Device converter now attached to ttyUSB0 when I start Grig (as root) I get [antonio@pcdesktop1 ~]$ su Password: [root@pcdesktop1 antonio]# grig -m 334 -r /dev/ttyUSB0 2016/04/03 11:38:40;;GRIG;;4;;grig_debug_init: Debug handler initialised. 2016/04/03 11:38:40;;GRIG;;4;;Checking GRIG configuration. 2016/04/03 11:38:40;;GRIG;;4;;..Configuration directory: OK 2016/04/03 11:38:40;;GRIG;;4;;..Radio config files: 2016/04/03 11:38:40;;GRIG;;5;;rig_daemon_start entered 2016/04/03 11:38:40;;GRIG;;5;;rig_daemon_start: Initializing rig (id=334) 2016/04/03 11:38:40;;HAMLIB;;4;;rig:rig_init called 2016/04/03 11:38:40;;HAMLIB;;4;;icom: _init called 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (355) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (309) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (310) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (311) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (313) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (314) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (315) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (319) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (320) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (321) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (322) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (367) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (323) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (346) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (324) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (328) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (330) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (326) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (327) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (347) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (357) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (363) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (329) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (362) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (345) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (356) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (360) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (370) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (361) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (331) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (312) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (316) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (332) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (334) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (344) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (368) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (335) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (369) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (336) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (358) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (337) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (338) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (339) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (340) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (341) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (342) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (343) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (366) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (303) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (304) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (306) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (307) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (302) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (352) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (353) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (351) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (364) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (365) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (354) 2016/04/03 11:38:40;;HAMLIB;;4;;rig_register (371) 2016/04/03 11:38:40;;HAMLIB;;4;;rig:rig_open called 2016/04/03 11:38:40;;GRIG;;5;;rig_daemon_start: Init successfull, executing post-init 2016/04/03 11:38:40;;HAMLIB;;5;;write_block(): TX 6 bytes 2016/04/03 11:38:40;;HAMLIB;;5;;0000 fe fe 4c e0 04 fd ..L... 2016/04/03 11:38:40;;HAMLIB;;5;;read_string(): RX 6 characters 2016/04/03 11:38:40;;HAMLIB;;5;;0000 fe fe 4c e0 04 fd ..L... 2016/04/03 11:38:40;;HAMLIB;;5;;read_string(): RX 8 characters 2016/04/03 11:38:40;;HAMLIB;;5;;0000 fe fe e0 4c 04 05 01 fd ...L.... 2016/04/03 11:38:40;;HAMLIB;;5;;write_block(): TX 7 bytes 2016/04/03 11:38:40;;HAMLIB;;5;;0000 fe fe 4c e0 1a 03 fd ..L.... 2016/04/03 11:38:40;;HAMLIB;;5;;read_string(): RX 7 characters 2016/04/03 11:38:40;;HAMLIB;;5;;0000 fe fe 4c e0 1a 03 fd ..L.... 2016/04/03 11:38:40;;HAMLIB;;5;;read_string(): RX 6 characters 2016/04/03 11:38:40;;HAMLIB;;5;;0000 fe fe e0 4c fa fd ...L.. 2016/04/03 11:38:40;;GRIG;;1;;rig_daemon_check_mode: Can not find frequency range for this mode (32)! Bug in backend? 2016/04/03 11:38:40;;GRIG;;5;;rig_daemon_post_init: GET bits: 0000000000000000 2016/04/03 11:38:40;;GRIG;;5;;rig_daemon_post_init: SET bits: 0000000000000XXX 2016/04/03 11:38:40;;GRIG;;5;;rig_daemon_start: Starting rig daemon 2016/04/03 11:38:40;;GRIG;;4;;rig_daemon_start: Daemon thread started 2016/04/03 11:38:40;;GRIG;;4;;Initialising key press handler and I don't see any freqquency on the Grig window. What is wrong in my understanding?? -- Antonio Montagnani Skype : amontag52 Linux Fedora 23 (Workstation) inviato da Gmail |
|
From: Stephane F. <f8...@fr...> - 2015-12-20 21:41:10
|
Good News every one! After a long silence, here is coming grig 0.8.1. This is mainly a maintenance release in order to ease the build process, esp. relative to deprecated symbols in gthread. Download it at: https://sourceforge.net/projects/groundstation/files/Grig/0.8.1/ I might give a try at releasing a win32 version, but beta-testers will be needed since I'm not running on Windows OS. Remember, Alexandru Csete, OZ9AEC, the original designer and developer of grig is looking for people to take over and maintain the project. The current release has been made on interim. 73 -- Stephane - F8CFE |
|
From: Stephane F. <f8...@fr...> - 2015-12-20 13:26:01
|
Hi, ven, Dec 18, 2015, Tom Coleman skribis: [...] > Running make, you will get a linker error complaining about g_thread_supported. It’s deprecated in the latest gtk+ libraries. I'm about to release a maintenance version 0.8.1 in order to address this point. Stay tuned :) Cheers -- Stephane - F8CFE |
|
From: Tom C. <to...@so...> - 2015-12-18 21:03:41
|
Hi Stefano Try this running configure: ./configure CFLAGS"=-I/opt/local/include -I/opt/local/lib/gtk-2.0/include \ -I/opt/local/include/glib-2.0 -I/opt/local/lib/glib-2.0/include" \ PKG_CONFIG_PATH=/opt/local/lib/pkgconfig PKG_CONFIG_PATH is set to the MacPorts package directory. You will need gtk-2.0 and glib-2.0 and usb libraries Running make, you will get a linker error complaining about g_thread_supported. It’s deprecated in the latest gtk+ libraries. Just look for the code below in src/main.c and comment it out as below: /* if (!g_thread_supported ()) g_thread_init (NULL); */ I just built grig on 10.11.2 with current MacPorts. Enjoy. 73, Tom From: Me <iu0dft@ya...> - 2015-12-15 17:58:12 Hi everybody, I get this ./configure error on my mac when I try to install grig 0.8.0 that uses pkg-config; I’m using the latest release (0.29) on Mac OS X 10.11.2 Configure: error: The pkg-config script could not be found or is too old. Make sure itis in your PATH or set the PKG_CONFIG environment variable to the full path to pig-config. Alternatively, you may set the environment variables PACKAGE_CFLAGS and PACKAGE_LIBS to avoid the need to call pig-config. Can you help me fix it somehow? Thanks in advance 73 Stefano IU0DFT |
|
From: Me <iu...@ya...> - 2015-12-15 17:58:12
|
Hi everybody, I get this ./configure error on my mac when I try to install grig 0.8.0 that uses pkg-config; I’m using the latest release (0.29) on Mac OS X 10.11.2 Configure: error: The pkg-config script could not be found or is too old. Make sure it is in your PATH or set the PKG_CONFIG environment variable to the full path to pkg-config. Alternatively, you may set the environment variables PACKAGE_CFLAGS and PACKAGE_LIBS to avoid the need to call pig-config. Can you help me fix it somehow? Thanks in advance 73 Stefano IU0DFT |
|
From: Mihai T. <mih...@ya...> - 2012-09-12 18:16:51
|
Hi Alexendru, When do you think that will be available a Windows 32bit version of Grig v.0.8? Thank you, Mihai ________________________________ PSprijina copacii - esti sigur(a) ca e nevoie sa printezi acest e-mail? |
|
From: EA5XQ - J. <ju...@ea...> - 2012-08-26 08:27:42
|
Hi to all Just landed on the forum. I am trying to compile grig.0.8 in Mountain Lion MacOSX however, once installed XCode 4.4, it seems that ./configure pointed me out that I need gtk+2.0 as well. Looking for in the net, I gathered that I need to install the full GTK+ environment (https://live.gnome.org/GTK+/OSX/Building) and I could break me some MacPorts that I have already installed. Is there any other way to obtain gtk+2.0 without such effort? Thanks Juan, EA5XQ |
|
From: Javier P. <jav...@gm...> - 2011-10-27 11:43:02
|
Hi Roger, Thanks for your help! Finally I've been able to solve it by using the rpc.rigd daemon instead of rigctld. Within Grig I now use model number 1901 (RPC rig) instead of 2 (NET rigctl) and it looks like everything is working now! :-). Regards, Javier El 25 de octubre de 2011 15:56, <ro...@ef...> escribió: > Have you gotten an answer yet? > > I've never worked with the software, but if you can't get the one to work, > is the default firewall on Ubuntu blocking it? > to test, login to the command line and run: > sudo /etc/init.d/iptables stop > enter your password and iptables (the firewall), should stop. Try it at > that point. > (not sure if you tried something similar, also, don't know the ports > involved) > > I did see this thread: > http://lists.gnu.org/archive/html/tlf-devel/2008-01/msg00009.html > > > > > Hi everyone! > > > > We are trying to setup a radio server, which is hooked up to a Kenwood > > TS-2000 rig, so that it can be accesible over the LAN by other computers > > running Grig. This is what we have been trying: > > > > 1) We have a server running ubuntu 10.04 LTS with Grig 0.7.2 installed. > > This > > computer is hooked up to a Kenwood TS-200 rig by means of a serial > > connection under /dev/ttyS2. > > 2) If we execute the command "rigctl -m 214 -r /dev/ttyS2 -s 9600" we are > > able to correctly communicate with the Kenwood TS-2000 rig. > > 3) As we need to use this radio remotely, we have added to our > > /etc/rc.local > > file the following command, so that the remote daemon starts after the > > server boots up: "/usr/bin/rigctld -m 214 -r /dev/ttyS2 -s 9600 &" > > 4) After the computer boots the daemon starts running and if we execute > > the > > command "rigctl -m 2 -r localhost" we are able to correctly communicate > > with > > the Kenwood TS-200 rig. > > 5) At this point we can also use the command "grig -m 2 -r localhost" and > > Grig works correctly with our rig. > > > > The problem comes now when we try to connect from another computer (in > the > > same LAN) to the previous server, who's IP address is 10.13.30.141. > > > > 1) If we execute the command "rigctl -m 2 -r 10.13.30.141" from any other > > computer we are able to correctly connect to the server and send commands > > the rig. > > 2) If we execute the command "grig -m 2 -r 10.13.30.141" from any other > > computer we obtain the following: > > > > 2011/10/23 13:32:55;;GRIG;;4;;grig_debug_init: Debug handler initialised. > > 2011/10/23 13:32:55;;HAMLIB;;4;;rig:rig_init called > > 2011/10/23 13:32:55;;HAMLIB;;4;;rig: loading backend dummy > > 2011/10/23 13:32:55;;HAMLIB;;4;;dummy: _init called > > 2011/10/23 13:32:55;;HAMLIB;;4;;rig_register (1) > > 2011/10/23 13:32:55;;HAMLIB;;4;;rig_register (2) > > 2011/10/23 13:32:55;;HAMLIB;;4;;rig:rig_open called > > 2011/10/23 13:32:55;;HAMLIB;;4;;netrigctl_open called > > 2011/10/23 13:32:55;;GRIG;;2;;rig_daemon_start: Failed to open rig port > > 10.13.30.141 (permissions?) > > 2011/10/23 13:32:55;;HAMLIB;;4;;rig:rig_cleanup called > > 2011/10/23 13:32:55;;HAMLIB;;4;;rig:rig_close called > > 2011/10/23 13:32:55;;HAMLIB;;4;;netrigctl_close called > > > > We don't understand why, when attempting to connect to the server from > any > > other computer, rigctl works but Grig doesn't, bearing in mind that we > use > > the same input arguments for both programs. Is there any additional > > configuration needed in order to use Grig with a remote radio over the > > network? > > > > We would be very grateful if someone could help us out with this issue! > > > > Thank you very much in advance, > > Javier > > > ------------------------------------------------------------------------------ > > The demand for IT networking professionals continues to grow, and the > > demand for specialized networking skills is growing even more rapidly. > > Take a complimentary Learning@Cisco Self-Assessment and learn > > about Cisco certifications, training, and career opportunities. > > > http://p.sf.net/sfu/cisco-dev2dev_______________________________________________ > > Groundstation-user mailing list > > Gro...@li... > > https://lists.sourceforge.net/lists/listinfo/groundstation-user > > > > > > |
|
From: Javier P. <jav...@gm...> - 2011-10-23 13:48:43
|
Hi everyone! We are trying to setup a radio server, which is hooked up to a Kenwood TS-2000 rig, so that it can be accesible over the LAN by other computers running Grig. This is what we have been trying: 1) We have a server running ubuntu 10.04 LTS with Grig 0.7.2 installed. This computer is hooked up to a Kenwood TS-200 rig by means of a serial connection under /dev/ttyS2. 2) If we execute the command "rigctl -m 214 -r /dev/ttyS2 -s 9600" we are able to correctly communicate with the Kenwood TS-2000 rig. 3) As we need to use this radio remotely, we have added to our /etc/rc.local file the following command, so that the remote daemon starts after the server boots up: "/usr/bin/rigctld -m 214 -r /dev/ttyS2 -s 9600 &" 4) After the computer boots the daemon starts running and if we execute the command "rigctl -m 2 -r localhost" we are able to correctly communicate with the Kenwood TS-200 rig. 5) At this point we can also use the command "grig -m 2 -r localhost" and Grig works correctly with our rig. The problem comes now when we try to connect from another computer (in the same LAN) to the previous server, who's IP address is 10.13.30.141. 1) If we execute the command "rigctl -m 2 -r 10.13.30.141" from any other computer we are able to correctly connect to the server and send commands the rig. 2) If we execute the command "grig -m 2 -r 10.13.30.141" from any other computer we obtain the following: 2011/10/23 13:32:55;;GRIG;;4;;grig_debug_init: Debug handler initialised. 2011/10/23 13:32:55;;HAMLIB;;4;;rig:rig_init called 2011/10/23 13:32:55;;HAMLIB;;4;;rig: loading backend dummy 2011/10/23 13:32:55;;HAMLIB;;4;;dummy: _init called 2011/10/23 13:32:55;;HAMLIB;;4;;rig_register (1) 2011/10/23 13:32:55;;HAMLIB;;4;;rig_register (2) 2011/10/23 13:32:55;;HAMLIB;;4;;rig:rig_open called 2011/10/23 13:32:55;;HAMLIB;;4;;netrigctl_open called 2011/10/23 13:32:55;;GRIG;;2;;rig_daemon_start: Failed to open rig port 10.13.30.141 (permissions?) 2011/10/23 13:32:55;;HAMLIB;;4;;rig:rig_cleanup called 2011/10/23 13:32:55;;HAMLIB;;4;;rig:rig_close called 2011/10/23 13:32:55;;HAMLIB;;4;;netrigctl_close called We don't understand why, when attempting to connect to the server from any other computer, rigctl works but Grig doesn't, bearing in mind that we use the same input arguments for both programs. Is there any additional configuration needed in order to use Grig with a remote radio over the network? We would be very grateful if someone could help us out with this issue! Thank you very much in advance, Javier |
|
From: Grant M. <mcd...@op...> - 2011-05-26 09:38:46
|
Hi team. I have grig working now but I have noticed a note on terminal that says: Rig_daemon_exec_cmd: Failed to execute RIG_CMD_GET RF Any idea what that means and what I should do about it? Regards Grant McDuling Ghostwriter, author, copy-editor and proofreader mcd...@op... mob 0400 261 149 www.camocomms.com.au Read my book The Fields of Hope http://www.amazon.com/The-Fields-of-Hope-ebook/dp/B004X6UCXM |
|
From: Stephane F. <f8...@fr...> - 2011-05-26 07:16:52
|
Sat, May 14, 2011, Grant McDuling skribis: > Hi, tried that, didn't work. Failed to open rig port. Any idea how I can ascertain what the rig port is? Is your serial port a plain old serial port at the rear of your computer or is it a USB-serial adapter cable? grig -m 127 -r /dev/ttyS0 # try also /dev/ttyS1, /dev/ttyS2, .. or grig -m 127 -r /dev/ttyUSB0 # try also /dev/ttyUSB1, /dev/ttyUSB2, .. The default hamlib's serial baud rate is 38400, make sure in your FT450 menu it is setup accordingly. Also the serial cable do need to have CTS/RTS wired. Regards -- Stephane - F8CFE PS: please don't reply privately, always keep the mailing list in the loop > On 13/05/2011, at 9:02 PM, Stephane Fillod wrote: > > > Hi Grant, > > > > Have you tried "grig --help" in a terminal or reading the man page (RTFM)? > > > > What you're looking for is "grig -m 127" for the FT450. > > > > Regards > > -- > > Stephane - F8CFE > > > > Fri, May 13, 2011 at 07:36:52PM +1000, Grant McDuling skribis: > >> Hi, I am using Ubuntu 11.04 and have just downloaded Grig, successfully I believe. I have copied the icon to my desktop and when I click it, the Hamlib dummy opens on my screen. How do I go about configuring it for my FT450? Have tried all I know, which isn't much. > >> |
|
From: Grant M. <mcd...@op...> - 2011-05-26 01:17:31
|
Hi, I have downloaded grig and can activate the GUI. It is set to the hamlib dummy. How do I go about configuring it for my rig, the FT-450? I can't see anywhere on the GUI where I can change the settings from dummy to FT450. Grant VK4JAZ Grant McDuling Ghostwriter, author, copy-editor and proofreader mcd...@op... mob 0400 261 149 www.camocomms.com.au Read my book The Fields of Hope http://www.amazon.com/The-Fields-of-Hope-ebook/dp/B004X6UCXM |
|
From: Stephane F. <f8...@fr...> - 2011-05-13 11:02:50
|
Hi Grant, Have you tried "grig --help" in a terminal or reading the man page (RTFM)? What you're looking for is "grig -m 127" for the FT450. Regards -- Stephane - F8CFE Fri, May 13, 2011 at 07:36:52PM +1000, Grant McDuling skribis: > Hi, I am using Ubuntu 11.04 and have just downloaded Grig, successfully I believe. I have copied the icon to my desktop and when I click it, the Hamlib dummy opens on my screen. How do I go about configuring it for my FT450? Have tried all I know, which isn't much. > > Regards > Grant McDuling VK4JAZ > Ghostwriter, author, copy-editor and proofreader > mcd...@op... > mob 0400 261 149 > www.camocomms.com.au > > > > > > > > > ------------------------------------------------------------------------------ > Achieve unprecedented app performance and reliability > What every C/C++ and Fortran developer should know. > Learn how Intel has extended the reach of its next-generation tools > to help boost performance applications - inlcuding clusters. > http://p.sf.net/sfu/intel-dev2devmay > _______________________________________________ > Groundstation-user mailing list > Gro...@li... > https://lists.sourceforge.net/lists/listinfo/groundstation-user |
|
From: Grant M. <mcd...@op...> - 2011-05-13 09:37:34
|
Hi, I am using Ubuntu 11.04 and have just downloaded Grig, successfully I believe. I have copied the icon to my desktop and when I click it, the Hamlib dummy opens on my screen. How do I go about configuring it for my FT450? Have tried all I know, which isn't much. Regards Grant McDuling VK4JAZ Ghostwriter, author, copy-editor and proofreader mcd...@op... mob 0400 261 149 www.camocomms.com.au |
|
From: <do...@kd...> - 2010-09-16 21:21:43
|
Is GRIG still being actively developed and supported? The user forum appears to have been inactive since 2008. Can GRIG be used with IRLP for remote rig access from a Netbook/Notebook PC via the Internet? Or should I try flrig with IRLP? Or ?? The solution must be Linux-friendly. -- Thanks!& 73, doc, KD4E "Communicators must defend free speech or risk losing freedom entirely." A Search Engine& More! http://ixquick.com |_|___|_| | |& | | /\ {| / \ {| / \ {| / @ \ {| | |~_|~~~~| | -| | | ============\ # http://KD4E.com Have an http://ultrafidian.com day! |