The easiest way to create rules is to use our basic rule creation walkthrough. This tutorial will guide you through the four steps to rule creation.
First, log in to dashboard.bitbrew.com and go to the Rules navigation item.
Next, click the Add Rule button.
There are four steps to complete on the create rule page.
Step 1
In step one, you'll select the data to capture with the rule. You can choose to capture all event types, or one specific event type. You can also choose to apply the rule to all devices or to a set of previously tagged devices.
Available Event Types
This is the complete list of event types you can choose from in the dropdown menu. If you're not sure which of the following events your devices are sending, check out our list of events for a standard BitBrew pilot device.
TCP EVENTS
Ambient Air Temperature: Temperature of external air, collected at configured interval.
Calculated Engine Load: Periodic engine load readings, collected at configured interval.
Distance Traveled Since Codes Cleared: The distance traveled since DTCs were last cleared.
Distance Traveled with MIL On: Distance traveled with a malfunction indicator lamp on
Engine Coolant Temp: Periodic temperature of engine coolant, collected at configured interval.
Engine RPM: Periodic RPM reading, collected at configured interval.
Fuel System Status: Periodic status of the fuel feedback control loop, collected at configured interval.
Fuel Type: The type of fuel the car uses.
GPS: Location provided at configured periodic interval.
Intake Air Temperature: Periodic temperature readings near the intake manifold, collected at configured interval.
MIL Status: Periodic check of status of malfunction indicator lamps at configured interval.
Number of Warmups Since Codes Cleared: The number of vehicle warmups since DTCs were last cleared.
Run Time Since Engine Start: Periodic time readings on engine runtime since car start, collected at configured interval.
Speed Acceleration Histogram: Number of seconds spent at configurable acceleration rates during a trip.
Speed Deceleration Histogram: Number of seconds spent at configurable deceleration rates during a trip.
Time Driven In Speed Ranges: Number of seconds spent in configurable speed ranges during a trip.
Time Run with MIL On: If a MIL is on, the engine run time since it turned on.
Time Since Trouble Codes Cleared: Periodic reading of time since DTCs were last cleared, collected at configured interval.
Trip End: Notification of a trip end.
Trip Speed Metrics: Summarization of various speed metrics during a trip.
Trip Start: Notification of a trip start.
Vehicle Speed: Periodic speed readings, collected at configured interval.
UDP EVENTS
Device Connect: Notification that a device has been plugged in to a vehicle's OBD-II port.
Device Disconnect: Notification that a device has been unplugged from a vehicle's OBD-II port.
Device Real Time Disconnect: Immediate notification that a device has been unplugged from a vehicle's OBD-II port.
GPS: Location provided at configurable periodic intervals and based on triggers.
Hard Acceleration: Vehicle's acceleration and speed are greater than or equal to configured thresholds.
Hard Brake: Vehicle's deceleration and speed are greater than or equal to configured thresholds.
Heartbeat: A GPS event sent 24 hours after the device's last connection to provide its location.
Idling: Vehicle's speed is less than or equal to configured threshold for a configured amount of time.
Impact: Notification that the configured thresholds for a vehicle impact have been met.
Speeding End: Summarization of a high or critical speeding event after the event is over.
Speeding Start: High or critical vehicle speed; sent before the event is over.
Trip End: Notification of a trip end with summarization of various metrics.
Trip Start: Notification of a trip start.
Vehicle Battery: Low, critical, shutdown, and return to normal.
Vehicle Current DTC: Notification of a DTC count change in the vehicle.
Vehicle MIL: Notification of a MIL triggered on in the vehicle.
VIN Change: Notification that the device detects itself in a new vehicle, based on a new VIN reading.
Step 2
Next, give your rule a name. We automatically fill in a name that matches your selection in step one, but you can choose any name you wish.
Step 3
In step three, you have the option to select from the fields provided in the event you selected. All fields are selected by default.
If you want to customize the selection, you must first uncheck the top object and pick the desired data types.
Step 4
Choose the destination for the events that this rule captures.
Finally, click the Create button and you're done!
If you want to customize your rule further, you probably want to know more about our rule syntax. We also have a page of advanced example rules if you have specific needs or want to get ideas.