Knowledge-based engineering, self-serve
Set the belt width, the length and the height and the whole machine follows: the frame, the legs and braces, the drums on their bearings, the return rollers on their shafts and brackets, the belt as a closed loop — every part exists because a rule says it must, and the parts list and the price are the same model read a different way.
Drag Length. Cross bars and return rollers are counted from it — each roller brings its shaft and its pair of drop brackets with it — and the belt loop, the slider sheet and the rails re-size in the data and in 3D.
Belt width sets the frame width, the drum and shaft lengths, the roller lengths and the brace lengths; height sets the legs. One input, a dozen dependent dimensions.
Nothing rotates in mid-air: drums run on stub shafts in flange bearings outside the rails; return rollers turn on fixed shafts held by brackets under the rails. Every one of them is a part in the list.
The Parts List page gives every profile by length, every shaft, bearing and bracket by count, the belt by area; the Price page turns them into money at your rates. Change the length and both pages follow.
Orbit the 3D scene with your mouse · double-click empty space to re-frame · every value recomputes live on the server-verified formula engine.
This is not a 3D file with sliders. The product model owns the facts (belt width, length, height, which side the motor sits); quantity rules mint the parts from them (cross bars and return rollers counted from the length, brackets two per roller, legs and feet four); map rules derive the geometry as a view of the product — when a rule adds a roller, its cylinder, its shaft and its brackets appear where the rail is; and the parts list and the price read the same relations. This one was built by our build service from a photo and a two-paragraph spec; the same engine powers plain calculators, instant-quote widgets, and full configurators.