Jump to content

Banner.jpg.b83b14cd4142fe10848741bb2a14c66b.jpg

blackdragon72

Members
  • Posts

    37
  • Joined

  • Last visited

Posts posted by blackdragon72

  1. I'm,afraid not. The AAF2 project was my first foray into ASCOM.

    I managed to get my two channel focuser driver up. It is (including visual studio project) available here:

    https://sourceforge.net/projects/arduinodualchannelascomfocuser/?source=navbar

    It uses one Arduino Nano to control two focusers. The protocol is based on Moonlite, and the main difference is that TempComp is handled by Arduino, not the driver (which I believe Moonlite does).

    I have not tested it fully since I have only one telescope, on which one channel focuser works fine.

    You should be able to connect the focuser via Moonlite driver directly, but my driver supports more commands than Moonlite so it wont talk to Moonlite focuser (it could be done by removing those additional commands).

    • Like 2
  2. I don't have the same setup, but I opted to use a NEMA 17 12v/200 step stepper from the off - over engineering, maybe, but it's been a fun project, and gives very precise control via the fine focus knob, which is good for my Hyperstar setup due to the very narrow CFZ.

    This certainly doesn't lack torque.

    I think I did not make myself clear.

    My motor has enough torque to turn fine focus knob, it is the knob which fails to rack focuser in, I guess it just can not handle the load.

    I need to find another motor to work with coarse focus knob - the current one does not have enough torque.

    I confirmed with manual focus that coarse focus knob can rack in/out without any issue.

  3. My UNO board and motor shield work perfectly with stepper with motor. But one problem: my motor can not drive coarse focus knob of moonlite CFL focuser (it is quiet stiff), so I hook it to fine focus knob. However my imaging setup is slightly heavier than what it can handle so it does not rack in when the telescope points up. It forces me back to coarse knob.

    Question is that: is there anyone using CFL moonlite focuser? And what motor do you use to drive coarse focus knob? I need to know so that I can get motor with enough torque.

  4. Just got UNO board today and try to test the sketch. I could upload 2.2 nano sketch and my modified UNO sketch, but both failed when I open ASCOM driver.

    What could be the reason?

    Ok, when I run ASCOM diagnostics, it says mscoree.dll not found. Is this file part of installation package? I am using win8.1.

  5. Yeah, it's a powered hub. I've got the Atik and serial to USB cable from the mount also connected. I tried it without the other devices connected.

    I tried a bunch of different combination to see if I could narrow down the fault and recorded them in the table below. For each combination, only the focuser USB device was connected and it was uplugged before testing. I recorded the voltage across the Nano +5v and GND pins for info.

    I know very little about electronics so really don't know what the table is telling me, but all I need to know to make it work is to make sure the power is plugged into the hub and turned off before attaching the USB cable to the laptop!

    attachicon.giftable.png

    I am using this. I usually have auto guide, ccd and usb-serial connected to the hub. It never gives me any issue with external power.

    http://www.amazon.com/Port-Compact-Black-USB-2-0/dp/B000T9S4CI/ref=sr_1_2/183-2930130-3956353?s=electronics&ie=UTF8&qid=1413086575&sr=1-2&keywords=startech+usb+hub

  6. Sounds interesting. I have no experience of Macs. What client program do you plan to use and how will it interface to the arduino?

    I dont know much about it either. Nebulosity support microtouch focuser in max osx (and of course many more focusers in Win), I hope they will add auto focus function in their future release.

  7. Don't forget the advantage in the pulley system. Mine is 4:1, so 1 revolution of the coarse focus knob = 256 steps. You could easily make it 5:1, 320 steps.

    When I made mine I had doubts on whether the motor's steps were fine enough but it was so cheap I figured it would be worth a go and maybe upgrade later. As it turns out it is more than adequate, I doubt that the movement would be quantifiable if it was much finer.

    http://www.astrodon.com/Orphan/parfocal_and_critical_focus_zone/

    Based on above experiment, step size is definitely critical for the imaging system, that is why I am more concern about step size. I also plan to use the same system for a much faster scope, which demands even finer step.

  8. By 'app' do you mean the sketch, client program or driver? Any focuser client that uses ascom should work with my focuser if you use my driver.. The device-dependant coding is in the driver. If you want to use the driver of another focuser you will need to find out what the comms protocol/commands are and rewrite the arduino sketch to work with it. I designed my own protocol in this case because I wanted to learn about both parts. I believe someone on SGL has made an arduino-based focuser that uses the Moonlight protocol & driver but I can't remember who it was.

    Yes. I was thinking if it can be used under mac osx. I plan to  migrate everything to mac, for me the only thing mac osx does not support is ASCOM.

  9. Yes it works fine. As the arduino site says if you are using the serial port in your program you need to make sure you put a short delay in your program before doing any comms. You will only ever use the focuser on Windows so its not an issue for that.

    Good. I thought the board will be reset every time there is a COM communication, eg, every time ASCOM driver is sending a command to the motor. I am thinking if it is possible to mimic another motorized focuser so that we can reuse the app.

  10. In essence, yes, correct - as long as you accept the same commands from the driver, and return the expected return codes, then it won't see any difference: my implementation uses an Adafruit motor shield to provide micro stepping control.

    It should *run* okay on an uno (I'm using an uno clone), but a "universal" sketch would be difficult due to the number of possible hardware variations - your motor board is different to mine, are both different to Dave's (IIRC).

    You should need minimal changes as you outlined above to implement your own clockwise & anti-clockwise routines, using step(1) and step(-1).

    Ask here if you have any problems...

    Are you facing any issue with auto reset, as mentioned here?

    http://arduino.cc/en/Main/arduinoBoardUno

  11. :rolleyes:

    There ought to be some way (eg, device ID or similar) to tell.

    I did not mean to ask for support for every system, but for nano and uno only, since these 2 seem the most popular choices. I am thinking that once we have a working version for Uno, we could use the tool to patch the new changes from Nano sketch to Uno so we can release both together.

×
×
  • 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.