dalem
Member
Good evening,
Here's something I've been pondering for a few weeks but have not found the time to test. Maybe someone has a better idea and can steer me in a different direction or tweak my thoughts.
We currently have this line which has parts entering traffic up stream at 4 different locations and and then is sorted back out down stream in 3 different exit points.
Currently, the system is programmed using 4 different FIFOs and those 3 exit points look in 3 different data files. These exit points each look at different word locations in those 3 different data files. Example, exit 3 looks at word 10 in data file 1, word 23 of data file 2 and word 30 of data file 3. Hope that's enough to explain the existing.
We are planning some changes to the system and getting this all lined up again has been a bit challening to get the proper placed for these exits to look in f different data files. Also, Up stream, the 3 downstream entrance points also have to lookk in these up stream data files for parts passing in front, so one entrance does not yield traffic when merging.
What I've been thinking is to drop down to one FFL/FFU so everything happens in one. Currently, each FFL/FFU enters a 0 (zero) with each chain pulse. (1') When an entrance gate opens, entrance 1 starts moving 111, 111, 111, etc, for I believe 20 chain pulses, then back to 0, 0, 0, etc. Entrance 2 (data file 2) dumps in 222, 222, 222, etc, 20 times then back to zeros.
OK, What I'm thinking is to continuously dump in the zeros no matter what, in one data file. When entrance one gate opens, I'll MOV 111, 111, etc 20 times into word 100 (assuming that's where I need to dump them in)Those 111 would MOV in immediately following the FFL and FFU in the same rung or in the next rung(s) when the FFL/FFU rung goes false. Entrance 2 would do the same, perhaps at word 140, and so on.
The thought here is such that when product is moving down the line, I can watch all in the same data file. When it comes to exiting the line, I'd only need to look at one location (word) in one data file. That's 3 places to look VS 12.
Also, when it comes to debugging and lining up all these entrance and exit points, I would only need adjust one 1 word in one data file for each of those 7 ent/exits. The old method has so many different data files (4) and look up points, etc, it took a lot of time fine tuning the tracking in so many different places.
If I can/need to clarify anything, let me know. (Maybe I sould have proof read above before posting. I've only had about 30 interruptions wile writing this. )
Any ideas, suggestions are always appreciated.
Thanks,
Dale
Here's something I've been pondering for a few weeks but have not found the time to test. Maybe someone has a better idea and can steer me in a different direction or tweak my thoughts.
We currently have this line which has parts entering traffic up stream at 4 different locations and and then is sorted back out down stream in 3 different exit points.
Currently, the system is programmed using 4 different FIFOs and those 3 exit points look in 3 different data files. These exit points each look at different word locations in those 3 different data files. Example, exit 3 looks at word 10 in data file 1, word 23 of data file 2 and word 30 of data file 3. Hope that's enough to explain the existing.
We are planning some changes to the system and getting this all lined up again has been a bit challening to get the proper placed for these exits to look in f different data files. Also, Up stream, the 3 downstream entrance points also have to lookk in these up stream data files for parts passing in front, so one entrance does not yield traffic when merging.
What I've been thinking is to drop down to one FFL/FFU so everything happens in one. Currently, each FFL/FFU enters a 0 (zero) with each chain pulse. (1') When an entrance gate opens, entrance 1 starts moving 111, 111, 111, etc, for I believe 20 chain pulses, then back to 0, 0, 0, etc. Entrance 2 (data file 2) dumps in 222, 222, 222, etc, 20 times then back to zeros.
OK, What I'm thinking is to continuously dump in the zeros no matter what, in one data file. When entrance one gate opens, I'll MOV 111, 111, etc 20 times into word 100 (assuming that's where I need to dump them in)Those 111 would MOV in immediately following the FFL and FFU in the same rung or in the next rung(s) when the FFL/FFU rung goes false. Entrance 2 would do the same, perhaps at word 140, and so on.
The thought here is such that when product is moving down the line, I can watch all in the same data file. When it comes to exiting the line, I'd only need to look at one location (word) in one data file. That's 3 places to look VS 12.
Also, when it comes to debugging and lining up all these entrance and exit points, I would only need adjust one 1 word in one data file for each of those 7 ent/exits. The old method has so many different data files (4) and look up points, etc, it took a lot of time fine tuning the tracking in so many different places.
If I can/need to clarify anything, let me know. (Maybe I sould have proof read above before posting. I've only had about 30 interruptions wile writing this. )
Any ideas, suggestions are always appreciated.
Thanks,
Dale