As the topic mentions this deals with the CMU200 from Rohde & Schwarz which hangs during startup.
This is a quite often occuring bug so I will deep into some details of it and will restrict the fault to plugin level.
The CMU is packed with modules and each module also packed with plugins so how to search for a fault....
The problem manifests itself as a hanging serial number detection during BaseDiscoverOptionsBegin eventually it will continue and even will mention the correct serial number but it takes time..... a lot of time..... while this normal would be done instantly.
So what is holding it?
As I have sort of specialized myself in the CMU and want to get to know every detail of it I was able to make a CMU test bench so I can quickly identify broken of defective modules and plugins.
It was not directly my intention to sort this specific problem out but as others on this board mentioned the same problem I decided to give it some more priority and narrow the problem down to plugin level and hope others will pick up where I stopped. Eventually I will also focus on repair of it but as I have so many projects running I just have a lack of time.
So lets cut the crap and start digging :
When you had enough patience to eventually load the serial number you will often find problems like dsp.cpp error or similar red screens on the CMU.
This allready gives you information that focussing on the dsp module would be interesting. By swapping the DIG module with a know good unit it an be confirmed that the DIG module is causing the problem.
Opening the DIG module you will see multiple plugins, the number will depend on the installed options.
The unit with 1100.3220.02 is the cause of the hickup
I have tested multiple not starting DIG modules and all come down to the 1100.3220.02 unit