AS Monitor stuck in configuration mode

Hello,

I have an AS monitor (3RK1105 1BE04 0CA0) that locked up in configuration mode when trying to rewrite a configuration after a device had been removed for startup testing. The monitor was downloaded the new configuration, then when teaching the devices, errored out. The log file indicated "Monitor authorization failure" Once this device locked up (3 led's flashing successively), it could not be stopped nor could another configuration be downloaded. There were no authentication changes to the configuration.

I ordered a replacement device, albeit an enahnced module since the basic module had a 2 week leadtime (3RK1105 1BE04 2CA0). The original configuration was downloaded (this configuration ran prior to any changes)as that was the last stable configuration prior to removing a device for testing. After the download, the newmonitor exhibited the same errors and was also locked up.

The details:
ASIMon software v2.01
AS Monitor v2.14
Original file XXXXX.asi
USB RS232 Com connection

I ordered the latest software revision, ASIMON Plus 2.12 and a third module for testing. We then tried whatever we could to restore the locked up enhanced module back to a shelf state or even a published fix using leer.asi, but the module could not be stopped andwould not come out of configuration to even load.

An additional test was performed using the original configuration file. We traced our steps and noticed a couple of key points that may have impacted this error.

The functional range selected was <2.0. With this selected, the module locked up after a download and while searching for devices (teach).To recover from this we saved our original XXXX.asi configuration to a XXXX.asi2, selected the functional range to Enhanced and successfully recovered the enhanced module. The basic module could not be recovered and is on its way to tech support.

My question is why would the device not be recoverable if the improper functional range was selected? This can be a common oversight during startup and it should not render the device useless. Has anyone else successfully recovered a monitor that locked up during a configuraion change? What sequence can be followed to restore a monitor to a default configuration when locked up once a download is completed? What are the functional differencesof an XXXX.asi file to a XXXX.asi2?

We are currently back on line with the noted changes: ASIMON PLUS 2.12, Function range "Enhanced", file configuration saved as XXXX.asi2.

Thanks in advance for the help

Posted by: James Tyler From: GB Innomech Ltd Created on 13 December 2005 In topic:Safety

I am attempting to configure a Siemens 3RK1105-1BE04-0CA0 ASi monitor, using ASiMon. My ASi node adddresses are present and correct - as confirmed by the configuration log and by the master. The only clues to the fault in my configuration are (a) the following in the config log: **** CONFIG ERROR ********************************* **** monitor authorization failed **** CONFIG ERROR ********************************* ..and (b) that the status LEDs 1,2,3 (yw,gn,rd) are not lit on channel II but on channel I sequence through 3,2,1,3,2,1,3 etc. This fault is not listed in any documentation I can find. I have tried many, many permutations of the configuration without success. Please - any suggestions? James Controls Engineer GB Innomech Cambs, UK.

Answered by:

By Expert: Paul Hingley From: Siemens Automation & Drives Answered on: 14 December 2005

This is an internal fault with the monitor. Please return the monitor to your distributor for replacment.