I'm going to look at a tac 32 in the morning shutting down with a 1529 fault, drive communication loss. It just came off free service and we've had it for just a few months. It's the hydro with pumping unit in pit and controller behind 2nd floor door frame. No experience with these newer types, but I'm sure it has the electronic butcher valves. Does my 1529 fault come from no communication between the cpu and the board that controls the valve?

I don’t think that’s related to it being an Endurance MTL. I’ve seen this fault several times with newer versions of software and we don’t have those in California. But I don’t think I have ever seen that shut the car down.

It’s a glitch that registers a fault on power up, but no actual issues with elevator. You mentioned its newer. I think it only happens on V5 generic software, and was fixed on newest V6 release. Disregard this when it occurs during power up. Now if 1529 happens at some other point rather than restoring main line power then there may be a different issue.

From V6R2H release notes - Prevent logging 1529 "drive comm loss" faults on TAC32H.

Keep in mind TKE runs the same software in all CPUA processors. So that includes Tac 50/04 32 bit, Tac 32H (includes HMRL), and Tac 32T. So its possible it may be in reference to a traction drive, also I’ve heard speculation that future HMRLs may control hydro pump motor with a drive rather than soft start. Point is you have to realize how much is packaged in current release software.

I was sure I had seen that fault before after power ups on tac32's and yall are right it's insignficant. The rubber bumper on the car door's strike jam was sticky, it stuck to the car door and got pulled out of the hole so when the door tried to close it wouldn't hit dcl. I love when I'm expecting something crazy and it turns out simple.

I meant Endura MRL, not Endurance MLT.
V6? I’m still on V5R0P. Is that on the Lobby?

Yes IDWT but it has a reported glitch already. Something about O60 not being able to be adjusted???? I'm sticking with P for the time being. I also saw V6 on big tin can, with the warning explained of the potential glitch.

As for the 1529 fault, what I heard was it was a boot up process line item, on initial fire up, CPUA looked for the drive. On a hydro, it couldn't find a drive, before it realized it didn't need a drive, lol. Latest version moved it a bit farther down, or gave the CPUA a hot minute to figure out it was a hydro before freaking out that the drive wasn't communicating.