wirelesspasob.blogg.se

Spyder 3 pro error message on wake up
Spyder 3 pro error message on wake up









spyder 3 pro error message on wake up

50 (hardware and CAN signals) is output for approx. If an engine start request has been generated, term. If the start/stop button is pressed while the ignition is on, J393 decides on the basis of a bus signal from J623 whether an engine start request has been generated or not. 15 is turned on, J623 decides whether the conditions for engine starting have been met (based on brake / clutch / driving position) and switches the term. 50 signal (discrete line and CAN signal) for approx.200ms in order to the fill the start request memory in the ECU → When term.

spyder 3 pro error message on wake up

Irrespective of the engine starting conditions, J393 generates the term. 15 (allowing short time delay between term.

spyder 3 pro error message on wake up

Release message from J393 to electrical steering column lock J764 → J764 released.ĥ. The key test is performed by J393 (correct key in interior /immobiliser) → steps 4, 5 and 6 are performed in parallel with key test.Ĥ. The signal of the pressed button E408 is transmitted to the central control unit for convenience system J393 via discrete lines.ģ. Pressing the start / stop button E408 when term. I would obviously like to just send the appropriate CAN messages to get this working on the bench without J393 CP activated.įor those interested, the Terminal Management characteristics on the Q7 4M are:ġ. Speaking with someone else, they have successfully got this same bench setup working with the Audi MIB2 stuff connected to a VW MQB CAN Gateway (5Q0907530M) which is also connected to the J393 from the same car (5Q0937086Q). With the MIB2 high, you need a CAN connected screen and controller or the MIB2 will definitely reboot. I am wondering whether I am missing some other CAN messages or whether. With the J393 disconnected, and can get the screen to wake-up but then it goes off again using CAN messages I have captured from my car. Hence, you need the key from the car and the antennas setup etc. (2) All Q7s have Kessy (here in Oz anyway). In a real car, you won't be able to start it. When CP is activated on this module it pretty much immobilisers the car - no T15 message. (1) Unless you get the CAN gateway from the car that the J393 was taken from, you get Component Protection activated. I too have struggled with the "virtual" T15 signal and the issue with this setup is you either need to have a CAN sniffer that can generate (TX) CAN messages (which I have) or have an appropriate J393 (BCM2) to generate the T15 message to wake-up the MIB2 which then wakes up the screen. I have been tinkering with an Audi Q7 4M MIB2 (Nvidia - not newer qualcomm) bench setup. Voltages on convenience CAN-H = (2.53V) and CAN-L = (2.46V) with everything disconnected (except gateway itself). 4.75V changing) with parking ECU connected (don't have a scope for now, but analogue multimeter shows it). Tried with parkings checked in installation list and unchecked. Parking aid ECU is ok, was tested in real A6 C5 car. I can connect gateway with VCDS, but parkings doesn't want to open a connection to K2. But because of instrument cluster is so bulky I'd like to wake up parking aid ECU with some real gateway which is many times smaller in size. A6 C5 facelift instrument cluster acts as "gateway" just like on newer cars. It has K2 line for diagnostics and Convenience CAN as shown in Elsa diagrams. Obviously it has Convenience and Diagnostic CAN buses. Need some help with CAN signal pairing between different generations.











Spyder 3 pro error message on wake up