Adamw

Only Aux 5-8 on the wire-in ecu’s can do highside drive

Yes this would still suggest power supply is missing as I mentioned above.

Yes, the tune, calibration or map is the configuration file for the ecu. It will have a .pclr file extension with a G4+

can you attach the .llgx files for these scopes

Was the problem occurring in this log? did it cut out at the end? Its running extremely rich, lambda drops below 0.6 is some places and is 0.65 at WOT, sure its not fouling plugs?

The analog input is being shorted to ground so you have the sensor wired wrong (or it is dead).

The main issue I see is differences in how the main relay is controlled. In the Early chassis the ECU sends 12V out to the main relay to enable it when the ign sw signal is received. In the later car the ecu grounds the main relay to enable. This is all done with hardware circuits on the adapter board. So you would really need to add a bit of extra stuff in to control the main relay.

Try increasing the exit decay rate, im normally up around 30-40%.

Try swapping the polarity of the connection between the VEMs device and the sensor. You could possibly have the vems grounding one side of the sensor and the ABS grounding the other side. The other possibilty is the ABS unit doesnt reference ground and bias' the signal up or down.

There are really no "typical settings", even basic stuff like the size of the hole through the boost source nipple or ignition timing has a big influence on the response of the turbo control system. There are some examples in the help file which I have attached below but I even see big differences in very similar cars so I wouldnt take it as gospel. I suggest following the guide in the help file here: G4+ ECU Tuning Functions > Boost Control > Closed Loop Boost Control > Closed Loop Boost Setup Guide

The old two wire sensors are not good options. They were orignally designed in 1970 by VDO for use with their consumer level gauges, gauges in those days where very low resolution and were really just an indication what was going on. The problem with them is they are very low resistance so they need a strong pull-up which consumes a lot of your available 5V output current, they are not linear, and their resistance curve varies significantly with the sensor temperature. Have a look at Honeywell MIP series, decent sensors for about 50-60USD depending where you are.

Cruise and launch status are already in the default generic dash stream. I dont know how configurable the powertune dash is to receive the others, but the basic process is described in their document here: https://cdn.shopify.com/s/files/1/0036/0615/1235/files/Custom_stream_setup_LINK.pdf?v=1620629266

Use the >online>monitor channels tool in the dash software to see if any speed is coming through. Those channels should still have been logged regardless whether the CAN was working or not.

Try the attached dash config. There was a divider of 10 on the DI speed channels in the dash config which would have made the speed read 10X lower in the dash but still should have shown something, so I have removed that. I dont see much else wrong. I also renamed the channels to "LF Wheel Spd" etc to make it clearer. ABBEY350Z07_03_2022_V2.U26

Can you do me a few more trigger scopes of cranking. I suspect there may be a small spike of electrical noise coming through intermittently which upsets the edge count. Does it have stock ignition system? Resistor spark plugs and leads?

Ok, can you attach the triggerscope file .llgx. and your tune, .pclx

Yeah it should be. The only problem is the Nissan reluctor speed sensors output quite low voltage at low speeds so may not be enough to register until about 20kmh. Connect the sensor between gnd and any DI and give it a try.

Are you using the latest firmware in the ECU 6.21.14? This sounds like you may have the problem that has already been fixed:

Attach a copy of your tune

Did you try defaulting the USB adapter? Instructions here: https://github.com/SeeedDocument/USB-CAN-Analyzer/raw/master/res/Document/11.Restore the default configuration description.pdf Can you also link to the video you mentioned as the link you gave only goes to a picture. Perhaps attach your tune also.

The 4 wheel speeds are already broadcast in our standard Generic dash stream. But from memory with the SDL since it was sold as a low cost dash, motec placed many restrictions on its CAN capabilities, (many of which are not documented anywhere), Im struggling to remember all of them but im pretty sure there is a restriction that it can only receive the first 7 or 8 frames of a compound message. Can you check if Oil temp and Oil press is coming through. We can possibly get around this by doing a custom stream at both ends that fits into 8 frames, or we could possibly break generic dash in half and send it as two 7 frame messages on two different ID's rather than its normal 14 frames on a single ID.

Generic dash is what is referred to as a compound message - or sometimes called a multiplexed or row counter. So with this technique you send multiple frames all with the same ID, typically we use ID 1000 or 0x3E8. One of the bytes in each frame is used as a further ID so that the receiving device knows what data is in each frame. This further identifier is called the Compound ID/Frame ID/Multiplexor or row counter. Example from Generic dash below, Byte 0 is the frame ID. So if the receiving device receives a frame with a value of 2 in byte 0, then it knows this frame has Inj DC, Inj PW & ECT in the 6 data bytes. Generic Dash 2 is what is referred to as a sequential message. With this technique even though you still only set one ID in the software, the ECU will send out only one frame on that base ID, then each further frame is sent with an ID that increments by 1. In generic Dash 2 there are 4 frames of data, so the first frame gets sent on ID 1000, the second frame on 1001, 3rd on ID 1002 etc.

The G4 does have internal logging.

Unfortunately not. The firmware engineer that does the trigger code has just gone on holiday for a month and he has many other high priority tasks to get through upon his return. I will put it on the list of feature requests but unfortunately it wont be in the near future. You best option will be to fit a more conventional trigger disc on the front pulley and use that with the existing cam sensor.

Correct, it uses decimal. We have added a small note above the ID field to make that clearer in the next release. 0x700 would be 1792 and 0x702 would be 1794.