Closed Paolo97Gll closed 1 year ago
Stupid typo :( Hopefully fixed here 4e5a14c13411251a5b8c6319464c6aa22c32d4e5, but not tested yet...
I can test it in the next days, I will let you know if it works
I confirm that it works as expected and results are consistent with the ones reported in the indigo server, thanks!
👍
@polakovic Just a quickie... in case your typo was case-related, the newest release of Conform Universal has strict casing, runs native on Linux, Mac, and will catch this sort of thing because it speaks native Alpaca (not like the obsolete Windows Conform that runs through the Chooser Dynamic Drivers). So you can test right on your Linux system. It also has an Alpaca protocol checker that looks for botches in the protocol, HTTP status values for various errors, Transaction IDs, and error reporting. This conform will be the standard going forward. Excellent unit test tool.
No, it was not case related. It was misplaced } :)
I'm using a SynScan EQ-8 mount with the
mount_synscan
driver. The indigo driver exposes the mount side of pier and I can see it from the control panel and ain imager. However, the corresponding alpaca request return "Property or method not implemented".Here an example taken from my server:
Request:
Response:
I think that the expected behaviour, given the official description in this section of the ASCOM Alpaca Device API, should be to report the current side of pier since this method is implemented in indigo (it's a read-only permission, so a get request it's ok).