Month: June 2021

A few days ago, while acquiring data, I inadvertently interrupted the AC power to the old Defender, resetting the trap. Power interruptions happen all the time here, but this one somehow changed something, I don’t know what, and the normal operating temperature rise from the intake to the exhaust increased dramatically from ~85°C to ~94°C. Surprised, I tried cooling the trap to near ambient and restarting, but the thermistor temperature rose and stayed high, in the 130° range, close to the 140° limit I had set.

Puzzled, I reviewed my notes and blog entries, and discovered that this was a very typical range 2 years ago. I might have been using the wrong nozzle at that time. Since the change, during the last two days, the trap had caught only 20 mosquitos (although I didn’t see any around), compared with several hundred in the previous day (although just after a rain). The trap was running at about 128° with an ambient of ~34°, for a 94°C rise.

I then tried the electric tire pump on the Schrader valve, and it read 105 psi, which is very high. I ran the pump for several minutes, but there was no change in pressure – nothing was dislodged. Restarting the trap, the temperature rose even higher to almost 135°C. I had made it worse. It may not be a good idea to use an flaky auto tire pump to clear out a hot trap. Perhaps the contaminants from the worn-out oil-free pump have really clogged the nozzle, although the pressure went up high and stayed there. In any event, the nozzle had to be cleaned or replaced.

I found an old nozzle that had been cleaned and had a like-new 40 psi test fixture result. I was determined to change the nozzle as quickly as possible, no frills. Fortunately, I have a high torque electric screwdriver, so with that plus 2 large slot screwdrivers to open the combustion chamber, and nothing else, away I went.

Fortunately, the awful top case screws are long gone to a better place. Power off, remove the basket and top cover, unzip the 3 sheet metal screws into stripped plastic supports, unscrew somewhat the two hose clamp screws, remove the power jack, remove the solenoid from the valve, and it all lifts out. Turning the assembly on its side, remove the 3 machine screws holding the plastic exhaust port from the combustion chamber, then the last 5 screws holding the chamber together. Taking care to not break the circuit board, NodeMCU and other stuff, I used the two large slot screwdrivers to pry the case apart, and it popped open without too much effort. (I had a few times back in the past given up on applying new gasket sealer to the case, the old stuff seemed to work just fine, and nothing looked like it was leaking out, so there.) The nozzle assembly came out with some rotation, and then I replaced the nozzle. Reassembly occurred, but not before using the hose to spray the awful remains the last couple of year’s catches.

A bit of DeOxit on the power connector to try to address the intermittency, and, amazingly, the trap started without issue. The connector is still intermittent, however, but this was not the time to fix that. The mosquitos scored 2 bites, maybe real, perhaps imaginary bites. Not bad.

The trap with the cleaned nozzle went up to 127°, a 96° from 31°C rise, but has since calmed down to 124.6 – 33.1 = a 91.5°C rise. I don’t know whether this is a better operating point or not, only the catch rate can tell this, but at least a clogged nozzle has been changed. I have been measuring tank weights and catches for 3 days now, another post will provide some results.

After getting the Defender up and running then failing on Thursday, restarting, and failing again Friday morning, after repositioning the NodeMCU and restarting, by mid-day it had caught about 10 or so mosquitos, not too bad. These mosquitos convinced me it was time to start the Patriot, and perhaps get cracking on the Liberty conversion.

At the end of last season, the Patriot was suffering some failures during a run. Normally, a failing trap fails to start, but stopping in mid-tank was rare. I tested the pressure last year with the auto tire pump, and it was high. I decided to test again and clean it if necessary before deployment.

My test pump, a Viair P70 purchased in 2015, had suffered after being used to keep a ring-type above ground pool ring inflated. After two seasons, the ring had become brittle, and had several large tears, and several small leaks, which I had patched, and was able to inflate, with a slow leak. This required the shop vac to be applied every day, and after a few times when the plastic bag covering to the vacuum blew aside and let the rain in, the vacuum bearings started making a screaming noise, adding to the experience. When I was not perfectly diligent, a few times during the cool of the night, the ring deflated to the point where a cascade of about 1000 gallons of water escaped over a partial collapse on the pool’s low side. I dreaded waking to see this out the window or on the pool cam in the morning.

So I took the Defender software and adapted it to a pool ring inflater. This required a 12 volt battery, pump, trickle charger, 5 volt auto adapter, a solid state relay, and a pressure sensor, plus additional temperature and humidity sensors connected to a NodeMCU on an interconnect breadboard. The pressure sensor had to measure very low relative pressures absolutely. I made on using two paint mixing sticks and a 100 g strain gauge. The ends of the sticks were taped to the ring about 30″ apart, and the ring pushing against the strain gauge deflected it enough to measure. The previous and now backup visual measure was provided by leaning the pool skimmer handle at about 45° against the ring. If it sank less that 1/4 handle width, the ring was ok. Full scale was about 2-3 rings sunk into the ring. Water would flow soon after.

The system worked beautifully. However, as time passed, additional leaks developed, one or two every few days. Unless these were identified and repaired, the system would be pumping so much that the energy removed from the battery could not be replenished by the trickle charger in time for the next inflation, and the system would enter a downward spiral eventually ending in failure and excessive battery discharge, and the lost 1000 gallons.

The first pump, $10 from Harbor Freight, was quite small, and took several minutes to reinflate the pool ring. This wore out right away, and I had “repaired” the pump once or twice before (the pump piston seal if overheated looses its flexibility and does not seal effectively). So I use my “good” pump, the Viair P70, and it was very effective, until it too started failing, with the same issue. After a few repairs, trying various things like silicone grease to improve the seal, which was a disaster, the pump would last only a few days before not pushing any more air, or worse, leaking air from the pool ring. I tried to purchase a new piston seal, but was informed by the Viair rep that the pump was obsolete, no parts were in stock, and I would be better off buying a new pump. This was very disturbing news, as I hate planned obsolescence.

Back to the Patriot. I had ordered two pumps with analog meters and no digital on/off to replace the Viair. That in itself was a problem, since the replacement pump for the automobile has a digital set point, and requires toggling the on/off switch to activate the pump, which prevents turning the pump on by applying power (as in the inflater), and also prevents its use to measure the Mosquito Magnet valve orifice conductivity as inversely proportional to the pressure with a given pump output.

Anyway, the working-for-now Viair pump showed 102 psi, pump A, 89-86 psi, and pump B 83 psi. This was much higher than the Defender good nozzle pressures in the mid 30s, so the trap had to come apart. This was easy because the case screws were removed last year when the trap started failing. The Patriot nozzle is held in by a single Philips bolt, although three screws must be removed to raise the assemble above the case bottom to remove the nozzle.

The nozzle had no markings, and the orifice consisted of a single hole in the center of the head. This hole is about 0.010″ in diameter, or about a #87 drill bit size. I don’t have this size, but a #30 wire wrap wire fits perfectly. I could see some black material in the orifice, and holding the nozzle up to the light, it looked blocked, so I tried to use the wire wrap wire to dig it out. This caused the wire to break and lodge in the hole. A variety of stiff, sharp objects later, the blockage was gone, and the hole clean looking. Hooking it up to the pump showed pressures on 80 psi for the Viair, and 60 psi for pump A (pump B was disqualified for its clunky digital pressure gauge). This is still higher than a Defender, but the hole blew air perfectly, and I reassembled, and started the trap. The trap worked! I put in an octenol cartridge and left it running.

When checked today, both traps are running and catching mosquitos, even though we have not noticed mosquitos in the evenings. The mosquitos in the Patriot seem particularly agitated, angry even, don’t let one escape! No explanation for this other than perhaps the more spacious Patriot basket with its clear top prompts the mosquitos to fly up into the hard plastic.

So begins the 2021 mosquito season.

What a miracle. I replaced last year’s NodeMCU software with a latest and greatest tech version now released on the wiki, patched accordingly, started it up, and it is running. You can see it working (or not), using an MQTT client connected to broker.hivemq.com. Follow the MMD/esp8356707 topic, or MMD/# topic wildcard to follow any and all other units in development. Here was the one of the initial messages:

Temp=120.8C (0) at 5:465 F=1 I=0 G=1 S=1 E=0 T=34.5C H=17.6% M=26920 (243/1024:5857) R=70~140 W=-73.85 B=0.0 V=3.5

(Kindly refrain from sending commands to the Defender, thank you. We are testing the new board and software.)

I should mention that we are suffering from wireless connectivity issues caused by the proliferation of poorly designed wifi-6 and mesh routers and access points, however, the NodeMCU recovers fairly quickly, so a short duration MQTT “offline” message every now and then is to be expected until the router manufacturers update their products to not interfere with low band IOT devices.

We will see how long this lasts. It is amazing to me when things like this “just work.” As I was writing this as a reply on the forum, I was forced to type:

“… Well, I spoke too soon. While typing this post, the system went off line, and restarted.

Temp=124.8C (0) at 5:779 F=1 I=0 G=1 S=1 E=0 T=34.7C H=18.9% M=26920 (223/1024:5241) R=70~140 W=-72.85 B=0.0 V=3.5
Offline
Offline
Temp=118.6C (-0.2) at 1:3 F=1 I=0 G=0 S=1 E=0 T=34.9C H=19.6% M=27440 (255/1024:6242) R=70~140 W=-74.85 B=0.0 V=3.5…boot

The unit is going offline periodically for periods of ~22 and ~45 seconds. It is rebooting.”

That was the end of that post. I copied the text, canceled the post, and continued investigating.

The system would not stay running, repeatedly rebooting. Worried about the igniter failing because of too many cycles, I sent it the MQTT command to cool down with error. The error transitions the trap into an error state after the cool down. The idea was to see if a cool trap had issues with connectivity and rebooting. The previous hardware was able to function to 35°C without issue, and this was close to that. However, the ambient intake temperature is not the same as the temperature experienced by the NodeMCU, which is adjacent to the combustion chamber, nearly touching it.

After several hours, the intake (and combustion) temperature dropped to 17°C, quite a bit cooler, and I restarted the trap. It ran all night, but failed at 9AM, with last words:

Temp=124.8C (0) at 5:39647 F=1 I=0 G=1 S=1 E=0 T=38.7C H=21% M=26800 (223/1024:5241) R=70~140 W=-74.85 B=0.0 V=3.5

The ambient temperature of 38.7°C is pretty hot. This suggests that the NodeMCU was getting too hot for reliable operation. Downstairs, case off (Not difficult: I removed the screws several seasons ago and put them in a safe place, or did I?). The new NodeMCU was fairly deep inside the case, nearly touching the combustion chamber. I was thinking of inserting a fiberglass cloth, or some sort of heat shield, when I noticed the rather stiff wires to the “power” switch. “Maybe I could use these stiff wires to push the NodeMCU away from the combustion chamber” I thought. So I re-routed the wires to do exactly that. What a proud boy I was. Not only was the board further away from the chamber, there was no restriction to any air flow (what?) from a heat shield, not to mention being a low cost solution, although it does require “tuning” in the form of wire bending. It has been several minutes now, and it is still working:

Temp=120.8C (0) at 5:2476 F=1 I=0 G=1 S=1 E=0 T=29.1C H=36.3% M=26688 (243/1024:5857) R=70~140 W=-73.85 B=0.0 V=3.5

2476 seconds and still running! However, it does seem odd that the ambient temperature sensor is reading much lower than before. This Add-On is lacking certain mechanical sophistication. Perhaps the wire bends positioning the ambient temperature/humidity sensor may be a bit too imprecise.

Another issue is that the switched voltage divider scheme is giving a too-high value of 1024 for the open circuit state. The other hardware (boards) have had the open value of 1015 or so. The circuit (see the wiki) switches the ThermLo net between ground and open circuit. When grounded, the analog-digital converter (ADC), measures the voltage from +5C (connected to 3.3 volts from the NodeMCU regulator) into the divider with R5 (20k0) on the top, and the thermistor on the bottom into the ADC input (a ~330 kOhm divider). When ThermLo is open, it measures just R5 to the 330 kOhm input. This scheme allows the software to calculate the thermistor resistance by a ratio, and not depend on the imprecise 3.3 volt regulator as a voltage reference. However, the open circuit measurement must not exceed the full scale value of 1023 (or 1024), doing so will lose precision. Evidently the NodeMCU +3.3 is a bit too high, or the resistors into the ADC inaccurate, or both. Another issue to investigate.

Still, even without the added precision, the combustion chamber temperature probe does its job. Maybe I can forget about switching the bottom, and just rely on the kindness of the circuitry as it is and use the values as they are, and it will work sufficiently. This would free up a pin to use for something else, some other feature, for example, an additional indicator light for the Liberty, or some such.

Well, while I was writing this, the unit went off line again, last words:

Temp=121C (0) at 5:2674 F=1 I=0 G=1 S=1 E=0 T=29.5C H=39% M=26688 (242/1024:5825) R=70~140 W=-72.85 B=0.0 V=3.5

That was just after its triumphant report a few paragraphs above! Gotta go, see what happened, see you later!

… (Passage of time)

Back again. Mechanical iffy-ness includes the draping of the power cord from the house to the Defender across a walkway, with a loose coil at both ends. This is insufficient to handle a hose pulling the cord forcibly away from the Defender. Fortunately, the 2002 design used a connector that will release with excessive cord pull without too much damage. The new Patriot, with its screw-on connector, will be less forgiving. Anyway, the unit is back on the air, and happy times are here again, again, at least for right now:

Temp=120.3C (0) at 5:735 F=1 I=0 G=1 S=1 E=0 T=30.2C H=28.2% M=26856 (246/1024:5952) R=70~140 W=-74.85 B=0.0 V=3.5

Welcome back to the Mosquito Magnet blog after a long off season. The forum has started to stir, a user has prodded me into releasing the source code to the NodeMCU software as a complete package, another user introduced me to a smaller but just-as-capable NodeMCU, the WeMos D1 Mini, and in preparing a release, updating the system software, etc., I needed a test machine, so I am finally starting the Liberty Add-On project. Check the wiki and forum, and stay tuned for more details.

On the forum, a discussion started regarding CO2 cartridges, and my reply started to veer off into blog land, hence this entry.

CO2 Cartridges

I think we have established that a clean nozzle is vital to the trap’s reliable operation, and that the CO2 cartridges are woefully inadequate (although I haven’t tried using one after each tank change!) to clear a clogged system. The problem is that the trap may fail to start because of some other issue, and using 3-4 of these irritatingly sort-of expensive and short lived capsules would drive anyone batty. Plus, the original directions of backing off and letting the CO2 flow for ?several seconds? when in fact it comes out in one quick “whoosh” adds an unacceptable dimension of doubt to the whole enterprise.

I should mention a few more details about cleaning here. I use brake cleaner, and haven’t tried MAF (perhaps more effective). After removing the filter, place both into a 4 oz glass jar, cover with solvent, and place the covered jar into a small ultrasonic cleaner filled with warm water, and run for about 30-45 minutes. This seems to work.

I then test the nozzle(s). I was fortunate enough to acquire a used Mosquito Magnet valve from ebay. I block the propane line intake port, screw the nozzle into the valve, and connect a prior generation electric automobile tire pump with gauge to the Schrader valve input. With the pump on, the cleaned nozzle reads 35-45 psi vs the >60 psi from an obstructed nozzle. If the nozzle reads high, it gets another round of cleaning.

Prior to starting the trap, the tire pump connected to a trap also gives the same indication of the nozzle’s condition. I have experienced pressures up to ~110 psi this way. My criteria for cleaning is trap failure, but this policy results in failed traps at inopportune times. For example, my “newish” Patriot trap was having trouble staying lit at the end of last season, but will I clean it before trying to put it in service? Nah. “Millions for Defense, Not One Cent for Tribute ‘No, no, not a sixpence, sir!'”

Actually, thinking about it, I probably should test the trap first, it’s just that I have to repair my prior generation electric tire pump(s) that have failed from overuse first. We shall see.