Robert, Since no one else seems to be jumping on this, I'll give it a shot... You can assign "multiple unit types" to a single phase, but it is the first unit type that the phase actually runs on. The other unit types (up to 3) need to be booked before the phase will run and get passed to strings SN0005, 6, & 7 of the phase for information only. So, I think that this short circuits your second question. Symbolic unit names are used if more than one unit of the same type needs to be booked for the batch. I've long since lent my RBatch documentation out and don't have a good reference in front of me. But this might give you a clue about your compilation error. The best way to get detailed compilation error information is to go underneath the RBatch II interface and fire up the original configurator scripts. Here's an excerpt from an old email to a client with the procedure to see details of recipe configuration errors: ---------------------------------------------------------- On the host AW, run the RBatch configurator as follows cd /usr/rbatch/bin rb_cfg APPLICATION_NAME [APPLICATION_NAME is the configuration name for the application]. This will give you an RBatch configuration menu list. To see the available useful engineering commands, type: @h The most useful commands will be: @cu @co @ca @cu will re-compile the "unit_cfg" database, i.e. the Unit Database. @co will re-compile the "oper_cfg" database, i.e. all Phase Database @ca will recompile the Unit Database, Phase Database, plus all Recipes Any errors encountered in the re-compiles will be spelled out in a text message with a line reference. The line reference is to the actual ASCII file that the RBatch package creates the executable binary files from. The unit_cfg and oper_cfg files are in /usr/rbatch/appl/APPLICATION_NAME and the ASCII recipe files are in /usr/rbatch/appl/APPLICATION_NAME/rcp. View these files with a text editor to find out what the error message is pointing to. But, don't edit these files! They will just get written over by the RBatch II graphical front end when changes are made. By the way, the password for using the @ engineering commands is most likely "gnomes". ---------------------------------------------------------- To get the required recipe function of selecting one of multiple paths, you'll need to use the "SELECT PATH" feature or one of the other fairly limited RBatch features available to dynamically modify the recipe path. I'm not sure how automated this process can be. I believe that "SELECT PATH" requires operator interaction. Possibly someone else on the list still has their RBatch documentation handy? Regards, Doug Lloyd DGL Controls -----Original Message----- From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On Behalf Of Robert Woolard Sent: Thursday, October 25, 2007 11:43 AM To: foxboro@xxxxxxxxxxxxx Subject: [foxboro] RBatch II Help My client is using RBatch II and I have some questions regarding getting a recipe to behave. 1. I see that I can assign multiple unit types to a single phase, but when I compile a recipe with this phase I get an error about not enough symbolic names. What are symbolic names and how can they be useful? 2. If I have a phase assigned to two unit types, will the recipe run the phase if either of the two unit types is currently booked? We have a point in the recipe where either a washer or a reactor is booked, and we need a phase to run to select which path to run - one path is for the washer and the other is for the reactor. I was hoping that a phase assigned to both the washer and reactor unit types would run for either booked unit. Thanks, Bob -- Robert W. Woolard Sequential Automation Consultants 601 Croton Rd. King of Prussia, PA 19406 http://www.seqauto.com bwoolard@xxxxxxxxxxx _______________________________________________________________________ This mailing list is neither sponsored nor endorsed by Invensys Process Systems (formerly The Foxboro Company). Use the info you obtain here at your own risks. Read http://www.thecassandraproject.org/disclaimer.html foxboro mailing list: //www.freelists.org/list/foxboro to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave _______________________________________________________________________ This mailing list is neither sponsored nor endorsed by Invensys Process Systems (formerly The Foxboro Company). Use the info you obtain here at your own risks. Read http://www.thecassandraproject.org/disclaimer.html foxboro mailing list: //www.freelists.org/list/foxboro to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave