LX90 ASCOM slew error help please

[netwolf]

I am getting the following ASCOM error when trying to slew the telescope.

"The selected coordinates are below the current minimum elevation setting"

Same message in Starynight and CDC. But Telescope does connect. Also connects via hyperterminal and responds to Meade Commands. Also connected via CDC And Stellarium native telescope control and while they connect and show the telescope position, when you try to slew nothing happens.

Also tried Skysafari via the WifeScope (mainsequence software) relay on the laptop. While Skysafari shows the position can not get it to slew. The Wifiscope software shows ASCOM Nudge move is not enabled.

Can anyone help, i have tried searching on the net and found nothing in the usual places. The error is spoken of but cant find a solution.
The cable is home made and connected via a Serial USB adapter.

Thanks
Fahim

[AndrewJ]

Gday Fahim

Im assuming you are Polar???
The scope has settable min and max elevation limits.
These are relative to the scopes base, not the horizon, and are designed to prevent equipment clashes.
In AltAz, there is normally no problem, but in Polar, trying to goto objects that have a large positive DEC, ( even tho visible ) means the scope must slew to a large -ve "elevation"

Andrew

[netwolf]

Andrew no I am setup on Alt/Az, so where would I set limits for this?

I did see a max altitude setting but no minimum one.

[AndrewJ]

Gday Fahim

On rereading the error more closely, ( and doing a bit of digging ), it may actually be based on a limit you have set via the ASCOM driver, as that would also explain why all the apps report the same error.
If the exact wording of the error is correct, it is not from the scope, as that phrase does not appear anywhere in the firmware.
Looks more like an ASCOM driver setting.

Andrew

[netwolf]

Andrew yes it is in the ascom driver I found the error here in the following source file that describes all error constant values.
http://stash.teamserver.tigranetworks.co.u k/projects/ASCOM/repos/meade-lx200-classic-driver/browse/ErrorConstants.bas

I have tried setting the elevation setting in the ascom Meade driver to 0 and 190m but neither works. Still get same error.

Also even trying to slew to the object you are pointing at results in same error.

[AndrewJ]

Gday Fahim

Looking for that error message header in the source code for the driver shows it can only get called if the scope is set up as "Polar"???
That said, something really weird is happening in the code as the use of Polar in the code doesnt appear to reflect reality,
it appears to mean Astronomical vs Terrestrial.
I am currently confused :sadeyes:.
Can you check if your "Targets" setting in the hbx
is showing Astronomical or Terrestrial

Edit
Hmmmm, i think they stuffed up
The error message ID they are using to declare "target is below lower limit"
is actually sent from the scope if the target is above the upper limit.
Check what yr scopes Max Altitude is, and set to +90

Andrew

[netwolf]

Thx Andrew will check out the the Max Alt setting and the Targets setting.
When i did Cntrl-F command via a terminal connection the hbx replied with an "A" which is supposed to mean Alt/Az versus P for Polar. But I will check for this Targets setting you mentioned and see if that is different.

BTW do you know if there a way to power on the Autostar HBX without powering the mount.

[AndrewJ]

Gday Fahim



I suspect you are AltAz and Astronomical.
The 497 firmware responds differently to the LX200GPS firmware, and the ASCOM driver is written to suit the LX200.
Pretty sure it will be the Upper limit is less than +90



Yep. Just supply 12V via a correctly wired dummy RJ plug and it will start, ( which is what i do when reqd )
or buy a pre made adapter like
http://www.astrogene1000.com/products/497_flash/index.htm
and you can plug the std Hbx cable into the box

Audiostars will beep at you but pressing enter gets past that.
Once started, you can enquire on status etc, but just dont try to slew.

Andrew

[netwolf]

Thx Andrew set the max alt to 90 and looks like the problem maybe resolved. I need to do more testing, did not get much of a chance with clouds rolling in. Also the Target was set to Astronomical so pretty sure the max alt was the setting to fix it. It was set to 0, cant see why this would be the default.