AM5 latest Firmware V1.2.4 beta and ASCOM V6.5.15 beta is released for test!: Page 2

AM5 latest Firmware V1.2.4 beta and ASCOM V6.5.15 beta is released for test!

Glass17

Dialog "Synchronize site settings" I published above.
It states "The Telescope's site setting differ from NANA's", but they looks the same except Elevation.
When I press "From N.I.N.A to telescope" I am getting error "Unable to set mount latitude to 50.479 and longitude to -120.806!", but my best guess it can be related with Elevation too ????

Mamete

Glass17 @Software@ZWO That's right, the coordinates are synchronized well from NINA to Telescope except for altitude. Altitude from error

Software@ZWO

Glass17

Mamete
We will solve this problem immediately. The new version will be released soon.
Best Regards

Glass17

I don't know the reason, but few days ago when I issue command got Alt 40 /Az 186 mount turned scope upside down and hit tripod even horizontal limit set to +20 degree.

Just to check is Horizontal limits working for tracking only or for tracking and slew?

Glass17

Mamete

Do you have plan add at least dummy (not used) Elevation in the future version just to remove annoying dialog messages?

Mamete

YBOURY Software@ZWO Thank you

Jhaunton

Glass17
Try setting NINA to 0 altitude as a short term fix?

ZipZapRap

I also have the latitude problem, but this is the one I get every time I connect.
If anything else is plugged into the PC, this error pops up. If I unplug everything, then I can connect to the mount and I have to plug everything else in afterwards.

zombi

My application also fail because of unsupported elevation - i have to simulate it using poth.
Please fix this issue asap:

YBOURY

Hello, following your last email for me, there are 2 films and the datalog of AM5 and NINA. "Movie 1" shows the drift of stars during polar alignment. The "movies2" shows the star trails of the capture image during astrometry resolution. I hope you to find the solution ;-) I remain available if you have other questions. You can the files by https://we.tl/t-OUVkQJSkSA (the files are too large)

bqb

I confirmed that my tracking button not lighting up is tied to firmware 1.2.4. If I tap it, it turns on, but when I release it the LED turns off. If I go into the app and turn tracking on & off a couple times, then the LED on the hand controller starts working properly as does the tap on/off. I downgraded to 1.1.2 and this problem does not exist.

Walf@ZWO

bqb You could attached ASCOM log，or send it to software@, then we do analysis it , thank you!

bqb

Also replied in the other thread. There is no ASCOM log because I'm not using a computer. The tracking button isn't working with the beta as I described.

psparky

Software@ZWO

Any idea when a new version will be release. I just hit Park in NINA, and the mount slewed counterweight up on the east side of the pier until it crashed the scope into the pier. Hopefully nothing is damaged.

Glass17

Parking counterweight up. Mount stopping tracking when tracking checkbox still be on and there is no way to stop and restart tracking in this condition. Meridian flipping broken compare to version 1.1.2 when Meridian flipping was not configurable, but worked.

Jean-Charles

Hi,
I'm using the latest version of NINA as my controller and I just migrated from a Sky-Watcher mount.
I just discovered a weird behavior: when I ask NINA to have the mount "Go Home", then the mount successfully does just that and stops tracking. However, if I ask NINA to "Park" the mount, then it does go home, but it then enables tracking (mount seen as tracking in the ASCOM driver), which makes no sense and might even be a bit dangerous if not caught on time.
Is the issue in my settings or is it a bug in the driver?
Thanks,
Jean-Charles
P.S.: I never had this issue with my previous mount, so I don't think it lies with NINA. I have also installed firmware 1.2.4

pwe169

YBOURY also happens for me

Tony10312h

Hello,
As I read through this thread I downloaded the firmware and ascom update at the top but then saw a few threads down that there is a more recent file version with the same name but had a few bugs fixed.
I just wanted to find the latest and newest firmware version please.

I had an images run last night with v1.2.4 beta (from the Feb 17th posted file here)
Happy to see the altitude limits, very helpful.
One issue that I did run into however was I seemed to have issues with keeping the mount in sidereal tracking. Using NINA, every time it would slew and center I found the tracking would turn off. Noticeable because the stars would oblong and could not get a solid plate solve.
The tracking light and box was checked in the AM5 app but it was infact not tracking until I selected "set tracking" in NINA.

Would like to know some feedback if anyone has seen this as well and if there is a newer firmware to test?
Thanks guys and Glad to see a great progress!

Love the Mount, I currently have it mounted in my backyard observatory and also have taken it on the road for vacation very mobile and robust at the same time. Hands on operation is great and now I am really hoping to dial in the hands off automation so looking forward to more progress on the firmware updates!

tempus

A new version was supposed to be released "soon" 19 days ago.
It would be nice at this point to get an update from ZWO.

biomedchad

So is there anyway to work around the meridian flip issue? Ima till running stable 1.12 firmware and 6.5.10 ascom driver

Perhaps stopping before meridian and then moving to an object on the other side and then coming back to the object once it’s passed.

Few additional steps to add in advanced sequencer in Nina. Not ideal but neither is not being able to flip.

Am5 flips fine with my asi air currently but not Nina

tempus

biomedchad. Stop imaging a few minutes before the meridian. Park the scope. Then, once the object is passed the meridian, start a new session. You'll need to sync the mount to the PC time and double check when the object crosses the meridian for your location in order to lose a minimum of imaging time. I haven't had the chance to test this yet but that's what I would do. And stick around in case it doesn't work so you don't lose half of the night.

Use 0 min past the meridian and 4 min max past the meridian in the time limits. With this narrow limit, NINA will stop imaging in order to respect those limits. That would work with any other mount but not sure with the AM5.

« Previous Page Next Page »