Question meridian flip and pier side problem

Hello,

Since my last upgrade to the latest firmware i have some problem with my Avalon Linear mount.
I notice a lot of bad behavior:

1) when i issue a park command my control software (voyager astronomy) immediatly receive a stopped signal (the mount is slewing to the park position)
2) when i issue a goto to a target, from time to time i have trailing stars send to the plate solver, which is indicate that the mount report slew end to early.

3) the most annoying and more problematic is the erractic reporting of the pier side to the orchestrator (voyager astronomy) when using ascom command to get the pier side.
the software take too much time to change the pier side after a meridian flip (more than 10 seconds) and report the wrong side of pier to the orchestrator before switching from west to east or vice versa.
I write to Leonardo (author of voyager astronomy) about this behavior and he told me to contact you as the mount report the wrong side of pier.

So i did write to Stephano for support at <This email address is being protected from spambots. You need JavaScript enabled to view it.>  but my email was certainly lost as i did not receive any reply.
Here is what i sent:

Hello Stephano,

I contact you because my linear fast reverse mount did not report correctly the side of pier after a meridian flip.
The avalon ascom driver take a very long delay (more than 5s) before reporting the change of the side of pier, and my sequencing software ‘voyager astronomy’ activate a meridian flip watchdog and stop the mount

Here is a screenshot after that the problem...

 

This is now a consistent and repeatable error.
The time of the PC is synchronized to an atomic clock and the bios battery is not depleted.

As you can see in this screenshot, the ascom mount has finally switched to Pier Side East but it has done this after a too long delay and when voyager is requesting the mount driver, the side of pier was pierWest (Reload Pier Flip Status After Slew) which is wrong according to the position of the scope !

How can we dig together to solve this problematic behavior ?

Thank you for your help in advance.
 --
HoxCa