Yes I updated through RM, but to me it seems strange that RM can up date a FW and then that FW not communicate with said RM?
If you would have red the update notes, you would have been aware of it. We write that stuff in order for people like you to read it. Of course Rig Manager can update your Profiler to a firmware which is not compatible with the Rig Manager version you're running. Simply because, in the next step, Rig Manager will update itself.
Display More2016.10. RM1.6.38
Profiler Operating System 4.0.6.12337 RELEASE
Rig Manager revision 1.5.40 is required!
Profiler Operating System 5.0.3.12660 BETA
Rig Manager’s 1.6 revisions are required minimum!
Profiler Operating System 5.2.0.12879 RELEASE
Rig Manager’s 2.0 revision is required minimum!
So I think you could try 5.0.3.12660 BETA or 4.0.6.12337 RELEASE
According to my records, v4.2.1.12583 Release, v4.2.2.12590 Release and v5.0.3.12660 Release are all options as they required RM v1.6 at a minimum.
thank you Damien for your help I’m sure it was a V5.X.X something I was on before!! Where can I get 5.2.012879 from???
You don't want it, Raoul, as it requires RM v2.0; see my note above.
I dont think it was 5.2.0.12879 sinc it require RM 2.0 minimum.
Please check your PM.
Correct, Damian. OS 5.1.1.12825 Release started the RM v2.0 requirement, which extended to OS 5.2.0.12879 Release and OS 5.3.1.13085 Release.
burkard what is the highest KPA FW release that I can use with RM V1.6. I really need to get my studio system back up and running like it was. ??
As I said earlier, and I apologise for not being the esteemed (and much-loved-by-me!) Sir Burkhard, v4.2.1.12583 Release, v4.2.2.12590 Release and v5.0.3.12660 Release should all be options for you, Raoul.
Check your PM's, bud.
The fact that 5.5.2 is communicating with RM doesn't mean all is well and will continue to be so IMHO, Raoul. The accompanying ReadMe states that Rig Manager 2.1.25 is the required minimum for OS compatibility. That's a long way off v1.6.
OS 5.5.2.13463 Release is the 6th release FW version to require RM 2 and above, so I'd say you're playing with fire, mate. I mean, this was originally also about preventing another unnecessary session halt, no?
As I said earlier, unless I'm mistaken, your only safe options are:
OS 4.2.1.12583 Release
OS 4.2.2.12590 Release
OS 5.0.3.12660 Release
