End of show .
El 02/03/17 a las 19:11, wsjt-devel-requ...@lists.sourceforge.net escribió:
> #4 You still haven't sent us enough of the log to see what was going on
> what it stopped...
rig_register (372)
icom_init: civ_version=1
rig_set_conf: civaddr='0x94'
rig:rig_open called
s
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
El 02/03/17 a las 19:11, wsjt-devel-requ...@lists.sourceforge.net escribió:
>
> 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://w
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
aptech/>
Best Firms 2016 #2 in Information Technology
____
From: Pino Zollo
Sent: Thursday, March 2, 2017 2:22 PM
To: wsjt-devel@lists.sourceforge.net
Subject: [wsjt-devel] IC-7300 control lost
El 02/03/17 a las 15:26, wsjt-devel-requ...@lists.sourceforge.net e
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
El 02/03/17 a las 16:36, wsjt-devel-requ...@lists.sourceforge.net escribió:
> #4 You still haven't sent us enough of the log to see what was going on
> what it stopped...
>
> I will do it tonight
---
write_block(): TX 7 bytes
fe fe 94 e0 1a 03 fd.
El 02/03/17 a las 15:26, wsjt-devel-requ...@lists.sourceforge.net escribió:
> #4 You still haven't sent us enough of the log to see what was going on
> what it stopped...
>
> I will do it tonight
>
>> I suspect a computer problem on your part right now.
> maybethe behavior is the same on th
El 02/03/17 a las 11:21, wsjt-devel-requ...@lists.sourceforge.net escribió:
> #1 Try reducing the poll interval on WSJT-X in File/Settings/Radio in the
> upper right corner.
Tried polling from 1 to 2 secondsno change.
#2 What OS are you on?
Linux Mint 17.3
#3 Have you tried uninstalling
oblem on your part right now.
de Mike W9MDB
From: Pino Zollo
To: wsjt-devel@lists.sourceforge.net
Sent: Thursday, March 2, 2017 6:33 AM
Subject: [wsjt-devel] IC-7300 control lost
El 02/03/17 a las 05:28, wsjt-devel-requ...@lists.sourceforge.net escribió:
> Do you have a dummy
El 02/03/17 a las 05:28, wsjt-devel-requ...@lists.sourceforge.net escribió:
> 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
Hi Mike
The problem shows also in RX only...
Any how I did wound the USB cable
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
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
El 01/03/17 a las 15:15, wsjt-devel-requ...@lists.sourceforge.net escribió:
>> HI Pino,
>>
>> do you have the correct baud rate selected and the correct serial port.
>> -s and -r arguments to rigctld.
>>
>
> ohoops.. this is the right command:
>
> /usr/local/bin/rigctld-wsjtx -m 373 -c 0x94 -s
El 01/03/17 a las 12:27, wsjt-devel-requ...@lists.sourceforge.net escribió:
> HI Pino,
>
> do you have the correct baud rate selected and the correct serial port.
> -s and -r arguments to rigctld.
>
ohoops.. this is the right command:
/usr/local/bin/rigctld-wsjtx -m 373 -c 0x94 -s 9600 -r
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):
El 01/03/17 a las 01:25, wsjt-devel-requ...@lists.sourceforge.net escribió:
> 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
> ne
t can get quite
long.
de Mike W9MDB
From: Pino Zollo
To: wsjt-devel@lists.sourceforge.net
Sent: Tuesday, February 28, 2017 6:57 PM
Subject: [wsjt-devel] IC-7300 control lost
El 28/02/17 a las 21:49, wsjt-devel-requ...@lists.sourceforge.net escribió:
> You need to run WSJT-X us
El 28/02/17 a las 21:49, wsjt-devel-requ...@lists.sourceforge.net escribió:
> You need to run WSJT-X using Hamlib NET rigctl and re-run this until it fails.
> de Mike W9MDB
Hi Mike,
it is not clear to me
please which commands shall I give ?
73
Pino ZP4KFX
19 matches
Mail list logo
