CubicSDR
CubicSDR copied to clipboard
cjcliffe
Help with Rig Control
I am setting up CubicSDR for the first time on Win 7 64, using an RTL-SDR to inject the IF signal from my TS-2000, and I want to use rig control and follow. I have it working with the exception of communicating with my rig. Other than installing CubicSDR, setting the model, baud rate, and port and then clicking “Enable rig” under rig control is there anything else needed? Absolutely nothing happens, not even the "PC" indicator on the display of the TS-2000. Is this the right format for entering the serial port, com2?
@ecj2016 did you have luck fixing the issue? I haven't had a chance to write the Rig Control docs but will take care of that soon -- I'll keep this open as a reminder to document.
One of the issues here involves re-writing the rig settings so it enumerates the available serial ports for selection instead of taking text input.
No, I haven't had any luck. I don't think hamlib ever starts. It would be nice if history would work for SDR-IF. The TS-2000 uses two IFs depending on which band you are on.
Is there a guide on persuading Cubic to talk to Rigs ? I wish to send from Cubic to my Icom R8500. It is connected to the system through the RS232 to usb converter, a standard Prolific 0x2303 chip.
@ecj2016 @MarkL-W sorry about that -- I've totally forgotten to go back and update the hamlib documentation for the 0.2.0 release. Will try to get that in soon.
Basically on Windows you'll be using "COM1" "COM2" etc. as a serial port configuration or "/dev/ttyUSB0" or something similar for Linux and OSX -- I need to add proper port enumeration to make this easier.
Hi Charles,
I forgot to state that I am using Sierra.
I found the "/dev/ttyUSB0" and selected a baud rate of 19200 as this worked with Mac Memories Manager, but I see no communication between devices. Perhaps I am missing a setting on the Icom, I will continue to look.
Regaards, Mark L-W.
On 10 January 2017 at 01:02, Charles J. Cliffe [email protected] wrote:
@ecj2016 https://github.com/ecj2016 @MarkL-W https://github.com/MarkL-W sorry about that -- I've totally forgotten to go back and update the hamlib documentation for the 0.2.0 release. Will try to get that in soon.
Basically on Windows you'll be using "COM1" "COM2" etc. as a serial port configuration or "/dev/ttyUSB0" or something similar for Linux and OSX -- I need to add proper port enumeration to make this easier.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/cjcliffe/CubicSDR/issues/444#issuecomment-271446874, or mute the thread https://github.com/notifications/unsubscribe-auth/AX2wwfR8hQ3oFmZeKo2jmQfRFmfDOLoGks5rQsqPgaJpZM4J_zv2 .
When I tried this a while back in Windows 7 and opened a case on it I did use “com2.” At least in my case it appears that Hamlib does not run because I don’t see the process in task manager.
Regards,
Ed
W4TBD
From: MarkL-W [mailto:[email protected]] Sent: Tuesday, January 10, 2017 16:10 To: cjcliffe/CubicSDR Cc: ecj2016; Mention Subject: Re: [cjcliffe/CubicSDR] Help with Rig Control (#444)
Hi Charles,
I forgot to state that I am using Sierra.
I found the "/dev/ttyUSB0" and selected a baud rate of 19200 as this worked with Mac Memories Manager, but I see no communication between devices. Perhaps I am missing a setting on the Icom, I will continue to look.
Regaards, Mark L-W.
On 10 January 2017 at 01:02, Charles J. Cliffe [email protected] wrote:
@ecj2016 https://github.com/ecj2016 @MarkL-W https://github.com/MarkL-W sorry about that -- I've totally forgotten to go back and update the hamlib documentation for the 0.2.0 release. Will try to get that in soon.
Basically on Windows you'll be using "COM1" "COM2" etc. as a serial port configuration or "/dev/ttyUSB0" or something similar for Linux and OSX -- I need to add proper port enumeration to make this easier.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/cjcliffe/CubicSDR/issues/444#issuecomment-271446874, or mute the thread https://github.com/notifications/unsubscribe-auth/AX2wwfR8hQ3oFmZeKo2jmQfRFmfDOLoGks5rQsqPgaJpZM4J_zv2 .
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/cjcliffe/CubicSDR/issues/444#issuecomment-271698845 , or mute the thread https://github.com/notifications/unsubscribe-auth/AS4chcmEga2RcPZ0J-eUx2gMlX0at2kPks5rQ_OrgaJpZM4J_zv2 .Image removed by sender.
Here is what I have sorted out. I found this thread looking for more documentation:
Enable Rig - Check to control the rig. The model, serial rate and control port must be set correctly or you will recieve an error
SDR-IF - ?Set the offset between the SDR frequenct and the radio frequenct for HamitUp like devices????
Control Rig - Check this to allow CubicSDR to Control the Rig
Follow Rig - Check this to allow the rig to control CubicSDR
Floating Center - Allow changes in frequency to change the waterfall display
Track Modem - ???
Model - Set your radio type here. All HamLib radios are supported.
Serial Rate - This must match the setting in your radio. See the radio manual for the location of this setting.
Control Port - This must be the port the radio is plugged into. ie. dev/ttyUSB0
For me to get a Pan Adapter working I checked Control Rig, Follow Rig, Floating Center and Track Modem. I have it all working but I have to change the mode in both the radio and CubicSDR in order to change the mode.
Struggling to get this to work ... I know my serial connection is good because "other stuff" such as the Kenwoood control program and Minos can talk to the radio, but no luck with Cubic. I have TS2000 selected, the correct baud rate, the right radio and the right serial port, and no other programs trying to use the serial port. When I check "Enable Rig" nothing happens, no tick appears, no error messages .. nothing. Ideas?
I have a dx3000. Mine started controlling and tracking the radio after clicking "Track Modem" for what it's worth.
Edit months later: It's unreliable and I don't know what options would make it work reliably.
