check your sequence. make sure your DPM is at 4" then your gate contact, then your lock then dcl. if your "timing" is off you will get that fault. for example if your DCL breaks before the door lock makes up or worst case, the gate, your sequencing will cause a fault.

how different is the futura to the meridia I have over a 100 futuras in our complex

very similar. they have turned into more of a hydro now. your IO's are modules with I think 10 ports (installed several 10 years ago). everything is done with a laptop/wizard like a Futura. biggest difference is the NTS/ETS vanes. you take out the number of slots to tell it which limit it is like a TAC 50/T 4 or 3 if I remember right as opposed to an actual limit. Which makes sense since CEC/Swift is owned by TKE.

So Futura would be based on a T3 and Meridia is based on the T4. Dar board vs DSP makes since

TAC 50 is more like Swift 5000, Meridia has more of a PLC look with modules kinda like the Omega 1000, kinda. Only the slotted limits (vanes) are the difference as far as that goes from a futura.

Cool I spent 65 percent of my time working on swift....I was getting 92 faults last week. The Tomahawk style door restrictor was binding up pushing the door off of DCL while GL and GLI was still active. I dunno if the 92 fault is the same for you. I been getting a lot of 9 94 lately. Driving me nuts always at the bottom term level. Relevels knocking it out. 45 landings the rope stretch is killing me.

the swifts love their sequence. good find! if I remember right 94 is nts? it is always one of those nuisance fault codes. a lot of guys hide by moving the software values way out. it will happen if you run an aggressive decel (150 or higher) on a geared job.

Swift 5000 is identical to T3 except in the ge300 drives interface. GVI (Swift) VS. DDI (T3).

From there on the Futura and TK product lines cross as far as labelling of I/O's, software, but not necesarrily on hardware.

The later versions of Swift (Futura, Meridia) have the best troubleshooting software I've ever seen. An event trapper that lets you set a fault as the event to trigger off of, and then when the event happens captures the last 45 seconds of I/O at 10 frames per second, on the I/O screen and allows you to replay I/O, 1/10th second at a time. Very cool.

And with Swift Remember..They bill themselves as Non-Proprietary. All manuals, wiring diagrams are available on their website.

http://www.swiftcec.com/

However for some reason Non-Proprieatry means proprietary in Canada with this company, unless the other company is Thyssen.

I dont have any Swift 5000, all Futura some really old futura with MGS and some brand new stuff that has the LED screen inside the controller. Being able to set up a frame capture for the Error you been trying to trouble shoot is awesome. The recorder on IMS is crap. Alot of times on the futura i have SD#s and SU#s flash shutting the car down. My 45 story still uses the Westinghouse music box so I fight this stuff all the time. Setting TSV values can be a pain due to the music box, My LPE setting is higher then I want to mention. Right now im having relevel issues at the bottom term landing car starts to yo yoing. I think I need to go over the brake cause the car went into the overhead today. Job is old enough not to have rope grippers. T3's and Futura you set your hoistway up the exact same way.

The recorder on IMS is crap

Agreed. And I don't know why they didn't take the one extra step and make it triggerable on a fault code, like Swift does.

You have to hook up the laptop and let it run for about 30 minutes, and then clear out the capture file, to keep from filling up the hard drive, and then do it again. All of this requires you to physically be there.