508d does not trigger alarm

I just started messing around with the 508D and it seems I have something wrong, most likely with the programming.   The unit is hooked directly to the MUX port and it seems to be functioning visually showing green or red when triggered. I have a bitwritter and I have zone 4 set as proxy sensor so when I do trigger the sensor my remotes DOES show that this zone "Proxy Sensor" has been triggered. The problem is neither warn away or full trigger seem to actually set my alarm off. The siren (Which works) never chips for warn away, or goes off during full trigger & my lights never flash at all, nothing! The only setting I see in the bitwritter is to have zone 4 as single or double, but regardless of this setting I cant get it to trigger under either. Any thoughts on what the problem could be? The brain obviously is receiving a signal from the 508D if it sends the remote the notification I haven't messed with it too much just noticed it tonight, any thoughts?

if when you arm, you by chance have an extra chirp, maybe another sensor if causing the multiplex wire to to be ignored.

so if the chirps are correct when arming, my suggestion will be incorrect.

yuk

quiet rural missouri, near KC.

If your system moves you physically and not emotionally, you have wasted your money.

No door chirping but it does if I leave a door open and arm.   I'm not sure I would say the sensor is being bypassed as I get confirmation that it has been triggered on my remote. Unless it does send the status or disabled sensors?

Let's find out whether the fault is on the alarm or the 508d. run a loop from the blue on the 508d to the green door trigger wire of the alarm, then arm the alarm and test. If that triggers the alarm then we know that the mux input on the alarm is faulty rather than the 508d.

Thanks Howie for the suggestion. I will try this , but I do know for certain that grounding the green wire on the viper with the alarm armed will trigger the alarm & the siren. So I supposed it must be something to do with the mux port. Have you ever run into issues with the MUX ports not working?

Alright guys I figured it out just wanted to share the info. I had Menu 1 item #12 (sensor full trigger) set to double instead of single. I guess I misunderstood this setting I thought having it set to double was enabling "dual stage" instead of going strait to full trigger.   But Anyways its working now! I'm still surprised there is no warn away with this setting on .