PdL

MrPLC Admin
  • Content count

    3048
  • Joined

  • Last visited

Posts posted by PdL


  1. I don't think there are specific examples on how to hook up a Powerlogic meter, as the connection is Modbus which is generic for all devices. Here is an older document, not sure if there have been changes since but I guess it can't be much different than it is today.

  2. Your "luck'' figures. The first word of your control area controls the screen number of the PT. So by turning on output 0.00 in your code you actually changed the value of register IR0000 which you also (temporarily) defined as control area to 1, and the PT displays screen number 1. When you want to change the screen by pressing a screen jump button, on the next scan the output is still on and the register value of IR0000 is set to #1 again. Thats why the screen ''reverts'' back... You should not use the control/notify area in your code for any other purpose than to control the screen number. If you set it to use HR0 / HR10, put a contact 253.15 (from the top of my head thats first scan pulse) that fires a MOV instruction that sets HR0 to #1 (or any other screen number you want to display at power on). By using the first scan bit the register is not continuously set, which allows you to change the screen by screen jump buttons. You should see the actual screen number reflected in the value of HR0. The PT will display the screen number that represents the BCD value of the control area first register. If you put HR0 in your watch list, and enter any BCD number (use #, eg. enter #10 for screen 10). Be sure to put monitoring mode to Hex and not decimal. (look for the icon in the CX-Programmer toolbar). Use you own imagination what you can do with the ability to control the screen number from your code. E.g. when an alarm turns on jump to the alarm screen, or when a code is entered jump to a settings screen, etc etc.

  3. CF cards especially the bigger sizes are cheap. We had a few trays of 128mb cards at my old company but the 2GB ones are even cheaper. My epxerience especially if the customer needs to download programs is that this method is monkey proof, the worst that can happen is that a customer mixes up restoring and backup, thats why I wrote this step by step instruction. No cable hassles No driver issues No software version issues Just about any laptop takes a PCMCIA adapter or USB-CF adapter. I never found the PLC backup tool to be worth much.

  4. I used to have a copy of a "fresh" registry file from a system where the toolbars were ok and stored it somewhere on my drive to apply whenever I had fights with the toolbars or windows. On a healthy system, have a look with regedit in the CX-Programmer section and copy the toolbar registry files. Just double click the *.reg files to apply them. Not sure from the top of my head anymore how they were called but I remember it was pretty intuitive to find them when I browsed the registry. If you are not comfortable messing with the registry, leave it.

  5. In that case, like lostcontrol mentioned you can use move, xfer etc to copy data e.g. from DM0000 to DM1000. The only downside is that it is oneway traffic, in other words if you do it like that, you cannot reflect changes from within the PLC back to Modbus area. Any change of data will be overwritten by the move instruction in the next scan.

  6. Hi. you might want to take a look at the SCU unit settings in the IO table. Not 100% sure if your version supports, but have a look. Instead of setting the port to Protocol Macro and using a dedicated macro, you can set te port to Modbus RTU slave. You can then map memory areas to specific modbus commands. E.g. set holding register commands to r/w DM area, input registers to W area, and coils to CIO area. Sounds like exaclty what you are after, and does not require a single line of code.

  7. Hi Sergei, I have suggested PMCR and asked him personally to join. I have changed jobs recently and am not actively involved with Omron products anymore, and given his widespread knowledge of both old and new Omron products and software together with his way of teaching and taking the time to help others I thought he would be a good candidate. Basically there is no guideline for this procedure, anyone can apply, whereafter the moderating team will give their opinions. Hope this answers your question!
    1 person likes this

  8. As of today, users PMCR and Michael Walsh joined the moderating team here on MrPLC. It is great to have them on board!
    2 people like this

  9. Make sure you have the zoom set at 100%. Any other level makes the objects look different. E.g. a label might fit on a button when zoomed at 150%, but when you zoom out to 100% it suddenly overlaps. 100% is how it will appear on the terminal.

  10. By my knowledge the NQ series cannot be simulated using CX-Designer or CX-Simulator simply because it is not part of the CX-One suite, this HMI is as I believe a low cost product from India and kind of an odd one out in between the NS series. The NQ Designer software is also not from the same development team as CX-One.

  11. A good tip from forum member pro17 to overcome the difficulty and cost of tyring to obtain small memory size CF cards: http://forums.mrplc.com/index.php?showtopic=22077&pid=106959&st=0entry106959

  12. I sure hope that when you do Bob, you will use a quality OPC server like Kepware. The Omron drivers for Kepware are way, way better than the big player SCADA systems native Omron drivers (Citect FINS, Cimplicity TCP/IP). The throughput performance doubles at least, the driver documentation is the best and collects all important info on a few pages as opposed to Omrons own bibles, the driver even tells you when you have forgot to set your routing tables where native Omron drivers let you look for days. The support for new memory types like DM bits (CJ2) Work area etc are released months before any other driver even earlier than Omrons own software CX-Designer etc. I can imagine your experience with BACnet OPC was a horror story but don't treat all OPC servers alike...

  13. I sure hope that when you do Bob, you will use a quality OPC server like Kepware. The Omron drivers for Kepware are way, way better than the big player SCADA systems native Omron dirvers (Citect FINS, Cimplicity TCP/IP). The throughput performance doubles at least, the driver documentation is the best and collects all important info on a few pages as opposed to Omrons own bibles, the driver even tells you when you have forgot to set your routing tables where native Omron drivers let you look for days. The support for new memory types like DM bits (CJ2) Work area etc are released months before any other driver even earlier than Omrons own software CX-Designer etc. I can imagine your experience with BACnet OPC was a horror story but don't treat all OPC servers alike...

  14. What OPC client application are you using? What is the update criteria? E.g. are the OPC tags being polled by a fixed interval, or is the client application controlling this (also known as unsolicited updates). E.g. when your OPC client gives a command to set a bool tag, the OPC successfully sets the bit value in the PLC, but next the question is how this data value update is being directed back to the OPC client. Some clients support unsolicited updates from the server, e.g. only the changed data is being pushed to the client, when no change by the server is detected no update are done. Some clients have a "poll after set" setting that will force a read back of any "set" data actions. Have you enabled the diagnostics function on the Kepware channel? (general Channel setting tab) Next you can launch View > OPC diagnostics for a detailed view on all events. Some more information is needed here, I suggest you open a dedicated topic and I will move relevant posts to it.

  15. I once had a problem with address formatting. I imported an alarms CSV file, address formatting was wrong but CX-Designer swallowed it anyway and was able to download. I got this error on the screen where I had my alarm list. Only when I manually tried to open/close the alarm list entry it gave me a fault on the address.

  16. Check the EDS file (open in Notepad) for the device name (I think the string is Model_name), perhaps it is not what you expect and you are overlooking it in the library tree? else, post the EDS file, so I can try.