1961-1965 Fiat 2300 Coupe




 Origin: IT Italy

Class: Coupé

Chassis: 114B

Advertising


Comments

Author Message


PL fck

2011-12-03 21:15		 Rinspeed wrote
i just think it's not very important to have codenames.


Looking on Ford Sierra or propably Capri, Opel Kadett it seems it's not bad idea, sometimes engines aren't different (displ, power, torque) on a first look, but some things are changed.


FR Rinspeed

2011-12-03 20:30		i just think it's not very important to have codenames.


PL fck

2011-12-03 20:27		 Rinspeed wrote
For the denomination. Put the original name (in the original counrty) or code in liter so not 114B for this italian cars.
For th cylinders, typical normal engines are inline, so i put x cyl for this type of engine and for special motor like V6, i put it.


So for example in Opel Vectra page you would to see a 1.8, 2.0, 2.5 16v against 1.8 CX18EV, 2.0 CX20XEV, etc? So, engine codenames are useful for us, or not? If yes, we can move an engine codename to separate pole in add motor form?


FR Rinspeed

2011-12-03 20:08		For the denomination. Put the original name (in the original counrty) or code in liter so not 114B for this italian cars.
For th cylinders, typical normal engines are inline, so i put x cyl for this type of engine and for special motor like V6, i put it.


PL fck

2011-12-03 20:00		@Rinspeed, a little question: how about engine names? What the best way to put infos?

Example here: 2300 is a 114B.000, a 2300 S is a 114B.006, now:
1. Stay that look
2. Put 2300 114B.000 and 2300 S 114b.006?
3. 2.3 114b.000 (2300)
4. 2.3 or 2300/2300S and a engine manufacture codename move to new space in add engines form?

And what about straight/inline engines. I put always Ix (I-inline x- number of cylinders) (earlier I put incorrect Rx (R-rzędowy, inline in polish), you are putting x cyl - why?

-- Last edit: 2011-12-03 20:01:51

Add a comment

You must login to post comments...