JayA

Welcome to Mr.PLC.com!  :) I'm glad you asked, because this is an excellent time to start a discussion on Scada with CX-Supervisor.  CX Supervisor is a wizard based HMI and Data Acquisition package manufactured by Omron.  It is not limited to Omron PLCs and supports other products through OPC. Data Logging is easy to setup when you are doing a time based process.  The wizards will lead you right through the setup.  When you want to data log based on event such as your process, CX Supervisor has a script language to enhance its' built in features. First of all, setup your dataset in Project Workspace|Data Logging Tab.  Add a new Dataset ("ProcessLog").  Add your items to be monitored as Pointnames.  Be sure to uncheck the box that says "Start Data Logging on Application Startup". Second, Open the Animation Editor and set it to Project Level Actions.  Add a Script with the following setup: Script Name:  Start_Data_Logging Trigger Event:  On Condition Expression (pointname):  Process_running StartLogging("ProcessLog") Third, add a new script at the Project Level with the following setup: Script Name:  Stop_Data_Logging Trigger Event:  On Condition Expression (pointname):  !Process_running (Please notice the '!" at the beginning of the Pointname - Inverted) StopLogging("ProcessLog") CloseLogFile("ProcessLog") Run the project and manipulate the pointname "ProcessRunning" from OFF to ON.  The log should start.  When the process is finished, manipulate the pointname from ON to OFF.  The log should stop and the file close.  The next time the pointname is On , a new log with a different time stamp should be created. :) Here's some pages from the Script Reference Manual.

This is perfectly legitimate no matter how you add a second Ethernet NIC to your computer.  I would leave your company connection as a server assigned IP and assign a static IP in the range of 192.168.0.xxx. BTW, 192.168.0.xxx is an international test network assigned for exactly what you are doing.  No router in the world will pass packets from this network out to the internet.

Awesome program!! :0 I just download comlite32 and was knocked out!  How long have I looked for a snooper program that would monitor both sides of a serial conversation without having to actually tap the cable!!!  This is going in my Top 10 Utilities directory.  Thanks Ken! :)  I will add it to the Miscellaneous download section on this site!

I, too, welcome feedback from all the forums.  It doesn't hurt to be in concert with other websites rather than in competition.  It's encouraging to see regulars from other PLC forum websites.

The DM(Data memory) is the ideal place to store records, primarily for three reasons: 1.     It is the largest area of memory in any Omron PLC. 2.     It is data retentive (battery-backed)(retains data on power down) 3.     It is the only area of memory that can be indirectly addressed. When you are working with a table of data that needs to be stored at a different location, use the XFER(70) function.  This is like the MOV(21) function because it has a source word and a destination word, but XFER(70) throws in a third operand for how many words.  The format looks like this: XFER(70)  Name of Function #0010      How many words to Transfer DM0000    First Source Word DM0100    First Destination Word :p

Jerry, I'm sorry but I have been off-line for a couple of days. I wish I could have been here for you this weekend.  It looks like you got some help elsewhere. Some thoughts on MCRO(99): 1.     MCRO(99) is used when repetive circuits bear some resemblance in structure but not addresses. 2.     It allows a template circuit to be built using internal registers(IR232-235 for input and IR236-239) and substitute real world I/O on a one to one basis. 3.     MCR0(99) is a programmer's cool instruction but a maintenance's guy's nightmare.  This is true also with indirect addressing. 4.     Careful attention must be paid to layout of real-world I/O.  The instruction expects that like I/O be in the same order as the template circuit. 5.     Circuits with timers don't work because the timers are never the same current value. MCRO(99) is a great idea, but it needs a lookup table for non-contiguous I/O. :-3

Here's some more bitmaps I found laying around.  I too would like to see a user's selection of bitmaps appropriate for import into OI and SCADA packages.  One tip:  When you are surfing the web and you see bitmaps that would work for your application, remember that you can download the individual graphic from the website by right click and Save Picture as.  Also check your Temporary Internet Folder for cached bitmaps which can be used in your application.  There are several shareware programs that will inventory your hard drive for all available graphic images and present them to you in a thumbnail version.  I will post one program in the download section. :p

Greetings Rui! The cable that you are looking for is a ZEN-CIF01.  It is not just a simple cable, but has active electronics in the RS232 plug end. You will probably have to purchase it. http://oeiwcsnts1.omron.com/pdfcata....Element :D

This is a common misunderstanding about which memory gets cleared when you tick Clear Memory during the download program dialog.  The memory to which they refer is the UM(user memory- which is ladder code only.)  All other Data Retentive areas of memory (DM - Data Memory, HR - Holding Relay, and AR - Auxilary Relay) are battery backed and will not be cleared by a program download.   I know that some other manufacturers include, along with a program download, additional files which represent data settings in areas other than program memory.  It is a seperate procedure using Syswin 3.4 and involves invoking the Data Display Editor (Editors|Data Display Editor), loading a .ddm file and downloading the file to the PLC with a separate download dialog. Regarding using move statements actuated by first scan flag:  this is a very appropriate way to hardcode DM's to a preset value.  The rub comes when your ladder code modifies these data locations due to changes in the process or by programmer innovation.  Some programmers have devised unique methods to control this, such as setting an HR after the first scan, so that subsequent restarts do not destroy the data.  Others compare a certain location to zero, and  if a code has been set there, then the move statements are not executed.  Obviously, the onus is on the programmer to make these decisions. :)

Jerry! Welcome to Mr.PLC.com.  Thankyou for taking a look at our section on Omron PLCs.  Your contribution on other forums is phenomenal! ;) A little background on STEP/STEP NEXT sequences: Definitions: STEP does no useful work in the program.  It is a marker to the beginning of a step.  The length of a step runs from STEP marker to the next STEP Marker. Ladder instructions placed between these markers are bounded by that particular STEP.  Usually, but not mandatory, only one STEP at a time is active., i.e. the CPU processes and executes only that active STEP.  All other ladder bounded by STEP markers is dead and does not execute.  The last STEP in the sequence is bounded by a STEP instruction with no operand(bit number). STEP NEXT (SNXT) is the action instruction of the pair.  It's like a BASIC GOTO.  "Where do I go NEXT?"  When SNXT is executed, the ladder in the STEP from which it is located goes dead(inactive) and program control flows to the STEP that SNXT activates.  This property of inactive steps not executing ladder allows the use of duplicate coils.  Unless you accidently cause two steps to be on at the same time, only one coil actually gets written to the I/O image table.  To end a sequence, execute a SNXT to an undefined STEP (STEP to nowhere) - an unused bit.  I usually use the last bit in the word I have chosen for STEP control.  If you want to recycle the sequence, then in the last STEP, SNXT to the beginning step. Branching is possible in a particular STEP.  Let's say you want that if input A is on, you want to follow the normal sequence.  But if input B is on, you might want to skip around a STEP.  It's a simple matter to place two conditional rungs with each input executing a different SNXT location. Multiple STEP/SNXT sequences can be executed at the same time in the same processor.  An example, let's say you are controlling a drilling, reaming, deburring index table.  You might have one STEP sequence control the indexing portion of the table.  When the index is complete, you start three simultaneous STEP sequences: one for drilling, one for reaming and one for deburring.  When these sequences have all finished, you branch back to the index sequence. OK, analysis of your STEP sequence yields the following: 1.   You have started your sequence with an input from a pushbutton which executes the first STEP.  (Excellent! This is the classic way to start a sequence.) 2.  Entering the first STEP, you actuated three coils and then wait for an input (1.01) to become active to go to the next STEP (right on!) 3.   Entering the second STEP, you acctuated the same three coils and wait for an input(1.02) to go to the next step (Perfectly legitimate - duplicate coils are appropriate.) 4.  Now the assumption is made that to recycle the sequence it will automatically start over at the beginning STEP.  A natural assumption, but it is necessary for you to execute a SNXT which activates the beginning STEP if this in truly the entry point that you want to goto.  In this case, the SNXT would be SNXT 200.00. 5.  To bring this sequence to an orderly end, in the last STEP, place a SNXT to nowhere ( an unused bit - 200.15?) and all STEPS will be deactivated. I have developed a number of Dos and Don't for STEP sequences and they follow: 1. Prevent energizing SNXT functions with a differentiated (DIFU) contact.  The SNXT function is already a leading edge instruction. 2. Prevent energizing two steps at a time that include the same output coil number.  The step closest to the END function will take precedence over previous steps. 3. To use the true diagnostic power of STEP/SNXT, make only one change in the output structure in each step.  If you are doing two actions in one STEP, then there should be two STEPs. 4. JMP,JME,IL,ILE,SBN, and RET functions should not be included in a step as they use the same internal mechanism as STEP/SNXT. 5. Contrary to all Omron documents, unless your CPU is a CxxK PLC,  the control bits do not have to be contiguous and in the same channel. 6. If it is necessary to trigger a differentiation (DIFU) upon entering the STEP, use a normally closed contact of 25407 (Step Start Flag) to energize the differentiated instruction. 7. If you have multiple STEP sequences in your program, make sure that the final STEP in each sequence is bounded by a separate STEP with no operand.  (Overflow can occur!)

This is a good Spanish language site for many different manuals and .pdfs for various automation manufacturers.  The Omron SYSWIN software will run for CPM1A/CPM2A/2C products.  All others are demo mode only. :D

I have aleady been through this exercise.  The Modbus/TCP specification is for implementing the original Modbus serial protocol on networks other than serial (ethernet, arcnet, etc.).  I am looking for examples of how manufacturers other than Modicon handle floating point registers in their products when implemented on serial devices.

Your absolutely correct, Chris, so here's the info for the whole forum: Clarence is probably referring to a C200HX-CPU63 PLC CPU.  There is an ethernet connection for this PLC and it is known as  C200HW-PCS01.  It requires a PCMCIA ethernet card for the interface and does provide for TCP/IP socket service through ladder commands.  The manual can be found at http://oeiweb.omron.com/oei/

Hi Chris!   It's not often that you run into someone who even knows what a C2000H duplex is, much less programs one.  What programming package are you using?  How come redundant PLCs (just curious)?  Any block style (If THEN ELSE) programming examples for C1000H or C2000H? Are you using the CQM1H series as well as CQM?  If you've got any pulse output examples, they might be useful in the PLC code area.  Let me know what you can offer for our forum. :D