We are getting a bit of subject but I think its a matter of developer choice. I applaud those open source developers who build open source code, it is often a collective endeavor that benefits a lot of people and provides the reward of contribution to others. If they ask for contributions that is reasonable, but I assume not required.
On the other hand their are commercial software developers and as a senior executive in a large database company; a Network software company and a games software company we made sure we had robust licencing strategies that ensured for the most part we got paid. We also incurred high costs in commercial promotion, support, consulting etc. Sometimes we got ripped off, but it was a small percentage . If it got out of hand we took legal action.
So you really have to decide what sort of developer you are, but don't try and go into the commercial world with an open source architecture and without commercial protection.
As for the consumer they too have a choice you can buy a commercial product like APT or Maxim or with a bit of effort go the open source route with EKOS/Stellarmate. Neither is more correct.
I had a similar problem when my Canon 1100D worked fine but not a later model. I found the answer was to use the indi-gphoto driver.
I also used the Stellarmate download with an RPI. I already had. Its a very comprehensive build and well documented. I rekon its saved me much more than $49 of time. I did try Astroberry about 9 months ago and found it lacking. Once you have Stellarmate installed you can keep it up-to date with the standard EKOS updates.
I built the -https://github.com/Hansastro/Focuser which uses the Moonlite protocol and runs on an Arduino. It works very well. You do need a decent stepper motor.
I currently run it on my ES 102 but have also used it on another 90mm scope.
See my comments and schematic at:
I am trying to work out the best way to take flats with my Canon 450D Astro Modified. I have tried just using AV mode to get the exposure and then using it in EKOS but flats seem slightly over exposed at 1/125, ie .008 secs.
So I wanted to try the calibration routing in the EKOS camera module based on a more accurate ADU.
EKOS calibration only works with FTS files not the Canon raw CR2. So I get EKOS to capture in that. The ADU target I use is 7500 based on a search of forums . So I put that into the calibration setting and start with .008 secs and it ends up at .029 secs .
Can I just transfer that value when taking CR2 Flats? Or as I will be using DSS for stacking am I better off using FTS flats (can I mix CR2, lights, Darks with FTS flats?)
My Flat illumination is an LCD panel on my shed observatory wall, plus I also stretch a white cloth over the lens to increase diffusion.
Or am I doing it all wrong?
Any advice much appreciated.
any view on this extra log? I looked at it and I'm not sure that I switched on enough options. Please let me know if it needs to be more helpful.
Mount currently away being tuned so cannot repeat for a while.
Sorry, try this one
I think the equmod driver crashed because the mount was not switched on after I started Indi.
I re-started Indi at least once after that. My main imaging sequence was from around 18:40 to about 22:30 when I was attempting to get 2 hours worth of 30 sec exposures (not 60 as stated before) with all the spoiled frames I ended up collecting about 270 exposures.
During this time I had to pause and re-start several times. The gap was not entirely consistent, but around 40 exposures. None of this affected the exposure sequence No other constraints were set. No guiding.
You say that once the eqmod driver crashes, it doesn't output debug logs anymore. If I try and repeat this exercise, will re-starting indi re-start logs, or do I need to re-boot the Pi?
I set up a job to take 240 x 60 secs exposures with my ZWO ASI178MC, with a 3 sec pause between each. Although I was testing guiding at the start of the session, all of this sequence was unguided.
After around 40- 50 exposures mount tracking switched off with no intervention. This happened several times. I was monitoring progress via VNC, .so I could see the lights suddenly had long star trails and tracking was "off".The job kept running.
Each time I re-started by pausing the exposure job; switching tracking on again, using "align-load and slew" against an earlier exposure and then re-staring the exposure job. On one occasion I completely shut down Indi and restarted, but the problem persisted. Eventually I got all my exposures but I had to constantly monitor the job and re ready to re-start.
My mount is an EQ5_pro controlled by EQMod.
I am running Kstars V3 build 2018-10-13T19:26:36Z
Any idea what is happening.