There's another solution should work well. What logging app are you using? If it supports hamlib (like Log4OM) there's one solution, if not there's another solution via hamlib.
#1 You can use FLRig to control your rig #2 Hook WSJT-X up to FLRig #3 Run "rigctld -m 4 -vvv -Z" -- this will show debug and time stamps if any errors occur #4 You need a virtual port pair like COM9/10 and run "rigctlcom -R COM9 -S 115200 -vvv -Z" #5 Any program the can talk via serial port to a TS-2000 then opens COM10 at 115200 baud. #3 is needed if the other app can talk to hamlib #5 if the other cannot talk to hamlib rigctlcom acts as a TS-2000 emulator and then translates to the rig (FLRig in this case). Mike W9MDB On Sunday, July 19, 2020, 06:06:49 AM CDT, Martin Davies G0HDB <[email protected]> wrote: On 18 Jul 2020 at 21:51, Bill Somerville wrote: > Hi Martin, > > thanks for that information. Even if it does turn out to be the K9JM > CI-V router, that's useful information to have. Are you using it because > you have a PW-1? Morning Bill, no I don't have a PW-1 so you might wonder why I've got a K9JM CI-V router in my system...! Previously, when I had an IC-7600 (until last October), I tried using both the CI-V port and the USB port for CAT purposes from two different apps (typically WSJT-X and a logging app), although the virtual COM port provided via the USB connection was used solely to enable the logging app to read the frequency and other data back from the rig - there was no actual control of the rig via that route (although it was possible). However, when both the CI-V port and the USB port were connected to the PC being there were frequent CI-V data collisions, so I sought a solution that would enable the two apps on the PC to access the rig without the data collisions occurring - the K9JM CI-V router was that solution, over three years ago. In essence, the K9JM router has a USB connection to the PC and one of the router's CI-V ports is connected to the rig's CI-V port; another of the router's CI-V ports is 'looped back' to the PC via a CI-V-to-USB adaptor. The 'primary' USB connection from the PC to the CI-V router is defined as COM3 on the PC and is used by WSJT-X, and the USB connection from the looped-back CI-V port on the router is defined as COM2 and is used by whichever logging or other app I'm running concurrently with WSJT-X (examples are Logger32 and Win-EQF*). The router ensures that there are no data collisions between the data on the two separate COM ports. Although it might seem like an unconventional use of the K9JM CI-V router, the configuration works very well although it might not now be necessary to use the router - the IC-7610 that replaced my IC-7600 last October has the facility for 'uncoupling' the data on its CI-V and USB ports so there should no longer be any risk of data collisions when both ports are being used for CAT purposes. I haven't yet tried this... Depending on how the K9JM CI-V router's software works, it's conceivable that there's some round-robin polling of the router's CI-V ports that could be leading (or adding) to a delay between the CAT PTT commands being received from WSJT-X via the CI-V router's USB connection to the PC and the PTT commands actually being forwarded to the rig via the router's CI-V port. -- 73, Martin G0HDB -- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus _______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel _______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
