Getting a 1529 and 2755 fault on a TAC 32H. The 1529 is a Drive comm loss and the 2755 doesn’t come up for me. Don’t know why getting a 1529 on a hydro.
I need a newer generic version to load in this TAC32. It currently has V4r2d and I don’t have anything more current than that. If someone has a newer version than this I would like to get a copy. Thanks
Check your can channels on DCV, shield to one wire and then shield to the other wire. Should be 2.5v on either channel. Really those faults show up if you have power issues somewhere, typically building power issues. You just need to do a TFR and should be good to go. If it continues try adjusting your power supplies to around 24.70vdc (both controller and COP). I look to set them up at 25. You can also check for loose connections and loose grounds wires. Software won't fix those faults tbh, it is more for adding additional features to adjustments and other not so critical bugs. But if you do want the newest generic pm me your email and I'll send it to you. You will need to change additional adjustments if you do update generic.
Edit* Also check your MUS on soft starter (N/O contact) that can be a potential issue
The 1529 is NOT a Siemens starter fault. It’s a fault for a traction car that says it lost CAN comm with the drive. The starter is not a drive and does not communicate with the controller. The fault happens on power up when the software looks for a drive before it checks to see that it’s a hydro and was fixed in V6R2H. The 2755 wasn’t directly addressed in any software update that I know of and can be caused by bad grounding and problems with the AC line but I noticed them a lot along with the 1529 faults and see them much less frequently after that update. Neither of these faults have anything to do with the 24v supply or the up to speed contact on the starter. To say that software updates aren’t for fixing bugs might be the strangest thing I’ve ever heard on here. I have 37 versions of CPUA software and I know I don’t have every version that was released. Almost all came with bug fixes and the ones that were just feature updates likely caused some bug that had to be fixed later. Don’t install V6R12A if you have FL_ floor lockouts because the software treated them like phantom parking calls when they were high. V6R4C was pretty solid for a 32H and I’ll never go past that again for TAC50-04s since the last 32 bit upgrade I did with V7R6C kept taking the risers down (34 stop triplex) and shutting one of them down for a sheave runout sensor that it doesn’t have. The CPUAs had to be fully recovered to go backwards but rolling back to V6R4C fixed everything. Just last week I installed the very latest V7R8B on 2 EVOs and it broke the CAN PIs on the hall riser. I could go on but I won’t.
Indirtwetrust, I guess I should have clarified on the software "fixing" issues. It "fixes", but seems to do so by just adding new adjustments to compensate for the issues of the previous software. That has just been my experience. To clarify, if it has been running fine for some time then randomly starts messing up, throwing a software at it doesn't seem to be the logical go to. However, I'm still learning with TAC controllers, so I could easily be wrong
That comes from guys putting things like checked starter connections on their tickets after a MAX call was generated that included a 1529. The system that creates those is new and doesn’t always give correct information. 1529 : The controller has not received CAN data from the drive for 0.4 seconds. A 32H has no CAN comm with the Siemens starter.
🤢 ugh you had to bring up MAX.... not a fan. To follow up, I spoke with the TN regional adjuster and was told the V7R8 and above is garbage - He told me the best generic for these hydro controls were V6R12- I've been having some issues with an endura and after slapping this generic on its been running non stop 🤞
Like I said earlier, don’t use V6R12 if you have FL_ floor lockouts or the car will be chasing phantom calls. I had to roll back to V6R10 on a ton of cars when V6R12 was still the latest. There isn’t an above V7R8 right now but the problem with all the V7 software is that it’s being updated for EVO features and code requirements and new bugs caused by those updates and isn’t tested thoroughly enough on other equipment.
