gmferg

PLC 5 requires only the DNet scanner module be placed in Idle mode to make changes to the scanlist. You can replace a device without doing anything as long as the replacement device meets the requirements selected in the "electronic key" setup in the scanlist for this node. I typically disable all electronic keying so that the scanner will allow a device to be replaced by anything else. I rely on the person that is doing the replacement to know whether the replacement is compatible or not.

Look at using an Event Task and trigger it off your input module that has the photoeye. This will help reduce the error caused by processor scan time.

Use the copy (COP) instruction.

I agree, Devicenet in Intellicenter MCCs is the best option. According to AB, this can not be done with Ethernet/IP due to the noise from a 480VAC system. For everything else, go Ethernet/IP.

Try leaving the domain field blank and enter the same username/password which you use to log into windows.

From Robert D. Law's DeviceNet Bible: "DeviceNet specifications state that 24VDC power supplies must power up to full voltage in no more than 250ms under full load and 7000uf capacitance. Failure of power supply to follow this specification will cause devices to Bus Off (solid red network LED) when AC is switched on to the power supply. If devices go Bus Off when AC is applied, cycle DC power off then on at the supply and see if devices still Bus Off. If they don't then power supply is out of spec. If they still Bus Off, then you have other issues with your network." Another entry from DeviceNet Bible: Maybe you could initiate a reset to the scanner after a set time after PLC first scan.

Is this for a Panelview Plus or a PC? If Panelview, did you setup the IP and SN for the Panelview? You must set this on the Panelview, not through RSView. Path to PLC processor must defined within RSLinx Enterprise which resides within RSView.

From the SLC Manual (1747-um011_-en-p): Clearing SLC 5/03, SLC 5/04, and SLC 5/05 Processor Faults Using the Keyswitch Toggle the keyswitch from RUN to PROG and then back to RUN; this will clear some faults. If the keyswitch is left in the RUN position, the processor mode cannot be changed from a programmer/operator interface device. If you return the keyswitch to the REM position, you can then use a programmer/operator interface device to change the processor mode. ATTENTION If you clear a processor fault using the keyswitch, the processor immediately enters the Run mode.

I've never routed a message going from DF1 and out. I've always gone the other way. I think you are close on your path. Assuming you have the table in the ENI setup correctly then 2,49 will only get you to the ENBT. Try this: 2,49,1,0. Adding the 1 tells the MSG to go out backplane of ENBT and the 0 tells the MSG to go to slot 0 of backplane.

That's correct.

Be careful, clamping signal can give the illusion that level sensor is perfectly calibrated at all times.

*.L5X only works for ver. 17, correct?

1b. Set IP address on laptop to 198.162.120.xxx. xxx = any number between 1 and 255 except 111.

That is my opinion, obviously there are others. I would suggest you try both as it is a good learning experience and you will prove to yourself which method you prefer.

Camera needs to be triggered a set time after an input is seen. This cannot be done using an STI. Use the EII.

The STI interrupts scan at a fixed time interval, not input trigger. An STI would actually be worse in this situation than not using it. Placing the timer within the STI would cause it to be triggered less often than if it were in the regular scan as the STI has to be set to interrupt at a slower rate than scan time. EII function file is absolutely the way to go for this project. It uses a physical input to trigger an interrupt instead of some arbitrary time interval. I would place only one rung within the EII routine: XIC input RES timer. The timer, placed in a different routine which is always scanned, should be free running with no inputs and a very high preset. Use the LIM and IOM instructions on a rung right after the timer rung to trigger the camera output. You may want to experiment with placing the timer in the EII routine as this will trigger it to start sooner than in the regular scan but it may not update accumulation soon enough. You may want to experiment with having timer in both locations and see what happens. I do like the idea of using IOM to trigger camera output right away instead of waiting until end of scan. I believe outputs in Micro 1100 are not updated until end of scan unless you use IOM instruction. If the OP could post the program here and post the scan time, that would help a lot in getting the correct answer. The scan time can be read while online under the Processor Status area.

An STI would not work for your situation. You want to use an input to create a delayed output. The very short times you are trying to achieve are all about scan time. You need to see what your scan time is at. One thing that would help reduce the drift is if you were to use only one timer with a GEQ or LIM instruction to trigger the output. Instead of looking for the second timer to timeout the 30mSec for camera trigger, allow first timer to go an extra 30mSec and check that accumulated time is beyond trigger point. Each time you stack timers, you introduce error since the timer is not triggered done until its accumulation time is GEQ preset and timer rung is scanned. Therefore, timer accumulation will always be greater than preset when done. There is also error introduced by scan time when starting a timer. The timer isn't actually started until the input is true and the rung containing the timer is scanned. The Micrologix 1100 has an EII function file. This is an event interrupt file. You can use an input to cause scan to be interrupted and "jumped" to a specific routine to execute that code. You could use this to reset a free running timer. This would at least eliminate the error caused by starting the timer at the exact time the input is triggered. Be sure to condition your RES with the actual input point. I believe the EII monitors a word of input bits not just the one you're looking for. If all else fails with PLC, look at installing a programmable timer relay to perform only this job of triggering camera.

Still exists... I've experienced it most often if you enter a UDT tag with an extension that doesn't exist.

I would think the fastest way to clear a processor would be to have a blank or near blank program and download it. I say near blank because I've never tried this and there maybe a minimum requirement for a project to be downloaded. Maybe you need at least one rung of logic? Another option may be to flash the processor.

I have to second the use of Control Logix CPU with DNB. It is much easier to program and the DNB is capable of reporting back more information about nodes status'. Explicit messaging is also much easier and straightforward.

I logged in to a customer's site with VPN access and did some testing. The following MSG setup is what I finally got to work: As a test, I simply changed the Instance number to match each of the three parameters and initiated the MSG each time. Then I entered the parameter for restart and sent a value of 1. After restart, the new settings were active. Now, I will utilize this on my next large DNet project and abandon the total number of parameters method. Thanks for the help Ken.

I have been using explicit MSGs to write parameters to PFlex Drive and 20-COMM-D to setup comms for DNet. These will setup Speed Ref, datalinks, etc. This saves a lot of time when commisioning hundreds of drives for a project. Part of this setup requires that I write to params 13, 25, and 26 of the 20-COMM-D to enable datalinks. Since PFlex 70/700 drives have varying numbers of total params and the 20-COMM-D params appear after the drive params, I need to know how many total params the drive has. I can then add 13, 25, and 26 to this total param count to hit the correct 20-COMM-D params. The following MSG setup is supposed to return the total number of drive parameters only. This works about 80% of the time. The other times, the MSG will either error out or return a number representing total number of drive params + 20-COMM-D params. Is there a more reliable method for retrieving the total param count? Is there a better method for writing directly to 20-COMM-D params?

Thank you for the response. I will do some playing when I'm at the customer's site again. I too wish I had a rack of drives to experiment with.

I have not used PFlex 4 or 40s. I am familiar with the 70 and 700 lines. If you performed a full upload of all parameters on a drive that was setup correctly, you should be able to then download those settings to a new drive which is at least communicating with RSNetworx. After downloading, did you cycle power to the drive? Some parameter changes are not active until drive is restarted. What sort of comms module do these drives have? Are they software setup or dip/rotary switch? Software settings will typically download with a drive download. Dip/rotary settings will have to be done manually. Error 78 = Device is in scanlist but does not exist. Scanner does not see this node on the network. Are you setting the node address and baud rate on the new drive to match the old drive?