Step-by-Step Guide

Setting Up User Contact Information

Before you can receive alerts and messages from your BaseManager system, you need to configure your user contact information and communication preferences. This is a critical step that is often overlooked after initial controller setup.

1. Click on the Menu icon (also called the "hamburger" icon) in BaseManager.

2. Select Administration from the menu.

3. Click Administration again to open a new window that displays all your controllers.

4. Click on My User Information to access your personal settings.

5. Verify that your Email address is entered correctly. This is how you will receive email notifications.

6. Enter your Phone Number in the designated field.

7. In the text number field, enter your cell phone number again. While this field was originally designed for separate pager numbers, modern cell phones use the same number for both calls and texts.

8. Select your Cell Provider from the dropdown menu. This step is required for text message delivery.

9. Ensure the Disable All Alerts checkbox is unchecked. If this box is checked, you will not receive any alerts regardless of your other settings.

Configuring Alert Timing and Delivery Preferences

Once your contact information is entered, you can fine-tune when and how you receive alerts.

1. Select your Time Zone from the dropdown menu (e.g., Pacific, Eastern, Mountain, Central).

2. If you want to receive reports, select a Report Time. For example, you might choose 6:00 AM to receive reports at the beginning of your workday, or 5:00 AM if you start earlier.

3. Choose your Email Frequency. You can select to receive emails once per day or as they occur.

4. Configure your Text Message Time Windows. You can block text messages during certain hours. For example, you might choose to not allow texts between midnight and 6:00 AM, but allow them from 6:00 AM to 6:00 PM during general working hours.

5. Consider your role when setting these time windows. If you're a manager, you might only want messages during working hours. If you're on-call or responsible for mainline emergencies, you may need to allow messages 24/7. Union situations may also require specific time restrictions to avoid unnecessary on-call pay.

6. Click Edit Save to save your contact information and timing preferences.

Subscribing to Controller Alerts

After setting up your contact information, you need to specify which controllers you want to monitor and what priority level of alerts you want to receive.

1. Click on Alerts and Report Subscriptions.

2. Click Edit Alert Subscriptions.

3. For each controller you want to monitor, you can choose to receive:

• High Priority alerts
• Medium Priority alerts
• Low Priority alerts
• All alerts (turn on all three priority levels)
• No alerts (turn off all priority levels)

4. If you're new to the system, it's recommended to start by subscribing to all priority levels. These priority levels are generalized buckets, and an alert you consider high priority might be labeled as low priority in the system. It's better to be overwhelmed initially and then filter out unnecessary alerts than to miss an important message.

5. If you find that low priority alerts are clogging your inbox or phone, you can return to this screen and uncheck that priority level.

6. If you only manage specific sites, you can select alerts for only those controllers and leave others unchecked.

7. Scroll down to review all your selections.

8. Click Save to save your alert subscriptions.

Setting Controller Limits and Thresholds

In addition to configuring your user settings in BaseManager, you must also ensure that your controller settings are configured correctly. These settings determine when alerts are triggered.

You need to set accurate limits for:

• Flow Limits (high and low flow thresholds)
• Pressure Limits (high and low pressure thresholds)
• Moisture Limits (if applicable)

These settings can be configured through BaseManager or directly at the controller. On new installations, it often takes some time to dial in these limits correctly. You may need to adjust them after observing actual system performance. For example, you might think you know what the flow limit should be, but after monitoring the system, you may discover it needs adjustment.

One useful strategy during system initialization is to enable flow variance detection without enabling shutdown. This allows you to monitor flow patterns for a week or two and observe real-time flow behavior, including slow-closing valves that might overlap with other valves turning on. This helps you determine where your actual high flow sits so you can set appropriate limits and avoid nuisance alarms in the future.

Understanding Device Two-Wire No Response Messages

The Device Two-Wire No Response message is one of the most common alerts you'll encounter. This is a high priority message that includes a flow biCoder number or other two-wire device identifier.

This message means that the controller sent a command out to a two-wire device (such as a flow biCoder), but did not receive a response back. In Baseline two-wire technology, commands are sent out to biCoders and then return to the controller. When you see this message, it indicates that the command went out but didn't come back.

In 99% of cases, this means the device is no longer connected to the two-wire path. The most common causes are:

• A wire has been cut
• A splice has failed
• The device has become disconnected

If you see a group of these messages (for example, 10 devices all showing no response), this strongly indicates that a wire was cut somewhere upstream, and everything downstream of that cut cannot communicate back to the controller. It's very rare for multiple devices to fail simultaneously, so grouped messages point to a wire path issue rather than multiple device failures.

This message can also occasionally appear when:

• The system is out of two-wire specification (wire run is too long)
• There are one or more poor splices causing signal degradation

In these cases, the signal may be strong enough to reach the device (so valves still operate and sprinklers turn on), but too weak to make it all the way back to the controller.

Note that lightning strikes typically do not result in this type of failure. Lightning events more commonly cause short circuits rather than no response messages.

Understanding Device Valve BiCoder Short Circuit Messages

The Device Valve BiCoder Short Circuit message is a medium priority alert that indicates a problem on the solenoid side of a valve biCoder, not the two-wire side.

The full message reads: "Valve failure short circuit solenoid unable to operate this valve" and includes a biCoder serial number.

This message means there is a short circuit somewhere between the biCoder and the solenoid. The short could be:

• In the solenoid itself
• In a splice where the solenoid wires are touching
• Where bare wires have made contact

This is specifically a solenoid-side issue. If there were a short on the two-wire side, the entire system would go down with an over-current condition, not just a single valve.

Understanding Device Valve BiCoder Open Circuit Messages

The Device Valve BiCoder Open Circuit message indicates an incomplete circuit on the solenoid side of a valve biCoder. This is a much more common message than the short circuit message.

The full message reads: "Open circuit solenoid unable to operate this valve" and includes a biCoder serial number.

An open circuit means the electrical circuit is not complete. Common causes include:

• A wire has been cut on the solenoid side
• A splice has failed
• The solenoid itself is broken
• Wires are no longer making contact

Open circuit failures are much more common than short circuits because splices fail over time and solenoids can break, whereas creating a short circuit requires wires to touch in a way that closes the circuit.

Understanding Open Circuit Messages on Conventional Wire Systems

When you see an open circuit message, check the valve identifier in the message. If the serial number shows "VA" or "VB" instead of a biCoder serial number, this indicates a conventional wire system (retrofit valve) rather than a two-wire system.

On conventional wire systems, the controller measures resistance across potentially 2,000 feet of common wire running out to the solenoid and back. An open circuit message on a conventional system means the problem could be:

• At the solenoid itself
• At a splice anywhere along the wire path
• Anywhere along the wire path back to the controller

The system has reached the resistance threshold limit and detected an open circuit somewhere along this entire wire path, but it cannot pinpoint the exact location.

Another scenario that triggers this message is when a conventional wire terminal on the controller has no wire connected to it at all. The controller checks for a complete circuit, finds none, and reports an open circuit for that terminal.

Understanding Controller Rain Stop Jumper Messages

The Controller Rain Stop Jumper message is a low priority alert that includes the controller serial number, time, and date.

The full message reads: "The rain contacts were triggered. All watering is stopped. The switch is in the open position. All watering will remain stopped until the switch closes."

This message typically means your rain sensor has been activated due to a rain event. While this is not particularly urgent, it's useful information to know why watering has stopped.

However, if you receive this message and you don't have a rain sensor installed, this is a good reason to call support. The message could indicate:

• Someone removed the jumper wire from the rain sensor terminal
• The screw terminal has loosened, causing an intermittent connection

If the jumper wire is removed or the connection is loose, all watering will stop even though you don't have an actual rain sensor.

Remember that the controller has three similar terminals:

• Rain
• Pause
• Flow

All three function as normally closed switches, just like the rain sensor terminal. It's common to see the jumpers for the Pause or Flow terminals removed or loosened, which will generate similar messages. If your controller says "flow switch" and you don't have one installed, check that the jumper is in place and the terminal is tight.

Understanding High Flow Variance Detected Messages

The Mainline High Flow Variance Detected message is a low priority alert that indicates the system has detected a difference between your set flow limit and the actual measured flow.

In your controller settings, you configure what's called a "variance" value (for example, 5, 10, or 15 GPM). This message appears when the actual flow exceeds your high flow limit by more than the variance you've set.

For example, if your high flow limit is set at 30 GPM and the system detects 37 GPM, you'll receive this message. The key word here is "detected" – the system noticed the variance and is alerting you, but it has not taken any action to shut down the system.

This is an informational message letting you know that flow exceeded your expected range. You may or may not consider this important depending on your site needs.

Understanding High Flow Variance Shutdown Messages

The Mainline High Flow Variance Shutdown message is a high priority alert that uses the exact same limits and detection as the "detected" message, but with one critical difference: the system has shut down the mainline.

In BaseManager or at the controller, there is a checkbox option for "shutdown on high flow variance." When this box is checked, the system will not only detect the high flow condition but will also automatically shut down the mainline to prevent potential damage or water waste.

This is an excellent example of why you should subscribe to all alert priority levels when you're first setting up your system. The "detected" message is low priority, while the "shutdown" message is high priority. However, you might personally consider even the detection of high flow to be high priority for your operation. If you're not subscribed to low priority alerts, you would miss the detection messages entirely.

The difference between these two messages is:

• Detected: System noticed the problem and told you about it
• Shutdown: System noticed the problem, told you about it, AND took action by shutting down

Understanding Pressure Variance Messages

Pressure variance messages work almost identically to flow variance messages. The POC (Point of Connection) Low Pressure Shutdown message is a high priority alert that includes both a limit value and an actual value.

Understanding the terminology:

• Limit: The set point you configured in the system
• Value: What the system is actually reading right now

These terms (limit and value) are used consistently for flow, pressure, and moisture measurements throughout the system.

For example, if your pressure limit is set at 35 PSI and the system reads only 31.7 PSI, you'll receive this low pressure message. Just like with flow, you can configure the system to either detect the variance or to detect and shut down when the variance occurs.

Understanding Program Priority Preempted Messages

The Program Priority Preempted message indicates that one program has interrupted another program based on priority settings.

This message occurs when:

• Two programs are scheduled to start at the same time
• A higher priority program starts while a lower priority program is already running

For example, if Program 1 (priority level 5) is running and Program 2 (priority level 2) is scheduled to start, Program 2 will preempt Program 1. The message will indicate that the lower priority program was paused.

It's important to note that the program is paused, not stopped. High priority programs must run to completion. Once the high priority program finishes, the system will automatically resume the program that was preempted, continuing from where it left off.

Using Message Time Stamps for Troubleshooting

Every alert message includes a time and date stamp. This information is valuable for troubleshooting, especially when trying to determine the cause of a problem.

For example, if you receive an open circuit message for a specific biCoder, you can check the time stamp and ask: "Who was working on site at 9:30 AM?" This can help you determine if the problem occurred during service work or maintenance, or if it's an unrelated failure.

Before deleting any message, if you're not sure what it means, take a picture of it with your phone. This is extremely helpful when calling support or contacting your regional sales manager. Often, someone will call and say "I had a message about zone 54," but there are three or four very specific messages that could all relate to the same zone. Each message indicates a different problem with a different solution. Support needs to know the exact wording of the message to provide accurate troubleshooting guidance.

Downloading the Complete Message Reference Guide

A comprehensive PDF document is available that lists all BaseStation 3200 messages with their full descriptions. This document serves as a quick reference guide for understanding any message you encounter.

Think of this guide like an OBD reader for your car. When a car's diagnostic system shows a code like "P2401," you can look it up to find it refers to emission control and could be caused by three or four specific things. This allows you to target only those potential issues rather than guessing. The BaseManager message guide works the same way – it gives you detailed descriptions that help narrow your focus to the specific problem.

While the messages provide good descriptions, sometimes you may need to contact support or search for additional information to fully understand the implications and solutions. The message guide helps you get started with accurate information.

This document is not currently published in the user manual but is available as a resource for BaseManager users. You can find the link in the show notes of the Tech Talk Tuesday video on the Baseline Web Training YouTube channel.

How Alert Messages Stack Up During Blocked Time Periods

If you configure your alert settings to block messages during certain hours (for example, blocking texts between midnight and 6:00 AM), the messages don't disappear – they stack up.

As soon as your allowed time period begins (6:00 AM in this example), all the messages that occurred during the blocked period will be delivered to you at once. This is similar to turning your phone back on after having it off – all the messages that came in while it was off will arrive as soon as it powers up.

This feature allows you to maintain work-life balance by preventing after-hours alerts while still ensuring you receive all important information at the start of your workday.

Video Walkthrough

Video originally published October 2020.

If you have questions, here are 3 ways to get answers:

1. Search within this Baseline knowledgebase

2. Visit the Baseline support page

3. Call 866-294-5847 or email support@baselinesystems.com, hours are from 6:00 am to 7:00 pm Eastern Time or 4:00 am to 5:00 pm Pacific Time.