--
You received this message because you are subscribed to the Google Groups "SDC Software Defined Connectors" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sdc-ut4lw+...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/sdc-ut4lw/4dec5ec5-da0c-4bc1-b9f1-4eafd22581c7n%40googlegroups.com.
Ken Wells, NM9P
FlexRadio, Inc.
4616 W. Howard Lane
Suite 8-860
Austin, TX USA 7872
Ken,
Here is the short update. With 4.1.5 installed.
I am still seeing no carrier when pressing TUNE in RTTY mode with 2 slices open(my typical SO2R config) and SDC skimmer connected and running on separate computer.
If I close the SDC skimmer, TUNE in RTTY mode works as expected.
If I close slice B and leave SDC skimmer running, TUNE in RTTY mode works as expected.
Here are more details on my testing.
Before installing 4.1.5 I thought it would be prudent to do a factory reset.
Steps followed:
1. Power down, remove remote power control, remove DC for ~3 minutes.
2. Factory reset by holding power button until it turned white.
3. Allow radio to fully reboot and stabilize for about 5 minutes.
4. Did NOT import saved profiles.
5.
Launch SmartSDR for windows 4.1.3, set Slice A to 14.089,
ANT1(rx)/ANT1(tx), select RTTY mode, select SO2R_TX1 profile, select
RTTYDefault Mic profile. This all factory standard stuff.
6. Press TUNE - carrier generated as expected.
7. Add second slice, set 21.085, ANT2(rx)/ANT2(tx), select RTTY, select SO2R_TX2, select RTTYDefault.
8. Slice A TX - Press TUNE - carrier generated as expected.
9. Slice B TX - Press TUNE - carrier generated as expected.
10. Start SDC skimmer on other computer.
11. Slice A TX - Press TUNE - radio switches to transmit, NO carrier.
12. Slice B TX - Press TUNE - NO carrier.
13. Stop SDC Skimmer - Press TUNE - carrier generated.
14. Start SDC Skimmer - Press TUNE - NO carrier.
15. Close Slice B - Press TUNE - carrier generated.
16. Upgrade to 4.1.5 following standard procedure.
17. Repeat steps 5 to 15 with exact same results.
--------------
Summary:
--------------
It appears to me that this issue will be reproducible on models with more than 1 SCU, ie. 6600 and 8600 models. This is consistent with the feedback I've gotten from my Flex Community and SDC Forum posts. 8400 and 6400 owners can't reproduce the problem. At least 2 other 8600 owners operating SO2R see the same problem. Hope this helps the engineering team to isolate the problem and get it resolved.
Eric - NR4O