AM5 latest Firmware V1.3.7 is formally released: Page 2

AM5 latest Firmware V1.3.7 is formally released

benoit

Hello, I just did an upgrade of all the softwares so i'm not really sure if it comes from the new 1.3.7 release.
Here is my setup:

The mount is connected to a mini pc running nina/phd2 using usb. ASI Mount Ascom version is 6.5.14.0
It is also connected to another pc running stellarium using network (the mount is connected to my home router). ASI Mount Ascom version here is 6.5.12.0
(phd2 -> 2.6.11dev6, nina -> 2.3 HF1).

I witnessed at least 2 times that while guiding, the mount synchronizes to another RA/DEC coordinates. It does not affect the guiding, and it appears to do so at a random time. I noted the last "jump", the coordinates went from (15:16:22, +56°14'54" the object location) to (15:15:53, +60°04'18" nothing here).

Do you have any suggestion on where to start to look at ? I'm a bit worried by this behaviour since I leave my gear running at night and would not be there to avoid a crash. The ascom logs shows nothing weird AFAIK except for the coordinate jumps.

Thanks !

ASIMount@ZWO

benoit Do you have any suggestion on where to start to look at ? I'm a bit worried by this behaviour since I leave my gear running at night and would not be there to avoid a crash. The ascom logs shows nothing weird AFAIK except for the coordinate jumps.

Would you please to contact our support and offer your guiding logs?

Tony10312h

Where is this new firmware file located? I am trying to find it for download.
Thank you
-Tony

Loden1111

ASIMount@ZWO Following the Firmware update, my ASIAIR Plus will not connect to the AM5 Mount. I have been using them both for a year with no problem and suddenly they will absolutely NOT connect. I can connect to the mount with my iPad, and the mount is logged onto the ASIAIR network according to the mount information page, but the AIP Plus cannot connect to the mount. VERY FRUSTRATING.

Loden1111

Loden1111 Will doing a factory reset fix this?

Loden1111

Loden1111 Update: I got the AA+ to connect to the AM5, but only by putting the AA+ in Station Mode and connecting to the AM5 as if I was connecting to my home network. That, obviously, means I cannot use Station Mode to connect to my home WiFi, which is rather inconvenient.

ASIMount@ZWO

Loden1111 Did you change the USB cabble to connect ASIAIR and AM5?
Would you please to contact our support to get further help.

PeterH

ASIMount@ZWO what's happening at ZWO? I have issues with my AM5 since July 23 and there is no reaction from support. First time Simon Lewis was reacting but the beginn of October the3re is absolute silence.

Is that the policy of ZWO selling items for some 1000 Dollars and if there are problems nobody cares?
in advance of your response

Peter

ASIMount@ZWO

PeterH Sorry for your waiting, I will ask our support to check. We have trouble to recieve emails by RMA system.

PeterH

no response? @ASIMount@ZWO

TheChief

I have been going around and around this mulberry tree long enough. I have an AM3 and so far it works very well with an ASI Air Plus. What really aggravates me is that no matter what I do I cannot connect the mount to any of my Samsung Android devices over Bluetooth and I cannot get the latest firmware for the mount. This is totally unacceptable.

ASIMount@ZWO

TheChief I am sorry.Can you find the AM3 name in the ASImount APP device list when you try to connect the Bluetooth.

ASIMount@ZWO

TheChief You can connect the AM3 via Bluetooth on your smartphone "ASI Mount" App. The Bluetooth button named 'BT' will be useful for you to confirm whether the mount is connected. The Bluetooth indicator will keep the blue light on until you succeed in connecting the AM3 via Bluetooth.

TheChief

I resolved the issue. I used the ASI Mount ASCOM Server to connect to the mount via WiFi over my home network. When the mount was connected I was able to update the mount firmware. Bluetooh is now functioning.

ASIMount@ZWO

TheChief I see.Thanks for your supporting.

hfhenrichs

Still several issues (both AM5 and AM3), the same as with the previous versions:

1) during moving North or South, the tracking is stalled.
This is very noticeable at 1x, 2x, 4x: the object moves diagonally, instead of only North or South.
This happens with both the ASIMount app and the ASCOM via a PC, so it is likely a wrong response of the mount.
I made sure the latest firmware was installed, and all drivers are up to date.

2) At speed 0.5x the tracking stops entirely when trying to move it against the tracking direction.
This is with te ASCOM driver. The ASIMount app doesn't allow 0.5x, but also at 1x it shows this odd behavior.
At higher speeds the response to East or West is as it should.

Could you please confirm that is the case for all AM5 and AM3 mounts, to make sure that is not due to the particular ones I happen to use?

In any case, could this be corrected? I would be very grateful. - Huib

ASIMount@ZWO

hfhenrichs Hi，it is the case for all AM5 and AM3 mounts that the tracking will be stalled when you move DEC axis or RA axis.After stopping moving DEC axis or RA axis,the tracking will be continued.

hfhenrichs

This means that the 0.5x and 1x in the RA direction commands are not functional at all for the AM3 and AM5, as I described above. Faster commands are also affected.
For instance, fine adjustment to get a solar system object in the middle of a narrow frame is very cumbersome.

This is disturbing. None of the mounts I know (iOptron, 10micron, Skywatcher) show this behavior.
The directional commands are always superposed on the diurnal motion, the only behavior that makes sense.

This is also probably the reason why the ASIAIR guiding calibration vectors deviate from being perpendicular with these mounts, which is of course not a problem, but now understandable.

Could this property of the AM mounts be corrected to get them to behave as what one would expect?
Or a workaround through the ASCOM driver for instance?
Thanks for your attention - Huib

Sonixx

Ist this only when moving the mount with arrow keys?
Assuming guidung would simply not possible with this behaviour.

hfhenrichs

@Sonixx
As I wrote, this happens when pressing the arrow keys with both the ASIMount app and the ASCOM via a PC.
This supports the conclusion that it is likely the response of the mount, as confirmed by ZWO.

« Previous Page Next Page »