OEM contact

Contact

Share payload, speed profile, protocol, and safety targets. We respond through [email protected].

Inquiry email

Send a quick RFQ

Use the form when you want to leave the first technical scope without opening an email client.

Input item	Why it matters
Payload and duty profile	Defines torque-speed and thermal feasibility early.
Wheel and mounting envelope	Prevents mechanical package mismatch during prototype.
Protocol and controller context	Clarifies mapping ownership and commissioning workload.
Safety/compliance boundary	Aligns STO/SLS and conformity evidence expectations.

Stage	Buyer action	Factory-side output
Initial email	Share scope, constraints, and rough timeline.	Acknowledge inquiry and flag missing technical inputs.
Technical alignment	Confirm architecture and interface assumptions.	Clarify feasibility boundaries and pilot validation checkpoints.
Pilot planning	Lock test priorities and acceptance criteria.	Propose pilot scope and change-control path.
Supply handover	Confirm recurring demand scenario.	Define communication rhythm for production-phase support.

Project type and intended application environment.

Payload, wheel size, target speed, and duty profile.

Controller/protocol assumptions (CANopen, EtherCAT, PROFINET, others).

Safety boundary (for example STO/SLS expectations).

Pilot timing and key decision milestones.

Include payload range, target speed profile, wheel envelope, control protocol, and any STO/SLS or compliance constraints.

Send high-level requirements first. NDA and detailed file exchange can be arranged during technical alignment.

Yes. We support pilot validation and then transition to recurring supply once interfaces and acceptance gates are confirmed.