HelgeMK wrote: Hi Craig,
I am not sure if useful, I followed those instructions when "rebuilding" the moonlite focuser - see this link:
github.com/Hansastro/Focuser
In the library for the LM335 (lm335-cpp), which is used here as sensor, the following formula is applied (to the end of the lib), maybe you can leverage:
return (500.0*analogRead(this->aquisitionPin)/1024.0) - 273.15;
Be careful with the formula. I remarked that the temperature is not quite right. I think the factor 500 come from some try and error. It is something in my list of thing to improve. (I am the author of the library)
The conversion from Celsius to Hex is not very difficult. You can find it in the github repository in the Moonlite.cpp file. At the end. For the temperature the function "convertLongToChar" is what you looking for probably.
What happened with negative value... I am not sure of that... Check the function before using it. I have to verify that. I don't remember well.
For your question about how to code 20.5 in signed hex. There is a trick. In the protocol such values are not transfered as they are but they are multiplied by 2. Then you don't have to transfer a floating point value. That explain why the display is always with round or .5 values and nothing in between. (See the file Focuser.ino line 106)
The compensation is not used to calculate the temperature. This value is used to readjust the focus when the temperature changes. You focus, note the temperature and the number of steps of the focuser. You wait some times until the temperature is not the same. You refocus and note again the temperature and the number of steps. You know the differences for the temperature and the position between the two measures and you can calculate a step/degree value. This is the compensation value.
Jean-Phi
Read More...
Hi,
I think about how to automatize my installation and I found in Ekos an option to close a cap to perform the Dark/Bias and Flat field.
I attached a screenshot of the windows for more clarity.
My question is quite simple: How does it work? Which drivers are used?
I didn't find any topic on this subject.
I plan to add a servo and a flat field screen. Is it possible to use a custom driver for that? (I plan to use an Arduino)
Best regards
Jean-Philippe
Read More...
Few weeks ago I found my old Toucam Pro. I just tried it again after years! It works!
I recorded a ser file and it is in black and white when I open it with Registax.
The Video4Linux driver work for this cam in YUV format. To have some RGB a convertion should be done, I suppose that here the images are stored in the ser file have only the luminance layer (It is the green channel which has the resolution of the sensor). The red and blue channel are 4 time smaller.
Jean-Philippe
Read More...
Thanks for the reactivity!
Just a newbie question: The source code is recompiled every night or we have to recompile kstars by ourself?
I just did an
apt-get install kstars-bleedingJean-Philippe
Read More...
After reading your thread,I confirm we have the save issue.
Seems to be not linked to the CCD driver.
Jean-Philippe
Read More...
Hi!
I am facing a strange issue with the guiding: When I click on "Capture" on the guiding tab, the pictures are taken continuously... With 1 second exposure, one picture is taken every second without end. i cannot stop it... (The concequence is that the guiding does not work.)
I use a Kubuntu 16.04 in a virtual box and a Rasperry PI as indi server. I installed all this week-end. Kubuntu, Kstars-Bleeding, the last indi server for Raspberry PI.
Is somebody else has the same issue?
I tried it on the simulator and have the same issue.
Here the module I use normally: EQMod (For a AZ-EQ6), V4l2 CCD (for a DMK41), gphoto (For a Canon 1200D), Moolite (for a self-made focuser) and Joystick.
Thanks!
Jean-Philippe
Read More...