PMC8_indi not working for south hemisphere

[nachoruiz29]

Basically the error that I saw is that the driver does not change the sign of the declination (conceptually the (+) sign is used for the northern hemisphere and the (-) sign for the southern hemisphere), in the Indi Drive of the PMC Eight it uses the (+) sign for the declination in the southern hemisphere, that generates a data reading error with the declinations with sign (-) in the southern hemisphere. That's why you can't put a signed latitude (-) (south latitude). If you put a north (+) latitude in your ASIAIR it will work correctly, but it clearly does not work to do that in the southern hemisphere.

[jfwells]

Odd, I have an iexos 100 and was suffering with incorrect gotos and tracking, until I checked the geography and it had me in the southern hemisphere. As a workaround, can you set the PMC8 mount location elsewhere -- i.e. in Windows or in ExploreStars and then set INDI not to update it?

[nachoruiz29]

no, because the issue is in the indi driver, it is not a problem of updating the latitude, but how it handles de declination (or at least that was my interpretation by reading the source code of the driver)

…

On Mon, Feb 6, 2023 at 8:24 PM John Wells ***@***.***> wrote: Odd, I have an iexos 100 and was suffering with incorrect gotos and tracking, until I checked the geography and it had me in the southern hemisphere. As a workaround, can you set the PMC8 mount location elsewhere -- i.e. in Windows or in ExploreStars and then set INDI not to update it? — Reply to this email directly, view it on GitHub <#1830 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAPPQ2TRX23MHWMJKUYSPITWWGB33ANCNFSM6AAAAAAUN2XIMY> . You are receiving this because you authored the thread.Message ID: ***@***.***>

-- Martin Ruiz

[knro]

Where in the code do you see this issue?

[nachoruiz29]

Karl, one of the main contributors for this driver is taking care of it. His is about to send the branch for compiling and testing. stay in the loop, a fix will come. El El mar, 7 de feb. de 2023 a la(s) 13:08, Jasem Mutlaq < ***@***.***> escribió:

I didn't check the code, do you have a solution for this? — Reply to this email directly, view it on GitHub <#1830 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAPPQ2UX6PY4PHS4Z7B7KTLWWJXO5ANCNFSM6AAAAAAUN2XIMY> . You are receiving this because you authored the thread.Message ID: ***@***.***>

-- Martin Ruiz

[knro]

It's fixed in #1856