Ford KAsket - Revision history

MechanicalCat at 15:07, 27 May 2025

2025-05-27T15:07:35Z

← Older revision		Revision as of 15:07, 27 May 2025
Line 26:		Line 26:
	For subsequent races the axle was made solid, and driven by a single Vevor 2000W brushless motor with 2000W eBike controller. Gearing was 11T to 64T giving about 11700 motor revs per mile. Motor's no-load speed is 4300rpm, giving a theoretical speed of 22mph.		For subsequent races the axle was made solid, and driven by a single Vevor 2000W brushless motor with 2000W eBike controller. Gearing was 11T to 64T giving about 11700 motor revs per mile. Motor's no-load speed is 4300rpm, giving a theoretical speed of 22mph.
	==Theme==		==Theme==
	Transportation space constraints required low-profile bodywork, so a low surrounding wall of plywood was fitted, in the shape of a truncated coffin. Coloured mahogany and with some genuine coffin fittings. Some genuine 'Ford' blue-oval and 'KA' boot-badges, with 'sket' CNC'd from mirrored plastic sheet appended, provided the name.		Transportation space constraints required low-profile bodywork, so a low surrounding wall of plywood was fitted, in the shape of a truncated coffin. Coloured mahogany and decorated with some genuine coffin fittings. Some genuine 'Ford' blue-oval and 'KA' boot-badges, with 'sket' CNC'd from mirrored plastic sheet appended, provided the name.

	== BOM ==		== BOM ==

MechanicalCat: Added BOM. Updated summary.

2025-05-27T10:42:28Z

Added BOM. Updated summary.

@@ Line 4: / Line 4: @@
 |Theme=Ford KAsket - a coffin
 |FirstRace=Scrumpy Cup 2022
-|CurrentStatus=Resting
+|CurrentStatus=Available for guest drivers
-|Motor=Various
+|Motor=Pair converted alternators. Later Vevor 2kW brushless.
-|ESC=Generic 1500W eBike controller X1 or X2 plus Arduino controller
+|ESC=Generic 1500W eBike controller X2 plus Arduino controller. Later generic 2000W eBike controller X1.
 |Battery=48V Li-Ion (2x 6S)
 |Transmission=Chain with various gearings - sometimes unequal to each wheel.
@@ Line 27: / Line 27: @@
 ==Theme==
 Transportation space constraints required low-profile bodywork, so a low surrounding wall of plywood was fitted, in the shape of a truncated coffin. Coloured mahogany and with some genuine coffin fittings. Some genuine 'Ford' blue-oval and 'KA' boot-badges, with 'sket' CNC'd from mirrored plastic sheet appended, provided the name.
 ==Other Lessons==
 At constant cruise the eBike controller of the non-prioritised motor tended to overheat. The Arduino was throttling it to prevent excessive fuse current, but FETs produce more heat when constantly switching (PWM'ing at part-throttle) rather than when turned on (at full throttle). So any design which drives a controller for a long duration at part-power should over-spec the controller.

Cstubbs at 07:44, 16 January 2025

2025-01-16T07:44:29Z

← Older revision		Revision as of 07:44, 16 January 2025
Line 32:		Line 32:
	{{VehicleResultsTable}}		{{VehicleResultsTable}}
	{{clear}}		{{clear}}

			-----
			{{FooterFB}}


			[[Category:Racers]]

Cstubbs at 07:43, 16 January 2025

2025-01-16T07:43:46Z

← Older revision		Revision as of 07:43, 16 January 2025
Line 29:		Line 29:
	==Other Lessons==		==Other Lessons==
	At constant cruise the eBike controller of the non-prioritised motor tended to overheat. The Arduino was throttling it to prevent excessive fuse current, but FETs produce more heat when constantly switching (PWM'ing at part-throttle) rather than when turned on (at full throttle). So any design which drives a controller for a long duration at part-power should over-spec the controller.		At constant cruise the eBike controller of the non-prioritised motor tended to overheat. The Arduino was throttling it to prevent excessive fuse current, but FETs produce more heat when constantly switching (PWM'ing at part-throttle) rather than when turned on (at full throttle). So any design which drives a controller for a long duration at part-power should over-spec the controller.
			==Race Results==
			{{VehicleResultsTable}}
			{{clear}}

Cstubbs: Cstubbs moved page KAsket to Ford KAsket

2025-01-16T07:40:20Z

Cstubbs moved page KAsket to Ford KAsket

← Older revision		Revision as of 07:40, 16 January 2025
(No difference)

MechanicalCat at 18:22, 15 January 2025

2025-01-15T18:22:19Z

← Older revision		Revision as of 18:22, 15 January 2025
Line 19:		Line 19:
	==Powertrain==		==Powertrain==
	Drive was initially by two converted alternators using two 1500W eBike controllers. A single throttle thumblever was input to an Arduino, which monitored the current used by each controller. The Arduino allocated throttle settings out to the two controllers and also turned on or off the field currents of the motors, to attain best performance.		Drive was initially by two converted alternators using two 1500W eBike controllers. A single throttle thumblever was input to an Arduino, which monitored the current used by each controller. The Arduino allocated throttle settings out to the two controllers and also turned on or off the field currents of the motors, to attain best performance.
	The two motors each drove one rear wheel. Each wheel was braked by a standard cycle disk, with cable-operated caliper. A single brake lever operated both.		The two motors each drove one rear wheel. Each wheel was braked by a standard cycle disk, with cable-operated caliper. A single brake lever operated both. Wheels are standard 4" split-rim mobility-scooter items with standard mobility tyres (front) and 4.10-4 Minimoto knobblies (rear). Rear wheel dia approx 10".
	The kart was intended to experiment with the following benefits potentially afforded by two motors:		The kart was intended to experiment with the following benefits potentially afforded by two motors:
	*No diff required, and no scrubbing losses. This wasn't successful: the extra motor weighs as much as a diff, and its losses appeared to outweigh the modest losses from a typical diff. The complexity of an extra brake was required - whereas a solid axle requires only one. If a brake is fitted to its input then a diff also requires only one disk.		*No diff required, and no scrubbing losses. This wasn't successful: the extra motor weighs as much as a diff, and its losses appeared to outweigh the modest losses from a typical diff. The complexity of an extra brake was required - whereas a solid axle requires only one. If a brake is fitted to its input then a diff also requires only one disk.
	*If the motors are geared differently, then the low-geared motor can be prioritised to give maximum acceleration but it can also be disabled (with zero field current) at high speed, leaving the high-geared motor to take the kart to a higher top speed. This feature was automated by the Arduino, with the only user control being the single throttle. This was even less successful: these eBike controllers throw an error when the field current is turned off and require power-cycling at standstill for them to restart, stymieing the feature.		*If the motors are geared differently, then the low-geared motor can be prioritised to give maximum acceleration but it can also be disabled (with zero field current) at high speed, leaving the high-geared motor to take the kart to a higher top speed. This feature was automated by the Arduino, with the only user control being the single throttle. This was even less successful: these eBike controllers throw an error when the field current is turned off and require power-cycling at standstill for them to restart, stymieing the feature.
	*If full power is demanded, but at a speed where a single motor would be unable to draw enough current to make full use of the fuse-limit, then current can be allocated to both motors. This was somewhat successful, but the same could be achieved simply by fitting a bigger single motor (and a current-limiting controller) instead.		*If full power is demanded, but at a speed where a single motor would be unable to draw enough current to make full use of the fuse-limit, then current can be allocated to both motors. This was somewhat successful, but the same could be achieved simply by fitting a bigger single motor (and a current-limiting controller) instead.
	For subsequent races the axle was made solid, and driven by a single Vevor 2000W brushless motor with 2000W eBike controller.		For subsequent races the axle was made solid, and driven by a single Vevor 2000W brushless motor with 2000W eBike controller. Gearing was 11T to 64T giving about 11700 motor revs per mile. Motor's no-load speed is 4300rpm, giving a theoretical speed of 22mph.
	==Theme==		==Theme==
	Transportation space constraints required low-profile bodywork, so a low surrounding wall of plywood was fitted, in the shape of a truncated coffin. Coloured mahogany and with some genuine coffin fittings. Some genuine 'Ford' blue-oval and 'KA' boot-badges, with 'sket' CNC'd from mirrored plastic sheet appended, provided the name.		Transportation space constraints required low-profile bodywork, so a low surrounding wall of plywood was fitted, in the shape of a truncated coffin. Coloured mahogany and with some genuine coffin fittings. Some genuine 'Ford' blue-oval and 'KA' boot-badges, with 'sket' CNC'd from mirrored plastic sheet appended, provided the name.
	==Other Lessons==		==Other Lessons==
	At constant cruise the eBike controller of the non-prioritised motor tended to overheat. The Arduino was throttling it to prevent excessive fuse current, but FETs produce more heat when constantly switching (PWM'ing at part-throttle) rather than when turned on (at full throttle). So any design which drives a controller for a long duration at part-power should over-spec the controller.		At constant cruise the eBike controller of the non-prioritised motor tended to overheat. The Arduino was throttling it to prevent excessive fuse current, but FETs produce more heat when constantly switching (PWM'ing at part-throttle) rather than when turned on (at full throttle). So any design which drives a controller for a long duration at part-power should over-spec the controller.

MechanicalCat at 18:11, 15 January 2025

2025-01-15T18:11:19Z

← Older revision		Revision as of 18:11, 15 January 2025
Line 26:		Line 26:
	For subsequent races the axle was made solid, and driven by a single Vevor 2000W brushless motor with 2000W eBike controller.		For subsequent races the axle was made solid, and driven by a single Vevor 2000W brushless motor with 2000W eBike controller.
	==Theme==		==Theme==
	Transportation space constraints required low-profile bodywork, so a low surrounding wall of plywood was fitted, in the shape of a truncated coffin. Coloured mahogany and with some genuine coffin fittings. Some genuine 'Ford' blue-oval and 'KA' boot-badges, with 'sket' appended, provided the name.		Transportation space constraints required low-profile bodywork, so a low surrounding wall of plywood was fitted, in the shape of a truncated coffin. Coloured mahogany and with some genuine coffin fittings. Some genuine 'Ford' blue-oval and 'KA' boot-badges, with 'sket' CNC'd from mirrored plastic sheet appended, provided the name.
	==Other Lessons==		==Other Lessons==
	At constant cruise the eBike controller of the non-prioritised motor tended to overheat. The Arduino was throttling it to prevent excessive fuse current, but FETs produce more heat when constantly switching (PWM'ing at part-throttle) rather than when turned on (at full throttle). So any design which drives a controller for a long duration at part-power should over-spec the controller.		At constant cruise the eBike controller of the non-prioritised motor tended to overheat. The Arduino was throttling it to prevent excessive fuse current, but FETs produce more heat when constantly switching (PWM'ing at part-throttle) rather than when turned on (at full throttle). So any design which drives a controller for a long duration at part-power should over-spec the controller.

MechanicalCat at 18:10, 15 January 2025

2025-01-15T18:10:28Z

← Older revision		Revision as of 18:10, 15 January 2025
Line 26:		Line 26:
	For subsequent races the axle was made solid, and driven by a single Vevor 2000W brushless motor with 2000W eBike controller.		For subsequent races the axle was made solid, and driven by a single Vevor 2000W brushless motor with 2000W eBike controller.
	==Theme==		==Theme==
	Transportation space constraints required low-profile bodywork, so a low surrounding wall of plywood was fitted, in the shape of a truncated coffin. Coloured mahogany, with some genuine coffin fittings.		Transportation space constraints required low-profile bodywork, so a low surrounding wall of plywood was fitted, in the shape of a truncated coffin. Coloured mahogany and with some genuine coffin fittings. Some genuine 'Ford' blue-oval and 'KA' boot-badges, with 'sket' appended, provided the name.
	==Other Lessons==		==Other Lessons==
	At constant cruise the eBike controller of the non-prioritised motor tended to overheat. The Arduino was throttling it to prevent excessive fuse current, but FETs produce more heat when constantly switching (PWM'ing at part-throttle) rather than when turned on (at full throttle). So any design which drives a controller for a long duration at part-power should over-spec the controller.		At constant cruise the eBike controller of the non-prioritised motor tended to overheat. The Arduino was throttling it to prevent excessive fuse current, but FETs produce more heat when constantly switching (PWM'ing at part-throttle) rather than when turned on (at full throttle). So any design which drives a controller for a long duration at part-power should over-spec the controller.

MechanicalCat at 18:02, 15 January 2025

2025-01-15T18:02:43Z

← Older revision		Revision as of 18:02, 15 January 2025
Line 27:		Line 27:
	==Theme==		==Theme==
	Transportation space constraints required low-profile bodywork, so a low surrounding wall of plywood was fitted, in the shape of a truncated coffin. Coloured mahogany, with some genuine coffin fittings.		Transportation space constraints required low-profile bodywork, so a low surrounding wall of plywood was fitted, in the shape of a truncated coffin. Coloured mahogany, with some genuine coffin fittings.
			==Other Lessons==
			At constant cruise the eBike controller of the non-prioritised motor tended to overheat. The Arduino was throttling it to prevent excessive fuse current, but FETs produce more heat when constantly switching (PWM'ing at part-throttle) rather than when turned on (at full throttle). So any design which drives a controller for a long duration at part-power should over-spec the controller.

MechanicalCat at 17:57, 15 January 2025

2025-01-15T17:57:16Z

← Older revision		Revision as of 17:57, 15 January 2025
Line 21:		Line 21:
	The two motors each drove one rear wheel. Each wheel was braked by a standard cycle disk, with cable-operated caliper. A single brake lever operated both.		The two motors each drove one rear wheel. Each wheel was braked by a standard cycle disk, with cable-operated caliper. A single brake lever operated both.
	The kart was intended to experiment with the following benefits potentially afforded by two motors:		The kart was intended to experiment with the following benefits potentially afforded by two motors:
	*No diff required, and no scrubbing losses. This wasn't successful: the extra motor weighs as much as a diff, and its losses appeared to outweigh the modest losses from a typical diff. The complexity of an extra brake was required - whereas a solid axle requires only one. If a brake is fitted to ~~the crownwheel -~~ a diff also requires only one disk.		*No diff required, and no scrubbing losses. This wasn't successful: the extra motor weighs as much as a diff, and its losses appeared to outweigh the modest losses from a typical diff. The complexity of an extra brake was required - whereas a solid axle requires only one. If a brake is fitted to its input then a diff also requires only one disk.
	*If the motors are geared differently, then the low-geared motor can be prioritised to give maximum acceleration but it can also be disabled (with zero field current) at high speed, leaving the high-geared motor to take the kart to a higher top speed. This feature was automated by the Arduino, with the only user control being the single throttle. This was even less successful: these eBike controllers throw an error when the field current is turned off and require power-cycling at standstill for them to restart, stymieing the feature.		*If the motors are geared differently, then the low-geared motor can be prioritised to give maximum acceleration but it can also be disabled (with zero field current) at high speed, leaving the high-geared motor to take the kart to a higher top speed. This feature was automated by the Arduino, with the only user control being the single throttle. This was even less successful: these eBike controllers throw an error when the field current is turned off and require power-cycling at standstill for them to restart, stymieing the feature.
	*If full power is demanded, but at a speed where a single motor would be unable to draw enough current to make full use of the fuse-limit, then current can be allocated to both motors. This was somewhat successful, but the same could be achieved simply by fitting a bigger single motor (and a current-limiting controller) instead.		*If full power is demanded, but at a speed where a single motor would be unable to draw enough current to make full use of the fuse-limit, then current can be allocated to both motors. This was somewhat successful, but the same could be achieved simply by fitting a bigger single motor (and a current-limiting controller) instead.