@Symtech It may suck, but if they are absolutely set on doing it, you will likely have to do it that way.. You can’t add isolation valves on the switch.

17 bar also seems high if your using a 134A or equivalent.

What refrigerant are you using?

@Symtech Pity they don’t have schrader valves on them. But you might have no choice bot the remove the gas and switches to test.

@chillmac Tell me about it, but them’s the rules… there can be NO device capable of blocking the flow between the source of compression and the safety device.

@the-chiller-guys I have convinced the insurance rep to accept me reducing the Cut out threshold for the purposes of testing, they will accept the software safety switch as a valid device so that issue is sorted….
Next on my list is Why are the HP switches ( both software and mechanical) set to 17 bar? Need to speak to OEM, and then the biggie, Why wont the Turbocors push Past 10 bar without tripping on bearing displacement they should be easily capable of alot more than that.

Going to be fun few weeks, still I’d rather be busy than bored

Paul.

@Symtech thats a good start i suppose.

Tech support at danfoss down in Florida is awesome, I would reach out to them directly, but have a Yenta recording ready for them.

Curious whats going on myself.

Can you upload a yenta recording during that condition and a logsheet, so I can pull it up and take a look?

@the-chiller-guys R134a, from the serial numbers the Turbocors are 2012 DoM and I cant see anything in what passes for the chiller logbook to indicate they have had anything replaced other than the DC Caps in 2022. When I put my test harness on It looks like the original Inverter cooling fan is still there so, its a good bet there’s a lot more going on with the PWM and bearings. Ill have to do a validation report on all the sensors and resistances… I only went there to do an inspection and HP switch validation for another company who is taking over the maintenance contract 😂

@the-chiller-guys Sure, I’ll upload it over the weekend, My Laptop is currently Logging A VRV Parameters Overnight for a colleague.

@Symtech that makes sense, usually how it goes.

run it into the ground, then blame the manufacturer lol

sounds good man, ill keep an eye out

@Symtech Just a FYI, I was working on a Chiller today and the HP switch is defo on a schrader valve. R410A. Alco controls HP switch with manual reset.
I have a spare in the van, so can send you a photo if you like. I am not familiar with your Chiller though, so maybe it’s differrent.

@the-chiller-guys Sorry, been up to my neck in Work, Just attached the Yenta file for one of the Turbocors that I tried to do an HP test on…. I had it running for an hour before the test so the time for the attempt is about 11:30 on the file. Let me know what you think

While were still on the subject of HP switch Validations, I managed to persuade the Insurance company that Pushing the machines to their failure point is not a wise move for the lifespan of the chiller and could result in damage and or Refrigerant Loss. They Partially agreed and said that I could LOWER the Fault threshold on Software switches for the purposes of testing but the mechanicals need to stay factory set and will have to be tested every 5 years… Progress!

This was going smoothly on Machines where I have access to the MANF passwords or with Turbocors I can use the TCSMT to alter the Alarm setting, which brings me to my latest issue. I have a chiller with turbocors that will NOT let me alter the High discharge Alarm setting but will let me change everything else… when I change it in confuguration1 tab it returns to its original setting. (Yes I am on OEM Access)

Any clues?

@Symtech I will take a look at the Yenta.

Per your last issue with the values not storing. Who is the OEM of the chiller?

I have never had this issue personally, but I do remember Danfoss mentioning that some OEM’s can write to the compressor. From what it sounded like if they have it set for a specific value, as soon as it establishes modbus communication, it will write back to that value.

I would try disconnecting the Modbus from the IO bard, and the interlock, see if the value stores, then try plugging it back in to see what happens when it regains communication.

I can take a peek in the book, or make some calls as well if needed, just give that a shot first, and let me know.

@Symtech Too me it looks like you are running with too little refrigerant in the evaporator. Could be charge, EEV, or something electronic holding it up. Im assuming the chiller controller is controlling the EEV correct? And this is a flooded Evap?

Long Story short, it seems to be beginning to surge just before it trips out.

If you look at the actual speed vs surge speed, it is just below it.
Suction Superheat is high, discharge SH is also high
Its running a high Front Radial Orbit Displacement, meaning its struggling to keep the impeller side of the shaft centered.

do you have a running logsheet? It doesnt have to be when its tripped out, normal operation is fine, just seems like some problem on the refrigerant side starving the Evap.

Let us know

@chillmac it does make it nice for a service guy, even if it’s frowned upon.