You are not logged in.

Dear visitor, welcome to SPRINKLER TALK FORUM - You Got Questions, We've Got Answers. If this is your first visit here, please read the Help. It explains how this page works. You must be registered before you can use all the page's features. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.

PerryNZ

Senior Member

Posts: 22

Location: New Zealand

1

Wednesday, March 12th 2014, 10:57pm

Irritrol Total Control PMV Query

A year or two back, when I installed the irrigation system here,
juggling aspects of a 'grew-like-topsy' irrigation reticulation
arrangement meant that may aspects were a compromise.

One consequence of that was to put one zone/station on the
PMV terminal of the controller. That station/zone has 5 rotors,
atop a row of fence posts, using a very low water volume.

Now I'm doing a few refinements and there's something I can't
fathom out from the Irritrol manual, when compared with what
I see actually happening.

I'm running 3 of the four programs, being B, C and D. I have the
PMV setting to OFF for B and ON for C & D. Despite that, the fence
top rotors operate when I run Program B, in Manual mode. The
manual says that if the PMV is set to OFF for automatic watering,
then it will also be OFF for manual watering.

I'm reluctant to get up @ 2.30am to see if the fence top rotors are
running at the time an automatic watering is happening, so I don't
know what's happening at that time.

I speculate that I'm missing something. Probably something obvious.
Or - if not - I may need to erase that program and re-enter it, in case
the micro-controller in the box has got its brains scrambled.

I'm open to suggestions about where else to look, if anyone has the
requisite experience with such things.

Wet_Boots

Supreme Member

Posts: 4,102

Location: Metro NYC

2

Thursday, March 13th 2014, 12:02pm

How about you just fix the system so that it can operate with normal programming?

PerryNZ

Senior Member

Posts: 22

Location: New Zealand

3

Thursday, March 13th 2014, 3:17pm

If money was no object, that would be a great idea.

Despite all the inception woes, it is working quite well.
The controller puzzle arose as a result of some tweaking
of the zone runs times, rather than another patch on an
already chequered set up.

I need to take lots of care with tweaking, as there's now
a robot lawn mower on the job, 17 hours-a-day. I don't
think the pop-ups would like being nudged by the mower.

Central Irrigation

Supreme Member

Posts: 364

Location: Central Minnesota

4

Thursday, March 13th 2014, 4:26pm

You can set a "false start time" for program B to check its automatic operation. Change B start time to come on 2 minutes later than the actual time displayed. Switch to RUN and wait for the system to come on. Remember to change start time back after the test. May also have to change the watering day also, if the day you attempt the test is not a day the system will water.

Have you tried turning PMV off for Program C and D to see if it might be solely related to program B?

PerryNZ

Senior Member

Posts: 22

Location: New Zealand

5

Thursday, March 13th 2014, 4:51pm

I had planned to try a manual "Program Cycle" [page 16] (of program B)
to see what happens.

I will also turn off the PMV on Programs C & D, and run them manually,
to see the effect.

Somewhere in my enfeebled memory, I have the idea that I found a tweak
that over-rode the PMV setting in the Station Times programming. I'll have
a deliberate and careful re-read of the manual to see if that prompts any
relevant recall.

PerryNZ

Senior Member

Posts: 22

Location: New Zealand

6

Friday, March 14th 2014, 12:16am

Resolved?

Rather than fiddle around, I decided to erase Program B and then re-install it.
I then tried the Program Cycle run, and the fence top rotors were off. When
the cycle had finished, I tried a Single Station watering that was the problem
when I tried yesterday. Again the fence top rotors were off. So it does look like
a software-type issue was implicated. [Ctrl] + [Alt] + [Delete] was the way!

Obviously, the feeble memory recall was even more feeble than I thought. :S

Rate this thread