CLICK ON THESE AFFILIATE LINKS TO SUPPORT THE CHANNEL: * Agena Astro: bit.ly/487tmnj * High Point Scientific: bit.ly/49z9qdv * Amazon: bit.ly/darkskygeek-amazon-affiliate-link
Oh! I had that 'issue' time ago, couldn't find a way to use my PegasusAstro Powerbox temperature probe to trigger the AF routine. The trick you implemented is very interesting. However, I currently trigger AF after NINA's HFR trend analysis and it worked fine to me... but I'll give a try. Thanks for releasing such amazing content and DIY projects, it is a flow of fresh air for the astrophotography community!
Just thinking out loud here (so to speak). I don't have a commercial power distribution box nor a temperature probe for my ZWO EAF, but I do have some temp. and temp/humidity probes from previous (non-astro) related projects. Perhaps a probe with an Arduino could be made to serve as the "other device" that reports to the Virtual Focuser ASCOM driver... Hmm... (still working on the OAG focuser adapted to my guide scope as well.)
Yes, that would work! You would need to write an ASCOM driver for your device that implements the IObservingConditions interface, but yeah, it would be 👌🏻
This is really a great solution for such common problem! I will definitely have a look! I'd suggest to put the temperature probe into contact with telescope metal body (or possibly focuser metal parts) - there is definitely a lag between ambient temperature and metal hardware. But focus position depends on the thermal expansion of telescope structure - which has typically strict relation with the temperature of that structure.
In my experience, it’s not so much the metal shrinking that causes the focus point to change. It’s the shape of the lens elements! Therefore, you can just let the temp probe dangle and it will be fine 😉
What are you using to remotely connect to your dew heater or powerbox? I have a Pegasus dew heater but it does not have wireless capabilities that I am aware of.
I’m not sure I understand. Between my Pegasus Astro Pocket Powerbox Advance and my dew heater band, there is an electrical wire. Then, between my Pegasus Astro Pocket Powerbox Advance and my mini computer, there are 2 wires (an electrical wire to power the mini PC via 12V DC, and a USB 3 cable). However, I remotely connect to the mini PC from my iMac (located in my office, inside my house) using Microsoft Remote Desktop. Does this answer your question?
I 'have a ZWO EAF and have been using NINA for temperature focus compensation since you introduced your virtual driver. I installed the new driver, and it worked as before when using the ZWO temperature sensor. But when I select the Pegasus Astro PPBAdvance and click the power icon I get "ASCOM Driver Error Unable to connect to DarkSkyGreek's Virtual Focuser Ascom Driver. Reason: Cannot connect to ASCOM.EAF.focurser". Switching back to the ZWO Focuser (1) as the source for temperature and focuser connects.
Yup, I know about that, and there is a workaround. I will try and document it in the repo. This has to do with Pegasus Astro Unity platform, which seems to be finicky…
This seems to be a one time hack. After I did the work around I can power cycle and reboot the pc and NINA will uses your driver driver for the focuser and read the temperature from the Pegasus Astro.
Great video, but I am a little confused, i use an older Pegasus focus motor, not the focus cube, just the motor with the controller built into my Pegasus UPB, and the motor has no temp probe, BUT I have the option of focus temp compensation without the use of your driver and with no temp prove, as it automatically uses the temp probe on the Pegasus hub for this, all in NINA, so I don’t see any benefit of you driver in this case…or am I missing something….🤔🤔
I don’t know anything about the temperature compensation built in to some focusers. But I would venture a guess that it is akin to guiding with the ST4 port, i.e. too limiting, and having software control the hardware with advanced algorithms provides more flexibility and is more future proof. CS!
@@darkskygeek well there is none built into this focuser that was my point, it just uses the temp probe that is connected to the Pegasus UPB Hence why asking if that is not just the same as using your driver I am confused
Ah, got it. Well, if Pegasus did that kind of custom integration, then yeah, that specific part of my driver is not strictly necessary. That being said, the averaging of temperature values over a 2-minute rolling window is absolutely critical, regardless of which temp sensor you are using. It really increases the accuracy! HTH
Fier que les deux YTeurs qui sortent un peu des classiques et brillent en termes de vulgarisation soient français ! Mais l'astronomie reste universelle ;-)
I have a wifi connected focuser, which sometimes disconnects randomly and it's disconnected until I click on "connect focuser" manually. This can be very annoying when it happens when I am not around. Can the virtual focuser supervise or maintain the connection to a such focuser by reconnecting automatically ?
Hello, I've just downloaded the virtual Focuser ASCOM driver to use with my ZWO EAF and PPBAdvance for temperature readings. When setting this up in NINA, I see the description correctly, but the temperature reading of the focuser does not match the temperature from the PPBAdvance and still seems to be pulling from the EAF. Am I missing something? Thanks
You are not missing anything. I have seen this once, and so I think there is a subtle bug in my driver which is exacerbated by the Pegasus Astro Unity platform (which has caused me a lot of issues, compared to their older ASCOM drivers). Thank you for filing an issue, I will take a look. Thanks!
In the case of a Q-Focuser that has an included temperature sensor that constantly shows -100C plus or minus 15C, is your recommendation just to use a different device to use focus temp compensation? No way to fix, just buy more gear?
CLICK ON THESE AFFILIATE LINKS TO SUPPORT THE CHANNEL:
* Agena Astro: bit.ly/487tmnj
* High Point Scientific: bit.ly/49z9qdv
* Amazon: bit.ly/darkskygeek-amazon-affiliate-link
Oh! I had that 'issue' time ago, couldn't find a way to use my PegasusAstro Powerbox temperature probe to trigger the AF routine. The trick you implemented is very interesting. However, I currently trigger AF after NINA's HFR trend analysis and it worked fine to me... but I'll give a try. Thanks for releasing such amazing content and DIY projects, it is a flow of fresh air for the astrophotography community!
Just thinking out loud here (so to speak). I don't have a commercial power distribution box nor a temperature probe for my ZWO EAF, but I do have some temp. and temp/humidity probes from previous (non-astro) related projects. Perhaps a probe with an Arduino could be made to serve as the "other device" that reports to the Virtual Focuser ASCOM driver... Hmm... (still working on the OAG focuser adapted to my guide scope as well.)
Yes, that would work! You would need to write an ASCOM driver for your device that implements the IObservingConditions interface, but yeah, it would be 👌🏻
Awesome. I had spoken with Pegasus about this very thing. What you have done adds a ton of flexibility when using NINA. Thanks
This is really a great solution for such common problem! I will definitely have a look!
I'd suggest to put the temperature probe into contact with telescope metal body (or possibly focuser metal parts) - there is definitely a lag between ambient temperature and metal hardware. But focus position depends on the thermal expansion of telescope structure - which has typically strict relation with the temperature of that structure.
In my experience, it’s not so much the metal shrinking that causes the focus point to change. It’s the shape of the lens elements! Therefore, you can just let the temp probe dangle and it will be fine 😉
@@darkskygeek hm, OK. I have very little experience with refractors.
Great timing. I just got my Dark Sky Geek OAG focuser which I'll be using with a SW Evoguide 50. Thanks JC!
This is awesome - thanks! This should let me use my mount's ASCOM weather station (BME280 via OnStep) for temp compensation.
Amazing projects as always! Love the OAG focuser too; just waiting on my PCBs! Planning on using one for my guide scope on my HyperStar setup.
you're a legend for this
Great stuff. Will really give this a test out over my next few imaging sessions using APT & maybe post a full report on my channel. Cheers.
Awesome project! Thanks for creating useful open source code for the astrocommunity:)
Just AWESOME... as usual ;)
5:38
I also use the same PPA. May I know where to buy the dovetail holder with the PPA in video?
You must be a fairly new subscriber to my channel 😁 The answer is in this video: ua-cam.com/video/sFOrMUbYT4w/v-deo.html. Clear skies!
@@darkskygeek
Oh~~!! Thanks.
Well done!
What are you using to remotely connect to your dew heater or powerbox? I have a Pegasus dew heater but it does not have wireless capabilities that I am aware of.
I’m not sure I understand. Between my Pegasus Astro Pocket Powerbox Advance and my dew heater band, there is an electrical wire. Then, between my Pegasus Astro Pocket Powerbox Advance and my mini computer, there are 2 wires (an electrical wire to power the mini PC via 12V DC, and a USB 3 cable). However, I remotely connect to the mini PC from my iMac (located in my office, inside my house) using Microsoft Remote Desktop. Does this answer your question?
I 'have a ZWO EAF and have been using NINA for temperature focus compensation since you introduced your virtual driver. I installed the new driver, and it worked as before when using the ZWO temperature sensor. But when I select the Pegasus Astro PPBAdvance and click the power icon I get "ASCOM Driver Error Unable to connect to DarkSkyGreek's Virtual Focuser Ascom Driver. Reason: Cannot connect to ASCOM.EAF.focurser". Switching back to the ZWO Focuser (1) as the source for temperature and focuser connects.
Yup, I know about that, and there is a workaround. I will try and document it in the repo. This has to do with Pegasus Astro Unity platform, which seems to be finicky…
@@darkskygeek Your work around in the repository fixed the problem.
This seems to be a one time hack. After I did the work around I can power cycle and reboot the pc and NINA will uses your driver driver for the focuser and read the temperature from the Pegasus Astro.
Great video, but I am a little confused, i use an older Pegasus focus motor, not the focus cube, just the motor with the controller built into my Pegasus UPB, and the motor has no temp probe, BUT I have the option of focus temp compensation without the use of your driver and with no temp prove, as it automatically uses the temp probe on the Pegasus hub for this, all in NINA, so I don’t see any benefit of you driver in this case…or am I missing something….🤔🤔
I don’t know anything about the temperature compensation built in to some focusers. But I would venture a guess that it is akin to guiding with the ST4 port, i.e. too limiting, and having software control the hardware with advanced algorithms provides more flexibility and is more future proof. CS!
@@darkskygeek well there is none built into this focuser that was my point, it just uses the temp probe that is connected to the Pegasus UPB
Hence why asking if that is not just the same as using your driver
I am confused
Ah, got it. Well, if Pegasus did that kind of custom integration, then yeah, that specific part of my driver is not strictly necessary. That being said, the averaging of temperature values over a 2-minute rolling window is absolutely critical, regardless of which temp sensor you are using. It really increases the accuracy! HTH
Good job..Thank You..
Fier que les deux YTeurs qui sortent un peu des classiques et brillent en termes de vulgarisation soient français ! Mais l'astronomie reste universelle ;-)
I have a wifi connected focuser, which sometimes disconnects randomly and it's disconnected until I click on "connect focuser" manually. This can be very annoying when it happens when I am not around.
Can the virtual focuser supervise or maintain the connection to a such focuser by reconnecting automatically ?
Ah, yes, that could be another use case for it. However, without that equipment, it would be impossible for me to implement that functionality.
Hello, I've just downloaded the virtual Focuser ASCOM driver to use with my ZWO EAF and PPBAdvance for temperature readings. When setting this up in NINA, I see the description correctly, but the temperature reading of the focuser does not match the temperature from the PPBAdvance and still seems to be pulling from the EAF. Am I missing something? Thanks
You are not missing anything. I have seen this once, and so I think there is a subtle bug in my driver which is exacerbated by the Pegasus Astro Unity platform (which has caused me a lot of issues, compared to their older ASCOM drivers). Thank you for filing an issue, I will take a look. Thanks!
@@darkskygeek great, thank you!
See my comment in the issue you filed. It should be fixed now. Thanks!
@@darkskygeek Tested and confirmed its working now. Thanks for the quick fix.
Sweet! And thank you so much for your donation! 🙏🏻
In the case of a Q-Focuser that has an included temperature sensor that constantly shows -100C plus or minus 15C, is your recommendation just to use a different device to use focus temp compensation? No way to fix, just buy more gear?
If your focuser temp probe is that far off, return it (if it is still under warranty) and have them fix it or send you a new one.
Great addition. One more wire gone...
Thank You for your Channel and hard work! Being Ascom compatible should work with other Astro imaging programs?
Absolutely!