RE: [Hamlib-developer] Icom PCR1000 - trying to get going ...

[<dar...@bt...>]

Stephane,

It's been a while but am still expecting to test a few radios over the next
few months.

Thanks for the notes on the PCR1000 - it was getting late last night and I
thought I was going bonkers! I'll run a quick test today and post back here.

Stephane: you mentioned there was an online resource for the PCR1000. Any
chance of the URL? I might stand a chance of getting some of the other
functions working once over this initial hurdle.

Jim: Thanks for the note on the switch from 9600 to 38400 - I had a
suspicion of this but no docs to back it up!

Many thanks,

Darren - G0WCW

-----Original Message-----
From: Stephane Fillod [mailto:f4...@fr...]
Sent: 06 March 2002 23:00
To: dar...@bt...
Cc: Hamlib developers
Subject: Re: [Hamlib-developer] Icom PCR1000 - trying to get going ...



Hey Darren, good to see you again!

On Wed, Mar 06, 2002, dar...@bt... wrote:
> Am I doing something dumb? I've used the pre-packaged Win32 app from Icom
> which works fine. Using rigctl and testrig (radio 401) I seem to get no
joy.
> I have set the line speeds from 2400 to 38400, set to /dev/ttyS0, and from
7
> or 8 bits using cs7/8 etc, to be sure all is the same. Am using RH 7.0 and
> the latest cvs release (downloaded yesterday).

fine. Reading the pcr1k docs, it looks like the default line speed is 9600.
I guess you already gave a look at the README.betatester file.

Would it be possible to run "rigctl -m 401 -r /dev/ttyS0 -s 9600 -vvvvvv"
and report the traces on the list or to me?
The "-vvvvvv" is very important since it will show off the traces
of the serial communication, giving hints where it breaks.

Actually, I developped the backend from documentation found on the
Internet. And obviously, I never got a chance to test it. But now,
the time has come :)

> Before I start delving into the PCR code and adding the other functions, I
> was hoping to at least get a correct response back from the radio! Anyone
> spot my mistake? 

mistake is not necessarily yours. Let's see what we can do with the
traces.


73's
Stephane F8CFE