Re: [Hamlib-developer] PCR1000 debugs

[Stephane F. <f4...@fr...>]

On Thu, Mar 07, 2002, dar...@bt... wrote:
> Log from the PCR1000 as requested. If you need specific commands executed, just let me know and I'll run them.

well, actually, there aren't much :)
Just get_info and get/set freq/mode. Still a good start.

> Have a look to see if anything obvious. If not, I'll need to start digging as well!

2 huge bugs!
It's so much easier when you can test..

> Rig command: _
> 
> TX 5 bytes
> 
> 0000	 47 32 3f 0d 00	G2?..
                     ^^
This should be 0x0a. First bug. fixed.

> RX 1 bytes
> 
> 0000	 0a	.
> 
> RX 1 bytes
> 
> 0000	 48	H
> 
> RX 1 bytes
> 
> 0000	 31	1
> 
> RX 1 bytes
> 
> 0000	 30	0
> 
> RX 1 bytes
> 
> 0000	 30	0
> 
> RX 1 bytes
> 
> 0000	 0d	.
> 
> RX 1 bytes
> 
> 0000	 0a	.

Obviously, the rig reply with "H100", i.e. "I'm in power off state".
This is the second problem. should be fixed and commited.

Thanks to Jim Tittsler, I better understand how it works. There's now a
pcr_open in pcr/pcr.c that talks at 9600 bauds to power on the rig, and
will change speed later on, when the code stabilizes a bit.

Darren, could you please run again the same tests with the newest cvs
code and send me the traces? Thanks.

Stephane