rkaczorek / astroberry-diy Goto Github PK

Hi,
Is it possible to disable the automatic standby mode, to prevent the focuser from slipping?
Thanks a lot for the great job!

What would it take to add support for a second A4988? My thought would be to use it to control a filter wheel.

This would be nice to have CPU temp on board :)

Relative and absolute positions are set at 0 upon startup. Many programs can not go to negative positions so it is not possible to move in both directions after startup

I've just configured the Astroberry Relays for the ASIAir Pro DC Hub and the On/Off toggle switches seem to be opposite to what it is. i.e. On switches off the port, Off switches on the port.

For now I switched the following and recompiled and it seems to reflect correctly that Off is now switching off the DC port, and On is switching on the DC port :-

gpiod_line_set_value(gpio_relayX, 1);
gpiod_line_set_value(gpio_relayX, 0);

Hi,
I would like to use the astroberry_focuser driver with A4988 motor driver on my RPi4, which I already use with kstars/ekos to drive my telescope and cameras. The RPi4 has Ubuntu 20.04 OS.
I tried to follow the instructions in the readme file to compile your driver but I had to register to Gihub to access to astroberry-dyi through <git clone https://github.com/rkaczorek/astroberry-diy.git> (it asks username and password) and once this done, the access was still not permitted because it has new dongle access.
I am a real beginner in using github software and installing it on my RPi4.

How can I add the astroberry_focuser driver running on Ubuntu 20.04 to my indi library ?
Thanks for the support,
Best regards,
Pierre Cevey

If I set some parameters in Astroberry Focuser in INDI Control Panel like the Resolution to 1/32 step then in Options panel I hit Configuration > Save, the next time I start this profile I get the settings I’ve saved.
If for the same profile I set Joystick > Enable and set custom buttons bindings in Joystick panel then I hit Configuration > Save the Joystick related settings are losed so I have to manually set it when I start KStars.

If I make the same procedure using Focuser Simulator instead of Astroberry Focuser, the Joystick settings are saved.

Is it possible to use this board which has only STEP DIR and EN inputs ?
https://www.ebay.com/itm/42-CH-Stepper-Motor-Driver-Expansion-Board-DRV8825-A4988-for-3D-Printer-UNO-R3-/132540586828

Hi,

it would be awesome if you could add support for a different stepper board for focusing as well.
https://arduino-info.wikispaces.com/SmallSteppers
Currently the only way to use those boards seems to be https://github.com/fehlfarbe/arduino-motorfocus

Thanks
Karsten

I am using Astroberry Focuser as a helicoidal focuser for my camera lens.
Max travel of the helicoid is only 117mm and I want to specify 390step for max. position.
The minimum value of max. position is 1000 steps, so I can't set 390.
Therefore I would like to change the position from 1000 steps to 100 steps.

The configuration of the lens and stepper motor is as shown in the attached image.

The stepper motor has 200 steps per revolution and the gears have 60mm per revolution.
The helicoid travel distance of the lens is 117mm, so the max. position is 390step.

To be honest, I have already changed the default value to 100 in my local environment, is it possible to change the original source code as well?

Consider changing approach for calculation of CFZ:

• from CFZ = 4.88 · λ · f^2 (http://www.goldastro.com/goldfocus/cfz.php)
• to NCFZ = 0.00225 · θFWHM · √τ · A · f^2 (http://www.goldastro.com/goldfocus/ncfz.php)

Hi,
I need help for astroberry-diy please.
I am using KStars/ekos on my Raspberry PI4, running with Ubuntu 20.04 without problem (connected to telescope, mount, camera, guiding camera).
I tried to install astroberry-diy (V2.9), mainly for astroberry-focuser, using your instructions. After connecting all pins to a step motor driver (Big Easy Driver from Sparkfun, with A4988 IC), it is visible on Indi control panel, with 3 tabs (Otions, Main control, General Infos), but I get an error at connexion : Problem initiating Astroberry Focuser.
I am not a computer specialist, therefore I send you print screens of the compilation and installation process for diagnostic : can you tell me if I can compile and use astroberry-diy with Ubuntu 20.04 and if there are special configuration to accomplish to have it work?
Thanks a lot!
astroberry_diy_compil_term_printscreen.odt

hello.

I would like to use to run your indi driver on my nanopi-m4.
There is a library wriringpi that works pretty well.
Unfortunately I have no gpio accessible via wiring pi on the pins 29, 31, 33 and 35 (the pins of the part relay)

On the other hand I have pins 8, 10, 12, 22 and 26 which are accessible (with numbers 15, 16, 1, 6 and 11 on wiring pi).

Hello.
Astroberry Focuser is great tool for me. It has been an indispensable tool for my astronomical observations.

Now, I have a request for Astroberry Focuser.
Could you possible to make the connection to the motor wireless ?
Perhaps this can be achieved by supporting remote GPIO. Remote GPIO can be supported by pigpio.

For example, you can install a Stepper motor and handler HAT in a Raspberry PI Zero W, and install an Astroberry Focuser Driver rewritten in pigpio in a Raspberry PI 4.
The Raspberry PI Zero W should be connected to the Raspberry PI 4 via Wi-Fi or Bluetooth PAN.
Controlling the focusing module with Ekos on Raspberry PI 4 would allow the Stepper motor on Raspberry PI Zero W to work.

Thanks

Hi,

I have this error when compiling.

INDI 1.7.4

[ 66%] Built target libbcm2835
[ 75%] Building CXX object CMakeFiles/indi_rpifocus.dir/rpi_focus.o
/home/pi/astroberry-diy/rpi_focus.cpp: In constructor ‘FocusRpi::FocusRpi()’:
/home/pi/astroberry-diy/rpi_focus.cpp:139:66: error: ‘FOCUSER_CAN_REVERSE’ was not declared in this scope
FI::SetCapability(FOCUSER_CAN_ABS_MOVE | FOCUSER_CAN_REL_MOVE | FOCUSER_CAN_REVERSE); // | FOCUSER_CAN_ABORT);
^~~~~~~~~~~~~~~~~~~
/home/pi/astroberry-diy/rpi_focus.cpp: In member function ‘virtual bool FocusRpi::initProperties()’:
/home/pi/astroberry-diy/rpi_focus.cpp:264:2: error: ‘FocusMaxPosN’ was not declared in this scope
FocusMaxPosN[0].min = 1000;
^~~~~~~~~~~~
/home/pi/astroberry-diy/rpi_focus.cpp: In member function ‘virtual bool FocusRpi::ISNewNumber(const char*, const char*, double*, char**, int)’:
/home/pi/astroberry-diy/rpi_focus.cpp:377:4: error: ‘FocusMaxPosN’ was not declared in this scope
FocusMaxPosN[0].min = (int) FocusMaxPosN[0].min * resolution / last_resolution;
^~~~~~~~~~~~
/home/pi/astroberry-diy/rpi_focus.cpp:381:17: error: ‘FocusMaxPosNP’ was not declared in this scope
IDSetNumber(&FocusMaxPosNP, nullptr);
^~~~~~~~~~~~~
/home/pi/astroberry-diy/rpi_focus.cpp:403:19: error: ‘FocusReverseSP’ was not declared in this scope
deleteProperty(FocusReverseSP.name);
^~~~~~~~~~~~~~
/home/pi/astroberry-diy/rpi_focus.cpp: In member function ‘virtual bool FocusRpi::saveConfigItems(FILE*)’:
/home/pi/astroberry-diy/rpi_focus.cpp:523:29: error: ‘FocusMaxPosNP’ was not declared in this scope
IUSaveConfigNumber(fp, &FocusMaxPosNP);
^~~~~~~~~~~~~
/home/pi/astroberry-diy/rpi_focus.cpp:525:29: error: ‘FocusReverseSP’ was not declared in this scope
IUSaveConfigSwitch(fp, &FocusReverseSP);
^~~~~~~~~~~~~~
/home/pi/astroberry-diy/rpi_focus.cpp: In member function ‘virtual IPState FocusRpi::MoveAbsFocuser(int)’:
/home/pi/astroberry-diy/rpi_focus.cpp:606:6: error: ‘FocusReverseS’ was not declared in this scope
if (FocusReverseS[REVERSED_ENABLED].s == ISS_ON) {
^~~~~~~~~~~~~
/home/pi/astroberry-diy/rpi_focus.cpp:606:20: error: ‘REVERSED_ENABLED’ was not declared in this scope
if (FocusReverseS[REVERSED_ENABLED].s == ISS_ON) {
^~~~~~~~~~~~~~~~
CMakeFiles/indi_rpifocus.dir/build.make:62: recipe for target 'CMakeFiles/indi_rpifocus.dir/rpi_focus.o' failed
make[2]: *** [CMakeFiles/indi_rpifocus.dir/rpi_focus.o] Error 1
CMakeFiles/Makefile2:104: recipe for target 'CMakeFiles/indi_rpifocus.dir/all' failed
make[1]: *** [CMakeFiles/indi_rpifocus.dir/all] Error 2
Makefile:127: recipe for target 'all' failed
make: *** [all] Error 2

During testing i found a small coding error in rpi_focus.cpp.

In line 691 and 692 you set twice pinMode(M2, OUTPUT);, but one should be pinMode(M3, OUTPUT);.

Hello,

does this work with driver ULN2003?
If not can you implement this?

best regards Jan

I need help in implementing AbortFocuser() function in the driver.
I'm missing basic concept how it should be handled according to INDI API.

Current Astroberry focuser cannot work on Raspberry PI 5.
To use the same GIPO numbers as before, gpiochip4 should be used.

I have created code to get the model name from /sys/firmware/devicetree/base/model and use the appropriate gpiochip number.
Could you merge the attached patch?

diff.patch

Or should I submit a Pull Request?

https://indilib.org/forum/astroberry/11133-astroberry-relays.html#79695

When building with indi 1.9.8 environment, the following warning is displayed where a deprecated member function of class DefaultDevice is used in a derived class.

 warning: 'void INDI::DefaultDevice::<function name>(ISwitchVectorProperty*)' is deprecated [-Wdeprecated-declarations].

Would you please modify it for the indi 1.9.8 environment?

It would be nice to have it supported, as it looks like natural Astroberry companion :). This board is quite cheap (compared to other hats) and should support big range of motors.

Will the Driver DRV8825 also work for this?
I am looking forward to buy this article and want to be sure, that the Driver will also work.
Ebay Product with Driver incuded

I, thanks for your job but its possible to add support for servo-motor ?
Today, my focuser is a sg90 servo connected in gpio17 on my rpi. Its possible to use astroberry-diy for control my focuser with ekos ?

Dear Radek!
First of all, I'd like to say a great thanks for your work on Astroberry Server and Astroberry DIY.
I have an RPI 3 model B+ with Raspbian, and I wanted to install the Astroberry focuser with cmake, following the installation instructions, but I always got this error message:

Scanning dependencies of target indi_rpifocus
[ 93%] Building CXX object CMakeFiles/indi_rpifocus.dir/rpi_focus.o
/home/pi/astroberry-diy/rpi_focus.cpp: In member function :
/home/pi/astroberry-diy/rpi_focus.cpp:212:73: error: was not declared in this scope
SetFocuserCapability(FOCUSER_CAN_ABS_MOVE | FOCUSER_CAN_REL_MOVE);
^
CMakeFiles/indi_rpifocus.dir/build.make:62: recipe for target 'CMakeFiles/indi_rpifocus.dir/rpi_focus.o' failed
make[2]: *** [CMakeFiles/indi_rpifocus.dir/rpi_focus.o] Error 1
CMakeFiles/Makefile2:215: recipe for target 'CMakeFiles/indi_rpifocus.dir/all' failed
make[1]: *** [CMakeFiles/indi_rpifocus.dir/all] Error 2
Makefile:127: recipe for target 'all' failed
make: *** [all] Error 2

Earlier the Astroberry Focuser worked perfectly in Kstars installed on my RPI2 with Ubuntu Mate, but unfortunately the SD card injured, and the whole setup destroyed. I don't remember, how I installed the working focuser driver, but when I tried to compile the driver, I got the same error message.
Please help me to solve this problem! (I am a really-really end-user :-) ).

Thanks in advance
Gabor

Could you please implement the ability to save and load different settings into different named settings files?

I am using two different focusers on one Astroberry DIY focuser. Only one of the two focusers can be connected at a time.

The Astroberry Focuser requires different settings for each focuser. This is because the specifications for Reverse motion, Max. Position, Max. Travel, etc. of the two focusers are different.

I believe that if the Astroberry Focuser can handle multiple configuration files, it will greatly simplify and improve the convenience of the settings for me.

https://indilib.org/forum/astroberry/11133-astroberry-relays.html#79695

If I connect a Joystick or gamepad, I can see 3 buttons to focus in, focus out and abort focus

What about adding the ability to use the analog axis of joystick to control the focus speed?

Axis close to 0 = abort focusing
Axis between minimum and maximum , a ramp related to relative minimum and maximum speed set.

If standby is enabled and a a move command is given and then a new move command is given within the timer window, standby from the first command will still be activated, possibly preventing the correct execution of later commands.

To reproduce-
Enable standby and set time to 60s.
Execute a step command.
Execute a second command after 50s

expected result - the motor should not go into standby until 60s after the second command
actual result - the motor goes into standby 60s after the first command and will try to go into standby again 60s after the 2nd, and this can disrupt a move in process at these times.

Thanks for producing this useful piece of software,

Keith