Registers for 80MHz Koolertron - 23 is 13

[jpagliaccio]

Hey Kristoff,

Great job with this code. Love your clean code style.

I have been using your code with a Koolertron 30 MHz and a SeeSil 60 MHz generator and just started testing with a 80MHz Koolertron, but the command registers are off.

It looks like for the 80MHZ generator, read Frequency register 23 is 13.

I was wondering how/where you got the register list. I am going to test and see if there all off by 10.

Thanks for sharing your code,
Joe

Update:

Kristoff, yes it looks like for the 80MHz unit all of the command registers are shifted down by 10, even parameters like ACTION and MODE. The register values under 10 look to be the same.
still testing. I will post any anomalies if I find them.
Thanks again.

[on1arf]

Hi Joe,
It has been a long time, but as far as I remember, the 'trick' I used is that I ran the windows application to control the JDS6600 with wine on linux and then used a tool to snoop the traffic that went over the serial port.
A tool like 'socat' should be able to intercept / sniff traffic on serial ports.
Another trick is to direct the traffic to a USB-over-serial device and use a tool like usbsnoop or wireshark to intercept the traffic on the USB bus.

[jpagliaccio]

Thank you Kristoff for the suggestions. That's really good. Great work. I think the basic read and write functions are working now with the 80MHz unit. Your DEBUG functions helped. Basically I copied all the registers greater than 20 and subtracted 10, then added a 10x multiplier for the frequency value to get it correct.

…

On Mon, Aug 8, 2022 at 2:15 PM Kristoff Bonne ***@***.***> wrote: Hi Joe, It has been a long time, but as far as I remember, the 'trick' I used is that I ran the windows application to control the JDS6600 with wine on linux and then used a tool to snoop the traffic that went over the serial port. A tool like 'socat' should be able to intercept / sniff traffic on serial ports. Another trick is to direct the traffic to a USB-over-serial device and use a tool like usbsnoop or wireshark to intercept the traffic on the USB bus. — Reply to this email directly, view it on GitHub <#7 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AB2TBIJ2HBUB6K2LEO5XQJTVYFFC7ANCNFSM552PRIRA> . You are receiving this because you authored the thread.Message ID: ***@***.***>