doing a car call card reader install on a 411 job, I have done a couple on 311 and gen2 cars, and have never had any trouble, however this job is giving some strange symptoms. basically a simple job, i enable card reader option under security parameters, i set i/o 326 which is ccrccc input, to address 08-1, which is a unused input on an existing serial io board. looks like the board was originally installed with the installation, and was to be used to lock out the individual floors, 12 floors. none of the inputs have been wired, as they must have opted out of doing this, i only want 2 floors to be unsecured, and the other 10 are locked out if ccrccc input is hi.
i set the 2 unsecured floors lock out inputs to 010. and the other floor lock outs are set to various addresses on the unused board, 08-2, 08-3 etc no wires to the inputs though. the building is going cheap on this, and only wants one card swipe to unlock all of the floors. I'm using the relay contact supplied by security system to correspond to ccrccc input 326. if input is hi, floors locked, if low unlocked.
the problem is as soon as i set ccrccc to the address 8-1, the car lights will light up, but the car will not go to the floor, if i turn it on inspection, the car call light that i pressed remain on. the strange thing is if i go back and set ccrccc 326 to 010 which turns on the input with software, everything works great, the floors are locked out, they will light momentarily if you push it and go back out as they are supposed to. i thought maybe a problem with the existing input board, so i added a rs5 board to the car link and addressed it as 29-1 and the same strange problem happens, locked floor car lights come on, the car will not go to floor, but the lights never turn off, the car also acts funny, it will some times run to the floor when it should not, and not cancel call. any way i found that if i go back and do a pf ram reset, then every thing works as intended. i experimented with it trying to figure it out, so i switched ccrccc back to 08-1 on original input board, and same strange problem, but if i do a pf ram reset, everything works great, any ideas as to what I'm doing wrong, never had this happen on the other 2 jobs i have done