Eddie Willers

The red X indicates that RSLinx is getting no valid response from the IP address you entered. First, be certain the format is correct. While the Net-ENI utility might force you to use leading zeroes, do not do so in RSLinx or your Internet browser; those programs adhere to the standard that leading zeroes in an IP address indicate octal numbering instead of decimal numbering. Verify the IP address of the 1761-NET-ENI using another method: 1. PING the -ENI, then open a command window and issue a "ARP -A" command. Verify that the PING was responded to and that the MAC ID shown by ARP matches the Net-ENI device. 2. Open the Net-ENI's address in a web browser to see the splash page. 3. use TCPING (download from the Internet) to verify that TCP Port 44818 is open on the Net-ENI.

From the RA Knowledgebase, document 32354: Error: Missing IP address '.' delimiter when opening NET-ENI utility. The following error occurred when trying to open NET-ENI utility: Error: Missing IP address '.' delimiter This error usually occurs when the Regional and Language Options in the operating system is set to something other than English (United States) There are two ways to solve this issue: Set the Regional and Language Options on the operating system to English (United States) In the Standards and formats press Customize and change the Decimal symbol: to "."

The simplest way to determine the IP Address of the 1761-NET-ENI module is to connect to it with a 1761-CBL-PM02 serial cable and use the free NET-ENI Configuration utility to upload the configuration. http://www.ab.com/programmablecontrol/plc/.../downloads.html Another way is a non-AB method. Use the popular Wireshark Ethernet protocol analyzer and filter for "arp" packets. Plug the 1761-NET-ENI into the same network switch as your PC and you'll see it sending out ARP packets with the device's MAC ID and IP address in them.

Get out the Parameter List in the PowerFlex 700 User Manual, Publication 20B-UM002, in Chapter 3. Start with the Monitor parameter group. Because each Parameter is 32 bits, but the "PCCC Object" we're using employs 16-bit data reads, you have to multiply the Parameter Number by 2 to get the "N150:xx" address. Parameter 1 = N150:2, length 2 Output Frequency Parameter 2 = N150:4, length 2 Commanded Speed Parameter 3 = N150:6, length 2 Output Current ... Parameter 12 = N150:24, length 2 DC Bus Voltage Parameter 13 = N150:26, length 2 DC Bus Voltage Memory ... and so on. Other easy-to-verify parameters include drive rating parameters, which don't change during runtime, like Parameter 26 "Rated kW" or 27 "Rated Volts". The parameter list also very helpfully describes the Units of each Parameter. For example, the Output Current is in units of 0.1 Amps. A value of "70" would indicate 7.0 amps.

Aren't you going to tell us the solution ?

Archiving, re-naming, deleting, etc. of FTView projects is done with the Application Manager, which you launch from Start -> Programs -> Rockwell Software -> FactoryTalk View -> Tools -> Application Manager. Thanks, Kiwi Sparky, for pointing out the difference in meaning between question marks and hashes in a numeric display. MrPLC has a pretty good image display mechanism. I use alt-PrintScreen to capture a screenshot from FTView Studio, then paste it into MS-Paint and save as a GIF or PNG file type to decrease the file size. Post the file to your Forum entry using the Attachments function (below your Forum post entry window). Sizing your file size (and cropping images) becomes more important when you have to show several images. Nobody wants to see giant desktops or scroll through quoted passages that include the previous images. Once the Attachment has been uploaded, the "Manage Current Attachments" lets you paste it into your Forum post window, as seen here:

Can you create an Archive file (*.APA) using FactoryTalk View Studio and post it ? Are you attempting to perform scaling in an Numeric Input Object, or in a Macro, or something else ? What kind of display objects are you using, and how are they configured ? Being able to see the application, rather than a brief description of the application, is the best way for a Forum member to help you.

Are these PanelView Standard terminals or PanelView Plus terminals ? Can you post one of the configuration files ? A device identity mismatch in RSNetworx means there is either a different firmware revision online than offline, or that the device is a different type (like a 6" instead of a 10" unit). In RSNetworx for ControlNet, you generally resolve this by right-clicking and selecting "resolve device mismatch", which updates the offline file. In RSLogix 5000 (if that's what you are using) you need to select "Compatible Keying" or "Disable Keying" for the PanelView device.

The only thing that looks like it might need adjustment is the "EIP_Path"; you show " 0 0" and I think it should be "1, 0". EtherNet/IP Path arguments are pairs of numbers designating the Port and Address of a "network hop". Port 1 is usually the backplane of a ControlLogix, and Slot 0 is the default slot for a ControlLogix. "Port 1, Slot 0" is also the default path for a PLC-5E or SLC-5/05. I think "Port 1, Slot 0" makes sense for a 20-COMM-E as well.

The PCCC driver in the 20-COMM-E is enabled all the time; there's nothing you need to do to set it up. Again, I have not used this combination, so I'm not 100% sure either. From what I've read in the Fieldserver manual, this configuration ought to work to read the Bus Voltage (I use it to test because it's always nonzero) from the drive: // Server Side Map Descriptors Map_Descriptors Map_Descriptor_Name ,Data_Array_Name ,Data_Array_Offset ,Function ,EIP_Con_Typ ,Node_Name ,EIP_Service ,File_Type ,File_Number ,Address ,Length SRV_AI_01 ,DA_N_01 ,0 ,Server ,Explicit ,EIP_01 ,Exec_PCCC ,N ,150 ,24 ,2 Because the drive uses 32-bit DINT or REAL datatypes but expresses them as 16-bit elements for compatibility with PLC-5/SLC500, it is very important that you select the correct starting element (an even number) and an even multiple of elements. You can read N150:24, Length 2 in order to get the Bus Voltage, but if you sent a request for N150:24, Length 1 it would fail. Probably you'll want to read a whole block of parameters from the drive at once into the Fieldserver. The "PCCC Object" appendix of the 20-COMM-E User Manual is the reference for this kind of messaging.

This definitely sounds like an unusual application. I certainly haven't done it. I read over the Fieldeserver user manual briefly and it appears it can be an EtherNet/IP Client and perform PCCC Reads and Writes to A-B controllers. The PCCC object is implemented in the 20-COMM-E module, so that the drive emulates certain "N-files" as though it was an SLC-5/05 or PLC-5E controller. These can be used to start and stop and control the speed of the drive, as well as to read and write drive monitoring and configuration parameters. What data do you need to read and write from the drives ? What have you tried already ?

You are in a similar situation as Forum members, but volunteerism, or even anonymity, are not shield from liability. Good for you for trying to help, and I strongly recommend that you provide signed and dated copies of diagrams (number every page), parameter settings, and descriptions of what you did to the system. As Paul mentioned, once a safety relay is tripped, it must be reset. Is there a separate Reset button for the safety relay ? Read the information in the PowerFlex 700 User Manual on page 1-13 about Input and Output contactors. I think that cycling the input power for this drive is going to wear it out prematurely. Your description of the PowerFlex 700's HIM indications sound like it is alternating between "DC Braking" and "Coast To Stop" stop modes. When a DC Braking or Ramp to Stop mode is stopping the drive, the HIM module will show "DC Braking" or "Decelerating" and then "Stopped" when the drive has actually stopped. When a Coast to Stop mode is selected, the drive will show "Stopped" immedately, because the drive is no longer participating in the stop of the motor, even if the motor is coasting. The fact that both stop modes are followed by a "not enabled" is consistent with the PILZ relay removing the Digital Input 6 Enable signal after 3 seconds. Check all the Digital Inputs to be sure only 2 and 6 are connected, and check to see if any of them are programmed for "Stop Mode B". The "Stop Owner" parameter might also give you some information about why the stop mode appears to be alternating.

In RSView32, the tag count limit is on Device Tags in the RSView32 Tag Database. You don't need to export them to count them; from the Tag Database editor, select Help and click "Tag Statistics". If you import an RSLogix 5000 tag database, you are very likely going to end up with a lot of tags in the RSView32 tag database that you don't intend to use. This includes a lot of sub-elements of UDTs and module-defined tags. A Tag does not have to be used on a display to count against the Tag Database licensed limits. RA Knowledgebase Answer ID # 43741 and # 7487 have some useful information about tag counts and a utility to delete unused tags from the RSView32 database.

As always, Paul, you provide a truckload of knowledge. Me, I just got a new sig line.

You had to include that last line, didn't you ? I agree that it is likely that the hardware enable jumper is removed, which is correct if Digital Input #6 is used as a non-programmable Enable. See page 1-21 of the User Manual for details on that location and function. You mentioned a Stop button, but did not describe a Stop Input defined in the Digital Inputs on the drive but rather a "Run Forward" whose absence is interpreted by the drive as a Stop. So, the Stop button probably goes to some other circuit, maybe the safety relay, maybe a PLC input. Get a wiring diagram and trace out all the signals visually and electrically so that you understand how the system has been implemented. It sounds like your system mixes a functional "Stop" button with a safety circuit that might be intended for an Emergency Stop. The description of the Digital Input 6 function on page 3-55 of the User Manual says: "Opening an “Enable” input will cause the motor to coast-to-stop, ignoring any programmed Stop modes."

You just use MOV instructions to move the value in the S2:xx register for Day, Hour, Minute, etc into a holding register, or examine it directly with instructions like EQU, GRT, LES, etc. I don't know if I'd use an SLC as the master clock for a facility unless I could set it frequently. They are about as accurate as any other simple clock like a digital watch; they can drift a few seconds per month. Sometimes they drift more when they're running especially hot. There is an RSLogix 5000 Clock Update Tool that runs as a Windows utility and sends the computer workstation time at scheduled intervals to Logix and PLC/SLC controllers on a network. If the workstation it's running on is also synchronized to a good quality time reference (like the NIST clock on the Internet) then you can get and keep very accurate time in your controllers. I was recently in a big machine shop that had a 50" flat-screen television mounted outside the part scheduling room with nothing displayed on it but an analog clock face. I'm sure it does something else, but in the three days I was there I never saw anything but the clock.

DTAMs can communicate with controllers. PanelViews can communicate with controllers. PanelViews cannot communicate with other PanelViews or DTAMs. As you describe it, you are just looking to have some kind of data entry device that transmits five lines of six-digit numbers from one place to another. I would probably do this with a MicroLogix 1000 (they can be as cheap as $90) on a DH485 network with 1761-NET-AIC isolators. Use the MicroLogix to store the data values and accept the command to Clear them. This would maybe also be a good application for the new Component PanelView terminals, which are less expensive and less functional than the Standard PanelView.

RSNetworx needs to be able to access the ControlNet network to configure the 1747-SCNR. You can use the 1784-PCC/PCC1 interface card or 1784-PCIC interface card, which are the most direct connection. You can also connect to the ControlNet using a 1770-KFC15 serial interface, or the slot-mounted 1747-KFC15 serial interface. You can also connect by bridging to the ControlNet from a ControlLogix system using a 1756-CNB, -CNBR, -CN2, or -CN2R module.

The important differences are the battery and the location of the CompactFlash slot. The new battery is coupled with an onboard flash memory chip to provide much longer battery-sustained user program backup. The /A and /B controllers run identical firmware with identical performance.

If you have an Administrator account for Windows, that user is automatically also made an Administrator for FactoryTalk. Run the FactoryTalk Directory Reconfiguration Wizard (Start -> Programs -> Rockwell Software -> FactoryTalk Tools -> FactoryTalk Directory Configuration Wizard). Use your Windows Administrator username and password, and this utility should allow you to log on to FactoryTalk and reconfigure the FT Local Directory. While you can remove the Windows-linked Administrator user from FactoryTalk for greater security, 90% of installations I've seen left it in place. Rockwell Automation Technical Support can also help you delete and reset the FactoryTalk directory configuration even without a FactoryTalk Administrator username and password, but you will lose access to all the projects that are on the machine.

In the USA, Rockwell/A-B has about 40 to 45% of the controller market. It's much higher in Canada; some say as much as 60 %. Siemens has between 20 and 25 % of the market in North America. It's the other way around in Europe, of course, and in Germany proper Siemens completely dominates the market. You'll see Omron and Mitsubishi as the principal controllers in Japan. The rest of the market is "everybody else". Depending on your industry, you might see Telemechanique/Schneider/Modicon have almost 10% of the market, or Omron, or Mitsubishi. Despite their popularity on this Forum, Automation Direct has a very small market share, about 2% last time I read a report. I get these numbers from an Automation Research Council (ARC) report; most marketing organizations of major vendors have access to these. I don't read the control-oriented magazines anymore because I'm sick of hearing how magical Ethernet or Wireless or Mesh or Zigbee are.......

Both points very well taken. A positive-ground Volkswagen once caused me a lot of head-scratching. I may have taken some liberties with the nomenclature because of the original poster's confusion. Bulk Power Supply +24VDC -> SMC Regulator "Power Supply", Pin 1, Brown Wire A-B Analog Output (+) -> SMC Regulator "Input Signal", Pin 2, White Wire A-B Analog Output (-) -> SMC Regulator "GND (COMMON)", Pin 3, Blue Wire Bulk Power Supply 0 VDC -> SMC Regulator "GND (COMMON)", Pin 3, Blue Wire

The SMC User Manual for this regulator (I had to look it up) shows the Power common and the Analog Input common to be the same terminal. Connect the Analog Common from the 1746-NO4V channel to the SMC Regulator's DC Common terminal (blue wire). On the 1746-NO4V module, the Analog Common is pin 1, 3, 5, or 7 depending on which of the four channels you are using. See page 3-13 of the User Manual, Publication 1746-UM005.

Connect the analog common from the 1746-NO4V to the V- on the regulator. This will give the regulator a zero voltage to which it can compare the analog input voltage.

The LEDs on the front of the controller will provide the basic diagnostics. Post the model of PLC-5 (like 5/25 or 5/40) and what the LEDs are doing when the keyswitch is in each (Prog / Rem / Run) position. What kind of power supply are you using ?