Compiled in Debian, all went well, seems to be running on the server, but mis-IDs the rig as a 9100 (is a 7100) and there is a stream of errors in above paste…
Will fiddle some more…
Dammit, that will teach me for trusting Icom manuals. It looks like the IC-9100 manual is a large ‘cut-n-paste’ from the IC-7100 one (even with some references to IC-7100 in there).
It looks like the CI-V ID that they list in the manual (0x88) is actually the ID of the IC-7100. The correct address is 0x7C.
If you want to pull the latest from Gitlab and rebuild (or just run the build script again) that should get the correct version.
Cool, i’ll build again…
Everything else is working on the server - TUNE blah blah all behaves…
The BIG win so far is that even with the 1.6x client, 2.0x server appears to be super snappy and the random frequency display issue seems to be gone - that was the only real bugbear of late my users were winging about…
GO GO VERSION 2!!!
1 Like
Fixed rig id issue, correctly has 7100 as rig 
Both VFOs are now showing (had not noticed, but only 1 was previously)
(FA) loop has stopped in log, now has a new loop:
Also, not sure if this is a thing, but the RADIO STATUS button on the server is blank/no action on graphs - 1.6x client correctly shows rig status…
Ah OK, that’s a pain, looks like I missed some commands? Interestingly, I don’t think any of those are actually used by wfview, do you have other software connected to the radio?
Nope… nothing. server is exclusive to wfview right now.
Never noticed them before.
Seems not to effect anything mind you…
No they are quite benign:
"1a05004600" is Send/read the Power OFF setting when no controller is connected.
"1b00000885" and "1b01000885" are related to repeater tones so I can definitely fix
"0c001000" is Send/read transceiver’s status (TX)
I assume that you probably have “CI-V output for ANT” enabled in the radio settings as I have never seen these on my IC-7100. There are various settings that can be enabled for transceive mode so they are automatically output. wfview 1.64 would have silently ignored these, but with v2 I wanted to know if we are missing commands.
It stops when no client is connected, which is nice.
Let me see how the various versions/platforms of client behave, not everyone is on 2.0x out there. In fact i think we are all on 1.6x since i only upgraded the server an hour ago…
Win(64) current download as a client is clean - no clutter in the log on the server 
SO - although previous versions have no problems, best to upgrade both ends to 2.0x
2 Likes