NewKleer

high number = more economical. 0 to 999, although if u manage to go over 999 i think itll still show 4 digits, just push everything else down to get 1000, u need to be doing, for example 100km/h at 1% or less injectory duty cycle. idling i think uses a few %, so ud probably need to idle at 300km/h to get close to 1000 its a relative thing, so each number on its own doesnt tell much. it would be useful, for example, to compare going 60km/h up a hill in 4th gear vs 5th gear. you might find that 4th is better (high number) because its using a more efficient part of rev range, whereas 5th would need more throttle at a less efficient part of rev range. what you use it for is pretty much up to the individual

0-400m is unlikely due to whats stated here will see how demand goes as to where i sell them, but im not really making any money from them so its more just about when ive got time to make them. will just be selling them to sau/pga members to start with, will then see how popular (or not) they are as to whether ill sell elsewhere

i hope to start making them end of the month, but could potentially blow out to mid august

serial cable for the integrated consult interface. flick the switch on the top to the right (and probably press a couple of buttons) and u can use it like a normal consult interface to hook up a laptop/ppc and do datalogging or whatever else u need to do

making a hud out of it is a bit out there, and would probably easily double the cost of it, assuming i had the time to do it. interesting idea from a safety point of view though the unit would come with both cables attached and ready to go. it would be as simple as plugging it into consult port and turning ignition on (or the other way around)

thats right, theyre correction factors or multipliers. from memory fuel is +/- x%, and ign timing is +/- x degrees (so fuel is a multiplier, timing an offset) unfortunately fuel/ign are the only interesting things you can do. you can do other random stuff (alter iaac valve, temperatures for fans to go on/off, cut out cylinders(cant remember if its ign or fuel), and turn the fuel pump on/off), but none all that useful for everyday running for all other things, such as rpm limited and speed cut, you have to manually remap/edit the ecu rom.

yeh thats it, you could do something like that via laptop/pda, but that would even be slower than in hardware - so my idea would be to use a microcontroller to do it from (and hence no need for laptop/pda there permanently). since u cant save any changes made via consult, its an active thing i would base it upon the consult lcd display im making, since the hardware etc is already setup for it, would just require different firmware etc on the microcontroller that runs it. so because it uses consult, theres no hardware setup, just plug it in and go. however, the drawbacks are that communication is serial, and each changes requires you to tell the ecu to stop sending data before making the next change request (just adds a bit more time) serial not a huge issue in itself, but the 2 main factors is it does add lag in the region of milliseconds somewhere from when it can read ur current rpm/afm, and when it can then apply the changes, and secondarily, if u pull the plug out in the middle of the car running, it will be "stuck" in the current adjustment until car is turned off/on again (or its plugged back in) so the idea is to have a 2D map of RPM vs AFM (another advantage over piggybacks that are traditionally 1D maps), with adjustments (+/- % for fuel). one extra thing to be noted, is that any change in adjustment (ie from one value to another) will result in adjustments going briefly back to normal/0% adjustment (between the time you tell the ecu to stop with current changes, and apply new ones). so the less "jumping" between different % adjustments the better. ie it will be better to leave it at say +10% for xxx rpm to xxx rpm, than going to 11% for only a few hundred rpm, then back to 10, as when it changes to 11, and then back to 10, it will briefly be running not sure how much of that is understandable Peter

i wasnt thinking of doing a direct piggyback type one like SITC, but via consult. you would map out adjustments for fuel and ign, and these would be applied on the fly via the active test functions of the consult protocol. its nature is slightly unreliable (due to serial comms) and response time wouldnt be super, but i imagine its effectiveness, at least for fuel mixtures would be better due to not being a piggyback and hence not messing up your ignition timing, so theretically you wont have the issue of ign advancing if u make huge leaning out changes to top end. wouldnt be better than an SITC though for ign (being plug and play would be the only advantage), however it may be good enough to be useful. hence what i was mentioning about before at the least amount of load points for it to be effective/better than using nothing. the problem is not its resolution (mapping resolution would only be limited by the amount of memory required to store the offsets for each point) but the response rate - eg if you rev from 0-8000 rpm in one second in neutral, then you are essentially limited by how quick the adjustments can be made to ensure your not going to be running incorrect or damaging offsets in the wrong rev ranges i never anticipated doing anything with the ign timing (perhaps aside from consult controlled static ign timing adjustments, which would just be set once and left, and not modified on the fly) due to that, but would be interested if itd be of any use.

ill add that to the todo list also a general update, ive sent off pcb's to be manufactured, and finalising changes to enclosure prototype. with any luck ill have both by end of july, and assuming ive got needed parts then and finish the firmware for the device, can start making some. the current todo list (of what i want to try and get done for final release): yes: switchable MPH/F, V/0-100% throttle clear/read error codes voltage input reading peak hold maybe: reset learnt data 0-60, 100km/h (store best times also perhaps) any other suggestions, let me know. ill look back over this thread from start to end when i get a chance, so if its already been mentioned ill consider it

its not compatible with any replacement ecu's like powerfc (which has its own diagnostic protocols). im not sure exactly where u mean in terms of mounting it? under/above the visor? so u see it when its up/down? by far the best place would be on steering column, or on dash perhaps, i havent tried alternate positions

would something that could control ign timing and fuel adjustments independant of each other (ie, leaning fuel wont change ign timing at that load point and vice versa) be useful? and how much resolution would be required for it? whats the minimum load point interval that would be acceptable? as soon as the first version of my consult lcd project is done, i want to look at doing something that will allow adjustments to fuel/ign independantly of each other, but the main drawback will be relatively slow response times (it has to actively monitor/adjust, can be as slow as 100ms real world) which effectively puts an upper limit on how often (and hence resolution) of the adjustments.

thanks for the comments peak hold - this shouldnt be too difficult. tps sensor - shouldnt be too hard to do a % thing, maybe as an option as for some diagnostic purposes it helps to know actual voltage? fault codes - im reasonably confident ill be able to get this done for the final thing. ecu reset - this is a bit misunderstood - ecu reset is actually only clearing the closed loop learnt data, not all learnt data (i dont actually know what all the values that the ecu learns, but presumably theres more) upgradable - will definitely be upgradable, just will require a roundtrip being sent back to me (was too hard to put some functionalty in to allow end users to upgrade it themselves, unfortunately). 0-100kmh - possible for the first release, depends on time constraints. 0-400m - possible, but hard to get this accurate. to determine distance, you could determine the time between each jump in velocity (consult only shows every 2 km/h), and if u record the time taken for this, work out the average acceleration, and then the distance. but acceleration isnt linear, and the calculations would, over time, become a bit inaccurate. BUT, its something i want to try later on, and measure it and see how accurate it can get, so its something ill look to do later on as for the screen, the main thing to consider was mounting position, and the usefulness of them. from an engineering background also, i had the ethical decision as to the configuration that would allow people to mount it somewhere relatively safe. mounting it on the steering column, just below all ur other gauges, wont distract the user too much from watching the road - whereas if it was a size that was too tall for that, but nice to fit in the ash tray or whatever, then you have the problem of people wanting to look at the data having to look down to it. while it is still a problem that people are looking at a screen at all rather than the road, i thought it was more important to put it somewhere that, if they must look at it, then they still have their eyes on the road. thus the steering column mount biased design took the cake.

prototype enclosure was made, see pics here. need to make a few minor corrections to it, which ive sent thru, and manuafacturing of first lot of enclosures will be before end of july. also getting final pcb's manufactured soon (made some changes to pcb today), then will need to order a few parts, then ready to make them.

sorry, no kits left or pcb's. best bet would be to either get one from blazt.biz (caz from these forums sells them i think), or plmsdevelopments.com alternatively, if you're interested in the lcd consult interface im making, that may be available in a month or two, and will have an integrated consult interface http://www.skylinesaustralia.com/forums/in...howtopic=102414

this was posted about 3 weeks ago, so safe to say it was around before the upgrade

i cant remember when the upgrade was, but i dont think it was a problem 6 months ago

that thread mentions nothing that i have here - the excessive spacing (essentially every new line is 2 or 3 new lines rather than 1)

maybe i need a monitor that does 3000x1500 resolution

i used to get it, and no longer do ie6/nortons antivirus

its the reverse placebo effect. there used to be the problem on the board, hence this topic, but its since been fixed. however some people dont realise its been fixed, and hence are thinking its somehow still happening

im getting the same thing most likely targetting some exploit in this board

my r31 popped out after a suspected overfllling of the oil on oil change. could be blowby in the old engine though

can we remove this from the forums? often ive seen or posted threads which have words in them that should either be entirely capitalised or no capitals, but there doesnt seem to be any way to do so Without Titles Coming Out Just Like This

thats a good point and worth noting - Joe Pampena came up with the initial design way back in 2001 (or even before perhaps). While marks's design is very similar, its not an exact duplicate, whereas JRD's is almost an exact duplicate of marks with no thought put into the design. Either way there just different degrees of copying an existing idea (maybe joe even got the idea elsewhere). The controllers are practically identical, however the paint on the JRD one seemed slightly more "sticky" if we want to split hairs

There were quite a few at two distinct periods, about 8 all up where the wait was around 2 weeks or so (only a couple longer than 3 weeks). i could post all the post numbers up, but after re-reading the thread, i think i have to side with you on this one, the far majority of people have been happy with his service, and with that many dealings theres bound to be some issues from time to time. I have suggested previously that all he needs to do is find a way to inform us of his availability in sending out the devices. Like i mentioned - perhaps if we see him not advertising any on ebay, then we can assume he's a bit busy at the moment (but unfortunately thru the two periods where he was having problems, he was still advertising them on ebay, which just meant more of a build up of people waiting on him). Given you said you read the whole thread before buying, you would have noticed that 95% of my posts were positive towards mark, it was just a little annoying that people would have a reason to buy from JRD to begin with when JRD is obviously a rip off of marks one, but for those wanting some guarantee of getting theirs delivered in timely manner during the periods where no one received any replies from mark, they had no alternatives. Thanks for at least making me review what ive said - there were 2 distinct periods where there were lengthy delays, but both times mark ended up getting back to people and explaining the delays. Given the lack of complaints recently, I think we should assume that there is no longer any issues and no reason not to buy them from mark. let us know how you go with a longer line to wastegate/boost source and whether it effects lag at all. ive got a boost source post intercooler on one of my setups and it does spike in the lower gears (where rampup is quicker)