Jamey

MrPLC Member
  • Content count

    28
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Jamey

  • Rank
    Sparky

Profile Information

  • Country United Kingdom
  1. Student advice

    No worries, Joe :)
  2. Student advice

    Any advice would be most appreciated!
  3. Student advice

    Hey, thank you so much for all your advice and insights, Joe!
  4. Student advice

    To recap, I need to write code to identify and differentiate between Assembled Items, Pegs, and Rings. And store, the results as bits in a Bit Shift Register. This will be used to Reject (1) or Accept (0) them.
  5. Student advice

    The distance between IP4 and the rejection station can accommodate TWO  of any combination of items. However, so far, the identification method and mechanism designed can cope with a stream of any combination of items.
  6. Student advice

    To recap, I need to write code to identify Assembled Items, Pegs, and Rings. I ONLY want to keep Assembled Items. Pegs and Rings must be rejected via the piston OP3. These are stored in a Bit Shift Register as 1 or 0. A 1 bit triggers the rejection piston. A 0 bit does NOT trigger the rejection pistion. Assembled Item = 0 Peg = 1 Ring = 1
  7. Student advice

    In LADSIM: RES is also used to reset Timers, Counters and Register bits. The Latch and Unlatch instruction are used on Outputs and a single bit too! There is no Latch or Unlatch instruction for INPUTS and no 'Seal In' at all!   Do I have to rewrite the code relating to IP3/IP8 and IP4 completely? At the moment: Rung 11 without IP4 - I can detect Assembled Items and Pegs but not rings - and the register works correctly. Rung 11 with IP4 - I can detect Assembled Items and Pegs and Rings - BUT the register increments errors - I suspect because the use of IP4 twice causes a double count to occur. Again, thank you.
  8. Student advice

    Rung 12 - This corrects the assembled items being labelled 1 (rejection). Because IP3 and IP8 operate simultaneously assembled items are ALWAYS labelled 1; so, the 1 has to be changed to 0 to avoid rejection. That is the function of this rung. Rung 14 - This rung just tidies up the register - from location 13 onwards, bits are not required. Rung 15 and 16 - the rejection rungs. An item labelled 1 in location 14 in the register triggers the rejection piston O3. It seems to work.   IP5 = Detects ALL items in the rejection area. OP3 = Rejection pistion. ----R1|  |14-- = When a 1 is in location 14 in the register it energises this NOC.   Also, thank you for taking the time to read this. It has been very stressful!  
  9. Student advice

    There has to be a solution that: (a) Identifies the three types of items. (b) Stores the data correctly in the bit shift register. Agh!
  10. Student advice

    When I use the Rung 11 that identifies only assembled items and pegs - the register keeps an accurate record. When I use the Rung 11 that identifies EVERYTHING by using IP4 - the register does NOT keep an accurate record. In the latter case, I think there is double counting caused by using IP4 on two rungs (11 and 13).
  11. Student advice

    It is supposed to represent the IP4 scanning beam. This is how the system operates: https://www.youtube.com/watch?v=6YFHfiQCqBs
  12. Student advice

    In the above 4 pics, you can see the changes in the register. pic 1. Register is 0000 0000 0000 0000. Nothing has been scanned and identified. pic 2. Register is 1000 0000 0000 0000. Peg has been scanned and identified by IP8. Bit 1 is input into location 15 (MSB). pic 3. Register is 0100 0000 0000 0000. Peg has been scanned by IP4. This SHIFTS all bits to the right (via Rung 13). pic 4. Register is 0100 0000 0000 0000. Item rejected by piston OP3. No affect on register. This is how it is supposed to work.
  13. Student advice

    1 = reject 0 = not reject I've written the code to put the first scanned item in location 15 (MSB). Then, when the item reaches IP4, rung 13 triggers a bit shift. In this software, each bit shift trigger moves EVERYTHING in the register one position to the right.   Pics below.   This is for the code that only identifies assembled items and pegs. It does NOT identify rings. However, what it does identify is correctly recorded and ordered in the register.  
  14. Student advice

    The problem is: Although, I can now identify and differentiate each type of item because I use IP4: It introduces errors into the register (outlined in previous post).
  15. Student advice

    Rung 11 does differentiate between all three item types. However, it introduces errors into the Bit Shift Register. Here, I discussed the operation of Rung 11 with and without IP4: