View Issue Details

IDProjectCategoryView StatusLast Update
00030173 - Current Dev ListBugpublic2019-01-02 22:59
ReporterWA9PIEAssigned ToK7ZCZ 
PrioritynormalSeverityminorReproducibilityalways
Status assignedResolutionopen 
Product Version6.5.0.164 
Target VersionFixed in Version 
Summary0003017: Redundant commands sent to rig when selecting spots in Logbook's DX cluster contributes to performance issues
DescriptionWhen in Logbook, selecting a DX spot causes a redundant and unnecessary command to be sent to the rig. It should be eliminated to improve the overall performance of the software.

What seems to happen is this...

When you click on a spot, the software sends THREE commands to the radio - (a) set frequency, (b) set mode, and again (c) set frequency.

What should happen is that the software should send TWO commands to the radio - (a) set mode and then (b) set frequency.

Mode should always come first when changing mode because - when sent last, there is a frequency offset caused on most rigs when the mode is changed.

So you will see this when clicking on a spot changes the mode. When clicking on the spot is for the same mode... the redundant command is transparent (but still happens).
Steps To ReproduceI did this most recently with an FT-991A connected. But I've seen this with an FT-857D and an FTDX-5000. This could likely be happening with all radios. So begin by connecting Rig Control with one of these radios. It's probably best to use the slowest CAT baud rate so that the appearance of this is easier to observe.

Launch Rig Control connected to a radio as mentioned above
Launch Logbook and connect to a cluster node (such as the WA9PIE-2 node... but it really doesn't matter)
Set the rig to USB or LSB
Find a spot in cluster pane that is a CW spot and select it (with double-click, let's say)

Observe that the rig changes frequency... then mode... then frequency.

What should happen is that the rig should change mode... then frequency.

(the procedure above is a method to observe this... but it happens every single time a spot is selected from Logbook; I just don't know if it happens for every single manufacturer and/or rig)
TagsNo tags attached.
ModuleLogbook
Sub-ModuleRig Control
TestingNot Started

Activities

There are no notes attached to this issue.

Issue History

Date Modified Username Field Change
2019-01-02 21:46 WA9PIE New Issue
2019-01-02 21:46 WA9PIE Status new => assigned
2019-01-02 21:46 WA9PIE Assigned To => K7ZCZ
2019-01-02 22:59 WA9PIE Summary Redundant commands sent to rig when selecting spots contributes to performance issues => Redundant commands sent to rig when selecting spots in Logbook's DX cluster contributes to performance issues