The main thing that I am doing is getting the virtual comm ports out of the range comm1-10. This does not give you complete safety as I have seen windows decide to assign comm12 out of the blue to a vcomm device but it does eliminate 85% of the confusion.
The reason I think this is important is that people get upset (rightly so) when all of a sudden their PowerSDR and DDUtil configurations that used to work no longer do. I think one of the main causes of this is the inadvertent comm port assignment shuffle when you stick in a card reader, camera, new mouse/.keyboard fob, etc and now comm5 isnt what you thought it was anymore. If you move them up, the chances that windows will do this decrease and you will enjoy fewer of those gotchas that frustrate everyone! 73 Neal On Wed, Jun 15, 2011 at 4:28 PM, Scott Myers <[email protected]> wrote: > > If I try to use the DDUtil support, I get a COM port conflict. If I > re-install PowerSDR to not include the controller and try to use PowerSDR > itself, it doesn't work. All of my virtual com ports start at 10 and > above. > > > > This is a problem one can have with virtual com ports with a FlexControl, > but there is a simpler solution than what has been suggested by Flex in the > set-up sheet. I decided to not do the com port assignment as Flex > suggested, as changing all the virtual ports in all my software would be a > real pain. I found that the simplest solution is to record where you have > all your virtual ports before installing the knob, then disable all your > virtual ports temporarily. Then install the knob and drivers. Then go > into > device manager and reset the com port for the FlexControl to a com port > where none of your virtual ports are (or other hardware ports). Then > re-enable all your virtual ports. This requires no reconfiguration of any > of your virtual ports and all will work as it once did, plus you have a > working FlexControl knob. This seems a much simpler solution than making > your virtual ports fit the one hardware port of the FlexControl. > > > > Put everything back as when you started. Then just go and manually move > the > FlexControl's com port where you want it to not conflict with your existing > software. > > > > 73, > > Scott AC8DE > > _______________________________________________ > Flexedge mailing list > [email protected] > http://mail.flex-radio.biz/mailman/listinfo/flexedge_flex-radio.biz > This is the FlexRadio Systems e-mail Reflector called FlexEdge. It is used > for posting topics related to SDR software development and experimentalist > who are using beta versions of the software. > -- Abroham Neal Software www.abrohamnealsoftware.com Work:(540) 645 5394 Mobile:(540) 645 8171 _______________________________________________ Flexedge mailing list [email protected] http://mail.flex-radio.biz/mailman/listinfo/flexedge_flex-radio.biz This is the FlexRadio Systems e-mail Reflector called FlexEdge. It is used for posting topics related to SDR software development and experimentalist who are using beta versions of the software.
