Problem with AM5N : Page 2

Problem with AM5N

F5146666

Hi Fotis,

I am a little confused here. Even though current investigation points to a mechanical issue with the harmonic drive with high probability (and you confirmed it yourself), it seems like you are still looking for an ASIAIR Update to blame. I understand that this would be the more favourable case for finding a solution, but I am still convinced that this is not the root cause of this issue.

I have always been using the AM5N with PHD2 over a PC. Just to make a clear statement here.

I had this RA issues until I interchanged the RA with the DEC harmonic drive. Since this swap no RA issues until now (several sessions over several days). "Just" sometimes issues in DEC, as the harmonic drive that was sitting on my RA-axis is now making troubles on the DEC-axis. But this is not as critical like having this drive sitting on the RA-axis with continuous movements.

Andreas

fotisr

F5146666 Andreas, my fear is the possibility of changes in the software after the update, may have caused damage to the hardware, mainly the RA drive. I can't shake the fact that my problem started the night after the update (morning of the same day). I set up everything and started exposing. I got one 10min perfect exposure, second was with stars slightly elongated on the RA and all the following exposures of the night were with double stars from the jumps. My timeline showcases a gradual deteriorating RA performance that might have started by weird pulses, wrong voltage or amperage sent to the stepper motor or the drive due to the software update. Unfortunately the beta 2.4 asiair firmware doesn't seem to correct the problem and the fear of permanent drive damage is creeping up on me. And zwo support does not seem to read older threads.....

R3Iro7Ea

fotisr
then we create a new post one every week

R3Iro7Ea

fotisr
What do you think, if it seems okay to you that I start this week, since they haven't reviewed my post tomorrow I'll create one with a title like:
Consistent RA Axis Issues with AM5N Mount – Massive Sub Losses

Let's see if this way they pay attention to us

F5146666

R3Iro7Ea

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

fotisr

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

I can't tell you exactly when it started, but it could have been after the 2.3.2 update. Do you remember when it was implemented?
In my area, we've had very bad weather, and I've been spending a lot of time standing around. I usually launch the session and go to sleep, so I haven't checked the guidance in many nights. But I've been losing a lot of subs each night for a while now, and it could coincide with the update.
I'd like to know if there's a way to downgrade the AsiaAir to try that option, or if resetting it to its original state might work. I don't know what else to do.
I've had it since October of last year and I haven't had so many problems until recently, so a software problem seems to fit the bill, which is why I reset the ASI Air or the mount, just like we do with mobile phones, although I see that the error is more pronounced the further I move away from the north, so it could also be something mechanical, now I can only pray that it clears up and perform more tests.

fotisr

R3Iro7Ea this is the way to downgrade on an Android device
https://bbs.zwoastro.com/d/18885-how-to-downgraderollback-asiair-app-firmware-with-android

I don't remember when it was implemented. It was about a month ago. I believe that if something works, I don't need to update, but I messed up with asiair giving in about 20 days ago and since then I got the jumps in RA (and mostly bad guiding numbers in between the RA jumps). I could not imagine an update could do so much harm...

fotisr

R3Iro7Ea it's like you've read my mind....

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.

« Previous Page Next Page »