![]() |
Re: wiring
Quote:
|
Re: wiring
Quote:
|
Re: wiring
You only have to look at the early steam locomotives to realize that a proposal like this is feasable but not practical. Whenever the early engines tried to move at a speed exceeding 5mph (4-cim robot on mecano speed w/ 12.5v), the boiler would be sucked dry, water would have to be put in, pressure would drop, train would stall until more steam was generated. Of course, the efficiency was less than a percent, with the mid-twentieth centry locos pegging 7-8% on a good day.
As for torque: steam/air engines of the piston sort is the only enigne on the planet that can produce maximum force at 0 rpm, unlike gas/diesel. Also, you fellows are probably considering full pressure for the full strike. On a steam engine, the valve gear (monkey motion) was adjusted so that the least amont of steam was needed to do the most work. On startup, steam was admited for maybe 75% of the stroke. As speed increased, the cutoff was reduced so the boiler wouldn't be sucked dry. Volume of steam consumed was decreased, and PV=nRT, so pressure dropped correspondingly. However, more power was produced at higher speeds, with a similar drop in total tractive effort applied to the rail. For steam enignes, 2-cyl: SP(B^2)(.85) ------------- = TE D S = stroke in inches P = pressure in psi B = bore in inches D = driver diametere in inches TE = tractive effort in pounds (7lbs on clean dry steel rail on 0% slope = 1 ton at constant speed) at START .85 = accounts for decearse in pressure difference between gauge and piston face -piston is connected straight to the wheel, no gearbox included -steam only |
Re: wiring
New proposal for pneumatic engine: short stroke, large bore, spring return cylinders in pairs pushing against a one way clutch bearing so that the stroke and lever length can be adjusted independently. Pairs are grouped in threes or fours to cover dead-zones created when the cylinders return to their rest positions. Each pair requires its own bearing. The number of groups needed depends on the power requirement, pairs from all groups should be distributed evenly.
for example: If we use a pair of numbers ,(G,P) ha ha GP, to name the pairs (G would be the group, P would be the pair, and (2,3) would be the 3rd pair of the second group), a simple, 3-speed, 3-pair configuration would look something like this: (1,1)(2,1)(3,1)[coupler***](1,2)(2,2)(3,2)[coupler***](1,3)(2,3)(3,3) ***to aid in maintenance, the shaft should be split and joined with couplers after every set*. * a set is composed of the nth pair of all groups [The first set includes (1,1), (2,1), and (3,1). The first group includes (1,1), (1,2), and (1,3).] Cylinders of the same pair fire simultaneously, pairs of the same group fire sequentially, and pairs of the same set can either fire simultaneously or sequentially. when cylinders of the same group fire, there should be a 50% overlap for groups of three, and a 33.33% overlap for groups of four, no such overlap is necessary for sets that fire sequentially, but it is acceptable to do so. Groups are activated in order as more power is needed. It is also acceptable to create subsets, or groupings of cylinders that fire simultaneously within a set in which all subsets (which must contain the same number of cylinders) fire sequentially. If subsets are used, lowercase letters following the last parenthesis of the cylinder's name are used to show the subset, with subscripts to show how many groups are active when the cylinder in question is firing, if subscript cannot be used, normal numbers are fine. For example: (1,1)a4,6; (2,1)b4,6; (3,1)a4c6; (4,1)b4a6; (5,1)b6; and (6,1)c6 make up the first set of an engine with 6 groups that uses subsets when 4 or 6 groups are active. High grouped arrangements are generally not used, due to weight. The one above is just a hypothetical example used to demonstrate the proper usage of a naming convention. EDIT: I'm creating a new thread to discuss this topic here. Sorry for off-topic posts. |
| All times are GMT -5. The time now is 22:02. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi