Re: [Hamlib-developer] Optoscan 535

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

Hi John!

Thanks for stopping by. That's nice to see people interrested in Hamlib.

Quoting "John R. Marshall" <hot...@us...>:
> I wonder if anyone is interested in coding a backend for the Optoelectronics 
> Optoscan 535 (A computer interface for the Radio Shack pro2035 and pro2045 
> scanners) It uses a version of the ICOM CI-5 interface.

Shouldn't be a problem since it uses the ICOM CI-V protocol.

> So if someone makes the backend, I'll make a kick butt gui for it. :-) I

take five, you've got a deal!

> subscribed to the list and I have the optoscan535/pro2035 combo so I'll be 
> available for testing (I'm good at breaking code ;-0) and I might be able to 
> fix some bugs myself, who knows.

Code breaker. Good. We need it. That's half of the work. I've heard stories
at the NASA where testers able to find 1 or 2 bugs per month were considered as 
*very* good testers.
Hamlib has be to be robust. Imagine controlling AO-40 with Hamlib, nobody wants 
to loose it again.

> You can find the specs for the interface here:
> http://www.optoelectronics.com/tech/pdf/os535/os535_ci5_spec_v10.pdf
> 
> And let me know what info you need for the scanner (freq range etc..).

Should be okay. I'll add in some basic support, and then we can implement
Optoscan specific commands.

> And heres the specs for the optoscan456 interface for the pro2004-6 scanners 
> if your interested: 
http://www.optoelectronics.com/tech/pdf/os456/os456_ci5_spec.pdf

Are there many differences with the os535?

> Come to think of it the Elecraft K2 would be another rig I'd like to see
> included (the specs are on their site www.elecraft.com) I'm going to buy the 
> kit as soon as I get around to getting my ticket, and have the cash :-)

Is the K2 remote controllable? I got to check this out. 
As Frank used to say it, "If we can talk to it, we want to control it!!"


Cheers,
 Stephane F8CFE