db all rsr and 13 vw cc

Hello, I have installed the DB-ALL in my 2013 CC in RSR mode. I have it flashed with the latest 3.36 firmware and have it set in RFTD/3x lock start mode. All wiring is correct, immobilizer is bypassed with a good RF loop. I hit the factory fob lock 3x, the car starts and then the engine immediately cuts out. I get 5x blinks of the hazards, which is 'Brake shutoff' according to the DB-ALL firmware manual. The DB-ALL blinks red twice which is "Brake not detected on CAN" according to the DB-ALL firmware manual. I am obviously not pressing the brake, so it seems like the DB-ALL is picking up a false positive brake signal on the CAN network. If I try to start it and hit the brake pedal before it trys to start, it cancels the start procedure as it should and gives me the same 5x hazard blink, 2x red LED blink on the DBALL. If I stick the fob into ACC mode and try to start from the keyfob, it starts and stays on, but will not turn off when I hit the brake pedal. Not really sure what it could be. My RF loop seems to work since I get an immobilizer error on the dash if I remove the keyfob from the loop antenna, so that seems to be fine. I've checked all connections.. any ideas?

Just to update for the sanity of anyone planning to install a DB-ALL in a 13 VW CC using RSR or D2D; I found that the as of firmware 3.36, there is indeed a false positive brake signal being generated/picked up by the DB-ALL. I ended up hooking up my Viper 5101 using D2D and using the XKLOADER2 to disable the 'ST-Brake' output. YES, this does in fact make it so that brake pedal shutdown does not work. Until they release an updated firmware, the brake pedal shutdown will not work. I am contemplating going the manual route and hooking a brake pedal sense output directly to the brake signal input on the Viper 5101. I would have like to have just used my factory keyfob 3x with RSR and not had an extra fob on my ring, but it's better than no starter. Now if only Viper would let consumers activate smartstart themselves...

Just to update, again; I worked with Directed in getting this resolved. Firmware 3.37 fixes this issue completely and is in alpha stage right now. Should be out soon for the rest.