Mark, Gpredict should be blissfully unaware of the com port numbers. It talks to hamlib via TCP/IP. The com ports should live only in the hamlib world.
Perhaps this weekend is time for a howto. My guess is it reads as follows. Install cygwin. Download, compile, and install hamlib. Test hamlib with you equipment. Tell gpredict how to find hamlib. Charles On Mar 18, 2011 1:16 PM, "Mark L. Hammond" <marklhamm...@gmail.com> wrote: > Alex, > > Thanks for the reply. > > By golly, you are right about the program not being there. I never > made it that far, since I was trying to use just the direct connection > to the hardware first. > > Well, shucks--we need to get Gpredict working on Windows hardware :) > > I'll dig deeper on the high com port part before I give up... > > 73, > > Mark N8MH > > On Fri, Mar 18, 2011 at 12:13 PM, Alexandru Csete <oz9...@gmail.com> wrote: >> Hi Mark, >> >> I have not used hamlib in a long time since I now have others to test >> rig interfaces in gpredict. When I used it few years ago on windows it >> worked well with high COM-port values. I always used USB to serial >> converters, which get high values. >> >> I would suggest you try the hamlib mailing list since this is where >> hamlib users and developers hang out: >> https://lists.sourceforge.net/lists/listinfo/hamlib-developer >> >> When you start rigtcl, you can try to pass the option -vvvvvv which >> will enable debug messages. This may reveal what is wrong. >> >> Otherwise, I have to say that I am puzzled by the fact that some >> people use Gpredict on windows to control radios. I didn't know it was >> possible because the hamlib network daemon (which is required by >> gpredict) is not available in the windows packages - at least I have >> never seen it. >> >> 73 >> Alex OZ9AEC >> >> On Fri, Mar 18, 2011 at 1:43 PM, Mark L. Hammond <marklhamm...@gmail.com> wrote: >>> To those who might know--- >>> >>> Does hamlib for Windows support more than just COM1 and COM2 for >>> hardware (radios, trackboxes)? If so, what is the syntax? >>> >>> I've tried the obvious permutations based on the command line help and >>> online help I could find...but it isn't working on COM5. It just >>> "hangs" with no errors and it's obviously not working either. I am >>> aware of the baud rate command line option, but that's not it...from >>> what I've read it gives the impression (but isn't clearly stated) that >>> it might not support above COM2. Surely that can be fixed (heh...not >>> by me!) >>> >>> Gpredict for Windows is very nice and a super program, but if I can't >>> use ports higher than COM2 because of hamlib, it's use in my shack is >>> very limited... >>> >>> 73, >>> -- >>> Mark L. Hammond [N8MH] >>> _______________________________________________ >>> Sent via AMSAT-BB@amsat.org. Opinions expressed are those of the author. >>> Not an AMSAT-NA member? Join now to support the amateur satellite program! >>> Subscription settings: http://amsat.org/mailman/listinfo/amsat-bb >>> >> >> _______________________________________________ >> Sent via AMSAT-BB@amsat.org. Opinions expressed are those of the author. >> Not an AMSAT-NA member? Join now to support the amateur satellite program! >> Subscription settings: http://amsat.org/mailman/listinfo/amsat-bb >> > > > > -- > Mark L. Hammond [N8MH] > > _______________________________________________ > Sent via AMSAT-BB@amsat.org. Opinions expressed are those of the author. > Not an AMSAT-NA member? Join now to support the amateur satellite program! > Subscription settings: http://amsat.org/mailman/listinfo/amsat-bb _______________________________________________ Sent via AMSAT-BB@amsat.org. Opinions expressed are those of the author. Not an AMSAT-NA member? Join now to support the amateur satellite program! Subscription settings: http://amsat.org/mailman/listinfo/amsat-bb
