I am looking for some guidance as to what incantation to use to get the base hamlib to permit usage of my Rigblaster PnP (a USB device) with my FT-897D --- wait, this is important --- without keying up my radio.
My hardware setup works flawlessly with fldigi (using hamlib) *as long as* I tell fldigi about the PTT on both RTS and DTR. So, on with the story:
My setup: Yaesu FT-897D, Rigblaster PnP, Ubuntu Fiesty, homebrew PC
My problem: For example, "rigctl -r /dev/ttyUSB0 -m 123" works great, but my radio keys up once connected and won't release (probably a control line assertion problem on /dev/ttyUSB0). All other normal uses of Hamlib produce the same result. I believe that fldigi gets around this by directly accessing the serial control lines of the device, and probably *after* Hamlib has asserted control. But that's a complete guess - I have not inspected the fldigi code.
My question: How do I get hamlib to send/receive serial traffic without asserting either DTR or RTS? If either of these lines are asserted, the Rigblaster PnP maps them to "key down" and activates my transmitter. This could be considered "bad". I could always write a separate program to chase after me and pull these lines down, but that just seems silly; is there an option to pass to Hamlib to tell it not to use these lines?
Aside from this single issue, I have been stunned (as a 14 year Linux veteran) at how well Hamlib and the Rigblaster has worked. Times have changed. Many thanks for some great work.
Thanks in advance for any help,
- Bill K6WFA
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have had exactly the same problem with a Micrham USB II device for my IC-765. First, I thought that the device wouldn't work under Linux but later I found a solution.
By default, hamlib enables the DTR and RTS lines, but they can be disabled using the so-called conf parameters. What you are missing on the rigctl command line is the --set-conf=param1=val1,param2=val2 argument.
Use rts_state and dtr_state for param, ON or OFF for val, i.e.
--set-conf=rts_state=OFF,dtr_state=OFF
I don't remember whether you need quotes around ON/OFF and/or param and I can't test before next week.
I hope this helps.
73
Alex OZ9AEC
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Your settings work perfectly, both with rigctl and grig (all I've tried so far). Thanks for taking the time to write back.
I am quite pleased (as I'm sure you are) that a simple solution exists - these USB interfaces are fantastic, with CAT, PTT, CW, and so forth all included on one virtual serial port.
Many thanks!
- Bill K6WFA
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am looking for some guidance as to what incantation to use to get the base hamlib to permit usage of my Rigblaster PnP (a USB device) with my FT-897D --- wait, this is important --- without keying up my radio.
My hardware setup works flawlessly with fldigi (using hamlib) *as long as* I tell fldigi about the PTT on both RTS and DTR. So, on with the story:
My setup: Yaesu FT-897D, Rigblaster PnP, Ubuntu Fiesty, homebrew PC
My problem: For example, "rigctl -r /dev/ttyUSB0 -m 123" works great, but my radio keys up once connected and won't release (probably a control line assertion problem on /dev/ttyUSB0). All other normal uses of Hamlib produce the same result. I believe that fldigi gets around this by directly accessing the serial control lines of the device, and probably *after* Hamlib has asserted control. But that's a complete guess - I have not inspected the fldigi code.
My question: How do I get hamlib to send/receive serial traffic without asserting either DTR or RTS? If either of these lines are asserted, the Rigblaster PnP maps them to "key down" and activates my transmitter. This could be considered "bad". I could always write a separate program to chase after me and pull these lines down, but that just seems silly; is there an option to pass to Hamlib to tell it not to use these lines?
Aside from this single issue, I have been stunned (as a 14 year Linux veteran) at how well Hamlib and the Rigblaster has worked. Times have changed. Many thanks for some great work.
Thanks in advance for any help,
- Bill K6WFA
Bill,
I have had exactly the same problem with a Micrham USB II device for my IC-765. First, I thought that the device wouldn't work under Linux but later I found a solution.
By default, hamlib enables the DTR and RTS lines, but they can be disabled using the so-called conf parameters. What you are missing on the rigctl command line is the --set-conf=param1=val1,param2=val2 argument.
Use rts_state and dtr_state for param, ON or OFF for val, i.e.
--set-conf=rts_state=OFF,dtr_state=OFF
I don't remember whether you need quotes around ON/OFF and/or param and I can't test before next week.
I hope this helps.
73
Alex OZ9AEC
Alex -
Your settings work perfectly, both with rigctl and grig (all I've tried so far). Thanks for taking the time to write back.
I am quite pleased (as I'm sure you are) that a simple solution exists - these USB interfaces are fantastic, with CAT, PTT, CW, and so forth all included on one virtual serial port.
Many thanks!
- Bill K6WFA