Problem with AM5N : Page 3

Problem with AM5N

F5146666

Agreed. We should insert a link pointing to this thread to avoid that we need to start discussion from scratch.

Understood. But still hard to imagine that oscillating guiding commands (which are a common user case in my opinion) could harm the drive to this extent. But never say never.
I would like to know whether there are still some power reserves on the stepper motors and drivers that could overcome this problem or if the deterioration of the harmonic drive is progressing anyway to an extent that cannot be compensated anymore (and also if the deterioration we are facing is common or an exemption).

R3Iro7Ea

fotisr
Tank you very much, as soon asposiblle i try it

R3Iro7Ea

here https://bbs.zwoastro.com/d/22574-consistent-ra-axis-issues-with-am5n-mount-massive-sub-losses

Garcimor

Hi everyone, thank you for all these messages. I have the same experience (sudden guiding errors, with a particular sound). It seems that the solution is not found for you now.

Garcimor

Garcimor Hi everyone, thank you for all these messages. I have the same experience (sudden guiding errors, with a particular sound). It seems that the solution is not found for you now.

@Tech@ZWO @PMTeam@ZWO

Corsair

Make sure to tag @Tech@ZWO and @PMTeam@ZWO in your post as well.

ASIMount-ZWO

I'm sorry to hear about your unpleasant experience! If all your guiding parameters are set to reasonable values, please first ensure that the entire setup is stable and not prone to shaking. You might try re-securing the equatorial mount, camera, EFW, extension tube, etc., or consider using a sturdier tripod. Additionally, you can provide the guiding logs from the ASIAIR to help us further analyze the issue. If you'd like to determine whether the problem lies with the AM5N, you can try using NINA for guiding to see if it is a software-related issue.If the device has obvious abnormal noises, please contact after-sales support directly for targeted assistance.
If your issue still has not been resolved, please contact after-sales support for one-on-one assistance or to arrange a repair for your device. Thank you for your continued support; we will keep following up on this issue until it is fully resolved.

Garcimor

Hi, all the details, log and video were sent at Zwo last week and I’m waiting for a answer from tech services. I hope it won’t take too long because the good season is beginning now. Thank you

3t2To05L

@ASIMount-ZWO:
If you have read this entire thread you will have seen that we have all previously performed the tests you suggest, and then some.
We are all observing practically the same problem.
It would be to be expected from ZWO a more collaborative treatment, since it is clearly not an individual problem but a product problem, a shipment problem or a problem in the firmware.
Within a month of buying the mount, I have to disassemble the observatory to send the mount to China for a supposed repair, which will take three or four months. I will lose the whole summer and then ... we'll see if the problem doesn't repeat itself. Because ZWO does not explain what is the problem we are suffering.
Thank you for your attention.

ASIMount-ZWO

3t2To05L This issue has already been reported to ZWO's development team, and they will work to resolve it. You can send the device to the nearest after-sales service center for inspection and repair until the issue is resolved.

3t2To05L

@ASIMount-ZWO You say: "You can send the device to the nearest after-sales service center for inspection and repair until the issue is resolved".
But how are they going to repair a mount whose origin of the problem they do not know.
Are they going to repair it without knowing what caused the problem?
Are they going to return the repaired saddle to me and it is possible that soon after it will suffer the same problem again?
At the moment, with less than a month of use, the mount is on its way to the factory, which will mean three or four months without my mount.

ASIMount-ZWO

3t2To05L Hello! I can understand your concern, but the specific handling plan still needs to be consulted with the organization that handles the repair.

Pedro

I am using an Askar SQA106, ASI 2600MC Duo on a TC40, PE200, CAA, EFW and EAF from my back garden paved with concrete slabs (no movement); anal about cable management and do my best polar alignment (usually below 10" for both DEC & RA) before setting off the Autorun in ASI Air Plus.
I have been happy with the AM5N since received last month with RMS total below 0.5 (RA below 40% Dec below 30% both @ 500ms and 0.5 Sideral), except that from couple of nights ago, when errors during RA guiding forced me to loose most of the subs taken due to star trails and drove me to increase RA to 85% in an effort to correct the deviations as quickly as possible. The strangest thing is last session (few days ago) was behaving properly and have not changed anything. There was no wind and no bumps with the rig as I was standing a couple of metres away.
I have read so many treads and responses suggesting to lower the time to below 100ms, below 30% aggressiveness and will try 0.25X sideral.

Update from last night 9 & 10Jul25
I tried the suggested settings above and also tried the setting of 100ms with RA between 30-50% and Dec 40-20% with 0.5 and 0.25 Sideral but the results were similar: RA excursions were outside the chart whilst Dec remains well behaved below 0.4”.
I went back to basics and had only connected the focuser and camera (CAA, and EFW) were still attached but no cables (power or data). Results were similar, continue to experience significant departures on the RA channel.
Also tried 2 different power supplies and a new USB cable between the mount and the ASI Air+ and also to the camera with the same results.
Clouds just rolled in and I am packing for the night… defeated.
I have added my mount chart, pictures of the excursions and ASI Air+ log for reference and have raised a ticket with ZWO but based on your posts should not be holding my breath...

ASIMount-ZWO

Pedro I'm very sorry, could you please submit a problem log from ASIAIR when there is a problem to help us further analyze it?

Pedro

Last night after ZWO pushed the update, I went outside again and tried removing the weights and tried changing again a range of RA and DEC guiding settings from 500ms to 100ms, 65% to 20%, 1 sec to 0.5 sec, 0.5 and 0.25 Sideral with the same results as shown in pictures attached.

Pedro

Just to probe the point, I then took the OTA with all the cables and optical train and mounted the whole rig in my 3-year-old iOptron CEM40 EC in the same spot, using the same ASI Air+ where moments before the AM5N had been tested.

I have attached a couple of subs with narrow band filters of the Lion’s Nebula, 300 secs, -10C and the performance over 200 secs of the optical setup using the iOptron mount. I believe this is fairly strong suggestion that there is something wrong with the AM5N, however, I am willing to be convinced otherwise.

Hopefully, the results will demonstrate that I am not totally inept in this hobby.

ASIMount-ZWO

Pedro Thank you very much for the test case you provided, it is very useful. The ZWO team will locate and solve this problem as soon as possible, thank you for your support and trust.

uxw0xVQo

I had the asiair plus and some zwo cameras and the am5n in the basket. After seeing those tracking issue with the am5n, I skipped the am5n, and purchased the asiair plus and the asi camera. Waiting for ZWO resolution of such tracking issue of the amn5 before placing the order.

ASIMount-ZWO

uxw0xVQo thank you very much for your support and trust ！

Pedro

I think is a wise choice.

I was enjoying the first few days when this strange behaviour had not materialised yet and was looking forward to control the mount via Bluetooth and the weight reduction is a bless... but the AM5N needs to work as advertised consistently.

ZWO needs to realise this issue is serious and needs immediate attention and positive resolution.

ASIMount-ZWO

Pedro I am very sorry, the ZWO team is paying close attention to collecting these issues and actively testing and verifying to resolve this issue as soon as possible, thank you very much for your support and trust ！

« Previous Page Next Page »