phuz

I quite often am found in plants that require some type of safety shoe (steel toe) and always dreaded wearing my steel toe boots. I was looking for something more comfortable that would still meet the criteria. I came across these Timberland Pro Mudsill Low safety shoes. They arrived yesterday and I already cannot wait until my next plant visit. They feel like any other sneaker, except they are front heavy. :) Just thought I would share in case others are in the same boat. http://www.amazon.com/dp/B000XEZ79W/ref=pe_385040_30332190_TE_M3T1_ST1_dp_1

I'm having some issues communicating with this PV 1200. I have my regular PV cable and a 25/9 pin adapter as well as two other serial cables with 25 pin serial / 9 pin serial connections. I've tried all three with and without my null modem adapter and cannot get any communication in RSLinx DF1 nor the PV1400 transfer utility, which is supposed to work for the 1200. Serial port settings match the config in the PV. I am on the assumption that the serial port on the PV actually works, but it may not. PV in config mode / download-upload screen.

We are using a Powerflex 755 with a Safe Speed Module for safe speed limiting and door monitoring. We have a 20-750-ENC-1 which was purchased for this project, but I am seeing in some documentation that a 20-750-DENC-1 (dual encoder) is required for this. We are receiving a feedback fault from the safe speed module which tells me the problem is with the encoder module and I am thinking we have the wrong one. However, while poking around Drive Executive under the Safe Speed module, under Feedback, under Fbk Mode (Parameter #27), I can choose Single or Dual, so I would expect the 20-750-ENC-1 to work. Wrong? Also, we cannot locate any manuals on the encoder modules. Are these available or are they buried in a different manual?

We have a Powerflex 755 and Powerflex 4 on the same network. Our ControlLogix and Panelview are also on this network. Everything is connected to an 8-port Stratix switch. Every so often (about 30-60 minutes if I had to guess), we will get a "Net Idle Fault" on the Powerflex 755 and F071 Comm. Fault on the Powerflex 4. We have no problem communicating with the drives. Other than checking the terminations of the patch cables, what else can we look at? EDIT: This is happening every time we do a download to the ControlLogix

I am running out of options for troubleshooting this, so I am hoping someone here can help or point me in the direction of someone who could. I have a VB.NET (.NET 2.0) application that uses the Interop.OPCAutomation.dll wrapper. It was developed on Computer A and works fine. The source code was then transferred to Computer B where it throws an error and will not test successfully. Computer A: Intel i7, Windows 7 Ultimate 64 bit SP1, Visual Studio 2012 Computer B: AMD six-core, Windows 7 Ultimate 64 bit SP1, Visual Studio 2012 These application does not have 32-bit and 64-bit dlls, so it shouldn't matter, but even so, they are both 64-bit systems. On Computer A, the application will connect to the OPC server and read/write values that I have without a hitch. On Computer B, when I attempt to connect to the OPC server (which is a mirror setup of the OPC server on Computer A), I get this error: Error HRESULT E_FAIL has been returned from a call to a COM component System.Runtime.InteropServices.COMException was unhandled ErrorCode=-2147467259 Message=Error HRESULT E_FAIL has been returned from a call to a COM component. Source=Interop.OPCAutomation StackTrace: at OPCAutomation.OPCServerClass.Connect(String ProgID, Object Node) at Weather.Form1.btnConnect_Click(Object sender, EventArgs e) in C:\Users\keperling\Desktop\Weather Data\Form1.vb:line 678 at System.Windows.Forms.Control.OnClick(EventArgs e) at System.Windows.Forms.Button.OnClick(EventArgs e) at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent) at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.ButtonBase.WndProc(Message& m) at System.Windows.Forms.Button.WndProc(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg) at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(Int32 dwComponentID, Int32 reason, Int32 pvLoopData) at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context) at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context) at System.Windows.Forms.Application.Run(Form mainForm) at Weather.Form1.Main() in C:\Users\keperling\Desktop\Weather Data\Form1.vb:line 0 InnerException: The code that occurs at Line 678 is: OPCMyServer.Connect("KEPware.KEPServerEx.V4", "localhost") Again, this identical OPC server is setup on Computer A. I have spent about 12 hours trying to determine what is different between the two systems, but there is nothing that sticks out.

I have this CompactLogix L18-ERM-BB1B with version 20.001.36 and I am not able to upload or download to it. Logix5000 tells me the offline version file is not compatible with the controller revision. So I try ControlFlash to bring it up to 20.12 or 21.11 and it fails telling me it received an unknown error code. Here's the error in the log file: 12/17/14 14:22:24 [FAILURE] Transfer: Error #11001: Unknown General Status error code received. GS=0x1E 12/17/14 14:22:24 [FAILURE] Transfer: File = C:\Program Files (x86)\ControlFLASH\0001\000E\009B\PN-156514.der, Block = 1.

Yes, that was my reaction too. What are the odds? An L1x series processor and 3.1 IE4C module and I happen to have both.

I have used PointIO a few times, but this is the first time using an IE4C. The wiring seems pretty straight-forward with Ch0 going to terminal 0 and the common is on terminal 4, if used. I started off having a solid red status light for the network status, so I changed keying, reset the module, re-seated it and the TB3 base, and finally got a green status light for both, but I am getting ZERO data. The channel faults are all 0, and the data is all 0, regardless of what I put on the input. I put a simulator between terminals 0 and 4 and the data still doesn't change from 0. What's more strange is on occasion, I have gone into the IE4C properties and under the Module Info, it would sometimes show Unknown or "Control Techniques PLC" for the vendor. I have seen about 4 different serial numbers appear, and even the revision number has changed. If I hit reset module, it goes back to saying Allen Bradley with the correct serial number and correct revision number, but still does not give any data. I am assuming the module is bad and I have another one en route, but was curious if anyone could explain this because I haven't seen it on any type of module before.

Unfortunately since you can't update these modules in the field, I had to buy a new one. Now with the 3.4 firmware version, all is well!

Thanks to a member on plctalk for shedding some light on this. https://rockwellautomation.custhelp.com/app/answers/detail/a_id/508507 508507 - CompactLogix 5370 L1 controller incompatible with 1734-IE4C firmware 3.001 modulesAccess Level: Everyone Date Created: 10/09/2012 09:23 AM Last Updated: 12/01/2014 10:49 AM QuestionWhy is the input data static from 1734-IE4C series C in CompactLogix 5370 L1 controller but works fine in 1734-AENT® chassis? Next, here are examples of typical conditions reported: L1 controller I/O status LED is solid green1734-IE4C module status LEDs appear fineOnline no errors are displayed in Controller I/O treeSame 1734-IE4C module works fine when placed in 1734-AENT® chassis AnswerUse 1734-IE4C module with firmware 3.002 or higher when using as local expansion Input module with CompactLogix 5370 L1 controllers. 1734-IE4C series C module firmware 3.001 is not compatible with CompactLogix 5370 L1 controllers. Note: 1734-IE4C module firmware is not field upgradeable.

I have to wonder if it needs calibrated, which I could do on the calibration tab. I mean it can't hurt at this point. I also may take this IE4C over to Fromm Electric and pop it in their demo L18 and see if that reads the data correctly.

Unfortunately I put 12mA on it from a separate source and still get nothing.

I have a few customers who have migrated from AB to Red Lion, who, as a bonus, is only 45 minutes from me. It's hard to justify the 2x cost for a comparable AB PV+ when Red Lion has more standard features. What gets me is the bootup time, which on a Red Lion, is next to nothing. And they certainly interface well with the PLCs. Good stuff!

OK, replacement module shows up, and I am STILL not getting any data. I have the unit powered with 24VDC and I have 24VDC on the FP+/-. Since my transmitter is powered from the same 24vdc, I have the current input going into Ch0 (terminal 0) and nothing else connected. Oddly, Ch1 and Ch3 show data of "85" even though there is nothing connected. 0 and 2 show "0". Ch0 and 2 also show channel faults.

Nope, this is local IO on the Compact backplane. I've tried it with and without power on the FP+ / FP-, with and without the common attached to the terminal 4. They are expensive little modules and I'd hate to see it end up in the trash.

Managed to go over to the local distributor, who has an L18ERM series A, so I created an SD card with firmware and set the appropriate settings. Brought it back and powered up this unit. SD card light was flashing, as if it were being read, then both OK and SD were flashing, then it rebooted, and now I am left with a solid RED OK light. I am sure the unit is toast, but might I have any last ditch efforts to kick this out of its current state? I was almost optimistic when I saw it reading the card. The unit I mirrored was identical, except for the serial number, which I changed on the flash card.

Yes, and I am friends with one of the local guys. I already reached out to him this afternoon before I called Rockwell. He might be able to help me get some files on an SD card tomorrow if someone doesn't email them to me tonight. Yes, my jaw dropped when she said that. I have always been more successful with resolutions from these forums vs. calling RA. In fact, one time I was troubleshooting a DeviceNet VFD issue, and the tech said "Here, I found something on that..." and they were referring to MY thread on a forum. I thought maybe they were referring to a knowledgebase article or something similar, but he was actually searching the internet. But I digress.

  Exactly. The minors shouldn't matter. I don't know what to make of this situation. Rockwell provided ZERO help. After about 10 minutes of obvious troubleshooting and requesting that I try v19 firmware (yes, they actually suggested I try v19 in a L18ERM), she said there was nothing else they could do to resolve it.

OR....could someone send me all the files from the SD card (assuming you have auto restore firmware on power up enabled)? Then I can just copy them to my SD card and see what happens at power up. I think it's my only chance to get this controller back to life.

The problem is the controller, according to control flash is 20.001.36. According to logix, its 20.01. I am not sure which is right. If I open my RSLogix5000 "about" page, it says I am on 20.01. So I shouldn't be having this issue. I don't even know how to acquire 20.001.36.

I am trying to setup a SLC rack as remote IO with a 1747-ASB. I have the DHRIO set as Node 01 and 230k and the ASB also at 230k. When choosing 1-slot addressing with 10 logical groups (10-slot SLC chassis), I get "noc" at power up. If I choose 2-slot addressing, I get "P04" at power-up, which is referencing a 16-pt discrete input module. I don't understand why. I have shielded cable between the two cards with 150 ohm resistor at each termination. I have done this on a PLC-5 before, but not a SLC. This is proving to be more difficult.

Has anyone had any trouble with this version at all? I've been using it for some time, even yesterday on a customer site, and today it crashes as soon as its opened. The windows crash details for APPCRASH state RSTOP.DLL as the fault module. I tried to repair utility in the RSLinx setup, but that didn't make a difference. Had to do a full uninstall and I put 2.59 for now because when I tried to reinstall 3.60, it wouldn't proceed forward because RSNetworx was not on v21. Not sure how I installed it the first time.

Just like my red Staples button says, "That was easy!" Thanks again, Ken.

I am trying to do this correctly. I have two remote SLC racks over RIO. Both have analog IO so I presume block transfers are inevitable. I am currently setup for 1/2 slot addressing as I understand this is a must for the NI4 and NO4I input/output modules. I added a generic RIO module, as required, in the CLX program for use with the analogs in the SLC chassis, but I am not sure exactly what I need in the block transfer messages. Could someone point me to some examples?

Thanks. If it's really that simple, I'd prefer to use 1-slot instead of 1/2 slot. I'll give it a shot later and let you know how I make out. Thanks for the quick reply, Ken.