Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Dr.Fiero]

 

Had everything going OK.  3 wireless cams, piped into my VA12A.
"Updated/backdated" from AHP 3.271 to 3.228 as seems to be the in thing to do.

Now, I switch to ANY of the cameras, and I get what looks like someone cranking the brightness to MAX until it goes white out, then it snaps to about 90% bright, all the way to max again.  This repeats endlessly.  About 1-2 seconds from partial image to whiteout.

Moved the VA12A to another port.  Same problem.
Reinstalled driver (2.87.0.33).  Same problem.

Ideas?!

[J.B.]

Unfortunately, the VA12A only works on AHP versions newer than 3.228

[Dan Lawrence]

Which are both BUGGY.   In fact, there is a strong theory that 3.271 is just 3.236 with support for the VA12A added.  Buggy software with support for a single item added is still buggy software.

[J.B.]

3.236 I believe was the first version to support the VA12A. It and 3.271 and indeed both buggy as I am having macro issues when using conditions in 3.271.
Version 3.271 I thought added better support for the cm19a kit they are selling now.

[Dan Lawrence]

3.271 also causes timers not to function properly.  Neither 3.236 or 3.371 were "bench tested" before release.  X10USA still suffers from a dearth of Software programmers.

[Dr.Fiero]

Awwwwww nuts! 

Well, I'd rather suffer with a few defects of timers in 3.271 AND have my cameras all working!
Guess I'll have to up/down grade it again.

Thanks for the tips guys.