Welcome to the FlexRadio Community! Please review the new Community Rules and other important new Community information on the Message Board.
The latest SmartSDR Software:
SmartSDR v4.1.5 | SmartSDR v4.1.5 Release Notes
SmartSDR v3.10.15 | SmartSDR v3.10.15 Release Notes
The latest 4O3A Genius Product Software:
The latest 4O3A Genius Product Software and Firmware
SmartSDR v4.1.5 | SmartSDR v4.1.5 Release Notes
SmartSDR v3.10.15 | SmartSDR v3.10.15 Release Notes
The latest 4O3A Genius Product Software:
The latest 4O3A Genius Product Software and Firmware
How to Receive Technical Support::
If you are needing assistance with FlexRadio products, please refer to the product documentation or check the Help Center for known solutions. Need technical support from FlexRadio? It's as simple as creating a HelpDesk ticket.
If you are needing assistance with FlexRadio products, please refer to the product documentation or check the Help Center for known solutions. Need technical support from FlexRadio? It's as simple as creating a HelpDesk ticket.
rig sharing with a GUI client
Jim Shaffer
Member ✭✭
I'm trying to implement rig sharing with my GUIClient using FlexLib Version 3.1.7. I have things working the way I want, except I'm not sure how to handle transmitting.
As I understand it, with SmartSDR, both users can transmit, but only one at a time.
I'd like to limit transmitting to just one user, if possible. I'm not sure how to do this. It doesn't seem to work well if I set IsTransmitSlice off for all the slices for the nontransmit user.
I also don't really understand PTTSource and SetLocalPTTForGuiClient().
Can someone give me some pointers?
As I understand it, with SmartSDR, both users can transmit, but only one at a time.
I'd like to limit transmitting to just one user, if possible. I'm not sure how to do this. It doesn't seem to work well if I set IsTransmitSlice off for all the slices for the nontransmit user.
I also don't really understand PTTSource and SetLocalPTTForGuiClient().
Can someone give me some pointers?
0
Answers
-
Jim,
Here's how things were designed. Each GUI client has it's own designation of which Slice is the transmit Slice. This means from a radio point of view, there are multiple Transmit Slices at any given point in time. As a result, we do a Just In Time (JIT) switch when a client keys the radio to decide which Slice to use as the Transmit context. This decision gets made based on the origin of the PTT signal. If the PTT is coming from a hardware input to the radio (like a footswitch), then we will automatically use the Local PTT client's TX Slice. If the PTT is a software PTT signal (xmit command), then we will use the Transmit Slice for the client that sent the command.
Does that help to sort things out? I trust that you've seen the SmartSDR v3.0 Migration Guide. If not, it may be worth having as a reference.
0 -
I've discovered that if I issue a Radio.SetLocalPTTForGuiClient(), that updates the client's GuiClient, notifying the other host. Is that what you do with SmartSDR? If so, when do you do it, and how do you know to do it?
0 -
Setting the Local PTT sets which GUI Client to use for the transmit context when using a hardware PTT plugged into the radio. There are some more details spelled out in the migration guide linked above, but in general, you would set the Local PTT to the client that is near the radio so that when you key it, the correct client context is used.0
Leave a Comment
Categories
- All Categories
- 388 Community Topics
- 2.2K New Ideas
- 658 The Flea Market
- 8.4K Software
- 156 SmartSDR+
- 6.5K SmartSDR for Windows
- 186 SmartSDR for Maestro and M models
- 439 SmartSDR for Mac
- 275 SmartSDR for iOS
- 265 SmartSDR CAT
- 204 DAX
- 386 SmartSDR API
- 9.4K Radios and Accessories
- 53 Aurora
- 297 FLEX-8000 Signature Series
- 7.2K FLEX-6000 Signature Series
- 970 Maestro
- 58 FlexControl
- 866 FLEX Series (Legacy) Radios
- 944 Genius Products
- 471 Power Genius XL Amplifier
- 347 Tuner Genius XL
- 126 Antenna Genius
- 306 Shack Infrastructure
- 215 Networking
- 468 Remote Operation (SmartLink)
- 142 Contesting
- 811 Peripherals & Station Integration
- 144 Amateur Radio Interests
- 1.1K Third-Party Software
