Adamw

The default limiter setup uses a control range of 200rpm, this means if the limiter is set to 8000, the ecu will start applying a limit at 7800.

Your setup is correct at the ecu end but you have a couple of mistakes in the dash set up. You have the ecu CAN receive set up on port 1 but it should be port 2. Also you have baud rate set to 500k, it should be 1M. You will need to manually delete the CAN receive channels off CAN 1 then do the import again on CAN 2.

This just depends on the resolution and range of values you need to cover. 8 bit gives you 0-255, 16bit gives you 0-65535. It'''s not so much about choking the bus but more about fitting all the data you want to send into the minimum amount of frames. Our software only let's you set up 6 different message ID's, you can only fit 4 x 16 bit channels into a frame so that means you could only send 24 channels of data. There are ways to send multiple frames with a single ID but I don't see the point of sending more data with most of it being zeros. All data is sent in native metric units so oil pressure is Kpa. cold start you might see 600kpa so that's why we need 16 bits for oil press. for damper position, I would expect 1mm resolution would be fine and assuming we are not talking about a stadium truck then probably 255mm will be enough range, so 8bits is all we need. I don't know how stack use the min max value. in some systems its just used to reject invalid data, in others me may also be used to scale the min/max value on the tachometer gauge for example. If you are talking about the 0x3E8, that is the message ID in Hexidecimal. Stack use Hex, Link uses Decimal. 0x3E8 = 1000 decimal. yep, good. Make sure you are logging in with your username, not your email address.

yes, this will receive wheel speeds via CAN. The termination resistor can only be removed (unsoldered) but try it as it is at present, I have had systems work fine with 3 resistors connected before. also attached an updated map that has a bit more CAN bus dash functionality set up. RX8 CAN example.pclr

you can also wire the coils in wasted spark to get 2 extra aux outputs if needed.

this is all you would need to send lambda from a fury internal wideband to the aemnet gauge. this would be channel o2-1 on the gauge.

here is an example including rpm, press, temp, speed and a low res analog channel.

What was the IAT in that region (5500 & 240kpa) in winter compared to summer?

If the loom is in good condition you can cut the plugs off and crimp on the new G4+ plugs(s). For a basic 4 cyl turbo I would typically go for the Monsoon, you may find the Atom just a little restictive in terms of number of inputs and outputs. As for the tune it is not really convertible, but you could manually copy over some aspects such as ignition table as a closer starting point.

Oh sorry, I must have been skim reading your post. yes we can duplicate the AEMnet stream to make this gauge work. You don’t need to duplicate all messages/ID’s, just the ones that contain the data you want to display. I will give you an example next time I have access to a PC (overseas on holiday at present).

Then you must have the pinout wrong, that should be all that is needed. You should be able to find a service manual online for this car no worries.

Did you have the pull-up turned on?

I don’t have a pinout handy, but it should be 1 pin to 12v, 1 to ground, 1 to the DI.

Some of the ViPec ecu’s had basic CAN receive but the G4 didn’t. Neither could receive Lambda as a CAN input.

That is the maximum map that the ecu has recorded since the statistics were last cleared. So your problem is unlikely boost cut. Given the maximum rpm shows 13000, I suspect you have a trigger error.

If the only change is injector size then you just need to adjust the master fuel setting.

There is absolutely no way the ecu can get a valid temp reading if there is no ect input assigned. So you’re either mixed up looking at something else or you have two temp inputs assigned as ect, so when you turn one off the other one starts working.

The AEM gauge doesn’t have any CAN receive capability, it transmits data only.

you can def activate more than 1 aux in test mode. but the way you have it set up now, your aux 1 is sending out a ground when on, aux 7 is sending out 12v.

their documentation says vipec is supported with a pre-configured template in their software. so set the dash protocol to vipec and set the speed to 1Mbit. set the ecu to transmit generic dash, baud 1Mbit and id 1000. if that doesn't work then attach your dash and ecu configs and I'll take a look.

I don't see any problem with the set up. Why is Aux 7 set to high polarity tho? if it works like that it would suggest there is a problem with the wiring. polarity = high means it works inverted to normal, so the aux output is off to command the fuel pump to turn on?

the purpose of a base map is to allow the engine to be started, it sounds like your existing map already does that. I'm pretty sure there is a ST185/205 base map included in the G3 pclink basemaps folder.

you can calibrate the tacho using the multiplier setting in the tacho settings menu.

I'm overseas on holiday so have only had a brief look, but the first thing I see is the MAP is reading wrong. As per the manual you need to make sure all inputs are set up, calibrated and reading correctly before starting . It should read near 100kpa with the engine off, yours is reading 25kpa.

as per the posts above, the set up info is in the help file: