b_carlton

Concerning double words (Long) in the Micrologix. Yes it's not a default but it is available. One problems is - the lack of instructions which support them. I don't have the reference here but I believe none for Multiply or Divide. I think they can be used in Add and Subtract. You can use Float (Real) but then you have to be aware of significant digits limitation. In then end sometimes you have to view the PLC as a pure computer, check what it has available as far as registers and instructions, then use that to achieve your purpose. In other words you have to think 'below the instruction'. By this I mean imagine what is happening in the actual CPU. For this it helps to have a background programming microprocessors using their lowest level instructions.

While I have used communicatiton capabilities of the DL06 it hasen't been with these drives. Perhaps if you post at the AutomationDirect site you may get helpful replies.

I'm sorry that I misinterpreted your first post on reading this 32 bit value as it was to be interpreted as a float (possibly because you mentioned F8).

Read into two adjacent N registers. Then do   CPW  (first N register)  F register  2   Example from one of my programs    CPW #N40:2 #F42:1 2   This copied the 32 bit pattern from N40:2 and N40:3 into F42:1

I would investigate the PLC operation before blaming the display. Look for any possible way the state can be changed in the program without a signal from the display.

The mapping is only needed if the Micrologix will be a Modbus server.

We most often have to add 1 to the address supplied by unit manufacturers for use in these Modbus instructions (RTU or Modbus TCP). Ill have to assume that the instruction is actually running (since it's in the Main Ladder and the status indicates Remote Run that is probably a safe bet)   Is it possible the unit documentation expressed the address in hex? If so you will have to convert that to decimal.

Hmm, doing the 'restore' on mine works fine. I don't know what else to tell you.

View - Toolbars - Restore Factory Toolbar Layout

You forgot to include the "prints" mentioned in the test directions. $12 - that's it?

On the "old computer" use the "Application Manager" under "Tools" use 'Backup Application" This will create a .APA file which packs together all of the application nicely into one file. Then just copy that file to the new computer. On that computer run the "Application Manager" and use "Restore Application"

For an AOI, anything not a BOOL, SINT, INT, DINT, REAL will have to be an in/out type. In the case of BOOL ... REAL the VALUE of the input parameter is passed to the AOI. The AOI cannot alter the actual input parameter. An output parameter of these types receives the final value from the AOI. The in/out parameters have a pointer to their location passed to the AOI. The AOI can read/write anything in the in/out parameter.

Each instance of an AOI gets its own name (because it is actually a different chunk of memory - saame type house but differeent lot). I haven't tried but I think the compiler will throw a hissy fit if you try to give two instances thee same name. If you really, Really, REALLY want to have only one chunk of code and call the same code from multiple places in one Program then create a subroutine and pass input and receive output paraameters. I don't think subroutines can do an in/out type of parrameter though.  The same with two identically named tags (instances) of  the same UDT.

An Add On Instruction (AOI) definition is a template. Think of it as the blueprints used to build a house. It has a name just as a specific set of blueprints might have a name. Let's say Joe's Builders created the house design as shown in the the blueprints and called the design 'Aspen Palace'. Now you, as a home buyer decide you like the 'Aspen Palace' design and you want one built on you lot. They don't just take a set of blueprints and drop them on your lot. They actually build the house. When done your house has a specific address - let's say "201 Main Street, Anytown, USA". Imagine also that each house also has a little plaque saying "Aspen Palace Built by Joe's Builders'. Your built house is an 'Instance' of that specific set of plans. The builder could build a number of these in various places. They would all be Instances of those specific 'Aspen Palace' house plans, but they would each have their own distinct and unique address. Now that you have created your AOI (Mult3). You want to use one of these at THIS place in your code. In effect the placing of the AOI box and specifying its parameters is building all the code and making space for the variables at that particular placed in your ladder (though it shows up as a box.) The box will have a title - Mult3. This is like the house plaque. It shows the TYPE of AOI. But you have to give a name to this specific instance of the AOI. That is the first 'parameter' at the top of the box. This name is applied to the code and variable space inside this particular box. If you want to use the AOI somewhere else, probably with different parameters, you will be creating another instance of the AOI template. Again it will have the name of the template - Mult3 - but this time the specific instance gets its own unique name to differentiate THIS set of code and memory space from the other instances of this particular AOI.   In like manner the User Defined Type (UDT) is a template for a set of variables. If you want to make an Instance of the UDT you create a tag with the TYPE of the UDT but with its own particular name. The name specifies the chunk of memory holding a set of variables as defined by the UDT template.

If you don't get full step-by-step information I can at least provide some information. We used the Allen Bradley 1761-NET-AIC as the RS232 to RS485 conversion. There are probably cheaper units but if you want to stay with Allen Bradley ... We used this with a Micrologix1500 but with the same type of port as on the SLC5/05. We interfaced with Powerflex drives using Modbus messages. So it's not exactly the same type of units but (again if no one has exact specific directions) it can at least help.    Just ask if you want to continue this.

As your inputs are arranged a quick release and re-apply of one button during the 1/2 second will re-fire the one shot. Once the gripper is energized, if EITHER button is released then set a latch which can only be cleared by releasing both buttons. Only after that latch is released will the buttons be recognized again. As this is a student exercise it may be acceptable to use the double press method to release the gripper. But typically any release of an input would be a command to de-activate motion. And typically two-hand safety is not allowed to be implemented in a standard PLC, only with dedicated two-hand safety control hardware.

It may be more likely that the analog value is fluctuating rapidly above and below the trigger point during the half second the button press is active. As long as it is not a safety problem bypass around the GRT box once the Gripper has been activated.   What is the usual sequence? Is the analog value above the trigger point before the anti-tie-down inputs turn off or is it the other way around? This system does not seem to allow for quick deactivation if the anti-tie-down inputs are released. How is the Gripper normally deactivated?

The EDS file tells RSLinx what is going on. To get RSLogix 500 up to date you need an new AOP (Add On Profile). This provides an updated .dll file for the new revision. Once more EDS = RSLinx AOP = RSLogix5000

Generally you won't need a message command (MSG) in the Micrologix. You have correctly set up the Micrologix to use Modbus/TCP and have assigned the N7 register to act as 'Input Registers' when the display requests that information.

Notice that he wrote about MOVing a value to the ACCUMULATOR. I've only seen this described once in creating a more accurate time source. With a preset of, let's say, 1 minute then, on the DN bit the expected preset was subtracted from the accumulator leaving whatever small amount over the preset had been loaded in evaluating the timer instruction. Thus the time between DN bits was,on the average, more accurate than just resetting the timer using a NC contact of the DN bit in the enable rung.

For a start - in the manual 1763-RM001 search for 'analog inputs'. That will at least give you the location of the onboard inputs. The 1763-UM001 will show you the wiring.   Otherwise the 0-10 voltage input is presented as a number (0 - 1023). Use ordinary math for processing and comparison.

To dforsythe - I also click on the address but I wait until the 'Relation List' pane shows with 'BOOTP' and click on it then the 'Disable BOOT'. I guess it's the same thing. With some devices it routinely notes success on the first try. Some, like PLCs' I often have to try more than once but I can't remember it ever being more than three times.

Using the BOOTP-DHCP server program I haven't failed to disable BOOTP (though it may take two or three button presses).

Yes, you should be able to do that without affecting the running.

Assuming you have the RSLogix 500 package. Fortunately for the 1100 the package is free. Just a download. Realize that the PLC does not have any of the comments or nicknames that the original source may have contained.