93TyphoonPacetruck
Member
Re: Need A New Name For A Chip!!!!!!!
SYTY All-In-One Chip
Straight to the point
SYTY All-In-One Chip
Straight to the point
JS Manufacturing said:Progress is moving forward, but typical of these trucks. 1 step forward 2 back.
Basically we have found a big bug in gm code, fixing it causes another issue. Like a can of worms at this point, we are just counting them right now so they can be fixed.
Captain Morgan said:
MotorMouth said:As long as it dose not ask "Would you like to play a game?" when you plug it in![]()
InvisiBill said:Bravo on this effort. I'm not sure how much I'll be able to contribute, but believe me when I say I'll give back whatever I can to this.
As for the open source-ness of this, I suggest releasing it under the GPL or a similar license. That allows anyone to use the code essentially for whatever, as long as they release their derivative works under the same terms. If they don't agree to that, they have no right to use the code and can be sued for copyright violation. It sucks that you'd have to do this, but it protects you (the coders) and us (the community) from people who only intend to steal others' work and give nothing back. The "play nice" idea would most likely work with anyone on this board, but those aren't the people you have to worry about stealing your hard work for their own profit.
turbodig said:We can GPL the code changes... no problems there. I don't honestly see there being a
lot of submitted code, but if someone wants to, it'll need to be submitted under the original
free license terms. Otherwise, they'll need to start their own new distribution.
As far as the license agreement, we plan on making it economically unfeasible for people
to copy and profit from it- ie, why buy what you can download for free?
There will be people who try to steal the code and sell it as their own.. these people will
be exposed at every opportunity. While we don't have the resources (or interest) in legal
battles, we hope that the community at large won't support the bottom feeders. That's
the best way to combat the problem- get the word out about people who don't play by the
rules.
JS Manufacturing said:I have eluded to some new developments being made on the ecm front.
Here are the basics.
Few select group of guys have been working on rewritting the code that runs our ecm. Not just hacks but rewritting, adding things, etc.
Some of the things being added or already added.
In testing or still to be added
- WB brand selection via bit
- Extended VE table
- Extended Fuel Multiplier
- Desired boost -vs- MPH
- WG DC -vs- MPH
- Eliminated closed throttle table
- Eliminated VE adder table
So if you can't tell, this will totally change tuning, how our trucks run, etc. I would say FAST owners will become jealous at the features we are adding.
- Output knock to electric gauge (autometer, etc.)
- Closed loop wideband (this is a biggie).
- 2 step staging rpm control
- full alky control via table
- and several more ideas I can't talk about.
With due time the chip will be released after more testing but we need a good name.
Anybody got some suggestions?
im still partial to that one-----^ :lol:Captain Morgan said:
Matarex said:how far a long is it? and is the a ETA on it!! (im just looking for the first chip)
btw what about GT-Chip, Iron~noX or the short ver. Inox
We are currently calling the new code, Code59 for now. The name could change but for right now that is what we are calling it.
To run this code you need to have a WBo2 Controller connected to your ECM on Pin F14 and a 3 Bar Map Sensor installed..You can still run this code on a low boost or naturally aspirated application , you just need to be using a 3 Bar Map sensor and it must be using fuel injectors. We have not tested this on a TBI application so I don't know if it would work on that.
Here are the features of the new code, with more things being added down the road after more testing is completed. This should get everyone excited.
Current Features of Code59:
Flags for these features have to be turned on in the bin using the 59 XDF to use these new features. Please read the Notes in the XDF on each item.
WBo2 Controller selection
- The code expects the WB sensor voltage to be present on pin F14 on the 749ecm (i.e. MAP2).
- Bit 0 : DIY / TechEdge v1.0 Sensor Nonlinear Output - Uses Table
- Bit 1 : FJO Nonlinear Output - Uses Table
- Bit 2 : Generic/AEM Nonlinear Output - Uses Table, Table can be calibrated to be used with sensor not on the list.
- Bit 3 : TechEdge v2.0 Linear Output - Uses Formula [AFR = (Volts * 2) + 9]
- Bit 4 : PLX Linear Output - Uses Formula [AFR = (Volts * 2) + 10]
- Bit 5 : Innovate Linear Output - Uses Formula [AFR = (Volts * 2) + 10]
- Bit 6 : AEM Linear Output - Uses Formula [AFR = (Volts * 2) + 10]
- Bit 7 : Zeitronix (Nonlinear Output - Uses Table)
- Second WBo2 Sensor Setting
- Bit 7 : RAW - Raw output of Voltage, Use formula in TunerPro to display AFR. DO NOT USE WITH WIDE BAND O2 FUELING FLAGS TURNED ON
Closed Loop WBo2 Fueling(Currently Not active when in PE)
- AFR High setting
- AFR Low Setting
- Sensor Ready Delay, amount of time to delay to make sure the wbo2 sensor is ready before WBo2 Closed Loop code is active
- F29_AFR table to calibrate what AFR you want to run. Matches the F29x table in Size You can dial in any AFR you want to run under 100 kPa and it will run it at that AFR, provided you are in CLOSED LOOP.
16x32 VE Table F29x covering (400-6400 RPMs, and 0 - 300 kPa (30psi)) - Replaces F29 and F30 tables with a much wider range of RPMs and kPa's you can controll fueling in. This table is used when in Open Loop, in PE, WOT and when F29_AFR flags are turned off. This is the table that AutoTune will help you tune.
F70_MPH Desired Boost Pressure VS RPM AND MPH - Changed table from TPS% to MPH based. Run Lower Boost for launching when at low MPH. You can scale the boost to come on as you increase MPH and RPM.
F71_MPH Wastegate Duty Cycle -vs- MPH - Changed table from TPS% to MPH based. Helps reduce boost spiking in 3rd/4th gear shifts by allowing you to adjust Wastegate% at the MPH your shifts occur.
Updated ALDL Outputs
- Actual AFR
- Desired AFR
- AE/DE/PE/DFCO/BLM Flags - Know now when you are in AE/PE/DE/DFCO or you BLM is active.
- $3f map variable (Real 3 Bar Map Variable, used by F29x, F29_AFR)
- $3e Filtered Map
F29x Table Only - No longer use F29c (Closed Throttle Table) at idle. Single Table for both Idle and Driving.
Expanded Boost Multipler F77x Table - Covers a wider range of 84 - 292 kPa
Updated BARO LOGIC
V8 EGR Fix
In the Works/Possible Future Features:
- Alky/NOS pump/fuel control - Cut boost if Fuel Pressure is low.
- Fuel Pressure Input into ECM and output into ALDL
- EGT Input into ECM and output into ALDL
- Security
- 2 stage rev limiter, launch control
- Knock output to a Guage (actually see how many Degrees knock you are getting) - In testing
- Highway Mode (better gas mileage when cruising, configureable)
- More WBo2 Control (When in PE mode, Open/Closed). Allow Full use of the F29_AFR when in Boost (Above 100 kPa) - We are still hashing out algorithm
- Expanded NVRAM support (will need it for More Learn cells for the WBo2 Fueling Algorithim)
MRKING said:Man you guys are the bomb . For the future knock output to gauge feature , how do you interface that circuit to get it onto the gauge ?