modify database without stopping the controller ac450
I have AC450 with 800xA
now ac450 is running but i have to modify digital input and digital output signals discription, i want to export it as dbt or excel file and modify it and then upload it again without stopping the controller
is that possible and how please?
Voted best answer
You can edit the signal descriptions without stopping the controller. See the manual 3BSE003838R0101 "Source Code Handling User's Guide" section 22.214.171.124 for specific instructions. The example in the manual shows how to manipulate the :ACT property; in your case you want to modify :DESCR
The general procedure is to dump the DB into source text using Online Builder command DUDBS with the /MODIFY parameter. You then edit that text file leaving only the DB elements you intend to change. I don't recommend using Excel, although it is possible so long as your completed file is plain text format (no hidden/special characters).
You can then edit the text for :DESCR to reflect your changes. The resulting text file is then read into the controller using Online Builder command TRDBS. This can take some time depending on the file size and the controller loading.
I recommending your first attempt using this method should be a single property on a single element. If you have Function Chart Builder you can use this file in the same manner (via "Backtranslate Source") - this is a good way to test and verify your MODIFY file before applying it to an actual controller.
If you want to modify the Description part then you can do it directly thru Online builder.
Follow the below procedure:
1. Open Application Builder (On your AC450 Engineering station).
2. Select the desired node (Controller Node of which you want to do modification) and click on ONB iron or Right click on the Controller Node and select Online Builder.
3. Online builder will launch and finally you will reach # prompt.
4. Now press command MDB<Space>DI101 (DI101: Example of Digital Input Signal, if your DI signal Tag name is say DI_001 then type command MDB<space>DI_001)
5. This window shows the Database of DI (shows the Input & Output Pin details)
6. Now type S2
7. You can find now a input pin (probably the 2nd pin) Description.
8. To modify, type M
9. Now you enter your desired Description. (Character limitation for Description)
10. Type END
11. If you have another DI or DO to be modified then repeat the above procedure Step 4 to 10.
12. Finally type command TSESS. Then you can see message ! Session Terminated !
13. You close the Online builder window.
14. Now on your Plant explorer workplace browse to Control structure, select the AC450 node which you just modified. Select MB300 Upload aspect.
15. Start Upload. After successful completion of the Upload browse to the DI or DO Tag and find the description is updated.
No - You cannot download changes from Function Chart Builder into the controller database unless you stop the controller. You cannot modify PC programs this way either.
You must modify the database on-line using On Line Builder as described in the previous answer.
- make the database changes using On Line builder
- dump the database changes using the DUDBS command
- also dump all the PC program source code using the DUPCS command
- Backup the FCB project source code somewhere safe
- initialise the FCB project and back translate the DB and PC source code.
- export the database source code into DBT or Excel files.
if you have many signals to change, then you can build a command file using the expert commands for on-line builder and run that. Look at the help files for details on writing and running .CF files.
You can put the required MDB commands ( including all the >> and ! Commands ) that you would otherwise have to enter manually. Some ways to build this CF file could be using a VB macro or lots of cut / paste ( personally I would write a macro to do this )
if you are familiar with Expert commands then you can also edit database records directly without using MDB. ( ie FINS, GINS and MPRO ) This is much faster because the error checking is bypassed. But of course it is easier to make a mistake so use these commands with great care.