I'm no expert, but is this command legit?
0000 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 exchange is like this - it seems that the radio sends back the
correct command with the extra byte and then something goes wrong:
write_block(): TX 7 bytes
0000 fe fe 94 e0 1c 00 fd ....... <-- Wrong
command
read_string(): RX 7 characters
0000 fe fe 94 e0 1c 00 fd ....... <-- wrong
command echoed
read_string(): RX 8 characters
0000 fe fe e0 94 1c 00 00 fd ........ <-- radio
sending 'radio off' message
rigctl(d): f 'currVFO' '' '' ''
write_block(): TX 6 bytes
0000 fe fe 94 e0 03 fd ...... <-- Read op
frequency
read_string(): Timed out 1.1068 seconds after 0 chars
I assume the driver is ok with the commands being echoed exactly as they were
sent and then being replied to by the radio.
--
David Tiller | Senior Manager
dtil...@captechconsulting.com
c 804.304.0638 / o 804.355.0511
[http://www.captechconsulting.com/siggen/logo.png]<http://www.captechconsulting.com/>
[http://www.captechconsulting.com/siggen/Dkblue_Facebook.png]<http://www.facebook.com/CapTechCareers>
[http://www.captechconsulting.com/siggen/Dkblue_Twitter.png]
<http://www.twitter.com/CapTechListens>
[http://www.captechconsulting.com/siggen/Dkblue_LinkedIn.png]
<http://www.linkedin.com/company/captech-ventures>
[http://www.captechconsulting.com/siggen/Dkblue_StackOverflow.png]
<http://www.stackoverflow.com/jobs/companies/captech-consulting>
[http://www.captechconsulting.com/siggen/Dkblue_YouTube.png]
<http://www.youtube.com/user/CapTechConsulting>
[http://www.captechconsulting.com/siggen/Dkblue_Instagram.png]
<https://www.instagram.com/lifeatcaptech/>
Best Firms 2016 #2 in Information Technology
________________________________
From: Pino Zollo <pinozo...@gmail.com>
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 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.
> maybe....the behavior is the same on the two USB ports.... any how using
> rigctld improves a lot.... I even could do some QSO:
>
>> de Mike W9MDB?
Having switched from JT65 to WSPR
-------------
rigctl(d): m 'currVFO' '' '' ''
write_block(): TX 6 bytes
0000 fe fe 94 e0 04 fd ......
read_string(): RX 6 characters
0000 fe fe 94 e0 04 fd ......
read_string(): RX 8 characters
0000 fe fe e0 94 04 01 01 fd ........
write_block(): TX 7 bytes
0000 fe fe 94 e0 1a 03 fd .......
read_string(): RX 7 characters
0000 fe fe 94 e0 1a 03 fd .......
read_string(): RX 8 characters
0000 fe fe e0 94 1a 03 40 fd ......@.
write_block(): TX 7 bytes
0000 fe fe 94 e0 1a 06 fd .......
read_string(): RX 7 characters
0000 fe fe 94 e0 1a 06 fd .......
read_string(): RX 9 characters
0000 fe fe e0 94 1a 06 01 01 fd .........
rigctl(d): t 'currVFO' '' '' ''
write_block(): TX 7 bytes
0000 fe fe 94 e0 1c 00 fd .......
read_string(): RX 7 characters
0000 fe fe 94 e0 1c 00 fd .......
read_string(): RX 8 characters
0000 fe fe e0 94 1c 00 00 fd ........
rigctl(d): f 'currVFO' '' '' ''
write_block(): TX 6 bytes
0000 fe fe 94 e0 03 fd ......
read_string(): Timed out 1.1068 seconds after 0 chars
write_block(): TX 6 bytes
0000 fe fe 94 e0 03 fd ......
read_string(): Timed out 1.873 seconds after 0 chars
write_block(): TX 6 bytes
0000 fe fe 94 e0 03 fd ......
read_string(): Timed out 1.1040 seconds after 0 chars
write_block(): TX 6 bytes
0000 fe fe 94 e0 03 fd ......
read_string(): Timed out 1.656 seconds after 0 chars
rigctl(d): T 'currVFO' '0' '' ''
write_block(): TX 8 bytes
0000 fe fe 94 e0 1c 00 00 fd ........
Connection opened from localhost:47297
read_string(): Timed out 1.89 seconds after 0 chars
write_block(): TX 8 bytes
0000 fe fe 94 e0 1c 00 00 fd ........
read_string(): Timed out 1.65 seconds after 0 chars
write_block(): TX 8 bytes
0000 fe fe 94 e0 1c 00 00 fd ........
Connection opened from localhost:47298
read_string(): Timed out 1.111 seconds after 0 chars
write_block(): TX 8 bytes
0000 fe fe 94 e0 1c 00 00 fd ........
read_string(): Timed out 1.1042 seconds after 0 chars
rigctl(d): 'currVFO' '' '' ''
Connection closed from localhost:47223
rigctl(d): 'currVFO' '' '' ''
Connection closed from localhost:47297
rigctl(d): v 'currVFO' '' '' ''
rigctl(d): v 'currVFO' '' '' ''
rigctl(d): f 'currVFO' '' '' ''
write_block(): TX 6 bytes
0000 fe fe 94 e0 03 fd ......
read_string(): Timed out 1.1047 seconds after 0 chars
write_block(): TX 6 bytes
0000 fe fe 94 e0 03 fd ......
Connection opened from localhost:47299
read_string(): Timed out 1.1017 seconds after 0 chars
write_block(): TX 6 bytes
0000 fe fe 94 e0 03 fd ......
read_string(): Timed out 1.1069 seconds after 0 chars
write_block(): TX 6 bytes
0000 fe fe 94 e0 03 fd ......
read_string(): Timed out 1.1046 seconds after 0 chars
rigctl(d): 'currVFO' '' '' ''
Connection closed from localhost:47298
Connection closed from localhost:47299
--------------------
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
