1734-vhsc24

Did you leave the encoder set to 200ppr?

Also possible that it was a lucky capture. If you have 1mm window and you're skipping every 8.6mm, then what, like 12% chance of getting it anyway?

It seems you have all the math now. Start from scratch with the math ad make sure you are programming and configuring everything to ensure you don't miss. Maybe program in error handling code for when you do miss the window, for example comms loss for 10ms.
 
Trying to understand the process

For a period of 1 ms, a missed pulse rate would be: Freq = (1000PPRx2600RPM) / 60 ~ = 43.33 KHz. Thus 43.33 KHz * 0.001 ms ~ = 43.33 Pulses equivalent to 8.6 mm.


Still a newbie trying to follow the thread and learn summat; I understand the math, it's basically multiplying by 1, like 90% of engineering, but I have a few queries:


You meant 3600RPM, not 2600RPM, so 12mm, is that correct (and ~6mm at 1750RPM)?




Does the following describe the process?

  • A defective discrete part triggers a failure at inspection station X
  • Record the current conveyor position, "Pfail," via [counter+encoder],
    • Triggered by defective part inspection event above
  • Calculate the future conveyor position when defective part will reach expulsion diverter:

    • Pdivert = Pfail + [known diverter position] - [known station X position]

  • Monitor conveyor position over time, and
    • Trigger diverter when conveyor position is within some +/- range of Pdivert
      • This is the GRT/LES test referred to?
      • And the problem is that sometimes the measured conveyor position jumps over the [Pdivert +/- range] values?


Does "RPI" mean Request Packet Interval, i.e. how often encoder sends position to PLC, or how often PLC requests position from encoder?


What is a typical distance between each part, defective or not?


What is the defect rate?


These are a lot of questions, thanks in advance for considering a response.
 
Last edited:
Did you leave the encoder set to 200ppr?
I am working with 200 PPR now

Also possible that it was a lucky capture. If you have 1mm window and you're skipping every 8.6mm, then what, like 12% chance of getting it anyway?

It seems you have all the math now. Start from scratch with the math ad make sure you are programming and configuring everything to ensure you don't miss. Maybe program in error handling code for when you do miss the window, for example comms loss for 10ms.



I do not understand this part: "Maybe program in error handling code for when you do miss the window, for example comms loss for 10ms".
 
Still a newbie trying to follow the thread and learn summat; I understand the math, it's basically multiplying by 1, like 90% of engineering, but I have a few queries:


You meant 3600RPM, not 2600RPM, so 12mm, is that correct (and ~6mm at 1750RPM)?




Does the following describe the process?

  • A defective discrete part triggers a failure at inspection station X
  • Record the current conveyor position, "Pfail," via [counter+encoder],
    • Triggered by defective part inspection event above
  • Calculate the future conveyor position when defective part will reach expulsion diverter:

    • Pdivert = Pfail + [known diverter position] - [known station X position]

  • Monitor conveyor position over time, and
    • Trigger diverter when conveyor position is within some +/- range of Pdivert
      • This is the GRT/LES test referred to?
      • And the problem is that sometimes the measured conveyor position jumps over the [Pdivert +/- range] values?


Does "RPI" mean Request Packet Interval, i.e. how often encoder sends position to PLC, or how often PLC requests position from encoder?


What is a typical distance between each part, defective or not?


What is the defect rate?


These are a lot of questions, thanks in advance for considering a response.

1 - I meant even 2600 RPM.

2 - Exactly


3 - The RPI of the I / O cards is set to 1 ms (minimum possible). VHSC24 card RPI is in 2 ms (minimum possible too)

4 - It is around 200 250 mm.


5 - I have no way to need it, varies greatly.
 
Did you leave the encoder set to 200ppr?

Also possible that it was a lucky capture. If you have 1mm window and you're skipping every 8.6mm, then what, like 12% chance of getting it anyway?

It seems you have all the math now. Start from scratch with the math ad make sure you are programming and configuring everything to ensure you don't miss. Maybe program in error handling code for when you do miss the window, for example comms loss for 10ms.


Using a periodic 1 ms task, can you really? In practice, it turned out to be, but what would the calculation be?
 

Similar Topics

i am bench testing a 1734 -VHSC24 Point I/O High Speed counter module, i cannot find any examples of wiring the outputs from the module. does...
Replies
4
Views
1,385
Morning Guys, I am installing a turbine flow meter with a pulse output to measure flow on a compactlogix 5069 -L306ER through a 1734-VHSC24...
Replies
3
Views
1,591
Hello to all and thanks for help in advance. I am trying to set up sensors to detect blade RPM of a mower using 2 sensors and a VHSC24 card. I...
Replies
3
Views
1,543
Does anyone know how to set the output window on-off values on the fly without having to inhibit the module? I could of sworn when I first started...
Replies
11
Views
2,377
Hey people! For a school project, I and a friend have a 1734-VHSC24 connected to an encoder. Simultaneously we have 2 x kinetix 5700 with servo...
Replies
2
Views
1,927
Back
Top Bottom