The RT3000v3 comes with optional RT-Range Hunter capabilities. The range functionality has been split into two feature bundles: Vehicle to Lane (V2L) and Vehicle to Vehicle (V2V). If both V2V and V2L feature bundles are enabled on an RT3000v3, it will have all the functionality that was previously contained within the RT-Range S Hunter. This article aims to guide users through the Range features on their RT3000v3 and highlight the key differences to using the RT-Range S.
To check which features are enabled on your unit:
- Power up your RT3000v3 and connect it to your PC via Ethernet.
- Open NAVconfig (latest version available here).
- Select Modify configuration.
- Use the 'Read settings from a device' option, select your RT3000v3 from the drop down and click 'Continue'.
- Click on the 'i' button in the bottom-left corner of the window.
- Scroll to the bottom of the feature code list and look for 'Range vehicle to vehicle' (V2V) and 'Range vehicle to lane' (V2L).
- The status will read either 'Enabled' or 'Disabled depending on whether these features have been unlocked on the unit.
The process is followed in the GIF below:
If the V2L features are enabled, your RT3000v3 will be able to output range measurements to up to eight lane markings for lane departure and lane keeping testing. If this is the only Range feature code enabled on the unit, mobile and fixed point targets, and feature point targets cannot be setup. As such, certain areas of the software will be locked.
When you are configuring your RT3000v3, the software makes it clear which features are available to you using padlocks. Watch the GIF below to see which features are configurable when only the V2L feature code bundle in enabled.
If the V2V feature is enabled, your RT3000v3 will be able to output range measurements from the Hunter vehicle to up to four mobile, fixed point or feature point targets. You will also be able to setup polygons and multiple sensor points. If this is the only Range feature code enabled on the unit, range measurements to lanes will be restricted.
When you are configuring your RT3000v3, the software makes it clear which features are available to you using padlocks. Watch the GIF below to see which features are configurable when only the V2V feature code bundle is enabled.
The RT3000v3 is completely compatible with the RT-Range S (Hunter and Targets).
The table below shows the combinations of products that are compatible to be used together in a Range system.
|RT3000v3||Any combination of RT3000v3s and RT-Range S Targets|
|RT-Range S Hunter||Any combination of RT3000v3s and RT-Range S Targets|
Note: RT-Range S Hunter/Target also requires an INS (e.g. an RT3000v2 or RT1003).
Old RT-Range Configurations
Configuration files from an RT-Range S Hunter (range.cfg) are transferable onto an RT3000v3, provided the RT3000v3 has the appropriate feature codes unlocked. Simply:
- Select 'Read from file'.
- Choose the RT-Range S Hunter as the product.
- Open the old configuration file.
- Change the IP address of the Hunter RT and make any other changes that you like.
- Commit to your RT3000v3, click OK on the warning message that comes up.
Although no new range functionality was introduced with the release of the RT3000v3, there are some small differences to the workflow when using an RT3000v3 compared to using an RT-Range S Hunter.
To configure the RT3000v3 as a Hunter, it needs to be initialized. This was not necessary with the RT-Range S.
Configure Range CAN messages
To configure the RT3000v3 to output Range measurements over CAN (FD or 2.0), CAN output must first be enabled in NAVconfig. NAVconfig is also where you must set the CAN Baud rate and configure the Hunter CAN messages. In the GIF below, the unit already has CAN enabled in NAVconfig. You can see that the baud rate and Hunter CAN messages are grayed out but the Range and Target messages are configurable. his unit only has the V2V feature codes. If the V2L feature was enabled, the Lane CAN messages would also be configurable.