[TenTec] Programming Jupiter From A PC

Wed, 26 Jun 2002 10:27:32 -0400

Here is the results of my attempt to write a program that reads a text file=
=20
containing memory numbers, frequencies, modes and bandwidths, then writes=20
the data to the memories of the Jupiter. The program is written in C and=20
runs on a Unix PC.

The text below is the debug output of my program with added comments. The=20
TX: is the data that was sent to the Jupiter=92s serial port and the RX: is=
=20
the data received back from the Jupiter. The data is dumped in hex (base=20
16) and any printable ASCII characters are displayed on the right of the=
 line.

I found several problems which are listed below. I do not think there is a=
=20
problem with my program, however, I won=92t know for sure until someone else=
=20
either fails or succeeds loading the Jupiter=92s memories using the=20
Programming commands.

1. Whenever I issue the STORE MEMORY command (*S..), the radio recalls=20
memory #105. However, the data is stored in the selected memory, because if=
=20
I manually recall the memory from the radio controls, the correct=20
frequency, mode, bandwidth is recalled to VFO A.

2. The only memory I can recall using the RECALL MEMORY command (*R..), is=
=20
memory # 0. Attempting to recall 1 through 127 always returns memory # 0.

3. When I try to recall memory # 13, I receive an error (Z) from the radio.=
=20
Note that the command for recalling memory # 13 is: *R<0d><0d> where the=20
first <0d> is the memory # (13 decimal) and the second <0d> is a CARRAGE=20
RETURN that terminates the command. The programming document clearly states=
=20
that the firmware is aware of the possibility of <0d> being in the data=20
portion of the command and correctly processes the command=85 WELL I GUESS=
 NOT!!!

4. Since all I was attempting to do with my program was to reload the=20
Jupiter=92s memories, which is required after upgrading the Firmware and=20
doing a Hard reset (Power on with any control pressed), I could live with=20
these minor issues, because I could now manually select all the memories=20
that I had programmed=85 Well to my surprise, after I had powered the radio=
=20
OFF for the night, the next morning I turned the radio on and attempted to=
=20
select a memory, well, all the memories were reset to their default (15.0=20
MHz) just like when a Hard reset is performed. I then started up my program=
=20
and reprogrammed the memories and manually checked each. They were all=20
restored. I then turned off the radio for about 30 seconds and then back=20
on, again all memories were cleared. I then manually programmed a few=20
memories and again recycled the power on the radio. The memories that I=20
manually programmed were still set. I then repeated the process of=20
programming the memories with my program, manually checked them, and=20
recycled the power. All memories were again erased=85

WELL SO MUCH FOR MY PROGRAMMING EFFORTS !!!!!!!!

Also, there is no way that I can find to store a SPLIT memory. Even though=
=20
the programming language allows VFO B to be programmed, without a way to=20
push the SPLIT button, VFO B is not recalled. For example, if one wanted to=
=20
program VFO A with 29.620 MHz and VFO B with 29.520 MHz and store the=20
values in a memory with the SPLIT set.

Any comments or suggestions are welcome.

Jere Sandidge, K4FUM
[email protected]

Start of debug

SEND THE SOFT RESET COMMAND =91XX=92
TX: 58 58 0d XX.
RX: 0d 0d 20 20 52 41 44 49 4f 20 53 54 41 52 54 0d .. RADIO START.

REQUEST VERSION =91?V=92
TX: 3f 56 0d ?V.
RX: 56 45 52 20 31 31 39 30 2d 35 33 38 0d VER 1190-538.

note: line from text file =3D mem #, freq A, mode A, bw, freq B, mode B
0 750000 A 6000 650000 A

SET VFO A =3D 750.0 KHz
TX: 2a 41 00 0b 71 b0 0d *A..q..

vfo A now displays 750000 and receives local AM station

SET VFO B =3D 840.0 KHz
TX: 2a 42 00 09 eb 10 0d *B.....

vfo B now displays 840000

SET MODE =3D AM
TX: 2a 4d 30 30 0d *M00.

vfo A and B now set to mode AM

SET BANDWIDTH =3D 6000
TX: 2a 57 01 0d *W..

vfo A now displays bw 6000

STORE MEM # 0
TX: 2a 53 00 0d *S..

vfo A now displays 15.000000 and memory # 105 ??????
note: after each memory store vfo A recalls memory # 105

RECALL MEM # 0
TX: 2a 52 00 0d *R..

vfo A now displays 750.000 and memory # 0 as expected

note: next line from text file =3D memory #, freq A, mode A, bw, freq B,=
 mode B
1 840000 A 6000 680000 A

SET VFO A =3D 840.0 KHz
TX: 2a 41 00 0c d1 40 0d *A...@.

vfo A now displays 840000 and receives AM station

SET VFO B =3D 680.0 KHz
TX: 2a 42 00 0a 60 40 0d *B..`@.

vfo B now displays 680000

SET MODE =3D AM
TX: 2a 4d 30 30 0d *M00.

vfo A and B now set to mode AM

SET BANDWIDTH =3D 6000
TX: 2a 57 01 0d *W..

vfo A now displays bw 6000

STORE MEM # 1
TX: 2a 53 01 0d *S..

vfo A now displays 15.000000 and memory # 105 ??????

RECALL MEM #1
TX: 2a 52 01 0d *R..

vfo A now displays 750.000 and memory # 0 NOT MEM # 1
note: recall any memory # always recalls memory #0 ?????

note: next line from text file =3D memory #, freq A, mode A, bw, freq B,=
 mode B
2 1818000 C 900 1850000 C

SET VFO A =3D 1.818 MHz
TX: 2a 41 00 1b bd 90 0d *A.....

vfo A now displays 1818000 and receives

SET VFO B =3D 1.850 MHz
TX: 2a 42 00 1c 3a 90 0d *B..:..

vfo B now displays 1850000

SET MODE =3D CW
TX: 2a 4d 33 33 0d *M33.

vfo A and B set to mode CW

SET BANDWIDTH =3D 900
TX: 2a 57 19 0d *W..

vfo A now displays bw 900

STORE MEM # 2
TX: 2a 53 02 0d *S..

vfo A now displays 15.000000 and memory # 105 ??????

RECALL MEM # 2
TX: 2a 52 02 0d *R..

vfo A now displays 750.000 and memory # 0 NOT MEM # 2

...

note: debug for memory 3 through 12 deleted from this memo

...

note: next line from text file =3D memory #, freq A, mode A, bw, freq B,=
 mode B
13 7047500 C 900 7047500 C

SET VFO A =3D 7047.5 KHz
TX: 2a 41 00 6b 89 4c 0d *A.k.L.

vfo A now displays 7047500 and receives

SET VFO B =3D 7047.5 KHz
TX: 2a 42 00 6b 89 4c 0d *B.k.L.

vfo B now displays 7047500

SET MODE =3D CW
TX: 2a 4d 33 33 0d *M33.

vfo A and B set to mode CW

SET BANDWIDTH =3D 900
TX: 2a 57 19 0d *W..

vfo A now displays bw 900

STORE MEM # 13
TX: 2a 53 0d 0d *S..

vfo A now displays 15.000000 and memory # 105 ??????

RECALL MEM # 13
TX: 2a 52 0d 0d *R..
RX: 5a 0d Z.

Note: received an error from radio (Z). Radio did not process the
memory # 13 (hex 0d) correctly as stated in Programming Doc.

End of debug=85

--- StripMime Report -- processed MIME parts ---
multipart/alternative
  text/plain (text body -- kept)
  text/html
The reason this message is shown is because the post was in HTML
or had an attachment. Attachments are not allowed.
Please post in Plain-Text only.---