To be honest I don't know. I did not even know that APT has all those cooling options and graphs, thank you for the screenshot above. I am liking the software more and more.
Is it possible just to switch the cooling on and to manually record the values over few minutes. I don't think you need many points to see if there is a difference.
edit: I think I have already fixed the internationalisation bug. If you want I can send the update now or we can do it later, after your tests.
Pat, on which sensor do you see 85 degrees C? The humidity sensor or the cold finger sensor?
How often do you see the reading?
Did you have issues with the old firmware/driver?
Can you disconnect from the camera, then hold shift while connecting in APT and when choosing the camera go to properties and tick "Trace on". That will enable logging. The logs will be saved in Documents/ASCOM folder. Seeing the log when the temperature is not correct may give me a clue...
edit: also does the temperature stay at 85C or does it only show 85C for a second and then go down again?
Pat, on which sensor do you see 85 degrees C? The humidity sensor or the cold finger sensor?
How often do you see the reading?
Did you have issues with the old firmware/driver?
Can you disconnect from the camera, then hold shift while connecting in APT and when choosing the camera go to properties and tick "Trace on". That will enable logging. The logs will be saved in Documents/ASCOM folder. Seeing the log when the temperature is not correct may give me a clue...
edit: also does the temperature stay at 85C or does it only show 85C for a second and then go down again?
i also get sometimes silly readings on CCD temps (eg +60C) but on next measurment it comes back...
Trace on activated, will keep you informed
Edit : btw : Kp = 0.04 seems to be good enough ! my first impression is that when I change it + it gives oscillations and - it 's very long to reach target...
Gilles, the 0.04 value was used in all previous drivers/firmwares. If you are getting a different result now then we have a problem.
I have uploaded a slightly modified version of cam86_view program to the usual place.
You can set the Kp parameter there (change the value in the box and click the button).
If you tick the box "auto temp" (after connecting to the camera) the driver will measure temperature every second and output the value in the info box.
This may help with the testing.
Also if you use this version of cam86_view, can you watch and see if you get temperature glitches.
Gilles, the 0.04 value was used in all previous drivers/firmwares. If you are getting a different result now then we have a problem.
I have uploaded a slightly modified version of cam86_view program to the usual place.
You can set the Kp parameter there (change the value in the box and click the button).
If you tick the box "auto temp" (after connecting to the camera) the driver will measure temperature every second and output the value in the info box.
This may help with the testing.
Also if you use this version of cam86_view, can you watch and see if you get temperature glitches.
Thanks
Don't worry : i had overshoots before too, and i played with cooling power min/max.
Now this is much better, but it will be very long to find good values !
I will play with your new soft in a few hours, need to clean the house atm...
Have a look at this : http://www.webastro.net/upload/minim...1489834743.jpg
I have seen the image already, I am closely following the webastro forum. Lots of interesting stuff happening there
My changes to the viewer software are really only useful for this test. It was a quick fix and there is no error checking at all for the parameters. But it can be useful to see if you get temperature glitches as well. If you could just run the "auto temp" option and leave it for a while and then copy/paste the temperature output, I could see if there are any glitches there as well.
The viewer is not using the ASCOM driver so it is different.
But I have a feeling that the temperature glitches are caused by the noise from TEC. Did you have the temperature glitches before this driver/firmware?
Luka, the 85 ° remained a few seconds, it is the 18bs20 probe, as Gilles the 0.04 works well but it is much longer than before.
It seems to me that I had activated the "trace on", or it finds the newspaper to be sure.
Another thing, since you look at Webastro, you can come and make a little hello there
Gilles, I finished parts of your request, see the new viewer in the GD (same revision number). Missing are cooler min and max which need to be added to the cam_view code. The data is currently dumped into the text box with comma separated columns so you can copy/paste into notepad and save as CSV, which can then be imported into a spreadsheet for plotting etc. I am thinking of making logging data go into a file but this will have to wait until tomorrow, too tired now, it was a BUSY day. All source code is in source code/luka folder.
I never developed in Delphi before Cam86 so making any changes is slow.
Also I have uploaded the new driver, v0.6.6L. This should (hopefully) fix the internationalisation issue with , or . for numbers. Can you please test.
Pat, the old cam used the same value of 0.04. If it is slower now then I have stuffed up something. Will need to investigate...
Gilles, I finished parts of your request, see the new viewer in the GD (same revision number). Missing are cooler min and max which need to be added to the cam_view code. The data is currently dumped into the text box with comma separated columns so you can copy/paste into notepad and save as CSV, which can then be imported into a spreadsheet for plotting etc. I am thinking of making logging data go into a file but this will have to wait until tomorrow, too tired now, it was a BUSY day. All source code is in source code/luka folder.
I never developed in Delphi before Cam86 so making any changes is slow.
Also I have uploaded the new driver, v0.6.6L. This should (hopefully) fix the internationalisation issue with , or . for numbers. Can you please test.
Pat, the old cam used the same value of 0.04. If it is slower now then I have stuffed up something. Will need to investigate...
Great, thank you very much
New Ascom driver is ok with international stuff
Hi Luka,
it's now late also here in France, but i want to share this with you :
Thanks to your code i've started to write a new tool to tune parameters of regulation.
This is early code, just to show how to use cam86ll.dll in delphi
(i've just put it on GD\incoming)
That prevents to rewrite low level functions, it's just fast Delphi coding.
With it I intend to log all parameters in a grid, easier to export in Excel
Maybe i'll try to add live graph, or job sequence, like "play with Kp=0.01 during 15mn then stop cooling until DHT temp = CCD temp, then restart cooling during 20mn with Kp=0.02", and so on
Just to say I think i can do that, don't spend time on it : on your side stay on difficult stuff, you've already made so much !
Gilles, I am interested to see why the uploads does not work. I put a test.txt file in the folder. Can you see it?
Using the DLL is a great idea. Do you want me to add other functions to it or to the firmware? For example, some parameters can be only set but not read.