YSI Total Algae Sensor: A Field Checklist for Rush Deployments

A consultant called at 2:30 on a Tuesday in July 2024. They needed a YSI EXO with a total algae sensor on a reservoir by 6:00 the next morning. The normal mobilization time for that kind of work was three or four days. They had about 15 hours.

I work in field applications support at YSI. Over the last seven years, I've helped coordinate 200+ rush deployments like this one, including same-day turnarounds for consultants, drinking water plants, and industrial environmental teams. Most of those jobs went fine. The ones that didn't went wrong for the same few reasons, almost every time.

This is the checklist I use when a YSI EXO and a total algae sensor absolutely have to be in the water by sunrise. It takes about 90 minutes to run through if you have all the parts on hand, and it catches most of the problems that make a sensor fail on site.

1. Do the YSI download and software check before you touch the sensor

Most people start with the sensor. I start with the laptop, because if you cannot communicate with the sonde, nothing else matters. If the EXO has been in storage for a few months, the software on the firmware side may not match. In one case last spring, an older EXO would boot up fine but refused to recognize a newly added algae sensor until we updated the sonde firmware.

Don't dig through old email attachments for a software installer. Go to the YSI site and search for YSI download; take the current EXO software and read the release notes. If there is a total algae sensor fix or a wiper-related note in there, that is relevant to you.

Then test the download path, not just the sensor. Connect the sonde, set the logging interval, run it for 10 minutes, and export the file. If your USB adapter or Bluetooth connection is flaky, you want to find that out in the workshop, not at a dark boat ramp at 5 a.m.

2. Give the total algae sensor a real optical check

The YSI Total Algae Sensor is an optical fluorescence sensor. It measures chlorophyll, and depending on configuration, phycocyanin or phycoerythrin, in RFU and derived µg/L. Because it is optical, anything on the window, any scratch, or a wiper that isn't moving can produce data that looks valid but is actually garbage.

Take the sensor out, inspect the optical window, and clean it with a soft, lint-free cloth. Check that the wiper arm moves freely across the face. Then fill a clean bucket with deionized water and let the sensor read in live mode. A clean blank should sit near zero and stay stable.

Here's something that surprises people: a sensor that won't stabilize on the bench will not stabilize in a lake. If the algae channel is drifting while sitting in clean water, do not ship it.

One more note on units. If your project needs a regulatory chlorophyll-a number, RFU is a field screening signal, not a lab result. Pair it with a recognized method such as EPA Method 445.0 for in vivo fluorescence, or your project's approved lab method, before you promise a compliance number.

3. Inspect connectors, O-rings, and seals with a digital micrometer set

Most "bad sensor" calls I've debugged are not sensor failures. They are connector problems, corroded pins, or dried-out O-rings. The electronics in the EXO are usually fine. The water path around the electronics is what fails.

Pull the sensor guard, look at the bulkhead pins, and check for green or black deposits. If you see any, clean the contacts carefully before you install the sensor. Also inspect the O-rings on the sensor ports. A slightly flattened O-ring can seal fine in the shop and start weeping a week later.

This is why I keep a digital micrometer set in every field kit. If you are replacing an O-ring from a generic spare kit, don't assume it matches. Measure the cross-section. An O-ring that is only a few thousandths of an inch thinner can create a tiny leak path that doesn't show up during a 10-minute bench test, but will show up as a wet connection after a day in the water.

It looks obsessive, but I've seen one flooded bulkhead connector turn a one-hour deployment into a two-day repair. Measure the O-ring.

4. Calibrate with fresh standards, and don't take shortcuts

If the EXO is carrying pH, DO, conductivity, or turbidity sensors alongside the total algae sensor, those need proper calibration before you go. Use unexpired standards. Check lot numbers. Write down the readings.

I'll get on my soapbox here: the cheapest standard is not the most economical standard. In early 2023, a project team tried to save money on a discounted pH buffer set. The buffers were off by roughly 0.3 pH units. The team only caught it after a full day of sampling. The $60 they saved turned into thousands of dollars in lost field time and an unusable data set. That is the real cost of buying on price alone.

5. Verify the depth chain, including any absolute encoder PROFINET system

If the EXO is going to hang on a winch, a profiler, or a stationary cable that moves between depths, you have two measurement challenges: the water quality readings and the depth labels attached to them.

In many setups, depth is not read from the sonde's pressure sensor at all. It comes from the winch position, often through an encoder. In one reservoir installation, the depth data was coming from an absolute encoder PROFINET module on the winch. The encoder itself was not broken, but a maintenance crew had replaced its battery and lost the zero reference. The YSI EXO was measuring perfectly. The problem was that every algae result was assigned to the wrong depth.

If your system uses an absolute encoder PROFINET setup, check the depth chain at two known points before you deploy. Lower the sonde to 0.5 meters, confirm the display says 0.5. Lower it to 2 meters, confirm the display says 2. That 5-minute test has saved me from publishing beautifully accurate data with completely wrong depth values.

6. Run a 15-minute live water check before leaving

Once everything is configured, do not just power it on and throw it in the truck. Put the EXO in a clean bucket, start live readings, and let it run for at least 15 minutes. Watch the total algae channel. Watch the other sensors too.

You are looking for three things: stable readings, no communication dropouts, and a wiper that actually cycles. If the sensor drops off the bus twice during a 15-minute bench test, it will drop off the bus three times in the middle of your sampling event.

If you are using a new sensor or a newly rebuilt cable, this is also the right time to see whether the signal is clean. If you already know how to use a Tektronix oscilloscope, you can put it on the signal line and look for dropouts or noise. But in a rush deployment, the faster fix is usually swapping the cable and testing again. The scope is for the workshop later, not for a panic at the boat ramp.

7. Pack a spare kit like your deadline depends on it

Because it does.

A small spare kit for an EXO deployment should include:

• a spare sensor guard and wiper
• an O-ring kit and connector lubricant
• spare desiccant and fresh batteries
• a spare USB or RS-232 cable
• an extra bottle of clean water or calibration standard

People sometimes skip the spare kit to save a few hundred dollars on a rush job. Then the wiper sticks, or a cable breaks, and the whole project has to be rescheduled. A $200 spare kit is cheap compared to the cost of an extra mobilization day. I learned that one the expensive way.

A few warning signs I take seriously

If the sensor was "calibrated last week," I still verify it today. If the connector looks clean, I clean it anyway. If the software seems fine, I update it anyway.

And if a sensor is intermittent, I don't assume it's the sensor. Most intermittent faults are cables, connectors, or power. In my experience, the sensor itself is usually the last thing to fail.

This checklist is built around freshwater bloom work with EXO and total algae sensors. If you're in marine water or heavy fouling environments, add extra biofouling controls to every step. But for a typical rush freshwater deployment, this is the routine.

Take it from someone who has stood at a boat ramp at 5:45 a.m. with a sensor that will not talk to the laptop: the 90 minutes you spend on this checklist is a lot cheaper than the 90 days you'll spend explaining bad data.