Jump to content

NLCbanner2024.jpg.2478be509670e60c2d6efd04834b8b47.jpg

Gina

Beyond the Event Horizon
  • Posts

    45,326
  • Joined

  • Last visited

  • Days Won

    120

Everything posted by Gina

  1. I'm onto it... Writing my own driver (or maybe driving GPIOs?) Driving GPIOs from INDI. There is also a driver for the Arduino as an alternative approach - indi_duino.
  2. As reported in another thread, I have the remote connection working I tried remote connection to INDI server from my Linux Mint laptop running KStars/Ekos and after reading the Ekos setup page again, set the connection parameters as Remote and 192.168.1.77 (the IP address of the RPi) with port as already set, which was correct. Then clicked Connect and selected the ASI camera driver from the list. AND... after further setting up, Ekos reported connection to ZWO CCD ASI178MM - the correct camera. Set a few more things and up popped a window containing the image from my all sky camera Another stage of the process achieved and I can go to bed happy Now I just need to get remote focussing working plus a few settings in Ekos for saving images to HD and I will have a workable RPi setup for the all sky camera Perhaps one of the other focuser drivers could be made to work... OTOH I wouldn't be surprised if there was all the info in the INDI resources needed to write one's own driver.
  3. Connected ASI178MM camera and tried starting indiserver with ASI driver but instead of coming up with the hardware camera it loads the simulator. And I still can't get rpifocus to work
  4. Not sure the command is correct though - will investigate... Here's a list of INDI drivers.
  5. I think there is but I don't know. One thing seems evident - installation is better in Ubuntu MATE than Raspbian. Here are some screenshots of the download etc. Astroberry Focuser search Astroberry download page Downloads folder gdebi package installer
  6. Just tried installing it in Ubuntu MATE Ran Firefox and found the Astroberry Focuser web site, downloaded the INDI driver and opened it in gdebi package installer by right clicking on the downloaded .deb file. Clicked Install and it went straight through reporting that the latest driver and same version was already installed, so installing the INDILib must have included it. Next thing then is to build the hardware. Could just run the simulator I guess...
  7. I don't think so. There is no feedback from the A4988 to the RPi, is there? So it can't tell if the driver is connected or not.
  8. I see... Oh dear I haven't tried installing the driver yet. I do seem to be having more success generally with Ubuntu MATE than I did with Raspbian though. It might be because I'm more familiar with Ubuntu than Raspbian as I use Linux Mint which is a fork off Ubuntu and is very similar. But that doesn't apply to the CLI as that is just pure Linux. I'm taking thinks fairly easy today after a very busy day yesterday so not rushing things - just pottering along
  9. Something wrong - the usual image post isn't working
  10. Found some connectors for the RPi GPIO pins In particular, an IDC connector on a 16way ribbon cable that fits the GPIO pins. This will connect to the required pins for the Astroberry INDI driver.
  11. Having nearly done my back in looking through boxes for something to connect to the GPIO pins and found nothing, I've ordered a connector and also a ribbon cable plus a couple of other bits from Amazon - due to arrive tomorrow. Wish I'd thought of this before...
  12. Captured best part of 100 OIII subs last night then it was meridian flip time so I changed to the Ha filter for alignment and rough focussing the SII filter, fine focussed and then went over to APT for SII imaging but by that time the cloud had thickened. Left it running overnight but on checking this morning saw no usable SII subs so I'll do those next clear night we get.
  13. Just modified a 5v 28BYJ-48 from unipolar to bipolar, opened the packet of the Pololu A4988 driver module and sorting out other bits. I could do with a connector for the RPi GPIO. I'll go and see what I can find...
  14. I already have the INDILib plus KStars/Ekos installed on my Ubuntu MATE RPi 3 so I'll just download and install the driver. I too am planning to check out all this today - I have a Pololu driver with A4988 ready to try. I shall also have the ASI788MM camera in all sky camera connected to the RPi and be testing that. The ASC is already indoors and ready to test. I shall need to change the 28BYJ-48 for a modified 5v version as the current one is 12v and was going to be run off Arduino Nano but I don't want to do that.
  15. True BUT... "The DRV8834 operates from 2.5–10.8 V" and my supply is 12v or 13.8v.
  16. I made a bit of a mess of the tabs on the stepper motor I modified too I may have a go with my modified stepper motor and A4988 Pololu driver tomorrow - been out a lot today but I'm in all day tomorrow. I have one driver left from my 3D projects. I expect to get some more soon or I might go for a different model.
  17. Clear sky and I'm imaging in OIII with 28MM lens. Still using 120s subs though I could have gone up a bit before saturating but since the final result is more dependent on total time I'm sticking with 120s so that I can use the same darks for calibration. Here is an OIII sub histogram stretched in Photoshop.
  18. Ah yes - I have read that I can buy a Mamiya 645 lens to EOS adapter and that could by connected to an EOS to T2 adapter to solve the problem in two steps.
  19. The smallest MXL timing pulley with 5mm bore is a 15t with pitch diameter just under 10mm meaning the big pulley would have to be a whopping 500mm diameter. Even the smallest pulley with 10t has a 6.7mm pitch diameter and hence 330mm big pulley - that's over a foot!! Not on. So the step down will have to be in two steps. Two steps of 5:1 and 10:1 would be possible, but for the pulleys available a 15t motor pulley would have to go with a 60t on intermediate shaft giving 4:1 leaving 25:2 for the final drive step. With another 15t pulley and 10mm pitch diameter the large pulley would be 125mm diameter (5"). This is quite feasible
  20. Anyway, without re-writing all the arithmetic, it works out that with a NEMA stepper motor motor with 1.8° step angle and 16x micro-stepping, a ratio of 100:1 would be required - very difficult to achieve in one go without using worm and worm gear and I haven't got the facilities to produce those. At first sight a NEMA stepper motor with built-in gearbox would look like a good idea but further investigation shows that their gearboxes are also not an exact integer ratio just like the 28BYJ-48! OTOH there are alternatives to the Pololu drivers that will do 32x micro-stepping meaning a ratio of 50:1 - a bit easier perhaps. I don't think 3D printed gears would be accurate enough and an alternative is belt drive with MXL timing belt and pulleys
  21. Drat - my post with all the calculations has disappeared
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. By using this site, you agree to our Terms of Use.