On Tue, Mar 12, 2002, dar...@bt... wrote:
> I'm going to be adding to this radio at some point, but will drop a note
> when I get going.
Sorry, what are you going to add to this radio?
Feature wise, this rig is rather limited.
check with "tests/dumpcaps 319" to see what it can do and is implemented.
> -------------- List of Functions --------------
>
> F: set_freq (Frequency) OK!
> f: get_freq (Frequency) OK!
> M: set_mode (Mode,Passband) OK! - USB, LSB, AM, CW
> m: get_mode (Mode,Passband) OK!
> V: set_vfo (VFO) ??
MEM, VFO, VFOA, VFOA
> U: set_func (Func,Func status) ??
> u: get_func (Func,Func status) ??
NB (Noise blanker), COMP, etc. anything that can be set on/off
This rig does not support set_func/get_func
> E: set_mem (Memory#) ??
a memory number. For the IC735, the range should be 1..10,
and 11-12 for the scan edge. Can you confirm?
> h: get_channel (Channel) OK!
well, a bit bugged. Should be fixed now.
G: vfo_op (Mem/VFO op)
FROM_VFO: i.e. 'MW' on the rig
TO_VFO: i.e. 'M>V' on the rig
> [root@g0wcw tests]# ./rigctl -s 9600 -vvvvv -m 319
[snip]
> Rig command: m
> TX 7 bytes
> 0000 ff fe fe 04 e0 04 fd .......
> RX 7 bytes
> 0000 ff fe fe 04 e0 04 fd .......
> RX 6 bytes
> 0000 fe fe e0 04 04 00 ......
> RX 1 bytes
> 0000 fd .
> icom: Unsupported Icom mode width 0xff00
> Mode: LSB
> Passband: 0
0xff00 should be fixed now. TBC again.
> Rig command: M
> Mode: AM
> Passband: 2400
> TX 9 bytes
> 0000 ff fe fe 04 e0 06 02 02 fd .........
> RX 9 bytes
> 0000 ff fe fe 04 e0 06 02 02 fd .........
> RX 6 bytes
> 0000 fe fe e0 04 fa fd ......
> icom_set_mode: ack NG (0xfa), len=1
> set_mode: error = Command rejected by the rig
Passband data now allowed. Should be fixed now.
> Rig command: h
> Channel: 1
> TX 7 bytes
> 0000 ff fe fe 04 e0 08 fd .......
> sa_sigioaction: activity detected
> RX 7 bytes
> 0000 ff fe fe 04 e0 08 fd .......
> sa_sigioaction: activity detected
> RX 6 bytes
> 0000 fe fe e0 04 fb fd ......
> TX 9 bytes
> 0000 ff fe fe 04 e0 08 00 01 fd .........
> sa_sigioaction: activity detected
> sa_sigioaction: activity detected
> RX 9 bytes
> 0000 ff fe fe 04 e0 08 00 01 fd .........
> sa_sigioaction: activity detected
> RX 6 bytes
> 0000 fe fe e0 04 fa fd ......
> icom_set_mem: ack NG (0xfa), len=1
> TX 7 bytes
> 0000 ff fe fe 04 e0 03 fd .......
> sa_sigioaction: activity detected
> RX 7 bytes
> 0000 ff fe fe 04 e0 03 fd .......
> sa_sigioaction: activity detected
> RX 6 bytes
> 0000 fe fe e0 04 03 20 .....
> RX 1 bytes
> 0000 11 .
> RX 1 bytes
> 0000 38 8
> sa_sigioaction: activity detected
> RX 1 bytes
> 0000 21 !
> RX 1 bytes
> 0000 fd .
> TX 7 bytes
> 0000 ff fe fe 04 e0 04 fd .......
> sa_sigioaction: activity detected
> RX 7 bytes
> 0000 ff fe fe 04 e0 04 fd .......
> sa_sigioaction: activity detected
> RX 6 bytes
> 0000 fe fe e0 04 04 01 ......
> RX 1 bytes
> 0000 fd .
> Channel: 1, Name: ''
> VFO: currVFO, Antenna: 0, Split OFF
> Freq: 21.3811MHz Mode: USB Width: 0Hz
> txFreq: 0Hz txMode: txWidth: 0Hz
> Shift: None, Offset: 0Hz, Step: 0Hz, RIT: 0Hz, XIT: 0Hz
> CTCSS: 0.0Hz, CTCSSsql: 0.0Hz, DCS: 0.0, DCSsql: 0.0
> Functions: FAGC NB COMP VOX TONE TSQL SBKIN FBKIN ANF NR AIP APF MON MN RNF ARO L
> OCK MUTE VSC REV SQL BC MBC LMP
> Levels:
>
About set_mem:
> Rig command: E
> Memory#: 1
> TX 9 bytes
> 0000 ff fe fe 04 e0 08 00 01 fd .........
^^
set_mem: this extra byte is confusing the rig. This is the case with rigs
that have less than 100 channels. Should be fixed now.
Thanks for the treaces. The CVS has a new version that should work better.
Cheers,
Stephane F8CFE
|
