Evo X Logging
Hey, it worked . I benched the stock rom , then used this XML , flashed with rwx patch and mode 23 enabled . they both work great. Thanks again. Are there anymore definitions to the ECU options?
EvoScan v2.9 valueZTXUser2 Index was outside the bounds of the array
Anyone logging a Zeitronix ZT-2 with EvoScan v2.9.0099, specifically the User 2 parameter? Wideband AFR and ZTXBoost are logging fine, but ZTXUser2 is just throwing index outside of bounds entries in the EvoScan error log.
I have the Zeitronix ZT2/ZT3 (Model 2010 w/User 2) selected under the Wideband menu. Zeitronix software logs the values as expected, so that should rule out a cable issue. Plus the OpenPort 2.0 cable coupled with ZT-2 serial on COM3 seem to be working fine for all other data items in EvoScan.
User 2 is wired up to the Zeitronix 150 PSI gauge sensor reading Oil Pressure which displays as expected on the LCD display. Data item values for GaugeMin/Max and ChartMin/Max are 0 and 255 respectively. Values have been between 40-105 PSI, well within the parameter range.
Only similar reference I could find was in this thread a while back but no mention of the fix. I've submitted a ticket to EvoScan but maybe someone here has a solution...
I have the Zeitronix ZT2/ZT3 (Model 2010 w/User 2) selected under the Wideband menu. Zeitronix software logs the values as expected, so that should rule out a cable issue. Plus the OpenPort 2.0 cable coupled with ZT-2 serial on COM3 seem to be working fine for all other data items in EvoScan.
User 2 is wired up to the Zeitronix 150 PSI gauge sensor reading Oil Pressure which displays as expected on the LCD display. Data item values for GaugeMin/Max and ChartMin/Max are 0 and 255 respectively. Values have been between 40-105 PSI, well within the parameter range.
Only similar reference I could find was in this thread a while back but no mention of the fix. I've submitted a ticket to EvoScan but maybe someone here has a solution...
Anyone logging a Zeitronix ZT-2 with EvoScan v2.9.0099, specifically the User 2 parameter? Wideband AFR and ZTXBoost are logging fine, but ZTXUser2 is just throwing index outside of bounds entries in the EvoScan error log.
I have the Zeitronix ZT2/ZT3 (Model 2010 w/User 2) selected under the Wideband menu. Zeitronix software logs the values as expected, so that should rule out a cable issue. Plus the OpenPort 2.0 cable coupled with ZT-2 serial on COM3 seem to be working fine for all other data items in EvoScan.
User 2 is wired up to the Zeitronix 150 PSI gauge sensor reading Oil Pressure which displays as expected on the LCD display. Data item values for GaugeMin/Max and ChartMin/Max are 0 and 255 respectively. Values have been between 40-105 PSI, well within the parameter range.
I have the Zeitronix ZT2/ZT3 (Model 2010 w/User 2) selected under the Wideband menu. Zeitronix software logs the values as expected, so that should rule out a cable issue. Plus the OpenPort 2.0 cable coupled with ZT-2 serial on COM3 seem to be working fine for all other data items in EvoScan.
User 2 is wired up to the Zeitronix 150 PSI gauge sensor reading Oil Pressure which displays as expected on the LCD display. Data item values for GaugeMin/Max and ChartMin/Max are 0 and 255 respectively. Values have been between 40-105 PSI, well within the parameter range.
AFR, User 2 (150psi zeitronix sensor, fuel pressure) and ZT2 boost: http://datazap.me/u/razorlab/initial...-6-7&zoom=2-90
Yes I am logging that very thing via Evoscan, a 150psi zeitronix sensor (for fuel pressure) in the User 2 input with a ZT2
AFR, User 2 (150psi zeitronix sensor, fuel pressure) and ZT2 boost: http://datazap.me/u/razorlab/initial...-6-7&zoom=2-90
AFR, User 2 (150psi zeitronix sensor, fuel pressure) and ZT2 boost: http://datazap.me/u/razorlab/initial...-6-7&zoom=2-90
Using the standard default evoscan ZTX request as it basically just gets it raw from the zeitronix unit:
Request: ZTX
Function: X
Units: Units
Thanks for the clue.
units surely have nothing to do with this, I don't even use units for anything inside evoscan, its just a display thing. might have been your com ports? and now they are working after you reset the PC?
I reinstalled the drivers for Evoscan and now can read parameters which I couldn't before but only selecting ECU: EVOX CAN MUTIII. Not sure what I need to do to fix this. I'm using an eeepc running Windows XP. Any help would be appreciated. Thanks.
Last edited by EvoOtto; Oct 29, 2015 at 08:37 AM.
UPDATE: Set the Units back to PSI and confirmed that everything works as expected when separating the OP2.0 and ZT-2 cables into two separate ports instead of shared via USB hub. There goes the plan to use a tablet w/hub.
Last edited by Sawdust; Oct 31, 2015 at 10:51 AM. Reason: Updated







