Menu
▾
▴
Re: [wsjt-devel] Fwd: RE: WSJTX v 1.7.0
|
From: Geoff M. at M. E. <ge...@me...> - 2017-01-21 21:53:30
|
Bill,
Thank you for taking the time to explain to me how to manually change the
CIV address.
73,
Geoff - W8GNM
From: Bill Somerville [mailto:g4...@cl...]
Sent: Friday, January 20, 2017 2:59 PM
To: wsj...@li...; ge...@me...
Subject: Re: [wsjt-devel] Fwd: RE: WSJTX v 1.7.0
On 20/01/2017 18:30, Joe Taylor wrote:
I did successfully install WSJTX v1.7.0 and had my first QSO with it.
It is a great program with very broad capabilities.
When I was configuring it for my radio, I noticed that the default C-IV
address for the Icom 756Pro, Pro2, and Pro3 is locked to 64h, but it is
often necessary to change this default address to a new address such a
5Ch to avoid conflicts with other radios on the C-IV serial buss.
Please consider adding the capability to modify the C-IV address in the
setup menu of WSTJ-X to accommodate other addresses for this radio
I sent this feedback to the developer's forum at:
wsj...@li... , but it was rejected because I am not
a member of that forum. Could you please get this message to the proper
people.
Thank you.
HI Geoff,
for more than 999 per thousand users the default configuration parameters
for rig control are ok but as you state there are occasions where a special
value is needed. Rather than complicating the settings options of WSJT-X,
which we prefer to try and keep generic, there is a currently undocumented
method to adjust any Hamlib configuration parameter. To see the parameters
that Hamlib allows to be configured for your rig you can use the rigctl
utility. We ship a version of the Hamlib rigctl utility with WSJT-X called
rigctl-wsjtx. To list the available parameters you must determine he numeric
Id of your rig, this can be done by passing the -l (that is el) command line
option, like this:
C:\Users\bill>C:\WSJT\wsjtx\bin\rigctl-wsjtx -l
Rig # Mfg Model Version
Status
1 Hamlib Dummy 0.5 Beta
2 Hamlib NET rigctl 0.3 Beta
...
324 Icom IC-751 0.7.1 Beta
326 Icom IC-756 0.7.1 Alpha
327 Icom IC-756PRO 0.7
Untested
328 Icom IC-761 0.7.1
Stable
...
the output above is reduced for brevity, I have shown the rig models you
asked about. So with the Id of the IC-756PRO series, which is 327, we can
now use the rigctl utility again to list the available parameters using the
-m model option and the -L option to list configuration parameters, like
this:
C:\Users\bill>C:\WSJT\wsjtx\bin\rigctl-wsjtx -m 327 -L
rig_pathname: "Path name to the device file of the rig"
Default: /dev/rig, Value: \\.\COM1 <file:///\\.\COM1>
String.
write_delay: "Delay in ms between each byte sent out"
Default: 0, Value: 0
Range: 0.0..1000.0, step 1.0
post_write_delay: "Delay in ms between each command sent out"
Default: 0, Value: 0
Range: 0.0..1000.0, step 1.0
timeout: "Timeout in ms"
Default: 0, Value: 1000
Range: 0.0..10000.0, step 1.0
retry: "Max number of retry"
Default: 0, Value: 3
Range: 0.0..10.0, step 1.0
itu_region: "ITU region this rig has been manufactured for (freq. band
plan)"
Default: 0, Value: 2
Range: 1.0..3.0, step 1.0
vfo_comp: "VFO compensation in ppm"
Default: 0, Value: 0.000000
Range: 0.0..1000.0, step 0.0
poll_interval: "Polling interval in millisecond for transceive emulation"
Default: 500, Value: 500
Range: 0.0..1000000.0, step 1.0
ptt_type: "Push-To-Talk interface type override"
Default: RIG, Value: RIG
Combo: RIG, DTR, RTS, Parallel, CM108, None
ptt_pathname: "Path name to the device file of the Push-To-Talk"
Default: /dev/rig, Value:
String.
ptt_bitnum: "Push-To-Talk GPIO bit number"
Default: 2, Value: 0
Range: 0.0..7.0, step 1.0
dcd_type: "Data Carrier Detect (or squelch) interface type override"
Default: RIG, Value: RIG
Combo: RIG, DSR, CTS, CD, Parallel, CM108, None
dcd_pathname: "Path name to the device file of the Data Carrier Detect (or
squelch)"
Default: /dev/rig, Value:
String.
serial_speed: "Serial port baud rate"
Default: 0, Value: 19200
Range: 300.0..115200.0, step 1.0
data_bits: "Serial port data bits"
Default: 8, Value: 8
Range: 5.0..8.0, step 1.0
stop_bits: "Serial port stop bits"
Default: 1, Value: 1
Range: 0.0..3.0, step 1.0
serial_parity: "Serial port parity"
Default: None, Value: None
Combo: None, Odd, Even, Mark, Space
serial_handshake: "Serial port handshake"
Default: None, Value: None
Combo: None, XONXOFF, Hardware
rts_state: "Serial port set state of RTS signal for external powering"
Default: Unset, Value: Unset
Combo: Unset, ON, OFF
dtr_state: "Serial port set state of DTR signal for external powering"
Default: Unset, Value: Unset
Combo: Unset, ON, OFF
civaddr: "Transceiver's CI-V address"
Default: 0, Value: 92
Range: 0.0..255.0, step 1.0
mode731: "CI-V operating frequency data length, needed for IC731 and IC735"
Default: 0, Value: 0
Check button.
no_xchg: "Don't Use VFO XCHG to set other VFO mode and Frequency"
Default: 0, Value: 0
Check button.
and amongst them is the configuration option "civaddr" which has a value of
92 decimal or 0x5c hexadecimal as you state. To change this configuration
option you need to create a small configuration text file called
hamlib_settings.json , for example to change the CI-V address to 0x5D (93
decimal) the file needs to contain:
{
"config": {
"civaddr": "93"
}
}
other configuration parameters could be added separated by comma characters.
The location of this file is platform dependent, on Windows it is
%LOCALAPPDATA%\WSJT-X\hamlib_settings.json or
%PROGRAMDATA%\WSJT-X\hamlib_settings.json . On Mac OS X it is
$HOME/Library/Preferences/WSJT-X/hamlib_settings.json and on Linux it is
$HOME/.config/WSJT-X/hamlib_settings.json or
/etc/xdg/WSJT-X/hamlib_settings.json . In all cases if you are using the
WSJT-X multiple instance support using the --rig-name=<unique-string>
command line option than each of the above locations would substitute
"WSJT-X" with "WSJT-X - unique-string", thus allowing different parameter
overrides for each instance of WSJT-X.
73
Bill
G4WJS.
|
