rslinx excel need help

[heehoo10]

I did a search of B3/14 in each ladder and it does not appear except for in the main

 

[Lancie1]

Something has to set and unset B3/14 for your program to work. It could be somewhere else, such as in an operator or machine control panel program, or in another PLC that is communicating with this one. B3/14 (B3:0/14) could also be controlled as part of a range, maybe including all the bits in Word B3:0; bits B3:0/0 up to B3:0/15. You could search for all occurances of B3:0. It appears that some Word B3:0 bits are used mostly by a "MMI" (Man-Machine Interface).

Either that, or you have accidently caused some bad errors in the program!

All I personally can determine:
B3:0/0 Undefined Always-On bit in Lad 2 Rung 000
B3:0/1 = CLAMP CLOSE BIT
B3:0/2 = CLAMP OPEN BIT
B3:0/3 = TRANSFER ADVANCE BIT
B3:0/4 = TRANSFER RETRACT BIT
B3:0/5 = CYCLE INTERLOCK
B3:0/6 = CURE TIMER DONE
B3:0/7 = AUTO CYCLE ONLY
B3:0/8 = ADVANCE TRANSFER DURING AUTO CYCLE
B3:0/9 = MMI MAX PROFILE DONE <-------Indicates B3:0 bits 9,10,11,& 14 may be coming from a MMI panel
B3:0/10 = PASSWORD OK
B3:0/11 = CLAMP SET ZERO
B3:0/12 = OSR #1- One Shot Rising in Lad 2 Rung 1
B3:0/13 = HIGH PRESSURE ENABLE
B3:0/14 = TRANSFER SET ZERO <--------This is the one to find!
B3:0/15 = OSR #2 in Lad 2 Rung 9.

 

[daba]

I think B3/14 is just a bit set manually, or from the MMI, to "zero" the encoder position, by storing the current encoder reading in N7:29 (MAIN:9)

MAIN:11 takes the analog signal and subtracts this offset.

 

[daba]

heehoo10 - check your inbox again.

I have re-developed your code to allow 40S(+) of recording, and improved upon the timing inaccuracies in the original.

Anyone else want to see it, it's here....

http://dl.dropbox.com/u/82993644/DEXTER_503_DABA_INDEXED.zip

I have sent heehoo10 instructions on how to make file 8 an STI.

 

[daba]

No, 20 seconds is the overall recording time. I:5.1 is adjusted with the zeroing offset, and the result is stored into the FIFO every 100mS.

20 seconds at 100mS intervals should be 200 readings, but heehoo told me they get much less, because of the inaccuracies in using timers in normally scanned logic.

I have given him clear instructions how to put his recording subroutine (file 8) under control of the STI.

I have also converted his code from using FFLs to an indexed arrangement - allowing him to extend the recording time up to 50 seconds.

To do this I made 5 contiguous integer files of 100 elements each, and set the bit in the status file to allow the processor to index across file boundaries (S:2/3). The index goes from 0 to 499, which I load into S:24, then MOV the data into #N100:0. This will store 500 values into the following addresses...

N100:00 to 99
N101:00 to 99
N102:00 to 99
N103:00 to 99
N104:00 to 99

Much tidier than all those cascaded FFLs.