Core rule: simulation is not authorization
MechaTraining is an educational environment. Except for the limited PLC educational-bench permission below, do not use an application, XR view, warning, recommendation, calculation, program, report or exported file to control, commission, validate, certify or authorize physical equipment or production.
Educational models may simplify geometry, dynamics, forces, timing, materials, sensors, controller behavior, hazards, standards and failure modes. A missing warning does not mean a condition is safe. A displayed warning may not represent every condition that would occur on a specific system.
Controls required outside MechaTraining
- Use trained, qualified and authorized personnel.
- Follow current manufacturer manuals, approved drawings, engineering specifications, workplace procedures and applicable laws and standards.
- Perform a documented risk assessment and use approved guarding, interlocks, emergency functions, PPE and hazardous-energy control.
- Independently verify units, coordinate systems, limits, loads, clearances, tools, fixtures, payloads, programs, sensor logic and expected failure behavior.
- Use the organization's approved offline verification, physical prove-out, inspection, sign-off and change-control process.
CNC machining applications
Mech CNC Mill and related CNC training may model G-code, MDI, work offsets, tooling, stock, material removal, feeds, speeds, loads, cost and safety events. These are instructional estimates, not a controller emulator certified for a particular machine.
- Never send a MechaTraining program or simulator output directly to a physical CNC controller.
- Independently verify program identity, postprocessor, units, coordinates, work and tool offsets, stock, fixtures, travel, spindle direction, RPM, feed, coolant, holders, reach and collision clearance.
- Perform the machine owner's approved dry run, single-block prove-out, guarding and part-inspection process with qualified supervision.
- STL, PDF, ZIP, hashes, warnings and cost reports are educational evidence; they do not certify dimensional accuracy, process capability, machine safety or production readiness.
Robotics, PLC and automation applications
Robotics and automation training may represent motion, programs, frames, payloads, I/O, sensors, PLC logic or process states. No current MechaTraining training application is safety-rated or authorized for industrial commissioning or production control. The PLC educational-bench permission below is not an industrial or safety certification; a contract alone does not change a training application's technical or safety status.
- Except for the supported PLC educational bench below, do not connect a training app or output to a robot controller, PLC, drive or actuator. Never connect it to a safety PLC, safety relay or production network.
- Do not use simulated reach, collision, payload, speed, stopping distance, zone, I/O or interlock behavior as a safety validation.
- Real deployments require the equipment manufacturer's procedures, qualified integrators, risk assessment, safeguarding, lockout/tagout and validated safety functions.
Limited permission: supervised PLC educational benches
Only the separately identified MechaTraining PLC app and its supplied firmware may exchange I/O or execute a student program on a supported ESP32, ESP32-S3 or classic Arduino Uno, Nano or Mega board, solely on a supervised, low-voltage, low-energy educational bench. Virtual machines remain the primary training environment. The board profile, firmware version, wiring and limits in the supplied hardware documentation must match the actual board; similar product names do not establish compatibility.
- A qualified instructor or responsible competent adult must approve the bench and supervise use. Use a suitable isolated, current-limited low-voltage supply and observe every component rating. Low voltage alone does not establish safe current, temperature, motion or stored energy.
- Never connect mains voltage, a production machine, physical CNC or industrial robot, a hazardous process, a safety circuit or production network. Do not use this software for emergency stop, guarding, life safety, safety validation, commissioning or production authorization.
- Never connect 24 V signals, motors, valves or other loads directly to GPIO. Use correctly rated interfaces and electrical protection. Classic ESP32 GPIO uses 3.3 V logic; the supported classic ATmega Arduino boards use 5 V logic. Confirm the exact board documentation before wiring.
- Provide a physical means to remove actuator energy independently of the computer, browser, USB connection, firmware and PLC program. Disconnect loads before flashing, changing wiring or performing first-run checks; independently verify output polarity, startup state, watchdog behavior and timing with no hazardous load connected.
- In remote-I/O and HIL modes, watchdogs and software STOP are instructional controls, not certified safety functions. In autonomous mode the board can continue running after USB loss, browser closure, session expiry or monitor disconnection. Optional autostart may energize outputs on power-up and requires a separate deliberate action.
- Firmware installation replaces the board program and can change ESP32 partitions. Identify the board and port, preserve any needed prior program and deliberately approve replacement. Compilation, simulation, a verified hash or an academic report does not prove physical electrical or timing acceptance.
This narrow permission does not extend physical-control rights to any CNC, Robotics, XR or Vision app and does not authorize a modified firmware or unsupported board to be represented as verified by MechaTraining. Stop use on unexpected behavior. Institutions remain responsible for their own laboratory authorization, procedures, supervision and legally required controls.
Vision, process, aeronautics and other engineering fields
Vision results, process estimates, sensor models, quality decisions and aeronautical examples may be affected by lighting, calibration, noise, environment, configuration, data quality and model assumptions. They are teaching aids and must not be used as the sole basis for rejecting or accepting production, controlling a hazardous process, navigation, flight, airworthiness, maintenance release or regulatory compliance.
Every future application remains subject to this general notice plus its own domain-specific instructions. If an app does not provide enough information to establish a safe real-world procedure, do not infer one from the simulation.
XR, mobile devices and future managed casting
- XR placement, scale, tracking and work-offset exercises are educational. They are not metrology, survey, machine calibration or alignment certification.
- Before moving, inspect the physical area and keep clear of machines, tools, edges, traffic, stairs and other hazards. Remain aware of people and surroundings.
- Hold or mount devices securely. Stop if tracking is unstable, the display causes discomfort or the device obstructs safe movement.
- Public self-service Classroom Casting is not enabled. A future institution-managed casting deployment must authenticate and authorize every participant and establish required privacy notices, consent, supervision and device rules before use.
- Obtain required notice and consent before camera use, any future casting, screen sharing or recording in a classroom, workplace or home.
- A synchronized hologram or future classroom cast may be delayed or disconnected. The authoritative training state remains the authenticated host session; neither view is a physical control channel.
Responsibilities of schools, instructors and employers
Organizations retain responsibility for learner eligibility, qualified supervision, accessibility, safe facilities, device hygiene, emergency procedures, recording rules and all physical-laboratory authorization. Instructors must explain the difference between simulation and real equipment and must not assign an activity that uses MechaTraining as the sole safety or production approval.
Stop use and report problems
Stop the activity if the software behaves unexpectedly, the displayed state conflicts with the assignment, tracking becomes unstable, a security warning appears or any person or equipment could be at risk. Do not attempt to compensate by bypassing a check.
For a software, security or safety-content concern, preserve the relevant non-sensitive details and contact support@mecha-training.com. For an actual emergency, use the local emergency procedure and emergency services; MechaTraining support is not an emergency-response service.