You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
WARNING: Filling out the template below is NOT optional. Issues not filling out this template will be closed without review.
FIRST: Before reporting any bug, make sure that the bug you are reporting has not been reported before. Also, try to use the nightly version if possible in case I've already fixed the bug.
Hardware
CPU: I5 4440
RAM: 16 Gb
GPU:
SDR: (Remote or local? If remote, what protocol?) Hermes Lite 2 local
Software
Operating System: Name + Exact version (eg. Windows 10 x64, Ubuntu 22.04, MacOS 10.15) Ubuntu 24.04.01
SDR++: Version + Build date (available either in the window title or in the credits menu which you can access by clicking on the SDR++ icon in the top right corner of the software). Version 1.2.0 from GitHub compiled today
Bug Description
A clear description of the bug.
Rigctl_server running on localhost:4532 crash at "m" command and return nothing at "\get_mode" command.
Sdrpp is set to USB with a BW of 3000
Steps To Reproduce
start sdrpp
in another terminal window start rigctl -m 2 -r localhost:4532
issue "\get_mode" or "m" command at rigctl prompt
Screenshots
Add any screenshot that is relevant to the bug (GUI error messages, strange behavior, graphics glitch, etc...).
Additional info
Add any other relevant information.
WARNING: Filling out the template below is NOT optional. Issues not filling out this template will be closed without review.
FIRST: Before reporting any bug, make sure that the bug you are reporting has not been reported before. Also, try to use the nightly version if possible in case I've already fixed the bug.
Hardware
Software
Bug Description
A clear description of the bug.
Rigctl_server running on localhost:4532 crash at "m" command and return nothing at "\get_mode" command.
Sdrpp is set to USB with a BW of 3000
Steps To Reproduce
Screenshots
Add any screenshot that is relevant to the bug (GUI error messages, strange behavior, graphics glitch, etc...).
Additional info
Add any other relevant information.
Messages on terminal window:
`Rig command: f
Frequency: 14128450
Rig command: F 14080000
Rig command: \get_mode
Rig command: m
get_mode: error = rig_get_mode(2528): freqMainA=14080000, modeMainA=, widthMainA=0
rig_get_mode(2528): freqMainB=14128450, modeMainB=, widthMainB=0
rig_get_mode(2578): debug
3:rig.c(2607):rig_passband_normal entered
3:rig_passband_normal: return filter#6, width=2700
3:rig.c(2628):rig_passband_normal returning(2700)
3:cache.c(35):rig_set_cache_mode entered
rig_set_cache_mode(37): freqMainA=14080000, modeMainA=, widthMainA=0
rig_set_cache_mode(37): freqMainB=14128450, modeMainB=, widthMainB=0
rig_set_cache_mode(107): freqMainA=14080000, modeMainA=USB, widthMainA=2700
rig_set_cache_mode(107): freqMainB=14128450, modeMainB=, widthMainB=0
3:cache.c(108):rig_set_cache_mode returning(0)
rig_get_mode(2583): freqMainA=14080000, modeMainA=USB, widthMainA=2700
rig_get_mode(2583): freqMainB=14128450, modeMainB=, widthMainB=0
2:rig_get_mode: elapsed=10010ms
2:rig.c(2586):rig_get_mode returning(-5) Communication timed out
1:rigctl_parse.c(2246):rigctl_get_mode returning(-5) Communication timed out
Communication timed out
Rig command: q
????????????????�������`
Regards
Franco Spinelli
IW2DHW
The text was updated successfully, but these errors were encountered: