a ..
60653 HW v2.0
and
60657 HW v2.1
both present themselves to a 60213(CS2) or 60216(CS3) as 60653
(I have no close knowledge of any 60653 with HW v2.1 - or any variant of the 66950)
Both appear under the "MS2" network section of the CS3
Both types update with the "ms2 v2.7 07.12.2016" module delivered with CS3 v1.2.0 update package (or earlier betas)
(Of course the diferent hardware device may use different/selected parts of the fuller package)
Subjective :
After the 2.7 update , there is no user panel changes I could detect.
The upper level versions appear unchanged, underlying files might be different.
Jury still out ....
After upgrade both items still report with "CS2 Slave" when connected to a 60216(CS3)
The CS3 ChangeLog mentions a bugfix for the CS3s update function relating to MS2s, but does not list an actual ChangeLog for the 60653/60657/MS2
The CAN bus ping DOES report a device type code of x32 for the 60653 HW v2.0 and a x33 for the 60657 HW v2.1
So while the devices are distinguishable via their device type , there no attempt to recognise this within the CS2/3 device information panels.
- they are both product 60653 and found under the MS2 section
Further note:
The CS2 does display the serial number of the 60653/60657 (internal , not necessarily the one printed on the outside of the case)
The CS3 does not identify the serial number to the user for cross reference - forcing the user to identify which is which themselves.
This may appear to be a moot point functionally as the MS2(60653/60657) has lost the dispatch capabilities available for the MS1(60651/60652) , but it always good to succinctly identify the devices using their own terminology/identification rather than impossing another layer AND failing to automatically link them
In summary, like the 60651 and 60652(belatedly the MS1), I suspect that the granular meaning is going to be lost.
While it "appears" that the 60653 aligns with a Grey case and HW=v2.0 and that the 60657 aligns with a Black case and HW=v2.1 , it is probable that during the transition in manufacturing that there may have been a crossover / mix. And anyway it is highly likely that any faulty 60653 will be repaired with a HW=v2.1.
And finally, while the marketing documentation does NOT use the term "MS2", preferring to stick with "Mobile Station 60653" and "Mobile Station 60657", an abbreviation has crept into the screen usage and propogated into some parts of the documentation.
e.g. pg22 of
http://medienpdb.maerkli.../1/pdf/60657_betrieb.pdf.. shows examples of panels with "Mobile Station" and "Information". In later versions you can find this changed to "
MS2 Information" and this change is evident in the screens of BOTH the 60653 and 60657
Either way the first point of reference for the naming of a products name should be the product itself and its own marketing and documentation.
