bagged2drag
MrPLC Member-
Content count
47 -
Joined
-
Last visited
Community Reputation
1 NeutralAbout bagged2drag
-
Rank
Sparky
Profile Information
- Country United States
-
Looking for some advice: We have some automation systems which have some Siemens devices communicating with Allen Bradley Compact Logix using Prosoft PLX32-EIP-PND communication gateways. From a hardware perspective, we have a single AB compact logix plc, connected to 4 separate and identical systems which each has a siemens CPU 1510SP F-1 PN connected to the AB via the PLX32-EIP-PND. All 4 gateways and Siemens systems are exactly the same, aside from the IP address in the PLX32-EIP-PND that points to the AB plc. All systems were integrated at the same time. We have had issues with one of the systems losing communication between the Siemens and AB. My team has been fighting this issue now for months with neither our automation team nor the 3rd party equipment provider being able to figure out the cause. I just started a few weeks ago, so I was just recently brought up to speed on this. Previously, it sounds like nobody had ever connected to the systems when the fault was occurring (we didnt have the internal resources available to do so) . My first thought was the Prosoft, as I have seen a number of protocol converters fail over the years. I helped my guys configure a new PLX32-EIP-PND and set the device name the other day, at which time we installed it. Fast forward to yesterday, and we see we are still intermittently losing communication between the AB and one of the Siemens systems (still the same one we replaced the PLX32-EIP-PND in). Yesterday, it had faulted and didn't come back online. I was able to finally get connected with the Siemens system while in this state. I could see active data on the ethernet port on the PLX32-EIP-PND that connects to the AB PLC, but there appeared to be no data between the PLX32-EIP-PND and the Siemens PLC. When I got online (in TIA Portal) I could see the PLX32-EIP-PND was showing as offline. I tried pinging it to no avail. All network connections looked good. All other network devices were still online. These connections do go through a small switch as well. Immediately after I unplugged network cable of the PLX32-EIP-PND and plugged it back in, the connection came back. For now, to rule out the network switch, I have swapped it between 2 of the Siemens systems (we will monitor to see if the fault follows the switch). In summary, we have replaced the PLX32-EIP-PND, and all thats between that and the Siemens plc is a small network switch. Looking back in history and it sounds like they have also tried a different ethernet cable as well, so I think that can be ruled out as the cause. Any ideas from anyone what could cause a loss of communication to only 1 device?
-
photovoltaic liked a post in a topic: smc2 ESI and IODD files
-
Thank you. I verified current programs match (change management is strictly controlled where I am), so I will proceed with my changes. I appreciate the information.
-
bagged2drag liked a post in a topic: smc2 ESI and IODD files
-
Would I simply be able to make modifications to the program and download the project to the HMI/PLC (whichever is applicable) then with no adverse effects? -Kris
-
I come from an AB background. My current job has a lot of Omron devices. We have a couple systems with NX102's with numerous IO link devices attached (IFM 1332, and some IO link sensors). I have the backup files from the integrator (.smc2 files). If I import the .smc2 files into Sysmac Studio and open the projects, will I need to manually add any of the .esi and IODD files to the project, or will they be loaded in automatically from the backup? The integrator alluded I will need to manually load the IODD files, but the IFM 1332 devices, for instance, appear to be loaded ok. It appears the files may be present, but I want to be sure prior to trying to update the HMI's, as downtime needs to be considered. Also, I have some banner sensors that are IO link. if I do need to add the IODD files for those devices, where do I add them? I assume these are IO slave devices? I don't see any configuration for them in the project, but again, the integrator alluded to the fact I will need to load these IODD files. Thanks,
-
Storing to Non-volatile memory - sporadic error
bagged2drag replied to bagged2drag's topic in Allen Bradley / Rockwell Automation
Thank you. I reached out for a quote this morning. Quite the tax, indeed! I don't use PV'+s anyway, but I can use my SD cards for my current HMI's too. Regards -
Storing to Non-volatile memory - sporadic error
bagged2drag posted a topic in Allen Bradley / Rockwell Automation
Hello, I am looking for some input. I have a 1769-L18ER-BB1B in which I have a some projects that I am saving to SD cards. I have saved a few already successfully, but when I went to save the latest sets, I keep getting an error that there is insufficient memory on the SD card when I select to store in Logix 5000. I am using software version 32.011. I have purchased 2GB Transcend SD cards and these have worked just fine before, but now I keep getting the error. I verified the cards are empty and still formatted FAT16. I have been using the same software revision and firmware revision for all programs. Regards, Kris -
HMS Communicator network issue
bagged2drag replied to bagged2drag's topic in Allen Bradley / Rockwell Automation
Oddly, shortly after I posted this, I decided to check the other PLC program, and indeed, the HMS communicator was also configured in that PLC as well with the same communication settings. I am guessing the machine builder just reused and modified the same plc program for the 2nd fixture. Next time I get to tha plant. I will be uploading an update with that device removed from the configuration. -
Hello, We have a system a vendor built which utilizes a Compact Logix PLC and a peripheral piece of equipment tied in via use of an HMS communicator. This system is also on the same network as 1 or 2 other plcs (depending what job is being run). The 3 plcs share some handshaking signals via produced and consumed tags. The system works just fine aside from 1 issue I don't seem to be able to resolve yet. When we boot up the system with the HMS communicator, we are not getting any data back and forth between the PLC and the HMS communicator if either of the other 2 systems are plugged in at bootup. Occasionally, even if the other 2 systems aren't hooked up, we also experience the same issue at bootup only. This issue is easily rectified if we momentarily unplug the other PLC's physically. Connection is immediately restored and works fine after. I had looked at all settings I know to, but I don't see anything that could cause this. I have set Unicast to disabled in the HMS device communication settings within Logix5000, thinking that it would help (which it has, as before we would often have the issue frequently when the machine was operating without the 2 additional systems hooked up). Any ideas what I should be looking for?
-
We had a computer failure in our facility and lost our latest backup from a project loaded in a machine. I have an early backup, and I uploaded the program from the machine. I would like to rename all the tags from the upload, as it is a bit older PLC so it didn't retain the names. I figured I could open the db from the old program and just copy the tags and paste in the new program, or simply rename the tags in the new upload, but I am unable to. Is there a trick? Do I have to be online with the PLC to do this? Or is it just not possible. If i recall, it is an S7-300 (315-2 PN/DP). I don't have access to the machine for some time, as I am working from home. I thought this would be a good opportunity to fix the program.
-
bagged2drag liked a post in a topic: Part tracking - counting rejects
-
Part tracking - counting rejects
bagged2drag replied to bagged2drag's topic in Allen Bradley / Rockwell Automation
I did very similar to what you suggested last thursday and it worked out well. I got rid of the for loop and utilize an add instruction with a DINT, driven off a timer. When the timer.dn bit is on, i increment the DINT 1(every 5ms). I use this dint to look at which position in my tracking array to count. I then add the value of the array position to a separate integer. When my position integer hits 101 (I am only counting 0-100 using a limit test in the logic), I move the value accumulated to a new integer which is what I use in my logic for my alarm. This all worked super well. My initial struggle was counting the value in each part of the array. I used indirect addressing to do it. -
bagged2drag started following Part tracking - counting rejects
-
Platform: Logix5000 I have a relatively simple task I am trying to complete. I need to track the status of a 100 part sequence to see how many parts have been rejected. Essentially, I need to keep track of the last 100 cycles and count how many parts of the last 100 have been vision rejects. I have written most of the logic, using FIFO with an integer with an array of size of 100. Where I am getting stuck a bit is how to accurately get the count of the array. I did make a for statement which will count the array and add it to a counter if the first bit is equal to 1, but this doesn't seem to be a clean way to do it, as I would also need to clear that counter before running the for statement. Thanks,
-
Click PLC and Keyence SR1000 barcode reader
bagged2drag replied to bagged2drag's topic in Other PLCs
I was able to get this partially resolved yesterday afternoon. So far I am able to send commands to the SR1000, and it is responding as expected. Now I will work to get the data back, as that doesn't seem to be working yet. -
Click PLC and Keyence SR1000 barcode reader
bagged2drag replied to bagged2drag's topic in Other PLCs
That could potentially be the issue. When setting up the send command, the click is quite a bit different than the AB. There is a checkbox for the termination command however; there is the choice of 1 or two characters, and hex only. I will give that a try next time I get out to the equipment. They give you an option of choosing the term from a table. didn't notice that the first time. I'm more used to robots where you just type [CR]. -
Click PLC and Keyence SR1000 barcode reader
bagged2drag replied to bagged2drag's topic in Other PLCs
Correct, pcmccartney1. The LON ascii command is what I was sending to trigger (read). I was getting a write success bit back on the plc, but I was not seeing the camera trigger. LOF is the trigger stop command. If I opened terminal on a PC, the same LON command starts triggering the camera. LOF would then stop triggering. That's where my confusion (lack of knowledge and experience) comes in. Why would I get a write success on the PLC? Does the write success ignore any sort of feedback? -
Click PLC and Keyence SR1000 barcode reader
bagged2drag replied to bagged2drag's topic in Other PLCs
You are right, there is an RS485 port. The programming port can also be used as RS232. Hopefully NevergoldMel can chime in. I've used RS232 on the Click before, but never for ascii (you have to choose ascii or modbus protocol with the click). My send and receive show up as successful, but I am not seeing any data (send isn't commanding the picture). I think the issue is more on the side of the Keyence.