Gordo26

Would using a decoupling capacitor be an effective way to reduce noise in the power supply? I've used this in the past in small electronics projects and I wonder if would be of use in this situation? Thanks for your input, I really appreciate it!

Hello, I have 3 identical conveyor stations which use an XWT-OD161 output card. I've had several instances where multiple outputs should be on, but aren't. The PLC is telling the outputs to turn on but they don't come on. After opening and closing the fuse holder for that output card the outputs start working again right away. I'm assuming the problem is inherent to the wiring of the stations as one person would have wired all three stations. I have several other conveyor stations using the same output cards that are somewhat different in how they are set up and I have not experienced this problem in any of those stations. If anyone has any advice or knowledge they could help me with I would very much appreciate it. At this point I'm not sure where to start in troubleshooting the problem. Thanks, Gordo26

My apology, I'm not using a DeviceNet communication module on the drive itself, I am using digital inputs to the drive that come from a remote output deviceNet card. I checked my deviceNet error and it does not come from the output card that I'm using to control my drive so I don't think the deviceNet error is the problem. Thanks for your suggestion though, much appreciated! Thanks, Gordo26

I had a strange occurrence today where my PowerFlex 70 drive just stopped. It had no faults, it just said Stopped, all I had to do was press the green start button to get it going again but this has never happened before. I did have a DeviceNet error just before this happened. I use DeviceNet inputs into the drive for start/stop/direction. Any suggestions on what the cause could be would be greatly appreciated. Thanks, Gordo26

There are several motors running off VFD's in the area and I did notice we use SO cord which runs along the same path as the wires for the proxy's. The proxy's are three wire PNP. As for a bad ground, I'll have to wait for some downtime before I'm able to check that out. Thanks very much for your help! Gordo

Just wondering if anyone else has ever seen this, and any advice that anyone might have. I have two proximity switches on a conveyor line, one is used as a decel, the other is used to stop the objects movement. For some unknown reason both of these switches are randomly turning on without any metal touching them at all. This happens to mess with the sequence of operation and is becoming quite troublesome. The proxy's go back to a multiport terminal, which is then fed back to a remote input card. Both the multiport, the input card and the multiport cable have been changed out and the problem still persists. Any help would be appreciated. Thanks, Gordo

Hello all, I have CS-Designer V3.2, the PT has system version 8.1. The PT is an NS15-TX01S-V2. The problem I'm having is after working with a screen for some time and downloading and uploading to and from the PT something goes wrong with the project. I open the project and it will either automatically say "CX-Designer Has Stopped Working, Windows Is Looking For A Solution", or it will display this immediately after I try and open up a screen. It's really frustrating because now I can't even work on the screen I've made changes to unless I revert to an older version of the project. Anyone else have this problem? Is there any kind of update that I might be in need of to repair this problem? Thanks in advance, Gordo

In going through the network and drawing out the topology and where the devices are located I think I found the solution. An outside company was contracted to put the deviceNet network in for us and I've found we are missing an EOL resistor which could be the cause of the problem.

Well, I discovered the solution to my problem. I had the Resume function on in the memory switch and this wouldn't allow the new string descriptions to load in.

Hi all, I have an NT631C Omron HMI and I can't seem to see the String I'm referencing in the History By Occurence or Frequency logs. I can see the a new fault get added to the list when I activate a fault. I can also see the time and date but not the string display that describes the fault. Any ideas on what the issue might be? It may be just some setting I'm not seeing but I've been through both the reference manual and the set up manual and I can't seem to figure it out! Thanks in advance for your help. Gord

Thanks for the response, what I'm seeing is bit 4000.00 flickering on and off. This is a DeviceNet input coming from another PLC. I do have separate power supplies for DeviceNet and my I/O. I'm logging a ton of Remote IO Communications Error on the master PLC for the network and the error code identifies the problem as coming from node #6, which is where I see the flickering bit. I've changed out the cable coming from the T branch and the problem still persists. Note that I have a exact replica of this slave PLC (node #6) at one end of the trunk set as node #7 and it has the same bit (4000.00) coming from the master and isn't flickering. Would I be right to say the problem is with node #6 or could the problem be elsewhere?

Hi all, I have a CJ1M CPU-11 PLC with an attached CJ1M-DRM21 DeviceNet unit attached. This unit is being used as a slave and has the master function disabled, this unit is Node #6. This unit is mounted in a panel used for a scanning station, there is an exact replica of this station located about 50ft and it is set as Node #7. Node #7 is on one end of the network (ie: the EOL resistor is located near this nodes branch). Currently I am getting a large number of Remote IO Communications Error logged in the master DeviceNet unit for the network and the errors are logged to Node #6. There are no errors showing on the 7-segment displays on any of the units at any time that I have been watching. Also, I removed the branch cable leading to Node #6 at one point and replaced it with a new cable, the problem seemed to have stopped for a short period of time but then it reappeared again (maybe 10min or so). I discovered the problem after seeing one of the DeviceNet inputs on Node #6 flickering on and off, which I assume is a direct cause of the Remote IO Communications Error. Has anyone ever seen this type of problem, is there anything that you could think that I could try to fix the problem? *Note: The voltage between CAN-H and V- is 3.2V, the voltage between CAN-L and V- is 2.4V and the voltage between V- and drain is 0.1V (Node #6 and #7). The network voltage at both Node #6 and Node #7 is 23.8V.

I went to View --> Memory View and checked my UM Memory usage there and it shows that I have no free UM Memory left!

Hi all, today while making some changes I encountered an error. I'm not sure why the error keeps coming up but I really need to make these changes before Monday. The PLC I'm using is a CJ1M-CPU11, which has 5K steps of UM, after going through the program I count that I have only used less than 2K steps. So I don't believe I've used up all my UM. I've checked all the manuals I have for this error and I've went through numerous forums and I still can't a fix for the problem. I've attached a screenshot of the error for you to view. And suggestions or advice would be of great help. Thanks, Gordo26

Hey guys, just wondering if anyone can tell me if it's possible to upload a DeviceNet network configuration from a PLC without actually having a CX-Integrator file to work with in the first place? I'm also not entirely sure how many or what type of devices are on the network. I'm connecting to the PLC using ethernet and I have the IP of the connecting PLC. I know I can connect to it, it just says that the "Functions of the relay device may not work properly", and the last thing I want to do is shut down any equipment. Any help would be greatly appreciated. Thanks, Gordo26