Joe E.

MrPLC Member
  • Content count

  • Joined

  • Last visited

Everything posted by Joe E.

  1. info possibilità aggiornamento

    Google Translate: You will need RSLogix 500 or RSLogix Micro. There is a free version of Micro (Starter Lite) and a relatively cheap paid version. RSLogix 500 is more expensive but also covers the SLC 500 series processors. Contact your local distributor for your pricing. If you don't have a project archive file for the PLC, you can upload it but you won't have any symbols, comments, or other documentation. The project file will have an "RSS" extension.  
  2. ML1400: Manipulate output through modbus/tcp

    To control a bit at a time, investigate the XIC and OTE instructions. To control a word or 2 at a time (all outputs at once), look at the MOV and COP instructions. Consider also how to handle problems. You WILL at some point have a communications error between the PC and PLC, invalidating the data stored in B10. You need to have a way to detect that failure and respond to it in a fail-safe manner.    
  3. RsLogix 5000 firmware upgrade

    Yes. If you don't have a support contract, try contacting your local distributor. They may be able to help you get the software you need.  
  4. DF1 and PLC5 vs SLC500

    That's interesting... I recently installed a CompactLogix processor to control some newer components as part of a system controlled by a PLC5. It's been working fine, but we decided to take it to the next level which requires passing a lot more than the 2-3 discrete signals. To save money and time, we added a ControlLogix chassis controlled by the CompactLogix via... Ok, cut to the chase.... I set up MSG instructions in the CompactLogix to get information back and forth between the CompactLogix and PLC5. When configuring the MSG instruction, you have to select either "PLC5 typed Read" or "SLC typed Read". I wonder what the difference is... Of course, this was over DH+, so it may be completely different...
  5. DF1 and PLC5 vs SLC500

    Agreed, the cable should be correct. If the registers are numbered differently enough (by byte instead of by element), the device may be trying to read non-existent registers. Not sure how the PLC would react to that. It may just return 0s or ignore the request.  
  6. studio 5000 ultilzation chalenge

    What kind of time period are you talking about? Daily, per shift, weekly, for the lifetime of the machine? The PLC can easily accumulate machine run or stop time (using RTO instructions or a periodic task for more accuracy) while the PLC is running. If you trust the RTC (Real-Time-Clock) to be accurate, you can use a GSV instruction to grab the date/time every scan. I usually use the GSV to grab the Wall Clock, local time, but in this case I might use UTC in case it's down through a time change (not sure if the RTC automatically updates for DST or if it will do so while the PLC is off). Then, on first scan (using S:FS or the power-up handler), you can grab the time again and find the difference between them to see how long the processor was not in Run mode. This should be accurate to within 1 or 2 scan times. If you're just interested in the times for the current shift, you can have your RTO/Periodic task accumulate run time and just subtract the shift beginning time from the current time to determine total shift time. Then you'd have your run time percentage. The time subtraction will be a little trickier if your shifts span days (like our 3rd shift starts at 10:30PM) but should be manageable.  
  7. DF1 and PLC5 vs SLC500

    My colleague just got a MicroLogix 1400 PLC talking to a PLC5 using DF1 via their serial ports. He used a straight serial cable with an in-line null modem adapter and a standard DE9-DB25 adapter. He then used a pair of 9-pin prototyping breakout connectors with a 3/c cable that just used 2-3-5 with 2,3 swapped. The cable connected the MicroLogix's 9-pin connector to the 9-25 pin adapter on the front of the PLC5. Looking at a diagram from a manual, he thinks it would work with just 2,3,5 on the MicroLogix end connected to 2,3,7 on the PLC5 end, but we don't have any 25-pin breakout connectors to easily test that.
  8. DF1 and PLC5 vs SLC500

    Not sure if it's helpful, but look around page 125 or so of this manual: It looks like there's a difference between the DF1 drivers of the 2 platforms with byte vs word addressing. Disclaimer: I've never dealt with this at this level, so this may turn out to be a wild goose chase.
  9. activity log set up validation warning error

    Where did the runtime you posted come from? Was it running in the old standard unit? Look at the PV+7 line as well. They're not cut-out compatible but we've converted a couple of units over with no issues.
  10. activity log set up validation warning error

    Hmmmm.....weird. I restored the MER on my machine too. It automatically upgraded the project to 8.2 since that's what we're running. It's weird that it would refer to a non-existent screen in the runtime file that was created for a compact HMI, but it could be that the runtime restoration process puts in some default values that are causing an issue. That seems crazy on the surface but would about par for the course for View Studio. I was able to test the runtime successfully by deleting [DIAGNOSTICS] from the "Display name" field in the Diagnostics List Setup dialog. I just left that field blank; not sure what that will do in the real world.   Was this mer file running on a PV+600 Compact before? What are the catalog numbers of the old and new HMI devices?
  11. activity log set up validation warning error

    You shouldn't have to recompile the runtime. You can use the ME Transfer Utility to upload the MER file from the old HMI and download it to the new one. That *should* work, but you said it doesn't. Can you post the mer and apa files here?
  12. Arduino to Compactlogix communications

    The Red Lion DSPLE that Ken talked about sells for around $600 (click here for Newark). If it's capable of doing what you want (and it probably is), it will be a far more economical and reliable solution. The DSPLE connects seamlessly and easily to a CompactLogix PLC and supports a generic raw serial port. They don't have a Mitutoyo driver in the version of Crimson 3 we're using, but may be able to help you with one. Their support is top notch.  
  13. HMI - Managing I/O Field behavior

    I haven't used that PLC/HMI before, but I have used WinCC Flexible/Comfort and S7-series PLCs. Do you have access to the PLC to modify code there? If so, you can use a numeric display with a button next to it or use a button with the numeric display superimposed on it. In the AB world, you can embed the numeric value inside the button caption itself but I don't know if you can do that in the Siemens world. The button would control a tag in the PLC that selects which number the function keys will increment/decrement. You can probably use a rectangle behind the button or an indicator/animation tag on the button to highlight the one that's selected.
  14. Index Tag Names though AOI

    Can you create new tags? If so, you can create arrays of tags called SOL of type BOOL[177], PhotoEye[177], etc. Arrays are 0-based, so unless you have a workstation 0, you need 177 elements to be able to index to SOL[176]. You can also create a UDT for each workstation of type WORKSTATION with sub-tags for whatever's in the workstation. Then you can create another tag called WorkStationTAG of type WORKSTATION[177]
  15. Point io power consumption calculator

    Rockwell's Integrated Automation Builder should do that for you. It's part of their product selection toolbox download:
  16. Panelview Plus 600 problem

    Rebuild the project from scratch, I'm afraid.
  17. safety relays

    Brief summary... A manual reset requires operator action to restore operation, like pushing a "reset" pushbutton. An automatic reset will restore operation as soon as the safety channels and any feedback circuits are closed. "Monitored" means that the reset circuit (whether it includes a pushbutton or not) is wired through feedback contacts on the devices being controlled. This would typically be normally-closed auxiliary contacts on force-guided contactors. If a contactor sticks closed, the aux contacts remain open and the circuit will not reset. Multiple contactors controlled by the same safety circuit will have their aux contacts wired in series to make sure they all drop out. We have also used redundant pneumatic dump valves with feedback contacts.
  18. Allen Bradley/RS Linx

    If you're using a USB adapter (like the UIC), connect it to the VM, then open Device Manager inside the VM to determine the COM port. Then use that in RSLinx.  
  19. Panelview Plus 600 problem

    Contact the person who locked it with a password.
  20. Produced/Consumed Tag Communications Active

    You are on the right track. The Studio 5000 help file has a list of the status values. Before I investigated the GSV instruction, and when communicating between machines where produce/consume isn't possible, I use a heartbeat flasher. Have each machine blink a flag that the other has access to read. If it stays in one state too long, you have lost communications.
  21. Logix 500 math instruction with Decimal Point

    I couldn't get it to work dividing an integer by a literal decimal number and storing in a decimal. What does work is dividing an integer by a literal and storing it in a float register or dividing an integer register by a float register and storing the result in a decimal:  
  22. My background: My first job (almost 2 years) working with PLCs was as a multi-craft maintenance tech in an AB plant. I rarely used the PLCs for diagnostics. Most of the time when I did, it was a system with a Soft Logix controller running on a PC that was always online and which we could only look at, not change. About 70% of my time was fixing mechanical issues, 30% electrical issues (sensors, cables, damaged wiring, etc.). I probably used the PLC code to help with 5% of my repairs total. It was very very little. I never made any changes to PLCs or HMIs. My second relevant job (almost 4 years) was as an Automation Specialist in a plant that was mostly AB Logix 500 but was about 20% Siemens S7-300/400. The company sent me to the 1-week programming 1 classes for both the SLC500 and S7-300 within the first few months of my time there. I worked with both, probably a 70/30 AB/S7 split for time spent online. I did very little original programming in the S7s and what I tried was very difficult. To be fair, some of the difficulty was just the way the programmers went about things, doing the entire machine in STL instead of LAD. There were some other things they did that made it extremely difficult to track down problems that I can go into if you're interested. My third (and current) relevant job (8 years in November) is Electrical Engineer in a manufacturing facility that's about 60/40 AB/Siemens. The AB stuff includes PLC2, SLC150, MicroLogix, SLC5/xx, ControlLogix, and CompactLogix PLCs and Panelview Standard and PV+, PV+6, and PV+7 HMIs. The Siemens equipment is almost all S7-300 (with a few S7 Technology processors) in Simatic Manager with a few newer ones having S7-1500s in Portal. The HMIs are the obsolete MP series (in WinCC Flexible 2008) and some of the newer Comfort Panels (in Portal). For drives, we just replaced the last AB 1370 DC drives but still have a lot of 1336x drives left. We've mostly moved on to PowerFlex 700, 700s, 4, 525, 755, and DC. Siemens drives include MicroMaster 420/440 and the newer Sinamics S120/G120s.   All that follows is my opinion, based on my experience. I have not encountered anything that the Siemens systems do better or easier than AB with only one very limited exception: their HMIs can communicate with AB PLCs out of the box, while the AB HMIs can't talk to S7s without adding some licensed software and jumping through some hoops. Unfortunately, their HMIs are far less robust and sturdy than the PV+. Other than that, Siemens is more cumbersome and more difficult to train people to use reliably. There are a LOT more ways for an electrician to mess up and break things in Siemens than AB. Software versioning is an absolute nightmare, due in large part to the Technology processors. The S7-Technology software (necessary for the motion control they're doing) supersedes and replaces the drive Starter software and is NOT backwards compatible with older versions. IOW, if your S7-T software is newer than the project, you have to upgrade the project to open it and you then can't go online with the drives without downloading to them from the upgraded project. I'm maintaining 5 virtual machines on my laptop to handle all of the versions of S7-T. If someone accidentally opens a drive object and upgrades it, then saves the project after making PLC changes, there's no way to fix the archives. It's a mess that Siemens tech support gave up on fixing. I can provide more details of that process as well, if you're interested. Bottom line: I can get far better results far faster using AB hardware/software than I can with Siemens. Outside North America, AB's distributor network is lacking, in our experience, which gives Siemens an edge overseas, especially in Europe. That doesn't make their hardware/software any better, though.

    Sorry I couldn't help more. The only Kinetix I've worked with is a 6500 and it's controlled by a CompactLogix L33ERM. I've never used the MotionView software.

    One of the things that annoys me the most about AB is their paid support system. If you don't have a contract with them, I think your best next step is to go to your local distributor. They're supposed to have experts on staff to help with different products. Our distributor has been very helpful with issues we've had, in some cases better than AB.

    Your local AB distributor is probably the best bet if you want to talk to a live person. I just searched for MotionView on Google and found Rockwell TechNote 823180 (Access level: everyone) that referred to this manual: A quick glance through the manual shows some references to MotionView and how to use it, but I didn't examine it in detail.