Howard,
In my experience, Rich S's statement that "The Digitrax PR4 will only work on COM Port 3" _IS NOT TRUE_.
My current JMRI configurations on a Windows machine show that I have successfully used PR4 devices at COM7 and COM17, including one JMRI configuration profile where I had set-up two different LocoNet connections, one per PR4.
So far as I know, the whole idea behind a "COM port number" is solely something used by the operating system as a convenient "handle" to allow software to communicate with a "communications hardware" device. The PR4 itself has absolutely no idea of the COM port number the software and operating system use. If the PR4 did require knowledge of that COM port number, then how could it be used with computers running Linux and OSX operating systems, which do NOT identify communications devices via "COM port number"? I have no problems running JMRI with the PR4 under Linux!
Do you have a BDL16, BDL162, or BDL164 board? Will it be used with the Standalone LocoNet? If not, then ignore Russ's message, as it would be irrelevant.
If you do have at least one of those boards, and you will use it on your Standalone LocoNet, then you will need to configure exactly ONE BDL16x board for those settings. The settings can be made using a LocoNet throttle plugged directly into the LocoNet jack of a powered-up BDL16x board, by following the directions for configuring OpSw settings in the BDL16x manual. If you do not have a LocoNet throttle, then I think you are "out of luck" for programming the BDL16x to those settings until you come up with an alternate solution for both "LocoNet Data Signal Termination" and "power on the RailSync" wires (as described in the web page I previously linked).
Regards,
Billybob
