Orion Ssag Drivers For Mac
Download game bakugan battle brawlers ps3 cfw iso. Empty config file.Fatal Fury?Playable?None.Fate/Unlimited CodesNot AvailableNot AvailablePlayableFIFA 2001 Major League Soccer?Playable?FIFA Soccer 2002?Playable?FIFA Soccer 2007?Playable?FIFA Soccer 2012???SLES-55653 Untested.FIFA Street 2?Playable?Fight Night Round 3?Playable?None.Final Fantasy XPlayablePlayable?None.Final Fantasy X (Sep 28, 2001 prototype)?Playable?Essentially the NTSC retail release with the debugger enabled. Everything works as intended.Final Fantasy X-2PlayablePlayable?None.Final Fantasy XIIMinor IssuesMinor Issues?Confirmation sound has slight glitch. Some stuttering during gameplay.Final Fantasy XII (International Zodiac Job System)Not AvailableNot AvailableMinor IssuesConfirmation sound has slight glitch. ( )Fatal Frame III: The TormentedNot AvailablePS2 ClassicsNot AvailableOfficial PS2 Classic.
Windows 8.1 64 bit
Windows 8.1 32 bit
Windows 7 32 bit (ignoring 64bit)
and trawling google from end of the world to other
especially to with 64 bit drivers in particular with Orion products
win 8.1 64bit
It all started with the starshoot 5mp, which has ezcap software, which is not good enough. I wanted to use other packages with it. Big brick wall !!
So I resorted to ASCOM. I had already done the EQmod stuff. but not employed yet.
( PHD V2 worked perfectly with my SSAG ) win 8.1 64bit
I downloaded the ASCOM 6.1 platform and the ASCOMSSAG drivers etc
all went well till i tried SSAG with ASCOM and PHD V2 (brick wall )
did all the suggested things i found everywhere. Nup!
big long story in middle here not worth writing
I ended up borrowing a win7 32bit computer did all of above and shazzam all worked perfect.
Even had my SSAG working as normal camera under the SharpCap v2.5
oh it takes amazing pictures too. cant wait to try it out on live Telescope
It will work with any ASCOM enabled imaging software too
APT etc.........
I am real close to getting the 64 bit SSAG driver to work with ASCOM too.
The solution as it stands is in the System registry to sort it out
as the SSAG driver is 64bit enabled.
a bit of cut and splice I am sure will work, unless ORION actually just add the register the driver correctly in the wowsys64 system folder.
to be continued.......
i am busy ATM repairing at PCB level a SBIG STL11000 for someone else. It takes forever doing test images to see if repair is successful.
I've just bought an Orion Starshoot Autoguider for my Celestron CPC 925.
I use Mac OSX 10.8.x and PHD guiding.
The autoguider gives me a nice clean image and PHD can detect and lock on to a star with ease, in loop mode, even when I move the scope with the hand controller at centering speeds. So no problem with the camera.
PHD is talking to the mount and the 'manual controls' in PHD move the scope in the correct sense. So nothing wrong with the wiring or connection.
Here's the problem;
Any pulse sent to the mount from PHD via the Autoguider causes the mount to cease tracking, in that axis, for the next 20-25 seconds, allowing the star to drift away.
Guide commands from PHD should either speed up or retard the tracking motor momentarily to bring the star back to the cross hair. In PHD the maximum pulse length is predetermined in the advanced settings (default 1000 milliseconds). Normal sidereal rate tracking should immediately resume until the next pulse is sent after the next exposure eg. 2.0 seconds.
But in my set up, the tracking motor simply stops for 20-25 whole seconds after a pulse regardless of that pulse's direction (speeding up or slowing down the tracking motor). If PHD is in guide mode with expoure duration of 2 seconds, the scenario would be thus;
An exposure is taken. Say PHD determines the star has drifted West. A short (say 150ms) pulse is sent to speed up the RA tracking motor. RA tracking then stops arbitrarily. 2 seconds later another exposure is taken. This time (with no tracking in RA since the first pulse was sent) the star has drifted much further west. PHD then sends a maximum duration pulse West. The next exposure reveals the star to be way off the cross hairs and PHD subsequently gives up and sounds the error. I press Stop. Approximately 20-25 seconds later, tracking resumes normally.
Why is it stopping the tracking?
PHD does this even when it is not guiding. As soon as any pulse is sent to the tracking motor (via the PHD manual 'nudge' controls), all further tracking motion arbitrarily ceases for the next 20-25 seconds.
When guiding manually, using the Nexstar hand controller, guide pulses are superimposed on top of the tracking motion either speeding it up or slowing it down and sidereal tracking resumes immediately the buttons are released.
Either PHD is inhibiting the telescope's sidereal tracking or the Autoguider is. How do I trouble shoot it?
Nov 20, 2018 ORION SSAG DRIVER - I was having a hard time figuring out how to get this thing into focus. Sign up for a new account in our community. Customers also shopped for.