Guide Purpose:

• This guide IS designed to:
  • Show what Types of events are generated for Verif-Eye.
    • Explains Service exception and Its trigger values.
    • Explains Service Verification and its trigger values.
  • Show Service verification Threshold Values.
    • Explains the Distance calculations.
    • Explains the time calculations.
  • Show PSV hardware transition
• This guide IS NOT designed to:
  • Explain how a profile is created.

All Events for Verif-Eye

Service Exception

These are events you want to report on when you cannot complete a service such as Not outs, Blocked, Tipped Over, and any other events you are not familiar with. This is represented in our 3^rd Eye portal as the red trash can on the map.

1. Discrete IP 1: This is a service exception event that is triggered by a Verif-Eye hardware connected to the video button (IO Port 1) of our 3rdeye gateway device. This event shows up as a red trash can on the map.
   1. An Inclinometer is typically connected into the Video button as seen in the image below.
2. Discrete IP 2: This is a service exception event that is triggered by a Verif-Eye hardware connected to the video IO 2 In and IO 2 out (IO Port 2) of our 3rdeye gateway device as seen in the image below. This event shows up as a red trash can on the map.
3. Discrete IP 3: This is a service exception event that is triggered by a Verif-Eye hardware connected to the video IO 3 In and IO 3 out (IO Port 3) of our 3rdeye gateway device as seen in the image below. This event shows up as a red trash can on the map.
4. Discrete IP 4: This is a service exception event that is triggered by a Verif-Eye hardware connected to the event button (IO Port 4) of our 3rdeye gateway device. This event shows up as a red trash can on the map
   1. This is considered our default exception event
   2. It’s very important to note that all vehicles with a red button box connect with the event button as seen in the image below.
5. Service Exception: This is a Tablet to Gateway Event to trigger an exception event from the tablet to the gateway.
   

Service Verification

These are events created when the driver uses the arms on a truck to complete a service or when trash is being physically dumped in the back of a rear loader.  This is represented in our 3^rd Eye portal as the green trash can on the map.

1. Di 1 Active: This is a service verification event that is triggered by a Verif-Eye hardware connected to the video button (IO Port 1) of our 3rdeye gateway device. This triggers when the device is going from 0 to 1 (that is, cold to hot). This port is directly correlated with Discrete IP 1 but shows a green trash can on the map.
   1. It is important to note that an inclinometer is typically installed on IO Port 1.
2. Di 1 Inactive: This is a service verification event that is triggered by a Verif-Eye hardware connected to the video button (IO port 1) of our 3rdeye gateway device. This triggers when the device is going from 1 to 0 (that is hot to cold). This port is directly correlated with Discrete IP 1 but shows a green trash can on the map.
   1. It is important to note that an inclinometer is typically installed on IO Port 1.
3. Di 2 Active: This is a service exception event that is triggered by a Verif-Eye hardware connected to the video IO 2 In and IO 2 out (IO Port 2) of our 3rdeye gateway device. This triggers when the device is going from 0 to 1 (that is cold to hot). This port is directly correlated with Discrete IP 2 but shows a green trash can on the map.
4. Di 2 Inactive: This is a service exception event that is triggered by a Verif-Eye hardware connected to the video IO 2 In and IO 2 out (IO Port 2) of our 3rdeye gateway device. This triggers when the device is going from 1 to 0 (that is hot to cold). This port is directly correlated with Discrete IP 2 but shows a green trash can on the map.
5. Di 3 Active: This is a service exception event that is triggered by a Verif-Eye hardware connected to the video IO 3 In and IO 3 out (IO Port 3) of our 3rdeye gateway device. This triggers when the device is going from 0 to 1 (that is cold to hot). This port is directly correlated with Discrete IP 3 but shows a green trash can on the map.
6. Di 3 Inactive: This is a service exception event that is triggered by a Verif-Eye hardware connected to the video IO 3 In and IO 3 out (IO Port 3) of our 3rdeye gateway device. This triggers when the device is going from 1 to 0 (that is hot to cold). This port is directly correlated with Discrete IP 3 but shows a green trash can on the map.
7. Di 4 Active: This is a service exception event that is triggered by a Verif-Eye hardware connected to the event button (IO Port 4) of our 3rdeye gateway device. This triggers when the device is going from 0 to 1 (that is cold to hot). This port is directly correlated with Discrete IP 3 but shows a green trash can on the map.
8. Di 4 Inactive: This is a service exception event that is triggered by a Verif-Eye hardware connected to the event button (IO Port 4) of our 3rdeye gateway device. This triggers when the device is going from 1 to 0 (that is hot to cold). This port is directly correlated with Discrete IP 3 but shows a green trash can on the map.
9. Container Service Event: This event is triggered through the Heil Cortex. It is when a HEIL AFL or ASL services a customer.
   1. This event can only be a service verification event and will show up as a green trash can on the map.
   2. Please not that this event does not trigger on all HEIL AFL’s and ASL’s (Reference guide “Support Truck Types”)
10. Arms_Below _Transit_Position 0: It is when an FEL fork goes up to do a dump.
    1. This event can only be a service verification event and will show up as a green trash can on the map
    2. Please not that this event does not trigger on all HEIL FEL’S (Reference guide “Support Truck Types”)
11. Arms_Below _Transit_Position 1: It is when a FEL fork comes down from a dump.
    1. This event can only be a service verification event and will show up as a green trash can on the map
    2. Please not that this event does not trigger on all HEIL FEL’S (Reference guide “Support Truck Types”)

Service Verification Threshold Value

Service Verification Distance Calculations

When threshold value is 0 or greater (> = 0), the value for JPEG time will be ignored and the logic for service verification calculations will be distance based. Keep in mind this logic only works when J1939 is connected, and the vehicle is broadcasting wheel speed. If none of this criteria is meet, the vehicle will default to creating event and distance 0.

Find different scenarios below

1. If the Threshold value is 0 and JPEG Time is 1.
   1. The Logic here is for event to be captured at Distance 0. Therefore, it will ignore the JPEG Time.
2. If the threshold value is 1 and the JPEG Time is 5.
   1. The logic here is to rollback in distance 1ft and then take picture. This logic ignores the value of JPEG Time.
3. If the threshold value is 5 and the JPEG Time is 20.
   1. The logic here is to rollback in distance 5ft and then take picture. This Logic ignores the value of JPEG Time.

Service Verification Time calculations

When threshold value is -1 and the JPEG Time is greater than, equal to, or less than 0 (< = 0 = >), the logic for service verification calculations will be time based. There are situations where the customer will insist on using a time-based profile even though the vehicle is connected to J1939. Find different scenarios below.

1. If the threshold value is -1 and JPEG Time is 0.
   1. The logic here is to ignore the threshold value and take the picture at JPEG Time which is 0 secs. This means as soon as the event is triggered a picture should be taken.
2. If the threshold value is -1 and JPEG Time is 10.
   1. The logic here is to ignore the threshold value and take the picture at Jpeg Time which is 10secs after the event has been triggered (This means taking a picture after the service).
3. If the threshold value is -1 and JPEG Time is -10.
   1. The logic here is to ignore the threshold value and take the picture at Jpeg Time which is -10secs before the event was triggered (This means taking a picture before the service).

PSV Hardware Transition

Inclinometer

Mechanical Mechanism

• Cold to Hot (0 → 1)
  • When the angle of the device is below the 68-degree plane.
• Hot to Cold (1 → 0)
  • When the angle of the device exceeds the 68-degree plane

Recommended State Capture: Hot to Cold (1 → 0)

Recommended Trigger Value1: We recommend using DI 1 Inactive since PSV is typically connected to IO Port 1, and it’s set to trigger at the recommended state capture. This can also be installed on the other Ports and use the trigger value associated with the ports such as  DI 2 Inactive, DI 3 Inactive, and DI 4 Inactive.

Pneumatic pressure switch

Mechanical Mechanism

• Cold to Hot (0 → 1)
  • When the air pressure goes beyond ambient line standard.
• Hot to Cold (1 → 0)
  • When the air pressure in the line returns to the ambient line standard.

Recommended State Capture: Cold to Hot (0 → 1)

Recommended Trigger Value: We recommend using DI 1 Active since PSV is typically connected to IO Port 1, and it’s set to trigger at the recommended state capture. This can also be installed on the other Ports and use the trigger value associated with the ports such as DI 2 Active, DI 3 Active, and DI 4 Active.

Hydraulic Pressure Switch 

Mechanical Mechanism

• Cold to Hot (0 → 1)
  • When the hydraulic pressure exceeds the threshold programmed on the switch.
• Hot to Cold (1 → 0)
  • When the hydraulic pressure reduces below the threshold programmed on the switch.

Recommended State Capture: Cold to Hot (0 → 1)

Recommended Trigger Value: We recommend using DI 1 Active since PSV is typically connected to IO Port 1, and it’s set to trigger at the recommended state capture. This can also be installed on the other Ports and use the trigger value associated with the ports such as DI 2 Active, DI 3 Active, and DI 4 Active.

Radar

Mechanical Mechanism

• Cold to Hot (0 → 1)
  • When the radar senses and object within its visible range.
• Hot to Cold (1 → 0)
  • When the radar can no longer sense an object within its visible range.

Recommended State Capture: Cold to Hot (0 → 1)

Recommended Trigger Value: We recommend using DI 1 Active since PSV is typically connected to IO Port 1, and it’s set to trigger at the recommended state capture. This can also be installed on the other Ports and use the trigger value associated with the ports such as DI 2 Active, DI 3 Active, and DI 4 Active.

Proximity Switch

Mechanical Mechanism:

• Cold to Hot (0 → 1)
  • When an object comes within range of the sensor and activates it.
• Hot to Cold (1 → 0)
  • When an object goes out of range of the sensor and deactivates it.

Recommended State Capture: Hot to Cold (1 → 0)

Recommended Trigger Value: We recommend using DI 1 Inactive since PSV is typically connected to IO Port 1, and it’s set to trigger at the recommended state capture. This can also be installed on the other Ports and use the trigger value associated with the ports such as  DI 2 Inactive, DI 3 Inactive, and DI 4 Inactive.

HEIL FEL 

Mechanical Mechanism

• Cold to Hot (0 → 1)
  • When the angle of the device is below the 68-degree plane.
• Hot to Cold (1 → 0)
  • When the angle of the device exceeds the 68-degree plane

Recommended Trigger Value: We recommend using Container Service Event based on the recommended state capture. This is triggered by the Heil cortex installed in the body of the vehicle

HEIL ASL 

Mechanical Mechanism:

• Cold to Hot (0 → 1)
  • When the arm rises above the trigger threshold, approximately 70 degrees above the perpendicular of the body.

Recommended Trigger Value: We recommend you capture when the container as it is being grabbed.  We recommend you use the Container Service Event.  This is triggered by the Heil cortex installed in the body of the vehicle

HEIL AFL

Mechanical Mechanism:

• Hot to Cold (1 → 0)
  • When the Curotto-can arm LOWERS below the trigger threshold, approximately 70 degrees above the perpendicular of the Curotto-Can.
• Cold to Hot (0 → 1)
  • When the angle of the device is below the 68-degree plane.
• Hot to Cold (1 → 0)
  • When the angle of the device exceeds the 68-degree plane

Recommended Trigger Value: We recommend you capture the Curotto-can servicing the customer. We recommend you use the Container Service Event. This is triggered by the Heil cortex installed in the body of the vehicle