There is a "quirk" in the WSUB3G IoT module where setting the number of data points causes the Start and Stop frequencies to be reset. For this reason an UpdateDeviceConfig command MUST follow a change in the number of data points in order to get the start and stop frequencies back to their desired values.
For example, running either:
rfeObj.SendCommand_SweepDataPointsEx(numPoints)
or
rfeObj.SendCommand_SweepDataPoints(numPoints)
will cause the contents of
rfeObj.StartFrequencyMHZ
and
rfeObj.StopFrequencyMHZ
to be changed. In my testing they always get changed to 500 MHz and ~510 MHz respectively.
I am using the IoT Module as follows:
RF Explorer 01.16 18-Jan-18 02.01.01
RF Explorer device model info:#C2-M:005,255,01.16
HWSTATUS:015
Device serial number: B3CKK7L7C7K9LC37
There is a "quirk" in the WSUB3G IoT module where setting the number of data points causes the Start and Stop frequencies to be reset. For this reason an UpdateDeviceConfig command MUST follow a change in the number of data points in order to get the start and stop frequencies back to their desired values.
For example, running either:
rfeObj.SendCommand_SweepDataPointsEx(numPoints)or
rfeObj.SendCommand_SweepDataPoints(numPoints)will cause the contents of
rfeObj.StartFrequencyMHZand
rfeObj.StopFrequencyMHZto be changed. In my testing they always get changed to 500 MHz and ~510 MHz respectively.
I am using the IoT Module as follows:
RF Explorer 01.16 18-Jan-18 02.01.01
RF Explorer device model info:#C2-M:005,255,01.16
HWSTATUS:015
Device serial number: B3CKK7L7C7K9LC37