Ferrante Enriques created a new topic ' Unguided RMS?' in the forum. 1 week ago

I'm trying to benchmark unguided imaging with my mount. In the guide module, with internal guider, I need to calibrate and then disable RA & DEC guiding to have the drift plot.
Is there any way to avoid calibration and just start plotting the drift? Is PHD able to do this?

thanks

Read More...

Ferrante Enriques replied to the topic 'ASI Camera - Gain/Offset/x-Bit' in the forum. 2 months ago

It could be very useful to have a comprehensive ASI camera guide as Jasem suggested. Think I'm not good enough to write it but I can contribute with my personal experience on a specific camera (ASI071 pro).
- My setup is a 115/800 f/a 6.95 apo refractor on a HEQ5 mount.
- Added a field flattener and LP filter. No focal reducer.
- Cooling always at -10. It's a low noise camera, there's no real gain to cool it further (as to specs on ASI website, astronomy-imaging-camera.com/products/as...ameras/asi071mc-pro/ ).
- Tried unity gain at first, then settled on 240 gain with 300s exposures . It doesn't seem to saturate too much (see attachments for M101, M81. deepsky objects that you can easily compare with yours). Probably would change for M31 or M42.
- Ignored offset as another owner on Cloudynights says it's now fixed at 50. Not really sure about that.
- Beside gain I left all other controls to their default values.

Overall I'm satisfied with these settings but please give me your opinion, there's always a benefit in trying different approaches.
Ferrante

attachments:
- ASI071 'Control' tab from Ekos/INDI
- M81 single raw 300s exp @gain 240 + histogram
- M101 single raw 300s exp @gain 240 + histogram
- M101 single debayered 300s exp @gain 240

Read More...

Ferrante Enriques replied to the topic 'ASI Camera - Gain/Offset/x-Bit' in the forum. 2 months ago

on another forum I asked about suggested ASI071 Pro gain/offset settings. Reply was:
"The offset for the Pro is now fixed in firmware and cannot be changed. I have heard that it has been fixed at 50.
When I first started using my original ASI071MC I used the unity gain, but I had to use very long exposures to get histograms like I was accustomed to seeing with my DSLR using an ISO of 800-1600. After researching the gain setting on the 071 I settled on gains of 200-300 as being roughly equivalent to ISO 800 on my DSLR. I eventually adopted a gain of 200 as being standard. "

Read More...

Ferrante Enriques replied to the topic 'Custom driver for AAG Cloud Watcher weather station' in the forum. 2 months ago

Ok, pull request created: update weather watcher driver #583

Read More...

Ferrante Enriques replied to the topic 'Custom driver for AAG Cloud Watcher weather station' in the forum. 2 months ago

hi Jasem,

I thought it was more generic and useful to let the user choose and customize his own keywords. Eg to specify that in the file I have 'rain' instead of 'precip'.
If you have time please take a look at the files attached (not confident to do any commit) and, renamed as .txt.

Next I would like to let the user choose the separator instead of =.

About Brightness I think that Lunatico measures the sky IR temperature. Thus different from SQM.

ferrante

Read More...

Ferrante Enriques replied to the topic 'Custom driver for AAG Cloud Watcher weather station' in the forum. 2 months ago

Almost everything is already ok!
Made a test with simulators (Telescope, CCD, Guide, Focuser, Dome) and Weather Watcher.
- Reads correctly wind, gust, precip, temperature. Keywords are different from the one in the Solo file. AAG driver needs exactly those names as keywords? else it would be easier to keep the one in the file (eg rain instead of precip).
- All warnings are working ok: update the weather_status in the 'main control' tab
- I also tried a scheduler sequence and increase the wind step by step. Dome / Mount were correctly parked when it reached the limit!
- Tried to enable debug but it always shows disable. think is a minor issue.
- works for both file and URL (tried with aagsolo.lunatico.es:10800/cgi-bin/cgiLastData ). But as keywords are different I used a modified file for testing.

I will keep on testing on simulators but hopefully will try in my real observatory as soon as the moon and clouds will give a chance.
It would be great to have brightness / light parameter too in a next version.

Thanks again for the great help in such a short time!
Ferrante

Read More...

Ferrante Enriques replied to the topic 'Custom driver for AAG Cloud Watcher weather station' in the forum. 2 months ago

fantastic! Thanks Jasem. I will give it a try right now and give you feedback as soon as possibile.

Read More...

Ferrante Enriques replied to the topic 'Custom driver for AAG Cloud Watcher weather station' in the forum. 2 months ago

To make it even more generic it could parse a local file or an url.

In the meantime I found that switch is a parameter to let other software to control the weather station. I would say it's not useful for this driver .

Looking at the historical data it seems that safe/unsafe is not boolean as in the docs.

2018-04-27 18:59:53|12.5|12.7|5504|10|1|0|0|64|5.9
2018-04-27 18:57:57|12.5|12.7|5504|10|1|0|0|64|5.9
2018-04-27 18:55:53|12.6|12.7|5504|10|1|3|7|64|6.0
2018-04-27 18:53:56|12.7|12.6|5504|10|1|2|5|63|5.8
2018-04-27 18:51:53|12.8|12.8|5503|10|1|1|4|63|6.0
There are no column headers but comparing to LastData, safe / unsafe should be the 4th from right. Values are 0,0,3,2,1..strange behaviour for a bool...hope I'm wrong
I will contact Lunatico and ask for their help.

Ferrante

Read More...

Ferrante Enriques replied to the topic 'Custom driver for AAG Cloud Watcher weather station' in the forum. 2 months ago

Thanks Jasem!
My best guess about those parameters is:
-Light is sky brightness in a scale from 0 (day light) to a custom value like 60000 on Lunatico website. From the online help: "The DARK condition has been defined for values greater than 2100 (K ohms), the LIGHT condition for values ranging between 2000 – 6 (K ohms), whereas the VERY LIGHT condition for values ranging between 6 – 0 (K ohms)". So 60k is max scale.

-safe is a bool where 0 is the unsafe condition based on custom thresholds set on other parameters of the sensor like rain, brightness etc. And of course 1 is the safe condition where observation is allowed.

- switch is not documented! At least not under this name.

Some additional resource:
- aagsolo.lunatico.es:10800 Lunatico test device.
- aagsolo.lunatico.es:10800/cgi-bin/cgiLastData Lunatico weather station data.
- aagsolo.lunatico.es:10800/cgi-bin/cgiHistData Lunatico last 48hrs data
- lunatico.es/aagcw/enhelp/ AAG cloud watcher windows client documentation
- attached the Solo (web interface) user manual

Hope that these infos are clear enough. Sorry but I don't have access to the device itself to test parameters and configurations.

Read More...

Ferrante Enriques created a new topic ' Custom driver for AAG Cloud Watcher weather station' in the forum. 2 months ago

Hello, I have my telescope hosted in a remote facility on the Alps that provides weather status report (based on AAG Cloud Watcher) locally via an URL as the device is not USB connected to my RPI3. The output itself is a text file (see 1st attachment) updated every 5 sec.
The standard AAG Cloud Watcher driver needs a USB connection to the weather station. That's not my case, so I'm developing a new driver that reads and parses the text file (btw if someone already did something similar please send me source code as C++ is not my primary language...).
Beside some useful information about the weather the main info in the file is a parameter that sums up all weather conditions: safe (0|1). If it's zero, that would trigger a shutdown procedure and/or prevent sequence startup.

Example 5 in the development tutorial shows how to snoop weather alerts (see Tutorial5.png) from a dome driver but I would rather expect to see this flag as Standard Property.
That would allow for example to read this parameter from any client, namely the Scheduler. While in the example it is bind to a specific client and that's the opposite of what standard properties are designed for.
But in the standard properties list, under General - Atmosphere section there are: Temperature, Pressure, Humidity. No Rain, Safe, Weather Alert or something that sounds like a danger.
Am I missing something?

Or, same question from another perspective: How the weather flag on the Scheduler screen (see Scheduler.png attachment) works? The decision for starting the shutdown procedure triggered by the weather flag is based on which information?

As an alternative option to driver development, it would be nice to have a 'Weahter Scripting Gateway' implementation like in Dome devices.

One last advice: would it be better to develop as 3dparty driver or bundled in libindi? As a first driver attempt I would go for libindi.

Thanks for helping!
Ferrante

Read More...

Ferrante Enriques replied to the topic 'QHY 5L II connection problem. Again' in the forum. 2 months ago

Your issue seems not related to the one discussed here. Whenever I have a timeout error I power off/on the camera and restart indi. Usually it is sufficient to fix the issue.
Yesterday a new release was available, have you tried to update?
If this won't fix it I suggest you post here your log file.

Read More...

Ferrante Enriques created a new topic ' Kstars crashes when Sesto Senso focuser succeeds.' in the forum. 2 months ago

Sesto Senso motor worked fine since the beginning but on last two nights before reaching focus position Kstars crashes.
Quite sure is the client because when I connect back all the driver are still working, moreover dmesg shows:

[15217.571387] kstars[5804]: segfault at 0 ip 000055e28d935707 sp 00007ffc1f00e550 error 4 in kstars[55e28d647000+875000]
And the indi logs are not very detailed about this (see attachment).
Does anyone experienced the same?

Read More...

Ferrante Enriques replied to the topic 'QHY 5L II connection problem. Again' in the forum. 2 months ago

@bowmangotti: in the meantime, as Jasem implicity suggested, using compressed memory works fine.
Use this script: github.com/novaspirit/rpi_zram

Read More...

Login

3rd Party

Choose from the numerous 3rd party INDI drivers to suit your needs!

Got Problem?

Check out the FAQ, the forum, and the bug tracking system to resolve any issues you might have!
You can also subscribe to INDI newsletter and development mailing lists to get the latest updates on INDI!