Snerkel

Have you changed the RSlinx on the PC to use the PIC/AIC+ driver ? The second problem can be that the PIC/AIC+ driver doesn't work very well with 2k or XP. You would be better using the KE or get a USB to DH485 adaptor. Bottom line the RS232 port on the AIC+ is only a signal isolator, it does not change the networks protocol. If the AIC+ is on DH485 network then the RS232 port uses the DH485 protocol.

Maybe if you stopped SHOUTING you wouldn't get the bum deal

Why not use one of the free ones, http://sourceforge.net/projects/pdfcreator/ is GNU and works well, I use it all the time with RSlogix.

I had something similar a few years ago, it was a corrupted project that caused the problem, the only fix in the end was to create a new project and copy paste stuff across. If I remember rightly mine stopped at a diagnostic test around about 40. Catching the boot sequence at "32" may take a few attempts. Note:- last time I did this was about 8-years ago so I hope my memory has recalled the boot sequence number and the keys correctly. Don't know what you do if you have a PV without keys

Try this... XIC PV_Button OTE Button_Repeat OTU PV_Button PV_Button is the momentary button Button_Repeat is the thing you want to drive or could be used as the momentary button in the rest of the program.

You could try clearing the PanelView memory While booting when diagnostic test 32 is displayed press and hold both the F6 & F5 (If that doesn't work try F1 & F10)

You hadn't got the NI4 configured in a slot... the attached file should work. You add modules to the IO configuration (double click it in the left hand pane) you will see your card added in my example. Revised.RSS

If you don't find any other answer what you can do (at least with the mains powered ones) is to short circuit the aux 24v DC output while the PLC is running, this generally instantly wipes the memory. Of course if you blow it up then I am not responsible. ps reason I know this is we had a machine that regularly had shorts on the PLC aux out when the operator kept cutting a sensor cable by mistake (until we redesigned it). Everytime this occured the program was erased.

Is it about time the Guest account can not post. 1. If you forget to log in you post accidently as guest. 2. Sly comments can be made without any trace (by normal users). 3. Threads get confused if created by a guest, then another guest answers.

dleehanson is right... dooh If you don't have the structured text addin you can just do a loop in ladder that should work.

Don't understand what you are trying to do, it sounds like you have one tag that you want to write to multiple timers so they all have the same preset ? Each timer has a unique tag, with appended things like pre tt I can't see how you could possibly do what you appear to want to do. If you have one adjustable value in multiple timers I believe the only way will be to have a MOV for each timer, each MOV moving the same tag value into each timers pre

You can definately MOV a value to the timer.pre so I would think you could from a touch screen. If the touchscreen doesn't support write to timer.pre then write to a dint then MOV this to the timer.pre in the PLC code.

I just measured the resistance of my cheap meter set to mA with my expensive meter set to ohms and it gives 0.3ohm

Try 500 ohm then, the documentation should give max resistance that the loop can have, but 500 ohm should work given that 1k gives 13mA. 1k is pretty standard as 24v will give you approx 24mA but maybe not for this unit. Even with a short circuit proof output I wouldn't risk it, especially on a regular basis.

Ohms law gives you the answers. The multimeter has a very low internal resistance when set to Amps. The 4-20mA loop is driven by a voltage source, the current is controlled by varying the voltage. With a 1k load you need 20V to produce 20mA, if the load is only 0.05 ohm then you only need 1V to produce 20mA The PLC will struggle to give the true current loop value into such a low impedence, and a minor spike of the output could cause its destruction. A cheap digital meter is probably the best to use if connecting without a resistor as the leads and internal impedence are likely to be higher. It is far safer to just add a resistor in series with the meter to protect the meter and the PLC.

Use a digital meter set to mA but make sure you put a 1k resistor in series with the test lead. I have seen others just use a digital meter set to mA with no series resistor, however this is bad practice, and could potentially damage the analogue output. Check the documentation for the recommended maximum and minmum resistance for the loop.

NOP = No OPeration (NOP is actually used in many programming languages) It doesn't do anything and would usually be used for instance to give a rung to add a comment etc. A comment could be attached to a normal rung but if the comment relates to a section of code, the rung may be deleted in the future and the comment for that section of code lost. The NOP is usually used as a marker for a comment, or to break up code visually. It is also often used with a LBL as this needs a coil at the end of the rung, it saves waisting a normal coil.

Do a compare of the analogue and an integer, if the analogue is GRT than the integer and it is the sample period then MOV analogue to integer. SOR XIC B3:0/0 GRT N7:0 N7:1 MOV N7:0 N7:1 EOR B3:0/0 is the sample period bit N7:0 is the analogue N7:1 is the integer that strores the max PS you can copy paste the line above into RSlogix by selecting to the left of the ladder (goes red) then pasting.

File Name: Day of Week + Week Number + Auto BST adjustment File Submitter: Snerkel File Submitted: 5 Nov 2005 File Category: PLC Sample Code Calculates the day of the week. Calculates the week number. Auto adjusts PLC clock for British Summer Time. Works with any SLC processor with a RTC does not require floating point. Click here to download this file

I have now downloaded a demo file for the PV and SLC http://forums.mrplc.com/index.php?act=Downl...&CODE=02&id=491

File Name: PanelView Display of multiple IO point status File Submitter: Snerkel File Submitted: 5 Nov 2005 File Category: HMI Sample Code Using 1 control list & 1 Multi-state indicator select any digital IO to display its state (ON or OFF). Simply copy the IO you want to monitor into B3:0 onwards. Fill the control list with descriptions for the IO you wish to monitor. Fil Click here to download this file

Another way is to use a control list and a multi-state indicator. The control list has a list of IO points, the Multi-state indicator has two states ON & OFF Paste the following into RSlogix SOR XIC B3:0/[N7:0] OTE B3:255/0 EOR N7:0 is the value from the control list B3:255/0 drives the multi-state indicator B3:0 to B3:254 are the words of bits that could be monitored.

I think us oldies (ish) are very misunderstood by those young wet behind the engineers. When they get a bit of experience with real plant not piddly little machines, and have modified more programs written by others than had hot dinners, then maybe they can start judging us. I try to write my software in a way that is easy to understand, and is very well documented, but getting software without annotation is part of the challenge of modifying existing kit... bring it on. ps I think this thread is getting a little off topic but is very interesting all the same