QE1984

Ok, copy that. Thanks.

@Adamw, I'm the mechanic that was working on the car with defjux. The turbo speed works fine on DI15 with DI- grounded through the capacitor. I have no problem leaving it this way if it's working, I just want to make sure it isn't an indication of something wrong with the wiring in general, whether that be poor grounds, power supply issue etc (all have been checked to the best of my ability). To reiterate, the same wire going into DI15+ was working fine on one of the lower speed DIs, but would overrun the frequency limit around 57k turbo speed. The rpm reading at idle is the same on the high speed input as it was with the low, so for now it seems to be functioning.

That's what I figured. Thanks.

I have a battery current sensor that outputs a duty cycle (PWM) @125 hz. I'm not sure if that's the most accurate way to describe it, but it measures from -80A to +80A. At -80A it's at 10%DC and at +80A it's at 90%DC. Is there an input that can handle this, or do I need to install some sort of DAC or filter on the output of the sensor? The sensor is similar, or maybe identical, to this one: https://www.lem.com/sites/default/files/products_datasheets/hab 80-s.pdf

I see. But if the table is set to zero, after doing a proper cam angle test, the cam should not advance at all once the test is done, correct?

If the VVT tables were at zero, should there be any change at all?

Great. Thanks Adam

Yes we cut one off to work with our previous ecu setup. If getting a new kiggly wheel and multitooth cam wheel would provide better results then we could go that way, but if there is no benefit, then it sounds like we're good to go.

Fair enough. It is a 12 minus 1 crank and the large section of the stock cam pickup is still present, which is maybe 100 cam degrees, or 200 crank degrees. Would there be any benefit to cutting it down or just leave it as it is?

Evo IX head with stock cam sensors, one tooth on trigger 2 on the exhaust cam. 12-1 Kiggly crank sensor on trigger 1. The car works and starts on "cam pulse 1x" but from what I've read, it should be able to run on "cam level". Triggerscope looks good, no sync errors, but I'm just curious why it doesn't work on cam level, and if that's an indication of another setup issue. When using cam level, I get sync errors and notice I'm only firing on opposing cylinders, like 1/3 or 2/4, depending on trigger offset. Again, if it's working, I'm not too worried, it just seems strange that cam level doesn't work. Thanks

I have it set up exactly like Adam shows in the video and CAN monitor looks similar.

I got my dash working on a windows pc, with a seeedstudio CAN analyzer, transmitting DASH2PRO. This is on the G4+. I assume my next step, if I want to transmit some of my Analog volt inputs, is to transmit a user stream including those inputs, and modify the xml file to accommodate. Is that right or am I missing something?

Thank you Adamw. Having the devices be the same bit rate won't be a problem I'll reach back out when we need a hand. Thanks.

We have a new Thunder ECU, AiM PDM32, Blink Marine CAN keypad and a 3rd party CAN device. Wiring everything together now, and have the BM keypad occupying the AiM CAN2, the Thunder CAN1 is connected to AiM CAN1 (ECU stream). What we want to do is send data channels from a 3rd party CAN device to the PDM. From what I understand, the Blink Marine Keypad takes over the entire CAN2 on the PDM, at least when using their plug and play software interface on RS3. And CAN0 is only for AiM branded units. So the question is, are we able to receive channels on the Thunder CAN2 and transmit those channels on the Thunder CAN1? Or can we add additional CAN devices to CAN1? Please help me understand what my options are before I make any final decisions. Thanks