I've never been able to communicate with my first generation star adventurer. Has anybody else had success with it, or is it only compatible with the WiFi version?
Perhaps I am missing something on my setup to use the USB serial interface.
INDI/KStars on Raspberry Pi 4, 4gb
Raspbian Buster with AstroPi3 script configuration
Skywatcher HEQ5 Pro Mount
Canon 600D Camera
Orion SSAG/ASI120mm @280mm Guide Scope
Waveshare Stepper Motor Board - DIY Focuser
Adafruit GPS Module
Generic Bluetooth Joystick.
Startech 7 port powered USB Hub.
Forgot to say I was using the 2i wifi version. I can't be sure but it could be something was added to the firmware of the 2i to allow the app to control it and therefor allow EQMOD to actually communicate.
Thank you for your information. I think I have the similar setup with you.
May I ask for your suggestion to solve my problem?
I configured my devices as below.
- Controller: StellarMate OS on RPi4B
- Device: SA 2i mount + SV305 guide CCD
(1) SA 2i - StellarMate: USB-to-RJ12 cable
(2) SV305 - StellarMate: USB cable (SV305 doesn't have ST-4 interface)
At the point, I tried to start tracking on my SA 2i (STAR sign mode), but it didn't move.
INDI drivers for SA 2i and SV305 seems fine and there's no error message on connections.
What should I need to check?
There was some recent commits to the INDI 3rd party github that appear to allow for both usb and wifi connections to the 2i, not sure if that has made it into StellarMate yet.
Here is what I have :
Raspberry Pi4 with StellarMate OS
SA 2i connected via USB-A to mini USB-B ( not into the ST4 jack )
ASI120mm mini connected via USB-A to USB-C
I then use the EQMOD driver with a baud rate of 115200 . Guide commands are sent via the EQMOD driver. I can guide, dither, do RA GoTos, manually move the mount in RA, and also Park and unpark the mount ( return to vertical position ). I did have some issues with plate solving because the mount returns a DEC of 0.0 always, and this confuses some aspects of EKOS.
You cannot use the SA specific profile that derives from the AltAz base profile, this does not work.
There, however, should now ( or soon ) be two new StarAdventurer specific profiles included with the EQMOD driver that are called USB and WIFI that preset the baud rate and set up the wifi connection, and those are probably preferred going forward.
Here I am with my first post. I recently bought a Raspi 4 and installed Astroberry on it. Took me some time to get it running with Star Adventurer 2i, Zwo Asi 120mm mini Camera and Svbony 165 Guidescope, as well as 2 Canon DSLR.
I first set up a profile with Zwo, Canon DSLR Driver and Simulator for the Mount. Now I tested the Star Adventurer 2i USB Driver and it works. I don't get to work the Star Adventurer 2i WiFi Driver. On which position do I have to set the wheel on star adventurer? Sidereal oder App? I set the Wifi Settings of the mount to my home network in App mode. Astroberry is also connecting to my home network. Is that the right setup? Any other hints?
Thanks in advance for any help.
The new StarAdventurer Wifi profile works fine even for my StarAdventurer Mini. So first of all, many thanks for that. This might really improve my portable setup.
However, I am struggeling with the alignment/polar alignment module, as I can not manually set the RA or DEC (DEC is always 0.0) position of the mount. This confuses EKOS and plate solving always fails.
I know radon199 mentioned the same problem and it would be great to know if someone already figured out how this can be solved or handled.
Figured out how to manually set the Telescope Coordinates:
1) Set "Main Control > On Set = Sync" and "Sync > Sync. Mode = Standard Sync" in the INDI Control Panel
2) Set the Current Coordinates in the Mount Control and Sync (Tracking must be turned on) in EKOS
Still need to figure out if this solves the platesolving issues tonight.