Nistune Forums

its strange that it can't write out to the usb chip.... is this happening whilst the engine is not running? the 1 degree CAS signal spinning triggers interrupts on the HD6802 IRQ line from the HD46510 it is highly preferred that the engine is running so there are interrupts to the ECU code for the p...

im working on R32 consult and the boards tonight. i'm making the R32 design similar to the working R32 for the NVRAM part so hopefully once i make a prototype board up it should work with the new design i've drawn up

I need the following hardware buzz outs on multimeter against GND (pin 14) on the 28 pin EPROM socket for Z31/Z32 R31: /CE PIN 20 does not buzz, connected to address selector (MB13T111 pin 14) /OE PIN 22 buzzes to GND (0 ohms) R32: /CE PIN 20 buzzes to GND (0 ohms) /OE PIN 22 does not buzz, connecte...

just worry about the romulator for now (if he has one)

there are no working Z32/R32 prototype boards yet because of some corruption issues when/how I use the /CE line to perform permanent store operations

this is not a problem for my ER34 and S13 SR20 daughterboards which were prototyped

okay i've finished up the final stablility issues with nissan consult.... its all working well now. i have a 4096 byte buffer in case the PC gets really loaded with other tasks. however if the PC gets too loaded for too long, that buffer fills up with consult data and will disconnect. just worst cas...

the consult connectors can be obtained through PLMS developments. i wont be doing these as obviously i am working with them with this :D the current solution is romulator and consult connector. you plug in a TP address and away you go. consult code for these (without eXtend consult) is almost finish...

fortunately its the willem programmer. for R31/Z31/R32/Z32 or any other 8 bit EPROM based ecu there is currently a small switchable adaptor i use i modified the 97d (latest is 97j) software for programming these type of NVRAM nothing decided yet. hopefully no firmware updates required once things so...

that explains the extra level of complexity (and 5 memory addresses rather than 2) used for your ecu

now i can look at the disassembly with a different frame of mind....

yeah i want to sell em, but only with the NVRAM chip and once all firmware issues have been resolved. we have the problem with logging mode bogging the car right now and i need to do some testing on it to see why unless people are happy using the romulator with the boards until NVRAM is available......

hmmm the z31 has modes simlar to the r32. do those modes seem to work in practice like in the service manual? my R31 only has two modes 1. if the selector is in diagnostics mode, it will flash the codes as indicated above 2. if the selector outside diagnostics mode, it will flash green/red codes dep...

chase the dot implemented latest version. 4/2 cells require some more work

time counter during recording had to come out when moving to multithreaded because it was leaving white 'blotches' over the screen. it will be put back in when i get time in 'save' mode i can put in a timestamped default file so you can just hit record. that would take about a night to implement the...

i've only done logging mode for the new changes on the bench, and was concerned when you mentioned that usb download was bogging the car around idle in regards to the higher stream rate for logging yes i hate to say that it probably looks like it is too much for the ecu to handle. nissan consult run...

worst case... should be able to clear those addresses

if you want dtcs codes from the diag pot if we cant get them easily undertandabout out of ecu, leave the connections to where the diag connected on PCB open (not connected to each other)

okay i need your help with this one here is the R31 stuff. it is split into two RAM addresses, with one bit representing each code ie 80 00 = RAM1: 1000000 RAM2: 0000000 = CAS 40 00 = RAM1: 0100000 RAM2: 0000000 = AFM 20 00 = RAM1: 0010000 RAM2: 0000000 = TEMP etc hex to binary if you use the window...