Gemini-2: "Error converting from J2000 to Know..." 5.2.1.x


#1

Hey guys,

Not a problem when I was using 5.1.1.16… and is a problem now. I can’t get SGP to slew my scope. I’ve tried setting my driver to use either J2000 or Jnow but it just gives me the same response which is no slew.

Logs:

[10/2/2016 7:28:01 PM] [DEBUG] [CP Update Thread] Error in control panel UI updater: Object reference not

set to an instance of an object.
[10/2/2016 7:28:01 PM] [DEBUG] [Telescope Thread] Telescope: Slewing to J2000 RA: 24.009275 (24h00m33.39s)

Dec: 67.3849 (67°23’05.64")
[10/2/2016 7:28:01 PM] [DEBUG] [Telescope Thread] Telescope: Slew received J2000 coordinates, mount

requires JNOW, converting…
[10/2/2016 7:28:01 PM] [DEBUG] [Telescope Thread] ASCOM Telescope: Error in Slew : Error transforming J2000

to JNOW!
at SequenceGenerator.Astrometry.b(TelescopeInformation A_0)
at p0.jl(TelescopeInformation A_0)
[10/2/2016 7:28:01 PM] [DEBUG] [Telescope Thread] Slew complete…


#2

I think you are referring to SGPro with those version numbers, but I am not 100% certain (either SGPro or you are referring to the upgrade of some other dependent software on version 5?).

Anyhow, this is not an issue with the driver (or a new issue in the SGPro beta). It is an error being thrown from ASCOM utilities because the position for RA is illegal.

[10/2/2016 7:19:50 PM] [DEBUG] [Telescope Thread] Telescope: Slewing to J2000 RA: 24.009275 (24h00m33.39s) Dec: 67.3849 (67°23’05.64")

Where did that RA come from? Is it from the MFW?


#3

That’s weird. Because I downgraded to .17 and it’s working just fine.

Yes, the grid was generated by FMW.


#4

I did recreate the sequence when I downgraded but used the same target ‘area’.


#6

OK. well, I’d need to see the sequence with that illegal RA in it to pin down where it came from. Do you still have it?


#7

Yup, the one labeled NGC7762 is .17 and the one labeled 1805 (problem one) is from 2.2.

NGC7762

IC1805

Thanks,
Chris


#8

[10/2/2016 7:53:07 PM] [DEBUG] [PHD2 Listener Thread] PHD2 GetPhdStatus - Post-Wait: Stopped
[10/2/2016 7:53:58 PM] [DEBUG] [Main Thread] Slewing to target…
[10/2/2016 7:53:58 PM] [DEBUG] [Telescope Thread] Slew telescope message received…
[10/2/2016 7:53:59 PM] [DEBUG] [Slew Monitor] Waiting for slew to complete…
[10/2/2016 7:53:59 PM] [DEBUG] [Telescope Thread] Telescope: Slewing to J2000 RA: 23.97655 (23h58m35.58s)

Dec: 67.0724138888889 (67°04’20.69")
[10/2/2016 7:53:59 PM] [DEBUG] [Telescope Thread] Telescope: Calling Observatory Slave Slew
[10/2/2016 7:53:59 PM] [DEBUG] [CP Update Thread] Error in control panel UI updater: Object reference not

set to an instance of an object.
[10/2/2016 7:54:07 PM] [DEBUG] [PHD2 Listener Thread] PHD2 - No messages received from PHD2 for 1 minute,

checking socket with status…
[10/2/2016 7:54:07 PM] [DEBUG] [PHD2 Listener Thread] Checking PHD2 state…
[10/2/2016 7:54:07 PM] [DEBUG] [PHD2 Listener Thread] PHD2 GetPhdStatus - Pre-Wait : Stopped
[10/2/2016 7:54:07 PM] [DEBUG] [PHD2 Listener Thread] Sending to PHD2:
{“method”: “get_app_state”, “id”:

1001}

[10/2/2016 7:54:07 PM] [DEBUG] [PHD2 Listener Thread] PHD2 GetPhdStatus - Post-Wait: Stopped
[10/2/2016 7:54:23 PM] [DEBUG] [Telescope Thread] Scope reports it is done with synchronous slew,

verifying…
[10/2/2016 7:54:23 PM] [DEBUG] [Telescope Thread] Telescope: Observatory is reporting slewing
[10/2/2016 7:54:24 PM] [DEBUG] [Telescope Thread] Telescope: Slewing has completed
[10/2/2016 7:54:24 PM] [DEBUG] [Telescope Thread] Telescope: Settling for 30 seconds
[10/2/2016 7:54:54 PM] [DEBUG] [Telescope Thread] Telescope: Settling has completed
[10/2/2016 7:54:54 PM] [DEBUG] [Telescope Thread] Slew complete…

Snippet from the .17 log file showing no issues… I’ll attach it for fun.


#9

@mads0100

The 2.5.1.17 version is not really “good”, it’s just in a different order. The next target would fail in either version (uncheck NGC7762-1 and you’ll be able to see this). They both have illegal RA, just in different orders. I’ll see what is allowing MFW to do this.


#10

Can I hand type the RA somehow to make it work?


#11

Sure… just subtract 24 from it. I have found a few spots in the code that could allow this to happen and they have been fixed in 2.5.2.3


#12

Haha… I’m an idiot… Thanks :).


www.mainsequencesoftware.com