Ben Posts:155
 |
| 03 Nov 2010 11:21 AM |
Quote
Reply
|
I'm trying to see/add RPM readout on the Status View Engine Health Analysis when vehicle is moving. Also would like to set up alerts so in case the engine reaches certain RPM end user can get an email alerting him/her this event is happening. Can I do this? Ben |
|
|
|
|
Mauricio
 Posts:268
 |
| 04 Nov 2010 11:18 AM |
Quote
Reply
|
Yes, you need to enable driver feedback on excessive RPM and set the excessive RPM threshold. Then the Go device will record the RPM when it breaks that threshold. You can then create an RPM over-revving rule that will send alerts when the event occurs. |
|
|
|
|
Ben Posts:155
 |
|
Siyo Posts:155
 |
| 16 Dec 2010 09:40 PM |
Quote
Reply
|
I enable driver feedback on excessive RPM, and set the excessive RPM over 1800 RPM, but i dont find where to create the excessive RPM rule. this options does not appears at Driving Exception, or at EngineMeasurement or at Engine Faults, so i would like to know how to create this rule. thank you Siyo |
|
|
|
|
Mauricio
 Posts:268
 |
| 17 Dec 2010 10:58 AM |
Quote
Reply
|
Hi Siyo, The RPM rule is found under Engine Management or Data Exception. It is "OBD: 12 - Engine RPM" You then must choose between what values you would like the rule to be broken. |
|
|
|
|
Siyo Posts:155
 |
| 20 Dec 2010 07:29 PM |
Quote
Reply
|
thanks Mauricio does this rule apply to J1939? i did some tests but it did not work.. (i only have J1939 vehicles) thank you |
|
|
|
|
Patrick
 Posts:110
 |
| 21 Dec 2010 02:00 PM |
Quote
Reply
|
Hi Siyo, The rule does apply to J1939. Which firmware version is the device currently using? You can determine this by opening the Device Details report in Checkmate and selecting More -> Show More Details |
|
|
|
|
Siyo Posts:155
 |
| 21 Dec 2010 03:19 PM |
Quote
Reply
|
Hello Patrick the firmware that the unit has, is 81.0.29 do i have to change the "OBD 12 Engine RPM" to "J1939 190 Engine Speed" ? to make it work with J1939? i also did it, but did not work. Thank you Siyo |
|
|
|
|
Siyo Posts:155
 |
| 30 Dec 2010 06:58 PM |
Quote
Reply
|
any answer? i really need to make this work.. thanks
|
|
|
|
|
Patrick
 Posts:110
 |
| 03 Jan 2011 03:04 PM |
Quote
Reply
|
Hi Siyo, Can you confirm that you have enabled the parameter "Beep when RMP over 1800" on the unit. This parameter is required in order for the device to log RPM values. If the parameter has been applied correctly, then the unit should beep to warn the driver when the RPM exceeds 1800. Can you confirm that this is the case? |
|
|
|
|
Siyo Posts:155
 |
| 03 Jan 2011 10:39 PM |
Quote
Reply
|
hello Patrick.. thanks for your answer. that is not the case, i thought that doing the RPM exception, i was going to receive an exception report when the vehicle exceeded the 1800 RPM, that was what i was expecting.. i confirm that the unit beeps, once it exceeds the RPM limit, but is not what i was looking for. i just need an exception report, that i get, once the vehicle exceeds certain number of RPMs.. thats it. is that possible? thank you |
|
|
|
|
Patrick
 Posts:110
 |
| 07 Jan 2011 03:42 PM |
Quote
Reply
|
The unit will only consistantly log RPM when it goes aboe this value if you enable the "Beep when RPM over x" parameter on the unit. If you do not want the unit to beep at the driver, you can also enable the parameter "Disable Buzzer" in the Logging Parameters tab of the device editor. This will stop the unit from beeping when the RPM goes over 1800 but it will still log the RPM value when the threshold goes over. |
|
|
|
|
Siyo Posts:155
 |
| 17 Jan 2011 04:28 PM |
Quote
Reply
|
thanks Patrick what i actually need, is a report that say "High RPM" once RPMs are over the 1800.. is that possible? |
|
|
|
|
Patrick
 Posts:110
 |
| 17 Jan 2011 04:43 PM |
Quote
Reply
|
Hi Siyo, Yes, you can setup an exception rule in Checkmate: The RPM rule is found under Engine Management or Data Exception. It is "OBD: 12 - Engine RPM" You then must choose between what values you would like the rule to be broken. Once you setup the exception rule, you will be able to run an exceptions report in Checkmate to see which vehicles broke the rule. Please note though, you must have your devices setup with the parameters given in this forum post. This so that the unit will record the RPM values you want it to. If the device is not setup with these parameters, it will not log any RPM data whatsoever. |
|
|
|
|
Siyo Posts:155
 |
| 18 Jan 2011 11:28 PM |
Quote
Reply
|
thanks Patrick, somehow i cant make it work.. this is what i have: 1- the vehicle is set to beep when RPM over 750 (i set it up a low value to force it) 2 -the exception is set "OBD: 12 - Engine RPM" logs a value between 750 - 1000 3 -recalculate data 4- Exception report - select vehicle - options - engine rules - select the exception created 5 -Apply 6 -There is no data to display am i missing a step? thanks Patrick |
|
|
|
|
Patrick
 Posts:110
 |
| 19 Jan 2011 09:27 AM |
Quote
Reply
|
Hi Siyo, It sounds like you have set everything up correctly. When you apply the parameter to a vehicle though, it will only apply to future data, not historic data. The best way to test would be to go to the vehicle which has the parameter and rev the engine upto 750 RPM. Then, run an exceptions report in Checkmate to verify that the exception was triggered for this vehicle. You can turn off the "disable buzzer" parameter if you want to be sure that the vehicle has received the RPM parameter correctly (the unit will beep when you rev the engine of 750). |
|
|
|
|
Siyo Posts:155
 |
| 19 Jan 2011 06:51 PM |
Quote
Reply
|
Hello Patrick how long it takes to checkmate to send the parameter updated to the go4 unit? i have been doing some tests, and the buzzer is not doing any sound when the unit gets the "x" value of RPMs that is been set. i just need to enable the beep on RPMs and wait to send the update, correct? thanks Patrick for your help
|
|
|
|
|
Patrick
 Posts:110
 |
| 20 Jan 2011 03:49 PM |
Quote
Reply
|
Hi Siyo, When you make a change to a device's parameters, it will take approximately 30 minutes for the change to reflect in the system. After this 30 minute "cache" window, Checkmate will push down the update to the device on the next "ignition off". The process to apply the update is: 1. Change the parameter for the device in Checkmate 2. Wait 30 mintues for the cache window to expire 3. Ignition cycle the vehicle so that it will connect to Checkmate and download the parameter update. You will need to enable the "Beep on RPM" parameter, and also ensure that the "disable buzzer" parameter is not enabled. |
|
|
|
|
Siyo Posts:155
 |
| 20 Jan 2011 06:46 PM |
Quote
Reply
|
Thanks Patrick well everything seems to be correctly configured, i even enabled "beep on auxiliar 1" and it works, it does beep when auxiliar 1 is grounded. but RPMs are not working, once it reach the value that is set, it does not make any beep. what other test can i do? thank you
|
|
|
|
|
Patrick
 Posts:110
 |
| 21 Jan 2011 09:47 AM |
Quote
Reply
|
Hi Siyo, I think that at this point the best option is for a troubleshooting session over the phone. Your first point of contact for all telephone support is the your Geotab registered dealer. This is the company you purchased the system from. Please contact this company and make them aware of the issue you are experiencing. They will be able to contact Geotab for Level 2 support on the phone if required. |
|
|
|
|