first of all I want to thank you Robert for this wonderful, and well-documented project. I looked for an ASCOM focuser which could be used with gamepad remote control, and I found this DIY project.
I recently finished building mine. I built an MT version, with a sligthly modified Rev4 PCB to get the USB connector close to the edge of the PCB as possible.
Even it was my first Ardunio project, downloading the firmware went like a charm. (except Ardunio IDE dropped various error messages when compiling "Focuserv264_DRV8825_HW203", but there was no problem with the "Focuserv264_DRV8825", so I used that instead.
First I tested it with the windows app and an old SkyWatcher refractor rack and pinion focuser. Then I installed the ASCOM driver and tried with EQASCOM / ASCOMPAD 1.20. I selected the MyFocuserPro2 focuser, configured it, but ASCOMPAD always said: "Sorry focuser is incompatible: Absolute requires position read!" I googled the error message, this is a general error prompt when ASCOMPAD is not able to read the position information from a focuser. I tried it with different settings, turned off and on, moved back to ASCOMPAD 1.18, but no change. It was strange, because first after the configuration it looked like it could read out some settings, but after this error message it displayed only zeros and "no"s.
I was very disappointed, because I thought I will can control it via gamepad. I rebooted the machine, closed and opened ASCOMPAD again, and I noticed, that it suddenly displayed "5000" as starting position. And it started to work with the gamepad!
According to my experiences, it displays the error messages after configuration / change settings. But ASCOMPAD saves the selected focuser, and automatically connects is upon starting. The workaround is to exit ASCOMPAD after changing the settings, and start it again. After a few iterations I could manage to set it to start from the stored position and not from 5000.
I could reproduce it reliably : Select focuser --> error message. Close and open ASCOMPAD: no problem, works fine. I kept ASCOMPAD 1.18 because I like it's user interface better than 1.20.
Anybody else experienced such thing? Is it an ASCOMPAD or a MFP2 issue?
I am very happy with my focuser, I can't wait to mount it to a real telescope and use it under the sky. Thank you Robert!
My build in operation: https://youtu.be/ytftqkUjy8Y
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If the PCB is for the "HW203" then you must use the HW203 firmware and not simply DRV8825. If you did that, then microstepping will be wrong because HW203 vs plain DRV8825 uses different pins to control microstepping.
So use the HW203 version - you can safetly ignore the warnings. These warnings are from the various libraries that other authors have written but as yet have not upped them to work with newer versions of the Arduino IDE.
I doubt that the issue is myFocuserPro2 as it passes ASCOM Conform and has been pretty rigoursly tested. But I need a trace file to be sure.
I would suggest you turn ascom tracing on and send me the trace file for "Sorry focuser is incompatible: Absolute requires position read!" as that would help and then I can investigate. SO if you can get one, send it to me, and I will look into it further,
Unless I can see what ASCOMPAD is doing there is little chance of finding whats wrong.
Regards
Robert
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yes, I have uploaded the changed file - you were right.
About ASCOMPAD - I have been looking at this and it does not appear to release the comport when it "disconnects" the driver - hence the next attempt to access the driver is denied "com port in use or busy". I am ploughing through the logs but it does not look like a quick fix.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This is what I have found
The application appears to require admin rights in order to access the comport. On first connection it fails, and then sometimes it works. If the disconnect option is chosen it is screwed from that point on.
At times you cannot exit the application at all - requires task manager to kill it.
I repeated all my tests with the Moonlite ASCOM driver - exactly the same results. This seems to suggest it is neither the Moonlite driver or the myFocuserPro2 drivers that is causing the issue.
The logs indicate that the application fails, it does not have rights to access the com port
13:08:25.031 Connected NotConnectedExc System.UnauthorizedAccessException: Access to the port 'COM5' is denied.[0D][0A] at ASCOM.Utilities.Serial.set_Connected(Boolean Connecting) in C:\ASCOM Build\Export\ASCOM.Utilities\ASCOM.Utilities\Serial.vb:line 520[0D][0A] at ASCOM.myFocuser2ASCOM.Focuser.set_Connected(Boolean value)
Access to the port 'COM5' is denied.
This error occurs with other ASCOM drivers, and this error does not occur with ASCOMAPP, Nebulosity, APT or other client applications.
It all points to ASCOMPAD issues. I notice there is source code but it is in VB and its not a language I like to code in.
Regards
Robert
Last edit: brownrb 2018-01-30
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi, I have the same problem, when i first connect the focuser to ascompad it is initially set as a relative focuser. After closing it down and reconnecting at a later date the setup shows an absolute focuser and i get the focuser not compatible with message. Disappointing that ascompad does not seem to close down properly.
Regards Charles Clark
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Robert, Thanks for the prompt response in sending me the video link. I notice that the Ascom driver in the video is different to the latest one (v266). I fing with v266 when I start the ascom driver it defaults to Relative (No option to select Relative or absolute like in the video) But once connected it changes to Absolute.
Question does the focuser only run in an absolute setting mode?
or am I doing something wrong the get it to run in Relative mode?
I agree Ascompad it tempremental when seting up and I have taken to sometimes changing a speed and ticking an update on connection to try to prevent any not compatible messages when connecting/setting up.
Many thanks for you prompt response your help and project is much appreciated.
I have a query on bluetooth but I will create another thread for this.
Regards
Charles Clark
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
myFocuserpro2 only supports absolute mode. The different driver version is irrelevant.
I can only assume that ASCOMPAD starts by assuming it is talking to a relative focuser, and only after connection is made then it can query the focuser and determine it is an absolute one.
I believe support for ASCOMPAD has long since gone and the package itself has not been updated for years. I understand it was developed at a time when relative focusers and dc motors were common.
I agian reiterate that this behaviour of ascompad happens with other ascom drivers also, such as moonlite ascom focuser. The issues are with ASCOMPAD and there is nothing I can do in myfocuserpro2 to make it work with ascompad.
If you can provide with with clear logs where myfocuserpro2 is not behaviing correctly compared to other ascom drivers I am more than happy to take a look, but trying to modify myfocuserpro2 to be compatible with something that is years out of date and unsupported does not seem to be a sound strategy.
Regards
Robert
Last edit: brownrb 2019-05-01
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Robert I was not suggesting that there Is a problem with my focused software as have demonstrated everything works fine when it is run with windows and Iknow that the problem is with ascompad . I was just seeking clarification that myfocuser only runs as absolute It is just that I am new to astrophotography and I am on a steep learning curve I am running my mount with Carte du Ciel with the aecom platform and want to be able to link up with apt software as well. This is what I have picked up on and its it's all self taught from YouTube
If you af any other better software packages (freeware) I would be grateful.
if not I will just muddle through with the work round for ascom pad you have shown me
Many thanks again
Regards Charles Clark
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Forgive me if I was sounding terse, I currently have 2 collapsed spinal disks and it makes me a little grumpy. Four days and I still have problems walking or standing up.
myFocuserPro2 cannot work as a relative focuser. Most client apps like ASCOMPAD etc will not know what type of focuser (relative or absolute) till after connection is made and that info is retrieved from the controller. Its the controller that determines what it is, and ascom just gets this info from the controller once connected.
Obviously ascompad is making an assumption that it is going to talk to a relative focuser, but it does query the controller after a connection is made and changes to "absolute"
APT works well with myFocuserPro2. So does Nebulosity. I actually like Nebulosity as it can do frame and focus, manage guiding, dithering, image capture and has a good set of tools for combining your captured images into a reasonable image (stacking) as well as post-processing functions.
You might also try astrotortilla which can do the platesolving. In general, imaging consistents of
1. Goto target
2. Focus
3. Frame and plate solve, center target
4. Start guiding
5. Start imaging sequence
For guiding there is PHD2 which works well when configured. NINA works well with PH2 and can also platesolve.
I tend to be very methodical in note taking. So when I was learning I liked to document everything. I broke things down into the above 5 steps. And I tried hard to master each. That meant countless nights under the stars getting focusing to be an accurate and consistent as I could, recording what I was doing, what settings worked, what the FWHM values were, what stars I was using (I tending to use the same ones over and over, only changing when they got out of sight, just before the meridian and about 30d above horizon)
Once I believed I had focusing down pat. I moved to guiding. Some are lucky, I never was. But I managed to become good at it through lots of practise. I would record the guiding graphs, let it run for 1/2hr, make a small change, etc, repeating till I knew as much as my brain could hold. And if a deviation started in the guiding graph I knew what to adjust to correct it.
I was blessed (cursed) using a mount which had heaps of backlash and was super sensitive to balance etc. I fought with the beast for 2 years, Then I bought an EQ8 and overnight everything changed. I no longer struggled with target gotos, balance, guiding (I could guide unguided for 20m) and just about everything else. If I had one tip it would be get the most expensive quality mount you can afford. It makes everything else easy. It is the single most important purchase you can make.
So first tip is go and buy a diary and start logging, hand notes, everytime you make a change write it down, look for patterns to emerge, they will tell you over time what works and what does not. On the odd night you go out and try something that worked before and find it doesnt work now - remember this - the only thing that has changed is the seeing - this is why using the same stars and checking fwhm values is important - one night might be 1.9 and another 2.3 is the best value - this is seeing, and it going to affect guiding, so don't panic when things that worked suddenly does not
I use satelitte maps to check cloud cover, especially infra red as it shows higher clouds.
I also use this site to know what the jet stream is doing. Whilst it might look like a great night with dark skies your eyes cannot see high cloud or the jet streams, but your cameras can and it will affect guiding and image results. http://www.weatherzone.com.au/satellite/world/new-zealand
Hi Robert,
Thanks for your prompt response and your pointing me in the right direction. I will definitely have a look at all of these items. I appreciate any guidance/tips/Knowledge given.
I sympathise with your back problems as I also suffer from a disc/facet joint problem, had my nerve ends cauterised twice to no real avail. Yes the pain nagging away can grind you down.
Any way take care and once again thanks for your help, it is much appreciated
I am currently awaiting a new bluetooth module an HC 05 to try out bluetooth as well as your ne android app. I currently have fitted an HC 06 which has worked in the past but whilst it pairs up Okay it doesnt want to comminicate with the controller. After reading through you bluetooth addendum I found that it only works with an HC05 so hopefully by Saturday I will receive that and give it ago. And hopefully we get some clear skies over here.
Once again
Many Thanks
Regards
Charles Clark
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The android bt app for myfp2 is nearly ready for release.
I released the android bt app for the mydewcontrollerpro3 today so I have copied some code changes from that into the myfp2 and just need time to test those changes before release.
there will also be android bt app for the myfocuserpro (v1).
Some people have managed to get the HC06 to work, I never bought one and they never said much about how, so I cannot help there. But most times it comes down to rxd/txd being transposed, wrong baud rate, wrong comport on pc end, or failing to use a voltage divider resistor network for the line going into rxd on the hc05.
Whatever you do, dont start -playing with/changing the firmware, that is sure fire recipe for stuffing things up.
If you are proficient in programming arduino, you can turn debugging on in the firmware and connect the arduino ide to the com port connect via usb to the controller, then use the windows app to connect via bt com port. This way you will see debug messages on the serial monitor which could give a clue as to what is happening.
Last edit: brownrb 2019-05-02
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Robert just to let you know I have had a message from eqmod support site informing me that there is an updated version v209 of ascompad setup program I have not tried it yet but I took the liberty of forwarding your findings in my request for guidance itmay or may not have any bearing on it
regards Charles Clark
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
About ASCOMPAD - I have been looking at this and it does not appear to release the comport when it "disconnects" the driver - hence the next attempt to access the driver is denied "com port in use or busy".
I don't understand how that could be as ASCOMPAD doesn't directly open or close any com ports . It is a pure ASCOM client application and only interfaces at an ASCOM level with the ASCOM driver - it ha sno knowlege of how the driver chooses to interface with the hardware. It wites to Connected/Link properties of the ASCOM driver whch has the responsiblility of managing the opening and releasing any COM ports it may use. When disconnecting a driver from ASCOMPAD it will send out a Connected=false and Link=false - if a com port isn't being closed then that surely is a driver issue?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Chris
Welcome. Good to have your feedback. I see you have released an update (no inference intended) and i understand it is being tested by Charles to see if that makes a difference to his situation.
I agree with your notes. What I do not understand is why when used with the previous release of ASCOMPAD we were getting these errors. These errors only seemed to occur with ASCOMPAD and using another client the issues could not be replicated with the same driver. We did test ASCOMPAD with my driver and with the Moonlite driver and both drivers exhibited the same issue.
Now it is entirely plausible that somehow there is something I have coded in the driver that causes this to happen to ASCOMPAD, that makes it stuff up with ASCOMPAD and not others, I do not know. What I do know is that you have a great deal more knowledge about ASCOM that I do and have been doing this much much longer than I have.
I am awaiting to hear back from Charles to see if the issues have gone away. If they have not I will delve into my code and take a much closer look. I do very much appreciate your feedback and response here, it is good to hear from you.
regards
Robert
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Robert i have briefly tried the updated version of ascompad and i have found upto now that as long as i connect in relative mode ie enter setup and properties it connects without errors occurring. I have been a bit engrossed at the minute sorting out my bluetooth connection problems, which i now seem to have succeed with. Need to do a few more connection tests on a second laptop that uses a plug in bluetooth adaptor.
I found after taking my pcd board out to check resistor configuration that my focuser would not communicate when trying to upload the firmware. I was getting time out errors.
I finally by trial and error after letting my arduino upgrade libraries and boards (in desperation
) change the processor programming to ATMega328P(Oldbootloader) and it uploaded the program without error. The bluetooth now works.
I can't say i amunderstanding this as previously the old setup before changing seemed to work okay. I am however using two laptops when i was trying to sort out the blue tooth.
Maybe that had something to do with it or maybe I am just confusing my self.
I know need to try the older laptop with the plugin bluetooth module to see if the bluetooth connection works with that as that is the one that i want to use with my mount.
Thanks with all your help much appreciated
Regards
Charles Clark
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Robert, second laptop has connected fine with the external bluetooth adaptor and works okay with windows version of myfocuser.
I have tried out ascompad v2.09 and it connects up via bluetooth.
I much prefer this frontend for asompad as i find it more intuitive. I have taken to entering setup to ensure it is starting in relative then connecting after opening properties and seems to be fine.
If i try to go straight to connect it tries to connect in absolute mode i get the message.
Sorry Focuser is incompatible. Absolute requires a position read.
Regards
Charles Clark
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Charles
Glad to hear you resolved the Bluetooth issues.
If you get can you please try the straight to connect which gives you the message, but when selecting the ascom driver please ensure trace is checked. The log will be produced in the documents\ascom folder and that could be very helpful if you could do that and post it here. the log will have detailed info on what is coming from the client as well as the responses. This will prove useful in looking at the issue further.
Cheera
Robert
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
With V2.09 you should find a file named "ascom_focuser_debug.txt" in the ASCOMPAD install directory. If you open that file in notepad I expect it shows an error when an attempt to read the stepper position was made - perhaps you could verify that and post it.
If you could then try out ASCOMPAD v2.12 and compare the ascom_focuser_debug.txt contents.
Yes, I updated ASCOMPAD - the way things work with EQMOD projects is public releases are held on sourceforge whilst development releases are made to the EQMOD Yahoo group. ASCOMPAD had undergone quite a number of development releases (things like dome shutter control added) that had never made it out to a public release. When I saw that folks we having issues I thought I'd might as well put the current development release onto sourceforge. There aren't any specific fixes made with regard to this particular problem but you never know and if I'm to investigate it further I need folks to be using software that is closer to the current development version.
I certainly wouldn't rule out a bug in ASCOMPAD - particularly if the same thing is happening across a number of focuser types. On the EQMOD Yahoo group I'm currently working with another user who is experiencing similar issues with the celestron focuser - so there have been a few more test releases with additional tracing issued in the past few days to that group. I generally prefer to use that group's resources to work through problems before making public releases. Obviously it is hard for me to debug not actually having an actual focuser that shows the problem - all I can do is test against the ASCOM focuser simulator (supposedly a gold standard for focuser drivers) and that doesn't show the issue (but of course it doesn't do serial comms etc).
Immediately after connection (by the link or Connected properties) ASCOMPAD does a series of tests on the driver to establish what type it is so it can adapt its control methods according. For absolute focus control ASCOMPAD needs to be able to read position and so a position read is made as part of this initial focuser driver interrogation. It seems that the celestron focuser is raising an exception to this initial read of position (and sometimes som other properties) and I'm wondering if it the driver/hardware needs some time to settle after the initial connect is made and before the read is made (any thought soon this?) ... anyhow investigations are ongoing and any insights you can offer are most welcome.
With regard to admin rights there is no specific reason I can think of why ASCOMPAD would require admin rights other than the fact it need to be give the same level of rights as the other software in the chain - i.e. ASCOM driver / serial port driver etc.
Chris.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
first of all I want to thank you Robert for this wonderful, and well-documented project. I looked for an ASCOM focuser which could be used with gamepad remote control, and I found this DIY project.
I recently finished building mine. I built an MT version, with a sligthly modified Rev4 PCB to get the USB connector close to the edge of the PCB as possible.
Even it was my first Ardunio project, downloading the firmware went like a charm. (except Ardunio IDE dropped various error messages when compiling "Focuserv264_DRV8825_HW203", but there was no problem with the "Focuserv264_DRV8825", so I used that instead.
First I tested it with the windows app and an old SkyWatcher refractor rack and pinion focuser. Then I installed the ASCOM driver and tried with EQASCOM / ASCOMPAD 1.20. I selected the MyFocuserPro2 focuser, configured it, but ASCOMPAD always said: "Sorry focuser is incompatible: Absolute requires position read!" I googled the error message, this is a general error prompt when ASCOMPAD is not able to read the position information from a focuser. I tried it with different settings, turned off and on, moved back to ASCOMPAD 1.18, but no change. It was strange, because first after the configuration it looked like it could read out some settings, but after this error message it displayed only zeros and "no"s.
I was very disappointed, because I thought I will can control it via gamepad. I rebooted the machine, closed and opened ASCOMPAD again, and I noticed, that it suddenly displayed "5000" as starting position. And it started to work with the gamepad!
According to my experiences, it displays the error messages after configuration / change settings. But ASCOMPAD saves the selected focuser, and automatically connects is upon starting. The workaround is to exit ASCOMPAD after changing the settings, and start it again. After a few iterations I could manage to set it to start from the stored position and not from 5000.
I could reproduce it reliably : Select focuser --> error message. Close and open ASCOMPAD: no problem, works fine. I kept ASCOMPAD 1.18 because I like it's user interface better than 1.20.
Anybody else experienced such thing? Is it an ASCOMPAD or a MFP2 issue?
I am very happy with my focuser, I can't wait to mount it to a real telescope and use it under the sky. Thank you Robert!
My build in operation: https://youtu.be/ytftqkUjy8Y
If the PCB is for the "HW203" then you must use the HW203 firmware and not simply DRV8825. If you did that, then microstepping will be wrong because HW203 vs plain DRV8825 uses different pins to control microstepping.
So use the HW203 version - you can safetly ignore the warnings. These warnings are from the various libraries that other authors have written but as yet have not upped them to work with newer versions of the Arduino IDE.
I doubt that the issue is myFocuserPro2 as it passes ASCOM Conform and has been pretty rigoursly tested. But I need a trace file to be sure.
I would suggest you turn ascom tracing on and send me the trace file for "Sorry focuser is incompatible: Absolute requires position read!" as that would help and then I can investigate. SO if you can get one, send it to me, and I will look into it further,
Unless I can see what ASCOMPAD is doing there is little chance of finding whats wrong.
Regards
Robert
Hi,
thank you for the hint regarding the different firmware versions!
These are errors, not warnings with Focuserv264_DRV8825_HW203.ino:
Arduino: 1.8.5 (Windows 10), Board: "Arduino Nano, ATmega328P"
Focuserv264_DRV8825_HW203:435: error: 'booleantcstarted' does not name a type
booleantcstarted; // indicates if temperature compensation is enabled
D:\BZd\tavcso\MotoFocus_Ardunio\Firmware\Focuserv264_DRV8825_HW203\Focuserv264_DRV8825_HW203.ino: In function 'void setup()':
Focuserv264_DRV8825_HW203:1693: error: 'tcstarted' was not declared in this scope
tcstarted = false; // temperature compensation is off
^
D:\BZd\tavcso\MotoFocus_Ardunio\Firmware\Focuserv264_DRV8825_HW203\Focuserv264_DRV8825_HW203.ino: In function 'void loop()':
Focuserv264_DRV8825_HW203:2308: error: 'tcstarted' was not declared in this scope
if ( tcstarted == false ) ^Focuserv264_DRV8825_HW203:2325: error: 'tcstarted' was not declared in this scope
tcstarted = false; // indicate that temp compensation was done ^exit status 1
'booleantcstarted' does not name a type
This report would have more information with
"Show verbose output during compilation"
option enabled in File -> Preferences.
I figured out, that a space is missing here: booleantcstarted -> boolean tcstarted
Then it complied without errors and warnings. Now I move on to the ASCOM part.
Yes, I have uploaded the changed file - you were right.
About ASCOMPAD - I have been looking at this and it does not appear to release the comport when it "disconnects" the driver - hence the next attempt to access the driver is denied "com port in use or busy". I am ploughing through the logs but it does not look like a quick fix.
I sent you my ASCOM logs in e-mail as well.
This is what I have found
The application appears to require admin rights in order to access the comport. On first connection it fails, and then sometimes it works. If the disconnect option is chosen it is screwed from that point on.
At times you cannot exit the application at all - requires task manager to kill it.
I repeated all my tests with the Moonlite ASCOM driver - exactly the same results. This seems to suggest it is neither the Moonlite driver or the myFocuserPro2 drivers that is causing the issue.
The logs indicate that the application fails, it does not have rights to access the com port
13:08:25.031 Connected NotConnectedExc System.UnauthorizedAccessException: Access to the port 'COM5' is denied.[0D][0A] at ASCOM.Utilities.Serial.set_Connected(Boolean Connecting) in C:\ASCOM Build\Export\ASCOM.Utilities\ASCOM.Utilities\Serial.vb:line 520[0D][0A] at ASCOM.myFocuser2ASCOM.Focuser.set_Connected(Boolean value)
Access to the port 'COM5' is denied.
This error occurs with other ASCOM drivers, and this error does not occur with ASCOMAPP, Nebulosity, APT or other client applications.
It all points to ASCOMPAD issues. I notice there is source code but it is in VB and its not a language I like to code in.
Regards
Robert
Last edit: brownrb 2018-01-30
Hi, I have the same problem, when i first connect the focuser to ascompad it is initially set as a relative focuser. After closing it down and reconnecting at a later date the setup shows an absolute focuser and i get the focuser not compatible with message. Disappointing that ascompad does not seem to close down properly.
Regards Charles Clark
Hi Charles
https://www.youtube.com/watch?v=l8_xCujBXg8
I believe the source of ASCOMPad is available. The issue I believe is ascompad.
Regards
Robert
Hi Robert, Thanks for the prompt response in sending me the video link. I notice that the Ascom driver in the video is different to the latest one (v266). I fing with v266 when I start the ascom driver it defaults to Relative (No option to select Relative or absolute like in the video) But once connected it changes to Absolute.
Question does the focuser only run in an absolute setting mode?
or am I doing something wrong the get it to run in Relative mode?
I agree Ascompad it tempremental when seting up and I have taken to sometimes changing a speed and ticking an update on connection to try to prevent any not compatible messages when connecting/setting up.
Many thanks for you prompt response your help and project is much appreciated.
I have a query on bluetooth but I will create another thread for this.
Regards
Charles Clark
myFocuserpro2 only supports absolute mode. The different driver version is irrelevant.
I can only assume that ASCOMPAD starts by assuming it is talking to a relative focuser, and only after connection is made then it can query the focuser and determine it is an absolute one.
I believe support for ASCOMPAD has long since gone and the package itself has not been updated for years. I understand it was developed at a time when relative focusers and dc motors were common.
I agian reiterate that this behaviour of ascompad happens with other ascom drivers also, such as moonlite ascom focuser. The issues are with ASCOMPAD and there is nothing I can do in myfocuserpro2 to make it work with ascompad.
If you can provide with with clear logs where myfocuserpro2 is not behaviing correctly compared to other ascom drivers I am more than happy to take a look, but trying to modify myfocuserpro2 to be compatible with something that is years out of date and unsupported does not seem to be a sound strategy.
Regards
Robert
Last edit: brownrb 2019-05-01
Hi Robert I was not suggesting that there Is a problem with my focused software as have demonstrated everything works fine when it is run with windows and Iknow that the problem is with ascompad . I was just seeking clarification that myfocuser only runs as absolute It is just that I am new to astrophotography and I am on a steep learning curve I am running my mount with Carte du Ciel with the aecom platform and want to be able to link up with apt software as well. This is what I have picked up on and its it's all self taught from YouTube
If you af any other better software packages (freeware) I would be grateful.
if not I will just muddle through with the work round for ascom pad you have shown me
Many thanks again
Regards Charles Clark
Hi Charles
Forgive me if I was sounding terse, I currently have 2 collapsed spinal disks and it makes me a little grumpy. Four days and I still have problems walking or standing up.
myFocuserPro2 cannot work as a relative focuser. Most client apps like ASCOMPAD etc will not know what type of focuser (relative or absolute) till after connection is made and that info is retrieved from the controller. Its the controller that determines what it is, and ascom just gets this info from the controller once connected.
Obviously ascompad is making an assumption that it is going to talk to a relative focuser, but it does query the controller after a connection is made and changes to "absolute"
APT works well with myFocuserPro2. So does Nebulosity. I actually like Nebulosity as it can do frame and focus, manage guiding, dithering, image capture and has a good set of tools for combining your captured images into a reasonable image (stacking) as well as post-processing functions.
Free: Try this, some say its going to be better than SGP and its also free
https://nighttime-imaging.eu/
You might also try astrotortilla which can do the platesolving. In general, imaging consistents of
1. Goto target
2. Focus
3. Frame and plate solve, center target
4. Start guiding
5. Start imaging sequence
For guiding there is PHD2 which works well when configured. NINA works well with PH2 and can also platesolve.
I tend to be very methodical in note taking. So when I was learning I liked to document everything. I broke things down into the above 5 steps. And I tried hard to master each. That meant countless nights under the stars getting focusing to be an accurate and consistent as I could, recording what I was doing, what settings worked, what the FWHM values were, what stars I was using (I tending to use the same ones over and over, only changing when they got out of sight, just before the meridian and about 30d above horizon)
Once I believed I had focusing down pat. I moved to guiding. Some are lucky, I never was. But I managed to become good at it through lots of practise. I would record the guiding graphs, let it run for 1/2hr, make a small change, etc, repeating till I knew as much as my brain could hold. And if a deviation started in the guiding graph I knew what to adjust to correct it.
I was blessed (cursed) using a mount which had heaps of backlash and was super sensitive to balance etc. I fought with the beast for 2 years, Then I bought an EQ8 and overnight everything changed. I no longer struggled with target gotos, balance, guiding (I could guide unguided for 20m) and just about everything else. If I had one tip it would be get the most expensive quality mount you can afford. It makes everything else easy. It is the single most important purchase you can make.
So first tip is go and buy a diary and start logging, hand notes, everytime you make a change write it down, look for patterns to emerge, they will tell you over time what works and what does not. On the odd night you go out and try something that worked before and find it doesnt work now - remember this - the only thing that has changed is the seeing - this is why using the same stars and checking fwhm values is important - one night might be 1.9 and another 2.3 is the best value - this is seeing, and it going to affect guiding, so don't panic when things that worked suddenly does not
I use satelitte maps to check cloud cover, especially infra red as it shows higher clouds.
I also use this site to know what the jet stream is doing. Whilst it might look like a great night with dark skies your eyes cannot see high cloud or the jet streams, but your cameras can and it will affect guiding and image results.
http://www.weatherzone.com.au/satellite/world/new-zealand
http://squall.sfsu.edu/gif/jetstream_sohem_00.gif
Cheers
Robert
Some of my imaging etc pdfs are here
https://sourceforge.net/projects/arduinoascomfocuserpro2diy/files/Astro%20Imaging%20PDFs/
Scopefocus
http://www.scopefocus.info/scopefocus-ascom
Hi Robert,
Thanks for your prompt response and your pointing me in the right direction. I will definitely have a look at all of these items. I appreciate any guidance/tips/Knowledge given.
I sympathise with your back problems as I also suffer from a disc/facet joint problem, had my nerve ends cauterised twice to no real avail. Yes the pain nagging away can grind you down.
Any way take care and once again thanks for your help, it is much appreciated
I am currently awaiting a new bluetooth module an HC 05 to try out bluetooth as well as your ne android app. I currently have fitted an HC 06 which has worked in the past but whilst it pairs up Okay it doesnt want to comminicate with the controller. After reading through you bluetooth addendum I found that it only works with an HC05 so hopefully by Saturday I will receive that and give it ago. And hopefully we get some clear skies over here.
Once again
Many Thanks
Regards
Charles Clark
Platesolve
http://planewave.com/downloads/software/
The android bt app for myfp2 is nearly ready for release.
I released the android bt app for the mydewcontrollerpro3 today so I have copied some code changes from that into the myfp2 and just need time to test those changes before release.
there will also be android bt app for the myfocuserpro (v1).
Some people have managed to get the HC06 to work, I never bought one and they never said much about how, so I cannot help there. But most times it comes down to rxd/txd being transposed, wrong baud rate, wrong comport on pc end, or failing to use a voltage divider resistor network for the line going into rxd on the hc05.
Whatever you do, dont start -playing with/changing the firmware, that is sure fire recipe for stuffing things up.
If you are proficient in programming arduino, you can turn debugging on in the firmware and connect the arduino ide to the com port connect via usb to the controller, then use the windows app to connect via bt com port. This way you will see debug messages on the serial monitor which could give a clue as to what is happening.
Last edit: brownrb 2019-05-02
Hi Robert just to let you know I have had a message from eqmod support site informing me that there is an updated version v209 of ascompad setup program I have not tried it yet but I took the liberty of forwarding your findings in my request for guidance itmay or may not have any bearing on it
regards Charles Clark
Hi Charles
Yes, I have just seen it. they do not say what was fixed/changed?
Regards
Robert
I don't understand how that could be as ASCOMPAD doesn't directly open or close any com ports . It is a pure ASCOM client application and only interfaces at an ASCOM level with the ASCOM driver - it ha sno knowlege of how the driver chooses to interface with the hardware. It wites to Connected/Link properties of the ASCOM driver whch has the responsiblility of managing the opening and releasing any COM ports it may use. When disconnecting a driver from ASCOMPAD it will send out a Connected=false and Link=false - if a com port isn't being closed then that surely is a driver issue?
Hi Chris
Welcome. Good to have your feedback. I see you have released an update (no inference intended) and i understand it is being tested by Charles to see if that makes a difference to his situation.
I agree with your notes. What I do not understand is why when used with the previous release of ASCOMPAD we were getting these errors. These errors only seemed to occur with ASCOMPAD and using another client the issues could not be replicated with the same driver. We did test ASCOMPAD with my driver and with the Moonlite driver and both drivers exhibited the same issue.
Now it is entirely plausible that somehow there is something I have coded in the driver that causes this to happen to ASCOMPAD, that makes it stuff up with ASCOMPAD and not others, I do not know. What I do know is that you have a great deal more knowledge about ASCOM that I do and have been doing this much much longer than I have.
I am awaiting to hear back from Charles to see if the issues have gone away. If they have not I will delve into my code and take a much closer look. I do very much appreciate your feedback and response here, it is good to hear from you.
regards
Robert
Hi Robert i have briefly tried the updated version of ascompad and i have found upto now that as long as i connect in relative mode ie enter setup and properties it connects without errors occurring. I have been a bit engrossed at the minute sorting out my bluetooth connection problems, which i now seem to have succeed with. Need to do a few more connection tests on a second laptop that uses a plug in bluetooth adaptor.
I found after taking my pcd board out to check resistor configuration that my focuser would not communicate when trying to upload the firmware. I was getting time out errors.
I finally by trial and error after letting my arduino upgrade libraries and boards (in desperation
) change the processor programming to ATMega328P(Oldbootloader) and it uploaded the program without error. The bluetooth now works.
I can't say i amunderstanding this as previously the old setup before changing seemed to work okay. I am however using two laptops when i was trying to sort out the blue tooth.
Maybe that had something to do with it or maybe I am just confusing my self.
I know need to try the older laptop with the plugin bluetooth module to see if the bluetooth connection works with that as that is the one that i want to use with my mount.
Thanks with all your help much appreciated
Regards
Charles Clark
Hi Robert, second laptop has connected fine with the external bluetooth adaptor and works okay with windows version of myfocuser.
I have tried out ascompad v2.09 and it connects up via bluetooth.
I much prefer this frontend for asompad as i find it more intuitive. I have taken to entering setup to ensure it is starting in relative then connecting after opening properties and seems to be fine.
If i try to go straight to connect it tries to connect in absolute mode i get the message.
Sorry Focuser is incompatible. Absolute requires a position read.
Regards
Charles Clark
Hi Charles
Glad to hear you resolved the Bluetooth issues.
If you get can you please try the straight to connect which gives you the message, but when selecting the ascom driver please ensure trace is checked. The log will be produced in the documents\ascom folder and that could be very helpful if you could do that and post it here. the log will have detailed info on what is coming from the client as well as the responses. This will prove useful in looking at the issue further.
Cheera
Robert
Hi Charles,
With V2.09 you should find a file named "ascom_focuser_debug.txt" in the ASCOMPAD install directory. If you open that file in notepad I expect it shows an error when an attempt to read the stepper position was made - perhaps you could verify that and post it.
If you could then try out ASCOMPAD v2.12 and compare the ascom_focuser_debug.txt contents.
I've put a temporary copy of here:
http://eq-mod.sourceforge.net/files/ASCOMPAD_V212_Setup.exe
..so you can acess it without having to join the EQMOD Yahoo group:
Chris.
Hi Robert, Charles
Yes, I updated ASCOMPAD - the way things work with EQMOD projects is public releases are held on sourceforge whilst development releases are made to the EQMOD Yahoo group. ASCOMPAD had undergone quite a number of development releases (things like dome shutter control added) that had never made it out to a public release. When I saw that folks we having issues I thought I'd might as well put the current development release onto sourceforge. There aren't any specific fixes made with regard to this particular problem but you never know and if I'm to investigate it further I need folks to be using software that is closer to the current development version.
I certainly wouldn't rule out a bug in ASCOMPAD - particularly if the same thing is happening across a number of focuser types. On the EQMOD Yahoo group I'm currently working with another user who is experiencing similar issues with the celestron focuser - so there have been a few more test releases with additional tracing issued in the past few days to that group. I generally prefer to use that group's resources to work through problems before making public releases. Obviously it is hard for me to debug not actually having an actual focuser that shows the problem - all I can do is test against the ASCOM focuser simulator (supposedly a gold standard for focuser drivers) and that doesn't show the issue (but of course it doesn't do serial comms etc).
Immediately after connection (by the link or Connected properties) ASCOMPAD does a series of tests on the driver to establish what type it is so it can adapt its control methods according. For absolute focus control ASCOMPAD needs to be able to read position and so a position read is made as part of this initial focuser driver interrogation. It seems that the celestron focuser is raising an exception to this initial read of position (and sometimes som other properties) and I'm wondering if it the driver/hardware needs some time to settle after the initial connect is made and before the read is made (any thought soon this?) ... anyhow investigations are ongoing and any insights you can offer are most welcome.
With regard to admin rights there is no specific reason I can think of why ASCOMPAD would require admin rights other than the fact it need to be give the same level of rights as the other software in the chain - i.e. ASCOM driver / serial port driver etc.
Chris.