Jeff, I have the same setup without the issues except that satpc32 needs to be started last which makes sense because otherwise it will complain about com ports not there.
I'm wondering if you have ever watched the com ports carefully, windows loves to move things around so when you turn on the 9100 first is it grabbing the usual lvb port? so the lvb gets what was the 9100 port? so instead of a simple w035 090 command the lvb is seeing $FEFE7CE01A05005603FD$FEFE7CE01C0001FD\w10 or some other string of 9100 setup/frequency command from satpc32 and all that crud blows it's mind requiring you to reset the LVB?
Just a thought...
73 Kevin WA6FWF
On 3/31/2015 2:57 PM, [email protected] wrote:
Does anyone have this issue,
I have to turn my sat system on in a certain sequence.
Turn on the LVBTracker.Turn on the 9100.Start SatPC32.Today I had a visitor in my shack who turned the Yaesu 5500 on first causing the LVB issue, so don't just say 'don't do that' J.
If I turn on the 9100 before the LVBTracker I get a memory error on the LVBTracker and have to do a re-calibrate, a real pain if you're trying to work a bird that's already up. If I run SatPC32 before I turn on the radio I get a SatPC32 error that could be a little easier to resolve then it is. I would like to see a de-select, select sequence of the cat control to acquire the radio instead of a SatPC32 reboot, sometimes with a task manager assist in Win7 to halt the rotor
serverSDX. I have no idea what would cause the LVB to behave in this manner. Anyone have the LVB issue? Any solutions?
73 Jeff kb2m
Sent via [email protected]. AMSAT-NA makes this open forum available to all interested persons worldwide without requiring membership. Opinions expressed are solely those of the author, and do not reflect the official views of AMSAT-NA. Not an AMSAT-NA member? Join now to support the amateur satellite program! Subscription settings: http://amsat.org/mailman/listinfo/amsat-bb