I like wfview very much ! I can activate most or all of the controls on my IC-7300 via the CI-V interface and code using OCTAVE ( MATLAB-like ) language, its instrument-control package and a USB-to-CI_V cable.
I would like to be able to access the waveform ( spectrum scope ) data via code. I understand that this data is only provided over the radio’s USB interface, not the CI-V interface. For my application, a smaller number of spectrum scope outputs ( every Nth sweep, for example ) would be acceptable.
Is there any way that wfview can or could make ( reduced rate if necessary ) spectrum scope data available to MATLAB / OCTAVE or python or C ?
Thanks for any and all comments.
73’s, Paul K Wagner, WB8ICI
The spectrum actually is over CI-V. Once spectrum is enabled, the CI-V bus will show a massive spike in activity with spectrum messages coming out at regular intervals. This page pretty well describes the format of the spectra (scroll down):
We will probably not be adding any kind of spectrum export features to wfview, but you can easily build such a thing using a little python or C. You can use wfview to enable the spectrum, close wfview, and then just save the data coming over the port to a file. Then it’s just a matter of parsing out the data.
EXCELLENT ! Cryptic IC-7300 manual control command section suggests spectrum is only over CI-V.
I will definitely try this out. Thanks very much for the tip.
The manual says “only when 27 10 and 27 11 are set to on … waveform data is output *4”.
( I made sure that Note *4 was performed before I attempted anything ).
I can set Scope ON/OFF status ( 27 10 ) to on or off, and the reply is OK ( 0xFB ), but …
I can NOT set Scope wave data output ( 27 11 ) to on or off, the reply is NG ( 0xFA ).
Elliott,
I used the command window to run wfview -d as you recommended.
I see evidence of a wide range of commands and responses with E1 as the CI-V PC address …
… but NO incidences of any commands or data containing 27 00 00 …
I followed your IC-7300 and wfview instructions to the letter.
( tried to upload my log file but couldn’t due to be a “new user” )
Come to think of it, I think we filter out spectrum commands from the logs due to how much data it is. This likely blocks the setup commands too.
If you are getting “FA” and you have sent the command just like the code I sent you does, then it may be that you do not have “unlink from remote = yes” or you have the wrong baud rate selected. I don’t know. I can tell you though, we wrote wfview per the 7300 documentation. There’s nothing magical about the commands we send to set it up.
If wfview is receiving waveform data (the scope is working) then you can always connect to the TCP server provided by wfview, as this will forward all CIV data received from the radio, including waveform data.