Nistune Forums

if you modify the patch code consult table entry to this then you can see it working on the display this is what I had ADR $008C ; IGN TIMING look for the signature FF FF FF FF FF FF 00 11 FF FF FF FF 00 8C and modify the last value i'll try it out when i get time. im just trying to make the log rec...

i might have a user selection for TP (ms) and BAR for display

BAR is pulled straight from rom editor. depends on engine cc/injector cc/cylinders variables in address files.make sure these are correct

standard consult (rs232 9600bps) can be cut back with less sensors to run full streaming mode, until there is an update made. this can run a higher resolution usb consult should also be able to do the same. it doesn't need to run anything cut back since usb works in packets and timesharing. all data...

logging has changed now when consult connected - it will be in 'record mode' otherwise in 'playback mode' the browse button will save a file in record mode or open a file in playback mode the last opened file will be available when opening log player subsequent times i may provide a timestamped defa...

battery voltage - no probs with my ecu. unless Z31 specific problem? have a look at my logs and they seem stable. i just read this as a ram value. if its the wrong value, then that would be the only thing causing the problem. i can't really 'fix' this problem unless totally wrong voltage due to wron...

this is a threading issue. more threads slow the system down. i can have a look into it but in future once NVRAM is used, wont need the romulator anyway

i think the romulator thread is probably chewing up more time than it should. i'll post here when i get to look into it

see included files. you must load R31 ADR and R31_NT BIN files to see these properly. logging has been improved heaps now

yes it finally works!

Test to see if Matt's login can respond to posts. Seems to work. Hmm.