Question which StarGo version to install for M 0 / M1: 640 SP7 ?

Hello,
I am running a M Zero and a M Uno each with StarGo v 7.0.0.  which is not listed anymore on the support site.
(I installed the new Ascom driver v 7.1.2.6.)

as "New" is listed now Install_StarGo_640_SP7.exe what is confusing me.
Which version of StarGo should I install?
thanks, Peter
 

thank you Stefano!
I was not and am still not aware if my one (7.0.0) is the B5....
meanwhile I installed the suggested 640 SP 7
StarGo is now 7.0.8 and fw is 7.0.0.
I can´t get the firmware to be installed - if I use StarGo GUI: System / firmware then StarGo shuts down.
If I open the fw loader in the StarGo folder it says: "not found"
any ideas?
Peter

Hi Stefano,
thanks again but it does not work - just to be sure:
the previous installed version was StarGo 7.0.0.B1, which is not the "EVO" version (?)  - it is not listed anymore on the support page. I now re-installed  7 0 0 B1 but even with this version the fw updater leads to a StarGo shut down.
 

with the 640 SP7:
 

with any version:
 

windows protocols: unhandled exception / out of range

 

 

Peter





 

Stefano82 wrote:

For the M-zero and M-uno you should install the Install_StarGo_640_SP7.exe - StarGo v 7.0.8
As explained on the corresponding support page, the Install_StarGo_700_B5.exe is Only suggested for EVO-zero.
Best regards.

 

Hi Stefano,

I think the page is really confusing as it is totally unclear which version numbers belong together.
In the comment below the new ASCOM driver you write:
This driver is for the StarGo.exe V. 7.0.8

But the version number 7.0.8 actually appears nowhere on that page!

Instead you provide:
Install_StarGo_640_SP7.exe
and
Install StarGo 7.0.0 B5

Only from your comment here in this post it becomes clear that StarGo 7.0.8 seems to be part of Install_StarGo_640_SP7.exe and not of Install StarGo 7.0.0 B5 (despite being a 7.x version).

Why don't you just provide complete packages which include everything (StarGo plus ASCOM) and name them consistently? Mixing 6.x and 7.x versions in the same package should be avoided as it is just confusing.
And why does only the EVO Zero mount require a separate driver with even a different major version at all? Whatever functionality is required for that mount should be covered by the same driver as for all the other mounts. And if a new driver is required it should always work with all previous mounts as well.
This version mix and their explanations hidden here in various threads is really not helpful for your customers.

Regards,
Stephan