ascominitiative / alpyca Goto Github PK

With the Omni Simulator running on my dev machine, discovery.search_ipv4() returns one server with an address of 127.0.0.1:32323, as expected.

Now if I start ASCOM Remote, hosting the COM Telescope Simulator on the same PC, in addition to the Omni simulator. I still get a single server response from search_ipv4(). This response is 127.0.0.1:11111, which is correct for ASCOM Remote.

I expected to see both 127.0.0.1:32323 and 127.0.0.1:11111 in the servers list from the search_ipv4 call when both the Omni Simulator and ASCOM Remote are active and serving drivers.

The Focuser StepSize is documented and hinted as an int, but it should be a float to be compatible with COM ASCOM.

Just looking around and noticed that the file EasySnippetTest.py is empty.

The DriveRates enum contains drivelunar, which should be driveLunar

The descriptions of pierWest and pierUnknown in the PierSide enum are swapped.

See this ASCOM Developer Help post by Tom Nathe. Remove the stray dot between import and alpaca as shown in the example here

This is the first release of Alpyca, so it is guaranteed to have 'issues'. This list is where you can file issues and suggest patches.

Please don't ask programming questions here. Instead post to the ASCOM Driver and Application Development Support Forum. Thanks.

When using ASCOM Remote to expose a filter wheel (Moravian EFW-3L) and connecting to it in Alpaca via filterwheel, changing the position appears to be a synchronous property and the corresponding PUT on the Alpaca API blocks for the duration of the filter movement.

I have no way of telling whether that's an Alpaca thing, an ASCOM Remote thing, or a Moravian ASCOM driver thing, but the end result is that if the wheel motion takes longer than 5 seconds, requests.exceptions.ReadTimeout is raised. I couldn't easily change that timeout value in the current version (2.0.4) because the timeout value (5 seconds) is not well exposed at the top level classes. It is there in the low level _get and _put methods at least (tmo keyword argument).

I ended up working around this by subclassing alpaca.filterwheel and making the changes locally, but it'd nice to have a better way to specify that timeout value for blocking filter movements rather than having to subclass an entire device! I also don't know if the Position setter blocking is a known/expected quirk or if it's device dependent.

DriverVersion has a type hint of 'str' but returns a float. This will raise an exception if the value from the driver cannot be coerced into a float.

The COM telescope simulator returns '6.6.0.0' as its DriverVersion. This is clearly incorrect, but other applications and APIs tolerate this.

I don't know who is correct, but the inconsistent behavior is frustrating.

It seems as though the Simulator needs to be corrected. Also, Conform needs to call out the illegal DriverVersion. I would suggest that Alpyca should not return a float, simply pass the driver's returned value through to the client, as DriverAccess does.

hello,

i have a Skywatcher AZ-EQ5 Pro and i use the USB serial interface to connect my mount with my pc.

when i send e. g. two commands:
self._telescope.PulseGuide(GuideDirections.guideNorth, 100)
self._telescope.PulseGuide(GuideDirections.guideEast, 100)

then it takes over 4 secs. to process them. my self written interface needs only a few ms to process it (same interfaces used: tcpip --> synscan --> usb --> mount).

so what's wrong?

When building docs for 2.0.4, I used poetry to update the dependencies for the package. After doing this the rinohtype PDF builder now crashes immediately. I have filed an issue
TypeError: Can't instantiate abstract class DynamicRinohDistribution with... #389

Hello,
all needed components are running, but i got no connection as before (few weeks ago):

/usr/bin/env /bin/python3 /home/.../.vscode/extensions/ms-python.python-2023.14.0/pythonFiles/lib/python/debugpy/adapter/../../debugpy/launcher 54369 -- /home/.../Dokumente/Sandbox/observatory/.../python/main.py
HTTPConnectionPool(host='192.168.0.200', port=11111): Max retries exceeded with url: /api/v1/telescope/0/connected (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f1fd8ac2170>: Failed to establish a new connection: [Errno 111] Verbindungsaufbau abgelehnt'))

Regards,
deppenkaiser

First off, thank you so much for your work on this library! It is MUCH MUCH better than writing all the puts and gets out for a telescope control system.

I have one question about the camera module. Has the Base64 handoff mode been implemented when getting image arrays? I'm using this library with the Remote Server, and I believe this would make a difference in my overheads.

Thank you!
-Carson

See (private) core group thread on Alpaca Parameter Casing. In Switch, change all parameters to use Id instead of Id. The documentation is already correct, this is just in the formation of query string parameters and PUT form field names.