Re: [wsjt-devel] IC-7300 control lost

2017-03-02 Thread Bill Somerville
Hi Pino, On 02/03/2017 22:33, Pino Zollo wrote: write_block(): TX 7 bytes fe fe 94 e0 1c 00 fd... <-- Wrong command read_string(): RX 7 characters fe fe 94 e0 1c 00 fd... <-- wrong command echoed read_string

Re: [wsjt-devel] IC-7300 control lost

2017-03-02 Thread Bill Somerville
On 02/03/2017 20:37, David Tiller wrote: I'm no expert, but is this command legit? fe fe 94 e0 1c 00 fd Hi David, yes it is. Many Icom CAT commands come in set and query versions, the difference is that the query version leaves off the value. So 1c 00 is the query command, and in t

Re: [wsjt-devel] IC-7300 control lost

2017-03-02 Thread David Tiller
I'm no expert, but is this command legit? fe fe 94 e0 1c 00 fd According to the manual http://www.icom.co.jp/world/support/download/manual/pdf/IC-7300_ENG_CD_0.pdf and this site http://www.plicht.de/ekki/civ/civ-p42.html there's a byte missing for the TX off command. The whole exc

Re: [wsjt-devel] IC-7300 control lost

2017-03-02 Thread Bill Somerville
On 02/03/2017 19:42, Pino Zollo wrote: > rigctl(d): t 'currVFO' '' '' '' > write_block(): TX 7 bytes > fe fe 94 e0 1c 00 fd... > read_string(): RX 7 characters > fe fe 94 e0 1c 00 fd... > read_string(): RX 8 cha

Re: [wsjt-devel] IC-7300 control lost

2017-03-02 Thread Black Michael
#1 Try reducing the poll interval on WSJT-X in File/Settings/Radio in the upper right corner.#2 What OS are you on?#3 Have you tried uninstalling USB drivers and reinstalling?#4 You still haven't sent us enough of the log to see what was going on what it stopped... I suspect a computer problem o

Re: [wsjt-devel] IC-7300 control lost

2017-03-01 Thread Black Michael
Do you have a dummy load you can test with?One question is does it fail only when you transmit and on certain bands? de Mike W9MDB From: Pino Zollo To: wsjt-devel@lists.sourceforge.net Sent: Wednesday, March 1, 2017 3:12 PM Subject: [wsjt-devel] IC-7300 control lost El 01/03/17 a

Re: [wsjt-devel] IC-7300 control lost

2017-03-01 Thread Bill Somerville
On 01/03/2017 21:12, Pino Zollo wrote: > 000fe fe e0 94 1c 00 00 fd > rigctl(d): f 'currVFO' '' '' '' > write_block():339 failed -1 - Input/output error > write_block():339 failed -1 - Input/output error > write_block():339 failed -1 - Input/output error > w

Re: [wsjt-devel] IC-7300 control lost

2017-03-01 Thread Bill Somerville
On 01/03/2017 12:59, Pino Zollo wrote: > it goes in timeout straight. > > --- > icom_init: civ_version=1 > rig_set_conf: civaddr='0x94' > rig:rig_open called > Opened rig model 373, 'IC-7300' > Backend version: 0.7.2, Status: Stable > Connection opened from localhost:49024 > rigctl(d):

Re: [wsjt-devel] IC-7300 control lost

2017-02-28 Thread Black Michael
In the WSJT-X rig selection you use "Hamlib NET rigctl".  First, start rigctld-wstx like you did before.  When you select the rig as above you'll see it connect and messages start flowing.That's the capture I need...you'll probably want to send it as an attachment as it can get quite long. de Mi