V3(.2.39) curiosities

John G3WGV

I've been taking a rest from software development in recent years, enjoying getting on the air with my home-brew controller, which kinda got stuck on V2.

Well I'm back to hacking code again, this time with my 6600 and V3.2.39. And I ran into some interesting problems! Setup is Smart SDR, with my controller and my logging program both connected to the same radio as non-GUI clients.

Multiple interlock messages

Whenever I tune (by the controller, on Smart SDR or via my logging program) I get three identical interlock messages as captured by my API traffic logger:

18:18:20.306 | [TCP>] C106|slice tune 0 7.026100

18:18:20.321 | [<TCP] S21120BDF|interlock tx_client_handle=0x00000000 state=READY reason= source= tx_allowed=1 amplifier=

18:18:20.321 | [<TCP] S21120BDF|interlock tx_client_handle=0x00000000 state=READY reason= source= tx_allowed=1 amplifier=

18:18:20.324 | [<TCP] S21120BDF|interlock tx_client_handle=0x00000000 state=READY reason= source= tx_allowed=1 amplifier=

18:18:20.324 | [<TCP] S21120BDF|transmit freq=7.026100 lo=100 hi=2900 tx_filter_changes_allowed=1

18:18:20.325 | [<TCP] R106|0|         | Latency: 18.95ms

This just seems to be unnecessary triplicate traffic. I don't recall seeing it before I started playing with V3.

Incorrect pan stream ID

This one actually caused my controller to crash and I had to write some defensive new code!

When a client changes band using slice tune, among the many TCP/IP transactions sent to each client are these:

18:23:40.126 | [<TCP] S6A5A947A|display pan 0x40000000 band_zoom=0 segment_zoom=0

18:23:40.126 | [<TCP] S6A5A947A|display pan 0x42000000 band_zoom=0 segment_zoom=0

The first transaction is fine but what's with the second one? 0x42000000 is a waterfall stream surely?

More duplicate interlock messages

The band change also results in a slew of identical interlock messages in the space of just 2ms:

18:23:40.129 | [<TCP] S6A5A947A|interlock tx_client_handle=0x00000000 state=READY reason= source= tx_allowed=1 amplifier=

18:23:40.129 | [<TCP] S6A5A947A|interlock tx_client_handle=0x00000000 state=READY reason= source= tx_allowed=1 amplifier=

18:23:40.130 | [<TCP] S6A5A947A|interlock tx_client_handle=0x00000000 state=READY reason= source= tx_allowed=1 amplifier=

18:23:40.131 | [<TCP] S6A5A947A|interlock tx_client_handle=0x00000000 state=READY reason= source= tx_allowed=1 amplifier=

18:23:40.131 | [<TCP] S6A5A947A|interlock tx_client_handle=0x00000000 state=READY reason= source= tx_allowed=1 amplifier=

All interesting stuff for those of us that get a kick out of tinkering around with the API. Perhaps Eric can offer some insight?

73, John, G3WGV