b_carlton

Ron - he wasn't looking for a password 'crack' but for the clear method. He says he has tried the method which AB publishes in its manuals (and which various posters supplied) but he seems to have a non-responsive unit.

The locations for non-array tags are resolved to actual memory locations at compile time. The result is then downloaded to the CPU. Go for an array. (And wouldn't those new values be 1386 and 1372?)

Responding to the second part of your question - assuming your out data is in a DINT - let's say My_Target_DINT COP My_Target_DINT Shuttle:O.Data[x] 4 (x being the first of 4 indexes) will distribute the DINT to the 4 SINTs. As another note you may want to consider using CPS instead of COP in each movement of data. Because of the asynchronous nature of I/O data transfer the use of CPS prevents one from happening in the middle of the movement of the 4 bytes which may yield temporairly mixed results.

Using My_DINT as a target COP Shuttle:I.Data[4] My_DINT 1

Background - We have just completed a project using CompactLogix to read and write via Ethernet/IP to Sick Barcode readers. It went fairly easily. The zip file available here helped immensly, especially the PDF on Ethernet Function Description. Once connected triggering the read and interpreting the response was fairly easy. We have also, using a Micrologix 1400 (which has the same messaging capability on Ethernet as the 1100), read and wrote the input and output assemblies (101 and 111) from a servo drive. It was not as difficult as had been suggested. Warning - BUT, the servo drive we talked to had information in 16 bit words. The Sick barcode reader has information in 8 bit bytes. I'm not sure how the information would line up since the only available target, I believe, in the Micrologix MSG command are 'N' files.

I'm sure you have reviewed the basic information for the Micrologix 1400 web server but I'm giving the manual link anyway It looks like the structure is limited. I don't know if it will be compatible with the usage you desire.

Just add the Milk and Sugar sections to look just like the Water section with the following changes: Inhibit the output of Milk or Sugar if not selected. Trigger 'Milk Complete' or 'Sugar Complete' if the timer is done OR the item wasn't selected. Is Milk AND Sugar considered acceptable also or is that 'just not done' in your area?

See the thread at plctalk.net

Probably a better chance at an exact answer at the Host Engineering (the creators of the Do-more and its software) site

You may need to select the source file within the Panelview also. That entry field is blank.

Yes, the power in using the COP command is understanding exactly what it does. It is a blind copy of the bit values. The length is in terms of the target length. In this particular instance the start of the source is on the first of two INTs. The destination is a DINT. We COPy 1 of the target lengths. So two INTs which happen to be adjacent in memory get copied to 1 DINT. For efficient use learn the layout of memory of your variables. Totally different tags have no guarantee of any physical relationship to one another. But members of an array do. Study and be comfortable with the layout of memory then the COP command can be your 'friend'. Also, be aware of CPS. If it is possible that you are using physical input or HMI or networked values as the source then use CPS to ensure that the source values can't change during the operation.

One instruction - the COP - moves the 2 INTs into the DINT. The second instruction divides the DINT by 1000.0 to produce the Real value. is your total solution using BTD to transform from the 2 INTs to the final Real less than 2 instructions?

Count both events individually then add the accumulated values together.

COP GenericModule:I.Data.[0] MyDINT 1 CPT MyREAL MyDint / 1000.0

Since it doesn't say 'Professional' I'd say it is the standard edition.

I have no CPU to program with it but Micro Starter Lite opens and runs on my Win 8.1 Toshiba laptop. No guarantees of course.

Some of the newer controllers come with a yellow sticker specifying which revisions of each level was required. When I first ran into this I found no firmware update files because I didn't have any of those revisions. I had to go to Rockwell to get the newest update files. Then everything was ok. This may be your problem.

Please post the program you have developed so far. What are your problems?

The Logix family does not support 64 bit floating point. So it's not a matter of displaying it. It's a matter of holding it at all. As a note, here is a link to a thread discussing 64 -> 32 bit floating point conversion.

The error does not necessairly mean that the adaptor's IP changed. It could mean that some other device was also assigned the same IP. You must keep careful control of all IPs used in the control network including devices, like programming computors, which may only occasionally be attatched to the network. Verify if the adaptors actually had a changed IP.

If you no longer have any use for the old file then just delete it from its directory. My directory of runtime files is at - C:\Documents and Settings\All Users\Documents\RSView Enterprise\ME\Runtime I have Windows XP, your runtime files may be somewhere else depending on Windows version

OK, now you need something like a shift register. Fortunately since you are only talking about 16 links it shouldn't be too bad. When I have some time this evening or tomorrow I'll help. Actually check out the attached INSPECTIONLIGHT.zip

Is it still not catching all instances? I assume the line is started again (sometime after the stop) then, sometime later, an operator presses 'Stop' again and you don't get the expected response. If so, what actually happens in the program when the operator presses the button again?

With the change we talked about then, 'Stop Switch' is hit, the counter counts links until 10, the light turns on, it continues to count links until 16, the counting is cleared (light turns off) and the system waits for the next actuation of the 'Stop Switch'. At least that's what should happen. What is actually happening? Specifically as far as actuation of the 'Stop Switch', counting of links, light turning on. Does something ever stop the links? What is the sequence?

Does the stop signal go away before the counter reaches 16? And you shouldn't delete your original program post, others won't know what we are discussing.