The Elecraft KAT500 tuner uses CI-V for communications.
tnx
Mike / K5JR
Alpharetta GA
toggle quoted message
Show quoted text
On Aug 11, 2022, at 9:36 AM, Skip Hansen <skip@...> wrote:
?I don't remember the exact timing of Doug Hall, but it's basically SPI
so dedicated lines is probably the best bet.
For wireless/BT link I'm thinking of an ESP32 or Linux based Raspberry
Pi external to the radio as a gateway.
Another issue that I just remember from the legacy Xcat project. CI-V
is supposed to be a SINGLE wire interface. When I did the original
Xcat I was planning on tying Rxd and Txd together and dynamically
controlling the output enable. Great plan, right? It turned out that
when you enabled the UART function the PIC helpfully enabled the
output for you so you didn't need to remember to do it ... which made
it impossible to do a true CI-V without additional hardware. I'll
make sure we can do real CI-V as well as the two wire version we've
been using for the Xcat.
Much to my surprise USB to CI-V cables are still readily available
which would make it easy to interface to modern PCs or a Linux based
Raspberry Pi.
73's Skip
On Wed, Aug 10, 2022 at 8:40 PM swguest via groups.io
<swguest@...> wrote:
On Wed, Aug 10, 2022 at 07:21 AM, Skip Hansen wrote:
I feel much better about this version as we don't lose any
functionality and I2C opens new possibilities.
Feedback please!
Sorry for the crickets from me. I've been down so many rabbit holes today I might have to change my name to Alice. I've been on the hunt thru my digital media swamp. I had to investigate everything I didnt recognize....Yup lots of rabbit holes.
So..the revision, I2C is good. No extra CS lines needed for multible devices like SPI.
IIRC I2C used to be 400khz max, may be more now, but that should handle any expansion one would want.
Doug Hall protocol needs discrete sync lines even using I2C?
The (future) wireless/BT link will have to be built out on the SB9600 command set....or?
