 
     |
| FYI: Member Romsk's Awesome V6 ALDL Monitor Tool Is 'No Longer Available' on TFS.... (Page 1/1) |
|
Vintage-Nut
|
SEP 08, 04:46 PM
|
|
|
I suggest that he 'should' post his products in 'The Mall' or least a link to his site... ------------------
Original Owner of a Silver '88 GT
Under 'Production Refurbishment' @ 136k Miles
|
|
|
82-T/A [At Work]
|
SEP 08, 07:08 PM
|
|
| quote | Originally posted by Vintage-Nut:
I suggest that he 'should' post his products in 'The Mall' or least a link to his site...
|
|
I believe he’s making a new one right now.
|
|
|
Vintage-Nut
|
SEP 08, 08:29 PM
|
|
|
|
|
Mickey_Moose
|
SEP 09, 09:57 AM
|
|
|
|
|
Romsk
|
SEP 10, 02:42 PM
|
|
All,
Thanks for posting info about my products and website. I have to figure out how to list items on the mall.
I sold my first ALDL Tool Suite on Ebay yesterday... I am on my way.
I had to call Elon Musk today and ask for his shoe size... you see, I like to keep my bee-oches in heels [laugh].
|
|
|
|
str8maxn
|
SEP 10, 03:10 PM
|
|
|
Would this work on an LT1 ODB1 port too?
|
|
|
|
Dennis LaGrua
|
SEP 20, 07:15 PM
|
|
| quote | Originally posted by str8maxn:
Would this work on an LT1 ODB1 port too? |
|
OBD 1 ECM's used 2 different connectors for scanners and used a couple of different interface codes .From what I have found not all OBD 1 scanners are universal. I doubt if the ALDL scanner sold by Romsk would work for a Corvette or even the Cadillac 4.9L engine, For those we use the Actron 3 scanner.
------------------
" THE BLACK PARALYZER" -87GT 3800SC Series III engine, custom ZZP /Frozen Boost Intercooler setup, 3.4" Pulley, Northstar TB, LS1 MAF, 3" Spintech/Hedman Exhaust, P-log Manifold, Autolite 104's, MSD wires, Custom CAI, 4T65eHD w. custom axles, Champion Radiator, S10 Brake Booster, HP Tuners VCM Suite.
"THE COLUSSUS"
87GT - ALL OUT 3.4L Turbocharged engine, Garrett Hybrid Turbo, MSD ign., modified TH125H
" ON THE LOOSE WITHOUT THE JUICE "
|
|
|
|
Romsk
|
SEP 26, 11:29 AM
|
|
I have been asked if I can support 1980's Corvettes. I am sorry, but I originally supported only the 1986 to 1988 V6 Fieros, I added the 1985 V6 on request, and just recently added the 1985 to 1986 L4 Fieros on another request. The 1984 L4 will be next, and finally the 1987 to 1988 L4 Fiero that use 8192 Baud (not going to be fun integrating that protocol in my GUI).
After that, I don't have the energy to support any more GM vehicles. Sorry. Its a lot of reverse engineering. Some of you suggested that I use TunerPro's configuration files (whatever they call them) to determine the data streams for each ECM, and I appreciate the advice. But the use of an effective "competitor's" tool to develop my own just does not hold up to my business ethics.
I have put a lot of effort into the GUI over that last decade (I started it just as a fun project), I am not going to hand over or sell the source code to anyone. It was written in ANSI C using National Instruments LabWindows/CVI V13.0, so not many coders use that IDE or code in pure C anymore.
|
|
|
|
Romsk
|
SEP 26, 11:38 AM
|
|
BTW... why coded in ANSI C?
C Code is just one step above assembly. It doesn't have the fancy features of C++ or the managed code that C# offers. But I write my code in way that approaches C++ and I have adopted techniques that self manages the code to prevent virtually any crashing.
Because of this, nothing happens like "clean up" or needless array checking behind the scenes like in C++ and C#, so I get the best performance out of the GUI - its just more adhering to certain coding styles, and thus "more explicit" coding ... which is becoming a lost art. And AI can't do everything... yet.
|
|
|
Vintage-Nut
|
SEP 26, 12:09 PM
|
|
| quote | Romsk:
the use of an effective "competitor's" tool to develop my own just does not hold up to my business ethics. |
|
 
|
|
|
|
