Hi,

The final story, in case anyone else run into same trouble, it was a hardware problem. When oppened the case of the carousel and plug it to PC running ASI Studio and selected it, it initially sounded a high pitch tone while initialization tried to move the motor but with no movement of the carousel (that was yesterday night)

This morning, after two coffees , I removed the only 31mm filter I had with mask (rest of the filters are mounted), thinking that the previous time I touched it I did something wrong. I tried again and it worked!!

Little video:

Hi!

Well, Tried with ASIStudio and got more information. It seems something is preventing the wheel to move. I recall having openned and cleaned filters last time (2 months ago! ! )

I'll open the wheel and check for easy movements, too tighten screws ... as ASI Studio states:

"Initialization failed. The carousel is slipping of blocked. There is a posibility that the space between motor shaft/stalk and carousel might too loose or too tight, or the O-ring is damaged or the central fixing screw too tight"

Screenshots:

1st, upon connection:

Hey!

Confiig files deleted. It did recreate them when running Kstars again but it did not help. It does not change the filter (it replies with error):

Hi folks!

I'm afraid I'm stucked with the same error. My ZWO EFW (previously ASI EFW) seems to connect Ok but fails to change the filter. I've tried different cables, and with compiling myself indi-core/ indi-3rd-party drivers, changing the Initial filter set in config file (initially set to 0, but driver replies valid range from 1 to 8 ). Nothing helped so far.

Here's what debug shows upon initialization:

Thank you John, Nou.

I took into account your remarks, and I believe I reached a non-textbook-orthodox-solution, at very least, it seems persistant through various autofocus procedures with different filters. Nevertheless, I'll continue studing it since this is much deeper as I thought, considering John's remarks.

I measured microns/tick and it is 0,7636 microns/tick. My resolution is 0,96 arcsec/pixel with a 203/800 Newtonian using ASI1600MM (sensor with pixels of 3,8microns and 4656x3520) I believe I also introduced wavelengths by filter (roughly)

I'm sorry but I skept what advisor propose me: 18 ticks with x5 multiplier. I went to 75 ticks initial step with No OverScan and no multiplier because I changed the algorithm to use to Polynomial and increased tolerance to 10% (instead of 5%, I tested with 20% and 10%, I can imagine the lower the better focused image) Seeing and temperature difference of the primary and ambient is something that should be seriously considered. I could say before that it was important, now I believe is critical!

You can see all parameters below. Like I said, solution is not orthodox (I ignored advisor) but it seems to work so far.

I'll keep testing and improving my knowledge!
BTW: Among the screenshots there is the solution autofocus found for L, Ha, Oiii & Sii. Next step I'll try the "Offset Generator" to put more time on imaging and less on focusing.

Hi,

(sorry, yesterday was impossible)

Attached ScreenShots of my configuration for Autofocus module. I simply manually drove to optical good focus (not perfect) and tryed with Luminance...

I also have bunch (56- compressed about 760MB) of autofocus-frames 32MB each... (iI'll try to batch convert those to 8 bits and try to upload later if need it)

Behaviuor was as described before: It reaches perfect focus but it continues to perform/evaluate on more different positions. it does stop nor recognizes focus) Curious as it could be, I finalized it and manually reach again autofocus which happened to be at - 2xInitialStep (it started at 8.535 ticks, after cancelling the process it was going no where, manually focused again at 7.535). I could of course have backslach in my optical train, but I doubt it could be as much as 1000 ticks. I sincerely do not know.

Hope you find what the problem is.

Many thanks in advance for your help.

Jason

Hi John!

For now I only have few "autofocus_frame_*" frames. No screenshots and log data yet. I'll try to get everything packaged and have it shared it with you.

Probably tonight (my night @ GMT+2)

Until then, thank you very much!

Read More...

Hi! I feel aliviated that at least somelse is experiencing same "Focus successfull according to Ekos but the stars are football ballons!!". In my case some times it also reaches a perfect solution but it does not recognize it and it continues back & forth trying to get a good solution and got ballons as stars.

I haven't changed my equipment since previous versions of Kstars. I miss the times when it beatifully reached good solutions on previous Kstars versions (much less complicated with options which tryed -unsuccesfully- to add better focus functionality if it only worked! - i.e: This "locked filter & offsets to the other filters from the locked one" is a pretty good idea. As the autofocus function is not working - or I don't know how to get it working- in 3.6.7, there is no point to calculate offsets. Pity!-)

If I could be of any help sending logs/autofocusframe pics, or following any instructions to get real data to solve it, please ask.

Jason

Read More...

Hi!

For the sake of closing my reported issues with ASI1600 & AS462MC as guider...

Yesterday I was able to nicely have indiserver recognize both cams at the same time connected to a feeded HUB and HUB to RPi4's indiserver.

I IMG-toasted a new SD card and started configuring everything from scracth. I'll move to SDD shortly and see what happens (speed x 8 !!) I also used "aliasses" for cameras.

At least now I have an working SD with Astroberry 2.0.4 and a lowenergy-consuming-PC W10 with Kstars/Ekos 3.6.0 connecting to RPi4.

Cheers & clear skies!

Jason

Read More...

Hi Wes,

From a completely newbie:

I'm having the same nightmare trying to recognize at the sametime both ASI1600MM and ASI462MC for guiding, connected both to same powered USB 3.0 HUB. If connected individually, ASI1600 is recognized by Ekos connecting through indiserver (only one ZWO COM driver with same default executable file indi_asi_single_ccd); while asi462MC sometimes connect some others don't.

I am even so desperate as to pull some github code for new driver asi_ccd (from here: github.com/indilib/indi-3rdparty/tree/master/indi-asi) and try to compile it. Thinking outloud, this branch's description would definetively help me by associating driver with serial number for the specific camera so they do not get entangled.

RPI's OS nicely detects both cameras as 'lsusb -v' comand lists, so my amateur's though is that the problem could be in indiserver and drivers selected for ZWOs cams (or even in the fifo pipeline defined) I also tried running a different indiserver (only for guiding cam) with different ports/pipeline etc and id did not work.

Anyway, Could you please tell me if you could guide normally (guider cam connected through main camera) and all options of main and guider cam works independently?

Many thanks and clear skies!

Read More...