pcmccartney1

Working with RA Tech Support for almost a week now with no success. Customer sent me an MER from a PV+1500 at v5.1 firmware and trying to restore to FTView ME6.1. Had another guy in the office restore is successfully to ME6.0. Also, had him create an APA at 6.0, I still couldn't restore the ME6.0 APA to ME6.1 I've repaired ME6.1, I've uninstalled and reinstalled ME6.1, also applied and validated all applicable rollup patches for June 2012. Getting an error message that says that there is either not enough disk space, or the project is open elsewhere, or the project doesn't exist. There's always a possiblity that the MER is corrupt. Customer doesn't have an APA. Anyone else had problems with MER restoration to project or MEW in FTView ME specifically 6.1? Thanks, Rick

Solved the problem! Found a Technote ID468530 that talked about mulitple tag databases possibly being present in the project. To figure this out, I created another VMWare image, downgraded the FTView ME from v6.1 to v6.0. At this point I was able to restore both the oem's apa and mer from v5.1. Looking the HMI_Project\Tag folder found two complete sets of databases names "XXX" and "XXX_Alt". I deleted the "XXX_Alt" version of the files and created a new apa. I was then able to restore the new apa in FTView ME6.1. Thx, Rick

Seems to me that your might check your startup/global or other macros. Those messages are what I see when a line in a macro couldn't execute properly due to a lack of comms. Might just be a timing issue.

The sercret to control flashing an ML1100 is to shutdown RSLinx. Use RSLinx to verify connectivity to the DF1 port and settings, then shut it down to do the control flashing of the firmware. As for the questioning of the need for firmware upgrade, usually they ship with the latest or nearly latest firmware installed. Early versions of the firmware had ethernet comms issues that were resolved in rev 7 and latter firmwares upgrades.

I found a smaller subset of those that appear in the top of each opened routine. Hovering over each will describe "Move Branch Rail", "Add Input Parameter", "Add Return Parameter", "Remove Parameter", "Remove All Unknown Parameters". If you are using any JSR instructions and select that element, the various buttons in the toolbar will appear with colors. These same options appear if you right click on the JSR. By left clicking on the toolbar and dragging, it can become floating. You can also left click and drag it back to a spot just below the title bar of the opened routine and the pull down bar to "re-pin it. Either way you can also right click the toolbar and hide it. but it reappears each time to open the routine.

My suggestion would be dependant of the number of signals you need to exchange. The "Native E/IP" driver actually treats each tag seperately and also creates overhead associated with it. I found, working with Red Lion tech support, that it was better to create an array and map as PLC5 like tagging to help reduce response times and round trip updates. If you only have a few INT then don't worry about it. Rick

S7-315F 2DP with an ET200pro hosting a RF170C with read/write heads with Moby-D tags MDS D424. Downloaded a read most every manual. Still not sure how to code a triggered read or write to a specific head. I believe I need to parameterize DB45 (Parameters) and DB47 (Commands) and view data in DB48. But unsure how to setup a steping drum sequencer that would monitor when the ASM is available or ready for the next command, when it's busy, that it is processing the command or that it has finished the command. Seimens talks about monitoring the status word, I have no idea where to find this. Also told that I expected to compare two counters (command counter and acknowledgement counter) to verify they are equal. Looking at DB45 I see a counter named counter_customer but no other references. Looking for some example code to trigger reads and wirtes to both heads. Any help would be appreciated. Rick

Bob, Did you eventually get it working? I remember something similar, RA wanted you to export and import every project to get functional. I believe the majority of my problems were in initial setup of Enteprise, maybe check there. Rick

Ken's suggested link is the correct direction. I echo his statements concerning a safety risk assessment. I did the same logic for a two hand control pendant to jog a shaft driven machine. The output was used to engage/disengage a clutch. The clutch was also SIL 3 device and could also lock it self out. Just goof around a little with the timer preset to get a more realistic expectation of a reasonable time to press both buttons within. OSHA has some values...memory seems to say something like 0.5 secs or less.

Try the application documentor in the FTView Tools. You can do "Find" there.

I presume you are talking about a redundant safety processor like an L62S. If so, you would define the slot for the processor and the "partner" slot must the next. slot in the rack. For full redundancy you must have an identical rack.

With the project closed (i.e. not open in ME) goto the Application Manager and Rename the project. Unfortunately App Manager must do these tasks for you as it creates and manages it's own index files.

Building an L43 with a 1769-SDN in the first slot. I've upgraded the firmware in the processor to v17.3. Now the SDN thinks it's a 1756-DNB and a bridging module. Any ideas? I've attempted to commission the node, but Networks won't talk to it. I replaced the SDN with another working SDN, was able to upload the configuration and scanlist from the SDN, but unable to download a different dnt to the module. I'm fearing that something has happened to the 1769 I/O Bus on the right side of the L43. Any ideas would be appreciated. Rick

Update......The 1769-SDN was found to be dead out of the box and replaced. Interestingly, I found a spare module in the store room with firmware version 2.1 for a MicroLogix1500. Put it on the L43 bus, but due to firmware, it wasn't visible in RSlinx and therefore Networx. Was able to insert another SDN with higher firmware version between the L43 and the v2.1 SDN. I was able to see the lower version module and able to flash up. Choose rather to sub over the DNet cable and flash thru the L43-SDN(v4.2)-DNet-SDN(v2.1). All is well.

Yes, it is only 0-10VDC. You could wire in the 4-20mA signal and install a high precision 250 Ohm resistor to read voltage then scale appropriately in the ladder.

Ken, Networks is giving an Error 12 Comms timeout. The working SDN is passing bus power to the the remaining i/o modules. Put the original sdn back in and no power is passed to the I/O. Remember the sdn is in slot 1. I think it's just a bad module. working on an RMA. Thanks, Rick

Read up on the "Macro" Pushbutton. You could put five "Macro" Pushbuttons on the screen corresponding to each Site. Each "Macro" Pushbutton would run a macro. Each macro would equate the Sire specific string tags into the generic string tags that you have displayed on the screen.

You could create and tag 10 strings and group them for Site1 and have visiblity based of the value of the combobox, then copy for each stie with corrected tags and state of combobox.

Seems to me you would want to use the parameter passing capability and possibly a global macro. But try parameter passing first.

Bob, I found a different thread with example programming for CJ1 to ML1400 via explicit messaging, but using the Ormon EIP module. User PMCR started the topic...try looking at it.

Devon it is an ABB Procontic B platform, google that and you will find datasheets, spare parts, manuals and contact information. I've attached one pdf that describes the basics of the system.

One other thought, there used to be a regional office in Stevenage, Hertsfordshire, UK.....Don't know if it still exists....They might be of some help....Only problem is that they dealt with the Kent-Taylor platforms.

Devon, My best guess is the Procontrol P13 that originated from Switzerland. It used a function block language rather than ladder logic. Each module is a seperate device called a "Drive Control Module" and therefore contained the code internal to the board. As long as you wired the device and set parameters correctly, the device was controlled properly. They had differing boards to meet various needs, Drive Control Module witout Command Memories, for use with unidirectional drives, MCC or swtichgear that could memory or latch in signals to start or stop. The Drive Control Module with two Command Memories was for operation of dampers, motor operated valves, slide gates. Many other modules for the control of analog loops. The controller was capable of high speed scans and control of analog loops which was ideal for rotating machinery like a combustion or steam turbine. As for spare parts or programming tools, I think you would need to contact ABB in Baden, Switzerland. I think the picture would be helpful. They might better identify the platform. There is a chance that it is a Procontrol P14 or P15. Rick

Devon, Going to need more information regarding the BBC PLC. I was ABB through the late 80's, 90's and half of the 2000's. ABB at that point had no less than 14 controls platforms, some were DCS's, some Hybrid PLC's others that qualified more as a PLC. Do any of the following names sound familar? Procontrol, Taylor MOD300, Masterpiece, Master. There was a small PLC made by a ABB company that focused on the dairy industry in Europe, their name is escaping at teh moment. Rick

You are going to have to look at KepwareServer. There are several ethernet protocols for GE included as drivers.