Dan -
I'll look forward to the update. Will it also cure the graphical crash on rotation?
Would you help me with some code. I'm sure it's syntax and I'm a hardware guy, not software:)
Here's what I tried for PTT polling. Where would this be indicated on the app?
Elecraft TQ command returns "TQ0" for PTT OFF and "TQ1" for ON
CMD_READ_PTT=02,00,<STQ;>,<R>,03,<00>,<00>,<STQ0=OFF;STQ1=ON>
Here's the S-meter Command:
Elecraft SMH command returns "SMHxxx" where xxx is the s-meter value expressed as a decimal number. I assumed this number is one hex byte. I queried the radio with steady state noise to get these values.
CMD_READ_SMETER=01,01,,<SSMH;>,<R>,04,<00,00,00,1A=S3>,<00,00,00,1A=S3>,<00,00,00,20=S5>,<00,00,00,2A=S7>,<00,00,00,2D=S9>,<00,00,00,34=S9+10>,<00,00,00,3C=S9+20>
Then I added a polling statement. A small dot blinks on the left corner opposite the heartbeat. I guess that indicates polling, but that's all I get.
Thanks.
Gary
K3OS
Elecraft radios config files
Re: Elecraft radios config files
Hi Gary,
First I need to know if TQ command can be used during both Rx and Tx. If this is the case, the right syntax for PTT read is the following:
CMD_READ_PTT=01,00,<STQ;>,<R>,03,<00>,<00>,<S0=OFF;S1=ON>
with the following explanation:
01 - read PTT status in each polling loop
00 - reat during both Rx and Tx
<STQ;> - send 'TQ;' command
<R> - separator
03 - 3 bytes are expected to be returned by the radio
<00> - this byte is discarded
<S0=OFF;S1=ON> - if the char in this byte is '0' then consider PTT off, if ''1' then PTT is ON.
For the S-METER things are more complicated, so you need to use calibration parameter too(it may require some tuning of the calibration parameter based on the specific values returned by the radio):
CMD_READ_SMETER=01,01,<SSMH;>,<R>,06,<00>,<00>,<00>,<T2>,<T1>,<T0>
with the following explanation:
01 - read the parameter each polling loop
01 - read only turing Rx
<SSMH;> - send the command 'SMH'
<R> - separator
06 - 6 bytes are expected to be returned by the radio
<00> - this byte is discarded
<T2> - hundreds digit of a decimal number (as a character)
<T1> - tens digit of a decimal number
<T0> - units digit of a decimal number
then for the calibration parameters. I don't have the right values for all S levels, so you need to change to the right values. Any values in between the defined ones are automatically interpolated by the application. Please be aware that all values assigned to each S are 3 digits decimal values.
CALIB_SMETER=<MAX=100>,<0=0;10=1;17=2;26=3;29=4;32=5;37=6;42=7;43=8;45=9;52=910;60=920;70=930;80=940;90=950;100=960>
with the following explanation:
<MAX=100> - decimal value corresponding with the S-meter bargraph in Pocket RxTx fully lighted
0=0 - 000 value means S0 (my estimation, as I don't have the real values)
10=1 - 010 decimal value means S1 (my estimation, as I don't have the real values)
17=2 - 017 decimal value means S2 (my estimation, as I don't have the real values)
23=3 - 023 decimal value means S3 (1A hex value in your example)
29=4 - 029 decimal value means S4 (my estimation, as I don't have the real values)
32=5 - 032 decimal value means S5 (20 hex value in your example)
37=6 - 037 decimal value means S6 (my estimation, as I don't have the real values)
42=7 - 042 decimal value means S7 (2A hex value in your example)
43=8 - 043 decimal value means S8 (my estimation, as I don't have the real values)
45=9 - 045 decimal value means S9 (2D hex value in your example)
52=910 - 052 decimal value means S9+10dB (34 hex value in your example)
60=920 - 060 decimal value means S9+20dB (3C hex value in your example)
70=930 - 070 decimal value means S9+30dB (my estimation, as I don't have the real values)
80=940 - 080 decimal value means S9+40dB (my estimation, as I don't have the real values)
90=950 - 090 decimal value means S9+50dB (my estimation, as I don't have the real values)
100=960 - 100 decimal value means S9+60dB (my estimation, as I don't have the real values)
Hope this clarify the syntax for the read commands.
73 Dan YO3GGX
Yes.K3OS wrote:Dan -
I'll look forward to the update. Will it also cure the graphical crash on rotation?
Yes, this means that polling is active.Would you help me with some code. I'm sure it's syntax and I'm a hardware guy, not software:)
Here's what I tried for PTT polling. Where would this be indicated on the app?
Elecraft TQ command returns "TQ0" for PTT OFF and "TQ1" for ON
CMD_READ_PTT=02,00,<STQ;>,<R>,03,<00>,<00>,<STQ0=OFF;STQ1=ON>
Here's the S-meter Command:
Elecraft SMH command returns "SMHxxx" where xxx is the s-meter value expressed as a decimal number. I assumed this number is one hex byte. I queried the radio with steady state noise to get these values.
CMD_READ_SMETER=01,01,,<SSMH;>,<R>,04,<00,00,00,1A=S3>,<00,00,00,1A=S3>,<00,00,00,20=S5>,<00,00,00,2A=S7>,<00,00,00,2D=S9>,<00,00,00,34=S9+10>,<00,00,00,3C=S9+20>
Then I added a polling statement. A small dot blinks on the left corner opposite the heartbeat. I guess that indicates polling, but that's all I get.
First I need to know if TQ command can be used during both Rx and Tx. If this is the case, the right syntax for PTT read is the following:
CMD_READ_PTT=01,00,<STQ;>,<R>,03,<00>,<00>,<S0=OFF;S1=ON>
with the following explanation:
01 - read PTT status in each polling loop
00 - reat during both Rx and Tx
<STQ;> - send 'TQ;' command
<R> - separator
03 - 3 bytes are expected to be returned by the radio
<00> - this byte is discarded
<S0=OFF;S1=ON> - if the char in this byte is '0' then consider PTT off, if ''1' then PTT is ON.
For the S-METER things are more complicated, so you need to use calibration parameter too(it may require some tuning of the calibration parameter based on the specific values returned by the radio):
CMD_READ_SMETER=01,01,<SSMH;>,<R>,06,<00>,<00>,<00>,<T2>,<T1>,<T0>
with the following explanation:
01 - read the parameter each polling loop
01 - read only turing Rx
<SSMH;> - send the command 'SMH'
<R> - separator
06 - 6 bytes are expected to be returned by the radio
<00> - this byte is discarded
<T2> - hundreds digit of a decimal number (as a character)
<T1> - tens digit of a decimal number
<T0> - units digit of a decimal number
then for the calibration parameters. I don't have the right values for all S levels, so you need to change to the right values. Any values in between the defined ones are automatically interpolated by the application. Please be aware that all values assigned to each S are 3 digits decimal values.
CALIB_SMETER=<MAX=100>,<0=0;10=1;17=2;26=3;29=4;32=5;37=6;42=7;43=8;45=9;52=910;60=920;70=930;80=940;90=950;100=960>
with the following explanation:
<MAX=100> - decimal value corresponding with the S-meter bargraph in Pocket RxTx fully lighted
0=0 - 000 value means S0 (my estimation, as I don't have the real values)
10=1 - 010 decimal value means S1 (my estimation, as I don't have the real values)
17=2 - 017 decimal value means S2 (my estimation, as I don't have the real values)
23=3 - 023 decimal value means S3 (1A hex value in your example)
29=4 - 029 decimal value means S4 (my estimation, as I don't have the real values)
32=5 - 032 decimal value means S5 (20 hex value in your example)
37=6 - 037 decimal value means S6 (my estimation, as I don't have the real values)
42=7 - 042 decimal value means S7 (2A hex value in your example)
43=8 - 043 decimal value means S8 (my estimation, as I don't have the real values)
45=9 - 045 decimal value means S9 (2D hex value in your example)
52=910 - 052 decimal value means S9+10dB (34 hex value in your example)
60=920 - 060 decimal value means S9+20dB (3C hex value in your example)
70=930 - 070 decimal value means S9+30dB (my estimation, as I don't have the real values)
80=940 - 080 decimal value means S9+40dB (my estimation, as I don't have the real values)
90=950 - 090 decimal value means S9+50dB (my estimation, as I don't have the real values)
100=960 - 100 decimal value means S9+60dB (my estimation, as I don't have the real values)
Hope this clarify the syntax for the read commands.
73 Dan YO3GGX
Re: Elecraft radios config files
Dan -
Thanks very much. Yes, the K3s will respond to the inquiry in transmit mode. I tried the PTT Polling per your suggestions. There is no indication of PTT anywhere on the screen. If I touch XMIT on the rig, nothing happens on the phone.
With the POLLING interval at 01, a lot of audible dropouts are created on the phone. Changing that to 02 is much better, but not 100% In both cases the "slide to lock PTT" is compromised and somewhat intermittent.
Gary
K3OS
Thanks very much. Yes, the K3s will respond to the inquiry in transmit mode. I tried the PTT Polling per your suggestions. There is no indication of PTT anywhere on the screen. If I touch XMIT on the rig, nothing happens on the phone.
With the POLLING interval at 01, a lot of audible dropouts are created on the phone. Changing that to 02 is much better, but not 100% In both cases the "slide to lock PTT" is compromised and somewhat intermittent.
Gary
K3OS
Re: Elecraft radios config files
Hi Gary,
Can you please point me to the CAT protocol document for Elecraft to take a look?
Feedback is a feature to be used when you operate from the transceiver buttons, over a fast network, just to have a bigger display. Whats the baudrate for the serial communication from jAReC? For better results you need to use the highest available Baudrate.
73 Dan YO3GGX
The only indication is that the PTT button background color will change from blue to red.K3OS wrote:Dan -
Thanks very much. Yes, the K3s will respond to the inquiry in transmit mode. I tried the PTT Polling per your suggestions. There is no indication of PTT anywhere on the screen. If I touch XMIT on the rig, nothing happens on the phone.
Can you please point me to the CAT protocol document for Elecraft to take a look?
Are you trying this over the local WiFi network or from the Internet through 3G/4G?With the POLLING interval at 01, a lot of audible dropouts are created on the phone. Changing that to 02 is much better, but not 100% In both cases the "slide to lock PTT" is compromised and somewhat intermittent.
Gary
K3OS
Feedback is a feature to be used when you operate from the transceiver buttons, over a fast network, just to have a bigger display. Whats the baudrate for the serial communication from jAReC? For better results you need to use the highest available Baudrate.
73 Dan YO3GGX
Re: Elecraft radios config files
Link to the K3s programmer's reference manual
http://www.elecraft.com/manual/K3S&K3&K ... ,%20F8.pdf
All testing is done on my local network using a dedicated computer, AMD A4 Windows 10. Phone is a Moto (Lenovo) G4, with Android 6.x. Baud rate to the rig is 38,400 which is the fastest available.
Today I am going to test using a tablet, a Google (Samsung) Nexus 10 with CM13 OS, an Android 6.x derivative. Will advise if the results are different.
Gary
K3OS
http://www.elecraft.com/manual/K3S&K3&K ... ,%20F8.pdf
All testing is done on my local network using a dedicated computer, AMD A4 Windows 10. Phone is a Moto (Lenovo) G4, with Android 6.x. Baud rate to the rig is 38,400 which is the fastest available.
Today I am going to test using a tablet, a Google (Samsung) Nexus 10 with CM13 OS, an Android 6.x derivative. Will advise if the results are different.
Gary
K3OS