-
Posts
1,264 -
Joined
-
Last visited
-
Feedback
100%
Content Type
Profiles
Forums
Events
Gallery
Media Demo
Store
Everything posted by NewKleer
-
yeh it will be backlit - the one in the pic is only getting about a quarter of needed power for backlight (torch was used so i didnt need flash), full backlight will be fine unfortunately i dont think a31 cefiros support consult (unless u are using a r32 ecu that does)
-
trying to read g-sensor via consult port would mean reprogramming the ecu (and knowing how to do something like that). would take 5% of the time of that to just read the voltage directly from the sensor.
-
well all the core stats will work in pretty much all cars, with the odd car not supporting one here and there (eg s14 i dont think shows ign timing, and N15 didnt support something, forget what). at this stage the GTR/Z32's would miss out on the extra couple of sensors they support, but nearly every other car would support most/all the sensors given here. im planning for a switch (switch between lcd/usb/serial mode), and 3 buttons on the top - whether i utilise them straight away or leave it for future upgrades to the program on the chip i dont know. but id imagine anything is possible, just other things might be a priority (fault codes, peak values, etc) the ecu sends data about 10 times a second, but u cant update the display too quickly as the lcd, like normal computer lcds, has a response time, how quick pixels light up/die out, so if u update too quick it will become blurry. about 3-4 times a second would be do-able thats exactly where i thought it could be put, on the steering column (or perhaps at base of windscreen). ill probably wait and see if i can get a sample of the low profile one, but i guess unless its decently comparable (and not too expensive) then the larger one looks to be the goods. overall size id imagine would be 182mm wide, 38mm high, and about 30-35mm deep
-
just try the other rb ones, i think one of them is close?
-
heres the larger of the two 40x2's im looking at 000kph 0000rpm 00.0v EC:xxx INJ:00% 00oB AAC:00 O2:.00v 000oC AFM:0.00V TPS:0.00V sensors are pretty much same as first, just rearranged. contrast/viewability/response time is a LOT better on this one than the blue one (response time is time pixels take to charge up/die out, which effects how fast u can update screen before blur). the only real downside, assuming i can get it in extended temp and correct viewing angle (optimised for looking from above rather than below) would be the size. at 182mm (standard 40x2 size), with an enclosure (adding 2mm each side, so 186mm), will be a tad too wide for a lot of DIN slots. so the question would be, how important would it be to be able to fit it in a din slot? the full profile LCD (this one) would be better in all aspects (backlight brightness, contrast, viewing angle, response time) aside from its size. using a standard size will mean also that other types of lcds are easily interchanged. id also be hesitant to use the low profile LCD due to it being very hard to find and not really as readily available.
-
injector is tuning points for boost controller - the DFA is tuned via AFM voltage (or moreso, 128 ranges of the AFM over the 0-5v range, or whatever)
-
quite possibly that would just be from an external accelerometer than something in the ecu? what other things are on the dash? if theyre largely mechanical type things (rather than typical sensor readings from consult) then id say thats what it is does it say anything in the service/user manual (if there is one?)
-
ecu's have g sensors now?
-
partially misguided. the ecu learns around the closed loop operation (ie, when the ecu is using the o2 sensor to get the AFR to 14.7:1 or whatever, while cruising). however most ECU's disregard the o2 sensor (and hence any adjustments) while in open loop, ie acceleration and so on, which is exactly where you want the adjustment.
-
I found a good cheap boost controller for $22!!!
NewKleer replied to CEF11E's topic in Engines & Forced Induction
this still holds for those who want to email the guy who appeared here directly. should read the whole thread, but i guess at 100 pages its a bit much to expect maybe a mod can edit this into the first post so people know what to do? -
better to look at what each individual thing does then try and compare them like that with consult you can view all of the cars main sensors, change fuel injection time/static ignition timing across the rev range (which ecuextend does can do all) an safc has multiple mapping points (as opposed to the global change), but works on tricking the ecu into thinking there is more/less air then there really is, so the downside is that incorrect ignition timing is used (which with slight adjustments, hardly matters, but problems arise if ur trying to go from eg 9:1 afr up to 12:1) and an rsm (i think) uses an accelerometer in order to measure acceleration, and thus speed, distance (which can be worked out with acceleration + time). thus anything via consult and rsm/safc only have a single overlap in they both show RPM - slight overlap in that they display/work out speed (via different methods) and can change amount of fuel that goes in (via entirely different methods again).
-
might be able to get something together in a couple weeks in the way of a beta, but a few other things i need to fix up/look into first
-
it wont work on the early 89's as they dont have consult. i think sep/oct somewhere they gained consult support. basically if u have the consult plug then it probably will work.
-
moneys on you being wrong theres only water temp, and for z32/rb26 i think theres a few more (intake air, fuel temps)
-
1) does that it automatically works out the best config (eg rows x cols) for the amount of gauges you have to maximise the amount of screen area the gauges take up. if u have 1 gauge itll be full screen for that single gauge, 4 and theyll take up roughly 1/4 screen each. on a widescreen with 6 then id have 2 rows of 3 gauges to fill it out nicely. so will take care of widescreens no probs! 2) good idea, ill add that to the list - would be good for anyone thats smart enough to get a car pc going 3) cant do that unfortunately, youll have to stick to traditional gauge for boost
-
im not sure that AFM voltage is linear (thus %age isnt that useful, and is misleading) and O2 sensor definitely isnt linear. variations exist from car to car, so even if it was worth while to make a version for each diff model skyline (and every other nissan model...), you still will have variations between each car of that model. i could probably set it up to get the smallest/largest TPS voltage it encounters and then display as a % once youve floored it once (to get the max) or have some manual setup for that (ie it tells u to foot off, then foot flat, then stores that and can work out % from that) it wont work with CA18 (doesnt support consult). and wont work on splitting up the LCD and somehow making LED displays either as they work entirely differently unfortunately.
-
still waiting on some parts to do some testing before i get boards done. however i might put this on hold while im working on the consult display which could, if i go overboard, include a usb/serial consult interface as part of it (if it does i might cancel this one). not sure that ill have the funds up front to do both at same time, so will have to see. its definitely the priority over this given being something thats useful everyday (whereas the majority of people wont have a laptop permanently in the car)
-
yeh impakt sells a consult lcd display (search consult in for sale) for $300, and the occassional second hand one pops up, however its quite bulky (box too tall for din slot) and pricey, however a lot of work needs to be done on something like this so i dont blame him wanting to get something out of it
-
one for each reply
-
tps varies from car to car and model to model, so % would be hard to do, unless i got it to allow you to dont press/press accelerator to floor for it to find min/max voltage and work out % from there, but i dont imagine that would be too high a priority, but a possibility nonetheless good to get some good ideas coming
-
thats a good idea - almost forgot that perhaps i should put some kind of buzzer on it (speed alerts, etc would be useful) assuming the hardware is right (ie, buttons/switches/etc), im pretty sure upgrading the program on the chip will be easy to do (in order to add more features etc, and for the stuff im doing for uni project)
-
click on people's profile from links in the thread and see who comes from vic (if they have it). id guess maybe 5-10 were from vic. reasons im not interested in doing anything with a palm: 1) step back in time programming wise 2) not as much a plugin and forget type of thing 3) size (very limited mounting positions) 4) availability (relying on second hand via ebay isnt good for something, which if successful, may be used by quite a lot of people) 5) cant beat the speed of doing it in hardware 6) ive already started on my consult software which eventually will have a pocket pc version if im not too lazy. a more advanced version of this will quite possibly form part of my last year uni project starting middle of this year, which was another reason behind it.
-
based upon the consult interface kit i made here in the group buys section, but essentially is half a consult interface, with a microcontroller and lcd added in. ie, typically a consult interface/program is: ecu-> signal conversion -> rs232 (interface) -> rs232 (computer) -> consult program i could make it: ecu-> signal conversion -> rs232 (interface) -> rs232 (computer) -> microcontroller/lcd but its 'cleaner' to make it: ecu-> signal conversion -> microcontroller/lcd still, i can see the use in making it able to be used as a consult interface (and cheaper if your going to have both anyway, to just get one that does both), something like: ecu-> signal conversion -> branch 1: microcontroller/lcd branch 2: rs232 (interface) -> rs232 (computer) -> consult program and maybe a switch to switch between them.
-
Couple more pics, this time of a built display. You can see the switch on the top pic sticking out, this switches between consult lcd and consult interface. 3 buttons will be on final device to left of these, sticking out similarly. current layout: line 1: speed, rpm, battery voltage, economy, injector duty cycle, ignition timing line 2: AAC %, o2 sensor, coolant temp, AFM, TPS Edit: updated screenshot (taken on angle as i had no contrast adjustment) initial post below, above is updates I finally finished off the first stab at my top secret consult lcd project over the weekend. Im thinking of making the final thing on a 40x2 LCD (normal yellow/green as i think its easiest to view in sunlight than the blue/white), but the general concept is the same as this attempt: Plugs straight into consult port (no config/setup required), and displays on the 20x4: line 1: speed, rpm, battery voltage line 2: economy (see below), injector duty cycle, ignition timing line 3: o2 sensor, AAC %, coolant temp line 4: AFM, TPS, tps switch open/close (O or C) Economy was one which i thought would be really useful - it shows instant speed per amount of duty cycle (fuel usage), calculated by (speed * 10 / duty cycle), the x10 is to show it more accurately). So theoretically youll be able to find out on the highway what the most fuel efficient speed to travel at is, whether windows down or air-con on makes much difference, and whether granny shifting actually saves fuel (eg people might think 50km/h in 5th gear is good for fuel, but if the throttle and hence injectors have to be open a lot more than they would be in 4th gear, then you might actually be using more fuel) I recorded a short movie of it. 4.16mb, MJPEG Codec (part of windows xp). Has since been changed to update values on the lcd roughly twice as often as it does in this, but shows it working anyway. Im hoping to get a custom box made for it perhaps, as nothing long enough (for a 40x2) is also slim enough in other dimensions (and wouldnt want to have to cut each box manually preferably). If made compact enough, you could mount it in front of stereo, on steering column, etc. Other possibilities for it include 0-100km/h times, remembering peak values, and perhaps integrating a consult interface into it. Im hoping if all goes well i might be able to get it done for around $200, but extra things and custom enclosure might blow that out a bit. Will see how it goes. Peter
-
yeh, unfortunately u only get a 4.98v reading permanetly thru EGT in consult, so appears as though it only changes when its past that cutoff point (or never!)