Hello,
I am trying a new installation of CQRLOG. FLDIGI and FLRIG are installed and working. However CQRLOG will not communicate with my rig. The serial comm to the rig is a Microham Digikeyer II, and this is working properly with FLRIG. I have already tried all the usual items:
I am in the dialout group
I am in the mhuxd group
Case of device name is correct (/dev/mhuxd/cat1)
I have set the baud rate manually
One thing I noticed is that there is no "IO error" until I specify the baud rate - if I do not all else is the same but no "IO error." Distribution is Debian Wheezy x64.I notice that my rigctl number 1608 is for the Orion but not Orion II, of course I do believe their serial comm parms are the same. But I cannot find any record of someone using Orion II and CQRLOG successfully...?
Startup command line follows:
larry@vfo:~$ cqrlogLoading libssl: /usr/lib/x86_64-linux-gnu/libssl.so.1.0.0Loading libcrypto: /usr/lib/x86_64-linux-gnu/libcrypto.soLoading libmysqlclient: /usr/lib/x86_64-linux-gnu/libmysqlclient.so.18Loaded 68149 LoTW usersLoaded 77985 eQSL users*User home directory: /home/larry/Program home directory: /home/larry/.config/cqrlog/Data directory: /home/larry/.config/cqrlog/database/Memebers directory: /usr/share/cqrlog/members/ZIP code directory: /usr/share/cqrlog/zipcodes/Binary dir: /usr/bin/Share dir: /usr/share/cqrlog/*/usr/sbin/mysqld --defaults-file=/home/larry/.config/cqrlog/database/my.cnf --default-storage-engine=MyISAM --datadir=/home/larry/.config/cqrlog/database/ --socket=/home/larry/.config/cqrlog/database/sock --skip-grant-tables --port=64000 --key_buffer_size=32M --key_buffer_size=4096K131230 17:42:23 [Note] Plugin 'FEDERATED' is disabled.131230 17:42:23 InnoDB: The InnoDB memory heap is disabled131230 17:42:23 InnoDB: Mutexes and rw_locks use GCC atomic builtins131230 17:42:23 InnoDB: Compressed tables use zlib 1.2.7131230 17:42:23 InnoDB: Using Linux native AIO131230 17:42:23 InnoDB: Initializing buffer pool, size = 128.0M131230 17:42:23 InnoDB: Completed initialization of buffer pool131230 17:42:23 InnoDB: highest supported file format is Barracuda.131230 17:42:23 InnoDB: Waiting for the background threads to start131230 17:42:24 InnoDB: 5.5.31 started; log sequence number 1595675131230 17:42:24 [Note] Server hostname (bind-address): '0.0.0.0'; port: 64000131230 17:42:24 [Note] - '0.0.0.0' resolves to '0.0.0.0';131230 17:42:24 [Note] Server socket created on IP: '0.0.0.0'.131230 17:42:24 [Warning] Can't open and lock time zone table: Table 'mysql.time_zone_leap_second' doesn't exist trying to live without them131230 17:42:24 [ERROR] Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist131230 17:42:24 [ERROR] Native table 'performance_schema'.'events_waits_current' has the wrong structure131230 17:42:24 [ERROR] Native table 'performance_schema'.'events_waits_history' has the wrong structure131230 17:42:24 [ERROR] Native table 'performance_schema'.'events_waits_history_long' has the wrong structure131230 17:42:24 [ERROR] Native table 'performance_schema'.'setup_consumers' has the wrong structure131230 17:42:24 [ERROR] Native table 'performance_schema'.'setup_instruments' has the wrong structure131230 17:42:24 [ERROR] Native table 'performance_schema'.'setup_timers' has the wrong structure131230 17:42:24 [ERROR] Native table 'performance_schema'.'performance_timers' has the wrong structure131230 17:42:24 [ERROR] Native table 'performance_schema'.'threads' has the wrong structure131230 17:42:24 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_thread_by_event_name' has the wrong structure131230 17:42:24 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_instance' has the wrong structure131230 17:42:24 [ERROR] Native table 'performance_schema'.'events_waits_summary_global_by_event_name' has the wrong structure131230 17:42:24 [ERROR] Native table 'performance_schema'.'file_summary_by_event_name' has the wrong structure131230 17:42:24 [ERROR] Native table 'performance_schema'.'file_summary_by_instance' has the wrong structure131230 17:42:24 [ERROR] Native table 'performance_schema'.'mutex_instances' has the wrong structure131230 17:42:24 [ERROR] Native table 'performance_schema'.'rwlock_instances' has the wrong structure131230 17:42:24 [ERROR] Native table 'performance_schema'.'cond_instances' has the wrong structure131230 17:42:24 [ERROR] Native table 'performance_schema'.'file_instances' has the wrong structure131230 17:42:24 [Note] /usr/sbin/mysqld: ready for connections.Version: '5.5.31-0+wheezy1' socket: '/home/larry/.config/cqrlog/database/sock' port: 64000 (Debian)select * from tables where table_schema = 'cqrlog_common'SELECT log_nr,log_name FROM cqrlog_common.log_list order by log_nruse cqrlog002use cqrlog002SELECT * FROM cqrlog_configselect * from db_versionSELECT * FROM cqrlog_common.dxcc_ref ORDER BY ADIFSELECT * FROM cqrlog_common.dxcc_ref ORDER BY ADIFhuu1huu2In createAll objects createdhuu3huu4Settings:-----------------------------------------------------RigCtldPath:/usr/bin/rigctldRigCtldArgs:-m %m -r %r -t %t -s 57600 -vRunRigCtld: TRUERigDevice: /dev/mhuxd/cat1RigCtldPort:4532RigCtldHost:localhostRigPoll: 500RigSendCWR: FALSERigId: 1608Starting RigCtld .../usr/bin/rigctld -m 1608 -r /dev/mhuxd/cat1 -t 4532 -s 57600 -vrig_open: error = IO error rigctld started!Result0:NResult1:YResult2:YConnected to localhost:4532Loading window size a position (height|width|top|left):651|807|27|20Section:frmQSODetailsLoading window size a position (frmQSODetails) (height|width|top|left):210|266|27|20CW initSunDelta:-4.999800000000000000E+00SELECT * FROM profiles WHERE visible > 0 ORDER BY nrSELECT * FROM profiles WHERE visible > 0 ORDER BY nr2013-12-30 22:42:39OnCloseQuery - NewQSOSaveForm: frmNewQSOClosing Details windowSection:frmQSODetailsSaving window size a position (frmQSODetails) (height|width|top|left):210|266|27|20Saving window size a position (height|width|top|left):651|807|27|20select count(*) from cqrlog002.cqrlog_configSaving ini file to databaseselect count(*) from cqrlog002.cqrlog_configSaving ini file to databaseClosing BandMap windowClosing DXCluster windowClosing TRXControl windowClosing GrayLine windowEnd dmDXCCComplete end dmDXCCClosing dDXCCClosing dData/home/larry/.config/cqrlog/database/vfo.pidCommand: kill 27109131230 17:44:09 [Note] /usr/sbin/mysqld: Normal shutdown131230 17:44:09 InnoDB: Starting shutdown...Closing ini file ...[TGtk2WidgetSet.Destroy] WARNING: There are 1 TimerInfo structures left, I'll free themAn unhandled exception occurred at $000000000051E22B :EAccessViolation : $000000000051E22B $000000000069A589larry@vfo:~$ 131230 17:44:10 InnoDB: Shutdown completed; log sequence number 1595675131230 17:44:10 [Note] /usr/sbin/mysqld: Shutdown completelarry@vfo:~$ ls -la /dev/mhuxd/total 0drwxr-xr-x 2 root root 120 Dec 21 11:27 .drwxr-xr-x 17 root root 3440 Dec 30 09:21 ..crw-rw---T 1 root mhuxd 248, 0 Dec 21 11:27 cat1crw-rw---T 1 root mhuxd 251, 0 Dec 21 11:27 fsk1crw-rw---T 1 root mhuxd 249, 0 Dec 21 11:27 ptt1crw-rw---T 1 root mhuxd 250, 0 Dec 21 11:27 wklarry@vfo:~$ larry@vfo:~$ groups larrylarry : larry dialout cdrom floppy sudo audio dip video plugdev scanner bluetooth netdev mhuxdlarry@vfo:~$ ^Clarry@vfo:~$
I assume all those "table has the wrong structure" errors can be ignored... but of course I have yet to record a QSO!
Thanks guys for your help!
Larry N8KU
Mon, 2013-12-30 23:07
#1
n8ku
Orion II
I suddenly had the brilliant idea of starting CQRLOG *before* any of the other programs - and it works! of course now FLRIG and FLDIGI cannot talk to the rig... so my question is, how do I resolve the this contention for the serial port?
Larry N8KU
Dont know if this will help, I am by no means a Linux person, just a user that can miander my way around, but this is what Petr posted to get both to work, although,, you have a bit of a more complex set up, but hey it's worh a shot::
There is a way how to have trx control both fldigi and cqrlog. Set the TRX control in CQRLOG and in fldigi preferences use Hamlib NET rigctl (Beta) asi rig and Device set to localhost:4532It will work both in CQRLOG and FLDIGI.
Tom K8WDX
Thanks Tom,
I have since realized that what I want is "fldigi remote" mode, If I just bring up CQRLOG last, and immediately set it to remote mode, then everything works. Still trying to figure out how to get it to just default to remote.
On the other hand, if I want to switch to working CW, with nothing but CQRLOG running, that becomes a pain, since it will not start working after FLRIG has tied up the port - only a reboot solves this.
Larry N8KU
I dont have Flrig loaded at all, the way I do it is, I have CQRlog running, the radio control is on Rig#1, I first switch it to Rig, #2 this takes TX control away from CQRlog, I then put CQRlog in Fldigi mode, then start Fldigi, which has rig control, then as I log in digi modes, all goes in the log, when done, I simply close Fldigi, take CQRlog out of Fldigi mode, then return CQRlog to rig 1, which gives CQRlog TX control again, seems to work for me, one day I'll get this compiling thing figured out and install the rest of Daves fine products. 73 Tom K8WDX
Tom K8WDX