PdL

I think PMCR has given an excellent explanation, no reason to open more topics and repeat the same questions. I have merged the 4 topics here.

Only thing that comes to mind is some kind of ground loop problem, at least a power problem not something to do with drivers or conflict I guess. How is the touchpad powered? and the CJ1M? Are they grounded?

In CX-Programmer, go online by peripheral port. Open I/O table, locate ETN21 unit. Right click, start special application (or something along that) > CX-Integrator with settings inherited, go to Tools > Routing table editor. Right click ETN21, Add SIOU to local network #1, download, power cycle CPU and you should be good to go.

A timer can only be directly modified using Block Set if I remember correctly. If you want to change the PV then follow Mendon Systems suggestion.

Snagit rules big time!

If you are referring to support for socket services, you will need a full blown ETN21 card for that.

________ ---| |------- | MOV(21)| 1.02 | &1 | | D20 | |________| ________ ---|/|------- | MOV(21)| 1.02 | &0 | | D20 | |________|

Let us know how it works out! And there are other Citect guru's around here that are far more experienced in Cicode. Hopefully someone else will jump in.

OK clear. Not sure though how to go about this. Would it be possible to still use common variable tags but use the super genie "one page entry" function to dynamically call a different function ? Just brainstorming here.

OK I think I understand your point now! I never heard of the Booty() function until now Anyway, wouldn't it be possible to assign the INT value in Cicode to a tag? Using WriteTag or similar?

Have a look at the AssVarTags function, it can do exactly what you are after. In your Super Genie, you refer to tags like INT1, INT2 with an offset and in the Cicode you assign variable tags to them, you can even use %% substitutes in your tag names that are replaced by strings you enter when you place a Genie that calls the Super Genie. See an example I posted some years back. I haven't used Citect since V6 but I expect this to still work. Citect: How to use multiple AssVarTags function in object command line

Check this very useful post from a fellow forum member: http://forums.mrplc.com/index.php?showtopic=22077&st=0&p=106387

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.

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.

If the PLC is equipped with an Ethernet unit, you can sync the RTC with a NTP server...

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.

Another method not requiring CX-Programmer, not even a computer or cable. http://db.tt/1nOgrf5n

Not sure about the UK standard, but here's some info I found on Wikipedia: http://en.wikipedia.org/wiki/BS_7671

Hi, and welcome. So besides baking pizzas, what's your link to the controls and automation industry?

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.

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.

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.

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

And I would like to welcome Michael Walsh to our team as well! Proud to have 2 Omron gurus on board