Seestar alpaca_v1.1.2-1 And Secondary development demo

Support@Seestar

Official Release Changelog

Added support for the S30Pro wide-angle camera in the Camera module; device scanning in NINA now distinguishes between telephoto and wide-angle cameras.
Added support for the S30Pro wide-angle focuser in the Focuser module; device scanning in NINA now distinguishes between telephoto and wide-angle focusers.
Added PulseGuide and IsPulseGuiding implementations to the Telescope module to support Dither in NINA.
Added Park and Unpark implementations to the Telescope module.
Added dew heater switch control to the Switch module, with control available through both NINA and the Switch web UI.
Added device SSID to the device list shown during scanning in NINA.
Guide Rate can now be modified in the Telescope module’s web UI; this affects PulseGuide speed and the Dither duration calculation in NINA.
Improved the Telescope module’s web UI: LocalDateTime can now be set and saved independently.
The Telescope module's SiteElevation property now throws an exception to indicate that it is not supported.
Various internal logic optimizations.
Miscellaneous bug fixes.

Support@Seestar

Seestar Alpaca Secondary development demo v0.1
ReleaseLog:
Note! Features not supported in this demo do not imply lack of support in the Seestar Alpaca driver; updates will be released continuously.
This demo is intended for secondary development reference only!

Overall

Supports scanning and connecting to Camera, Focuser, Filter Wheel, and Telescope.
Supports displaying connection status and parameter information for Camera, Focuser, Filter Wheel, and Telescope.

Camera

Supports Gain and Exposure settings.
Supports StartExposure and image display.

Focuser

Supports Target position move.

Filter Wheel

Supports Position Change (Dark, IR, LP).

Telescope

Supports manual move.
Supports Home.
Supports setting tracking rate.
Supports setting manual move rates for primary and secondary axes.
Supports RA DEC Slew.
Supports Alt Az Slew.

seestar-alpaca-demo-v0.1.zip

2MB

Demo video:
https://drive.google.com/file/d/1XHGjMZulFld5ZOq4z5Dx8wJgeHJTmpYE/view?usp=sharing

paulitoweb

Support@Seestar when could have alpaca support on ASIAIR?
Best regards,
Paolo

Software@ZWO

paulitoweb
Hi, Paolo.
I'd like to ask why you need ASIAir's Alpaca.
Best regards,
Travis

paulitoweb

paulitoweb for example to integrate other device to the ASIAIR rig like motorized flat panel or the dom.
Regards,
Paolo

KatNRick

And where might this be found. The video only gives format not supported errors.

Support@Seestar

KatNRick Could you please let me know which video player you are using? I uploaded the video to Google Drive, and it should play normally on a computer.

tom-dd132

I would like to suggest a small Alpaca extension for Seestar to allow uploading observing plans via the standard ASCOM Alpaca Action() mechanism.

For example, the Seestar Alpaca telescope device could expose the following custom actions in SupportedActions:
UploadSeestarPlan
ListSeestarPlans
DeleteSeestarPlan

UploadSeestarPlan would take a single JSON string parameter containing the complete plan (similar to what the mobile app sends today).
This approach keeps the interface fully compatible with ASCOM Alpaca, while making it easy for third-party tools (Python, C#, etc.) to upload complex Seestar plans in a structured way.

Software@ZWO

tom-dd132
Thank you for your suggestion, we will consider it.

Lilo

paulitoweb
))) impossible. The rules are clear if u use ASIAIR you must buy zwo hardware then.

Software@ZWO

paulitoweb
The Wireless Smart Camera (Air camera) currently supports Alpaca and can use camera modules (via software such as NINA and phd2), but there are no plans to support the flat panel and the Dome at the moment.
Regards,
Travis

curtismacc

While the latest update provides some much appreciated additional features when using NINA, Sharpcap, etc. there are still a few things that could help to improve the overall user experience with these 3rd party SWs.

First, as noted in the release information at the top of this thread, the telescope's site elevation is not supported which means that NINA will show a dialogue box noting the difference in site elevation between what's in NINA (the actual site elevation) and what is in Seestar (0m). That dialogue box has to be answered for NINA to proceed. This prevents automatic startup when not present at the computer.

Also, as far as I can tell, for NINA to successfully get the Seestar to open the arm and GoTo and object one still has to be connected to the Seestar with the App. This can easily hinder automatic startup when not in range of the home internet when in Station Mode. Just let NINA talk to and control the Seestar without need for the App to connect.

Regards,
Curtis

Software@ZWO

curtismacc
Thank you for your feedback.

Regarding site elevation synchronization between NINA and Alpaca, you can set the site elevation to 0 in NINA. This will prevent the synchronization dialog box from popping up when connecting to the Mount due to differences in site elevation.

As for your second point, I don't understand your meaning. Why is it still necessary to connect to Seetar through the application? NINA can directly control Seetar. Please provide more information.

Regards,
Travis

curtismacc

Software@ZWO Travis,
Yes, we can set the site elevation to 0m but it would be best if the Seestar could sync the correct elevation.

I will try to make my second point more clear. When running a Sequence in NINA (or Sharpcap as well), the Seestar will not slew to a target as commanded by the sequence if the Seestar App on a phone or tablet is not first connected to the Seestar. Nothing has to be done in the App other than connecting to the Seestar. Only then, can NINA Unpark and Slew the mount to a target. If the App is not connected, the Seestar will not slew to the target. The ARM will remain in the closed position and no motion of the telescope will occur. The remaining instructions in NINA's sequence, such as changing the filter, imaging, etc. will occur as they should, but the Seestar will still be in the ARM closed position. But, when the App is connected to the Seestar first and then NINA is connected, it's sequence can move the telescope. Interestingly, the App can be closed once NINA Unparks and moves the ARM and the rest of NINA's sequence will execute without any problem. Here is another way to say this.

Case #1

Seestar App is not connected to the Seestar, but the Seestar power is ON.
NINA can connect to the Seestar (camera, telescope, filter wheel, etc.)
NINA can manually open the Seestar ARM by using the N/S/E/W buttons on the Telescope page of NINA, but
A Sequence in NINA cannot move the Seestar ARM with a Slew instruction unless the ARM is first opened manually in NINA. In other words, NINA cannot operate the Seestar fully automatically.

Case #2

Seestar App is connected to the Seestar but no further action is taken, i.e. the ARM is still closed.
NINA can connect to the Seestar
A sequence in NINA can Unpark and move the ARM with a Slew instruction to a target object
The Seestar App can be closed and NINA will continue to be able to instruct the Seestar to follow commands including Park and Disconnect when finished.

I have tested this repeatedly and have pointed this out in my NINA with Seestar YouTube videos so others don't get stuck. I think the team should do their own test and then figure out how to remove this limitation because with it fully autonomous operation of the Seestar with software like NINA or Sharpcap is still not possible. One has to be there and connect the APP before NINA tries to move the ARM.

Best Regards,
Curtis

paulitoweb

Software@ZWO yes I know because I own an Asi585air so I thought it was easy to port the alpaca support also on ASIAIR.
Thank anyway, regards,
Paolo

Software@ZWO

paulitoweb
I understand now. You mean to make the ASIAir box support Alpaca as well, but unfortunately, there are no plans to do so at the moment.
Regards,
Travis

Software@ZWO

curtismacc
Hi, Curtis
Thank you for your feedback. I think I understand what you mean, and I will conduct the test.
Regards,
Travis

Software@ZWO

curtismacc
By the way, Seestar firmware doesn't remember altitude, but Alpaca can if needed, via a configuration file. So I'll consider adding it.
Thank you again for your feedback.
Regards,
Travis

Software@ZWO

curtismacc
I just tested the issue you mentioned. Since I wasn't in the office, I tested it remotely using the company computer. I used a command to restart the device, without using the physical buttons. After the Seestar restarted, I connected directly to the Seestar telescope via NINA, without using the app (which is impossible since I wasn't on-site), and was able to directly point it at the target's right ascension and declination. Therefore, it would be best if you could provide some test videos for me to analyze the problem. Of course, I'll restart Seestar using the physical button to test it once I get to the office. If there are no problems, I'll record a video and post it here. By the way, what version of Alpaca are you using? Is it 1.1.2-1?
Regards,
Travis