FORGECNC ACADEMY — VIDEO 01 First launch and basic setup Script draft · screenshots captured · recording pending Browser practice and application setup. Physical installation, controller commissioning, homing, probing and live cutting are separate lessons. Estimated duration: 12:58 at 130 words per minute with demonstration pauses. OUTCOME The learner can find the main controls, save and export a clearly labelled practice machine profile, distinguish a simulated connection, and inspect an offline practice job. PREPARATION 1. Open the local ForgeCNC website on this computer. The browser preview uses the retained 0.2.0 build. 2. Use a fresh browser profile for the recording so personal machine settings and account details do not appear. 3. Download the website’s ForgeCNC-offline-preview-only.nc sample. It is a visualisation exercise, not a machine-ready cutting programme. 4. Use only Virtual xPRO for the connection demonstration. No physical controller, spindle or axes are operated in this lesson. SCENE 01 — Welcome and open the practice environment Estimated 0:00–0:48 Screenshot: screens/01-browser-practice.png NARRATION Welcome to ForgeCNC. In this first lesson, we’ll organise the screen, create a practice machine profile, and preview a simple job. We’ll use the browser preview, so you can follow along without connecting a CNC. On the website, open the Browser demo page. Choose Get preview sample, then Open browser workbench. Keep the downloaded file for later. The installed Windows and Linux apps provide the physical controller workflows; their installation and commissioning are covered in separate lessons. ON-SCREEN ACTIONS 1. Show the website’s Browser demo page. 2. Click Get preview sample and retain ForgeCNC-offline-preview-only.nc. 3. Click Open browser workbench and switch to its tab. ON-SCREEN EMPHASIS First launch → practice profile → offline preview LEARNER CHECK The workbench is open and the named sample file has downloaded. RECORDING NOTE The screenshot shows the actual local website. Crop the browser address from the finished film rather than presenting 127.0.0.1 as a public address. SCENE 02 — Find your way around Estimated 0:48–1:34 Screenshot: screens/02-first-launch.png NARRATION Choose Basic from the workspace controls. Start by finding four areas: connection status at the top, tasks down the left, the job and three-dimensional view in the centre, and Machine watch on the right. We are disconnected, so live position information is unavailable. That is expected. Read the words beside a light, not just its colour. NO DATA means ForgeCNC has no current report. You do not need to unlock, home or move anything to follow this lesson. ON-SCREEN ACTIONS 1. Choose Basic in the workspace selector. 2. Point to the connection badge, left navigation, central panels and Machine watch in that order. 3. Hold on DISCONNECTED and a NO DATA tile. ON-SCREEN EMPHASIS Read the state words: DISCONNECTED · SIMULATED · NO DATA LEARNER CHECK The learner can locate the status, tasks, job view and signal panel. RECORDING NOTE This is an empty Basic workspace. Do not replace it with a screenshot containing an already running job. SCENE 03 — Make the screen comfortable to use Estimated 1:34–2:22 Screenshot: screens/03-display-options.png NARRATION Open Manage to see the display choices. Choose Dark, Light or High Contrast to suit your screen. Workshop mode gives you larger controls when you need them. You can resize panels and choose a different workspace for a different task. Save updates the current saved arrangement; Save As gives a new arrangement its own name. These controls change how the screen is arranged. They do not change machine home, work zero or permission to run a job. ON-SCREEN ACTIONS 1. Open Manage and point to Theme. Keep Dark for visual continuity in this recording. 2. Close the menu; point to Workshop, Save and Save As without inventing a new machine setup. 3. If demonstrating a resize, restore the layout before the next scene. ON-SCREEN EMPHASIS A workspace is a screen layout LEARNER CHECK The interface is readable and the learner knows where display choices live. RECORDING NOTE Record a brief real resize if desired; the still illustrates the Manage menu. SCENE 04 — Locate the machine profile settings Estimated 2:22–3:09 Screenshot: screens/04-machine-directory.png NARRATION Open Settings, then Machine. This is where you organise your workshop machines. You can search the directory, choose a manufacturer, model and size, or use Custom Build. Read the information beside the model, including its dimension source and hardware-validation status. A catalogue entry is a reference; it does not prove that the fitted controller or machine has been tested. The QueenBee reference is protected. For this exercise, we’ll create a separate, clearly named training profile. ON-SCREEN ACTIONS 1. Open Settings → Machine. Enlarge or detach the panel so the fields are readable. 2. Point to Find a machine, Manufacturer, Model and Size / version. 3. Point to Hardware validation, then choose Custom Build. ON-SCREEN EMPHASIS Catalogue reference ≠ hardware qualification LEARNER CHECK Settings → Machine is open and the profile choices are understood. RECORDING NOTE The screenshot is an enlarged settings panel. Show the navigation into it in the recording so viewers can follow. SCENE 05 — Enter the practice profile Estimated 3:09–4:14 Screenshot: screens/05-profile-fields.png NARRATION Name this profile TRAINING ONLY, Example router. I’m using fictional travel of four hundred millimetres in X, three hundred in Y, and eighty in Z. These numbers exist only for this exercise. On a real machine, enter confirmed usable travel, not the outside frame dimensions. Leave Fitted controller as Not identified yet for our fictional machine. The displayed baud rate is also unverified. Add a note that this profile is for training. For a physical setup, identify the actual controller, firmware family and connection rate before proceeding. ON-SCREEN ACTIONS 1. Enter TRAINING ONLY - Example router and Fictional training example. 2. Keep Fitted controller at Not identified yet. 3. Enter X 400, Y 300 and Z 80 solely in the isolated practice profile. 4. Enter the visible note: fictional dimensions, no physical machine, controller and baud unverified. ON-SCREEN EMPHASIS FICTIONAL TRAINING VALUES · Do not copy to a physical machine LEARNER CHECK The name, travel fields and notes clearly identify an unverified practice profile. RECORDING NOTE Use a close view of the name, controller, dimensions and notes. Do not frame 115200 as a recommended universal baud rate. Custom Build requires all three travel fields to save; do not suggest guessing missing physical values. SCENE 06 — Save and verify the profile Estimated 4:14–5:00 Screenshot: screens/06-profile-saved.png NARRATION Choose Save and select machine. Read the confirmation: the profile is saved for connection setup, and no controller settings were written. It should now appear in Saved machines. That distinction matters: saving this record does not configure a controller, establish machine home or authorise movement. When you create your real profile later, give it a name you will recognise and check the saved values. For now, keep this training profile clearly separate from any real machine. ON-SCREEN ACTIONS 1. Click Save & select machine. 2. Scroll to the confirmation and read it before moving on. 3. Show that the training name is selected in Saved machines. ON-SCREEN EMPHASIS Saved profile · no controller settings written LEARNER CHECK A named practice profile exists and the confirmation is visible. RECORDING NOTE The provided still focuses on the confirmation. Record the Saved machines selector as a short follow-up insert. SCENE 07 — Export the application configuration Estimated 5:00–5:50 Screenshot: screens/07-backup.png NARRATION Before making more changes, scroll down to Export application configuration and save a copy. Keep the file somewhere you can find again. This backup covers application setup information such as saved machines and work datums. The Tool Library and controller settings have their own backups, and native job journals are separate. We are exporting a practice configuration here. We are not restoring anything or replacing an existing workshop setup. A later lesson will cover checking and restoring each kind of backup. ON-SCREEN ACTIONS 1. Scroll to Export application configuration. 2. Click it and show the downloaded filename without exposing personal folders. 3. Retain the exported file; do not import it over the learner’s existing configuration. ON-SCREEN EMPHASIS Application configuration · tool library · controller settings are separate LEARNER CHECK An application-configuration download has completed. RECORDING NOTE No training backup needs to be distributed. The actual capture used an isolated browser containing only this practice profile. SCENE 08 — Connect to the virtual controller Estimated 5:50–6:40 Screenshot: screens/08-virtual-selection.png NARRATION Return to Saved machines and select the QueenBee reference for the practice connection. Open the Setup workspace, then the connection menu at the top. Choose Virtual xPRO and the Normal, Idle scenario. The virtual controller always represents the QueenBee reference, even if another profile was selected earlier. Choose Connect. This is practice data inside the application. Physical serial is the separate installed-app route for real hardware, which we will cover after installation and the initial machine checks. ON-SCREEN ACTIONS 1. Select QueenBee xPRO · reference in Saved machines. 2. Return to the main workspace and select Setup. 3. Open Connect, confirm Virtual xPRO and Normal · Idle, then click Connect. ON-SCREEN EMPHASIS Virtual xPRO · simulated QueenBee reference LEARNER CHECK The simulated connection is established, with its SIMULATED label visible. RECORDING NOTE Do not select Physical serial or interact with hardware. Keep the Source control in view when introducing the virtual connection. SCENE 09 — Read the connection state Estimated 6:40–7:29 Screenshot: screens/09-virtual-connected.png NARRATION Use Request status to refresh the displayed state. Notice Connected and the SIMULATED badge. Machine Status shows the practice controller’s coordinates and operating state. MACHINE and WORK are different coordinate views: machine position uses the machine reference, while work position uses the selected work coordinate system. We’ll explain that relationship properly in the datum lesson. For now, recognise that these are simulated readings. A normal-coloured light, or an idle state, does not independently prove that a physical setup is safe. ON-SCREEN ACTIONS 1. Click Request status · ?. 2. Point to Connected, SIMULATED, IDLE and the MACHINE / WORK controls. 3. Choose Return to workspace. Do not click Home All, Unlock, jog or probe. ON-SCREEN EMPHASIS Connected is a link state; SIMULATED identifies the evidence LEARNER CHECK The learner can identify simulated readings and find Request status. RECORDING NOTE The normal practice scenario can show HOME VERIFIED without a homing action in this lesson. Treat it explicitly as scenario data. SCENE 10 — Understand the preparation sequence Estimated 7:29–8:24 Screenshot: screens/10-setup-guide.png NARRATION Open Setup guide in the sidebar. It gives you the order for a real job: connect and identify; home and enable; load the job; review stock and fixtures; select the work datum; fit the tool and set Z; inspect and simulate; then check and run. Some information is detected, while other steps are reminders you review yourself. Ticking a reminder does not approve motion. Today we are learning the interface. Leave physical setup steps outstanding and follow the current Start reason when preparing a real job. ON-SCREEN ACTIONS 1. Open Setup guide and frame its step navigation. 2. Point down the eight steps, without claiming that they have been performed. 3. Point to Check & run as the final decision; leave manual review checkboxes untouched. ON-SCREEN EMPHASIS The guide organises preparation; the current checks govern Start LEARNER CHECK The learner recognises the sequence and knows why this lesson is not a completed live setup. RECORDING NOTE For the film, pause briefly on the list rather than opening and rapidly reading every stage. Later videos cover the individual tasks. SCENE 11 — Load the offline practice file Estimated 8:24–9:20 Screenshot: screens/11-job-loaded.png NARRATION Open the connection menu again and disconnect the virtual controller. Confirm Disconnected at the top. Choose CAM Review, then Load Job, and select ForgeCNC offline preview only, dot N C, from your downloads. Check the filename after it loads. This file contains two simple rectangular routes for visual practice. It is not a cutting programme for your machine. The file area shows the analysed job, and the three-dimensional viewer shows its route. A loaded file still needs its own setup and review before any physical operation. ON-SCREEN ACTIONS 1. Open Connection → Disconnect → Return to workspace. 2. Choose CAM Review from the workspace selector. 3. Click Load Job and choose ForgeCNC-offline-preview-only.nc in the operating-system picker. 4. Wait for analysis and point to the exact filename and disabled Start state. ON-SCREEN EMPHASIS DISCONNECTED · ForgeCNC-offline-preview-only.nc LEARNER CHECK The same sample filename and two rectangular routes are visible. RECORDING NOTE Record the file-selection action on the target recording OS. The supplied screenshot shows the resulting loaded state, not an OS-specific file picker. Never distribute this file as machine-ready G-code. SCENE 12 — Inspect the route before playback Estimated 9:20–10:10 Screenshot: screens/12-toolpath.png NARRATION In the viewer, JOB focuses on the loaded toolpath. TOP shows its plan view, and ISO gives an angled view. Fit brings the route back into frame if you lose it while exploring. Read the legend to distinguish cutting moves from rapid travel. You can orbit by dragging, pan with a right drag and zoom with the wheel. Notice the warning that machine placement is unverified. Looking at the route does not set a datum or position real stock on the machine. ON-SCREEN ACTIONS 1. Choose JOB, then TOP. 2. Point to the route legend and the unverified-placement message. 3. Record a short ISO / Fit demonstration, then hold the clear plan view. ON-SCREEN EMPHASIS View controls change the view, not the work offset LEARNER CHECK The learner can see and reframe the complete sample route. RECORDING NOTE Keep the route large enough for viewers to distinguish the inner and outer rectangles. SCENE 13 — Open the stock-carving preview Estimated 10:10–11:02 Screenshot: screens/13-preview-stock.png NARRATION With the controller still disconnected, choose Simulate stock. The panel on the right describes the proposed blank: its origin, width, depth, top surface and thickness, plus the flat cutter diameter used for this preview. These are visualisation inputs. If you change them, choose Apply and reset stock to rebuild the preview. For this practice file, keep the displayed example values. In a real job review, you would compare them with the intended stock and tool before interpreting the result. ON-SCREEN ACTIONS 1. Click Simulate stock. 2. Point to Preview stock and its labelled fields. 3. Keep the automatically proposed example values for continuity. Explain Apply & reset stock without implying that it updates hardware. ON-SCREEN EMPHASIS Preview stock dimensions are visualisation inputs LEARNER CHECK The stock preview is open, with the sample filename and controls visible. RECORDING NOTE Do not call the proposed blank a measured physical workpiece. Use a close insert for the field labels. SCENE 14 — Play, pause and scrub Estimated 11:02–12:02 Screenshot: screens/14-preview-scrub.png NARRATION Choose Play to watch the approximate material removal, and Pause to stop the preview. Drag the timeline to examine a particular point. Show route overlays the cutter lines; Reset takes you back to the beginning. These controls send no commands to a machine. The preview uses one flat-end cutter and a two-and-a-half-dimensional approximation. It does not model collisions, all tool shapes or tool changes. Use it to understand the route and likely shape, then complete the separate setup and preflight process for a physical job. ON-SCREEN ACTIONS 1. Record actual Play, then Pause, with the changing stock in view. 2. Check Show route and scrub to approximately 72 percent, matching the still. 3. Point to Reset and the statement that no commands are sent to a machine. ON-SCREEN EMPHASIS Preview playback ≠ machine execution LEARNER CHECK The learner can pause and inspect the route at an intermediate point. RECORDING NOTE The supplied PNG is a paused, scrubbed state. Film the actual playback for the final lesson; do not present a still as a recorded running sequence. SCENE 15 — Find help and check your progress Estimated 12:02–12:58 Screenshot: screens/15-help.png NARRATION Close the preview and open Help and guides, or press F one. Search for the task you want to understand next. The website Academy and illustrated manual provide the matching written instructions and full-size screenshots. You should now be able to find the main controls, save a practice profile, export configuration, recognise a simulated connection, and preview the sample while disconnected. Pause here and repeat any step you want to practise. Next, follow the installation lesson for your operating system, then the controller connection and commissioning lessons. ON-SCREEN ACTIONS 1. Close the preview, then open Help & guides. 2. Show guide search and point to the browser-versus-installed-app and first-job guides. 3. Finish with the learner checklist and links to the Academy, manual and next lessons. ON-SCREEN EMPHASIS Practise → install → connect and commission → prepare a real job LEARNER CHECK The learner can find help and choose the correct next lesson. RECORDING NOTE Closing card: ForgeCNC Academy · Lesson 01 complete as a learning exercise. Do not label a machine commissioned or a job approved. TRAINING VIDEOS TO PRODUCE 02. Install ForgeCNC on Windows (5–7 minutes) Choose the correct package, complete installation and first launch, locate updates and record the installed version. Prerequisites: Lesson 01; Windows computer Footage: Windows installer and first-launch recording on a clean test system. 03. Install ForgeCNC on Debian and understand other Linux packages (6–9 minutes) Install the tested Debian package, understand dependencies and serial permissions, and distinguish documented support from unqualified distributions. Prerequisites: Lesson 01; target Linux system Footage: Debian installation and launch. Record other distributions only after their package and permission steps are verified. 04. First physical connection and commissioning Stage A (8–10 minutes) Identify the actual controller, select its port and baud, read firmware/settings and inputs, and save no-motion evidence. Prerequisites: Installed app; supported actual controller; machine-specific procedure Footage: Native connection UI plus controller identification and input-state footage. No-motion stage. 05. Home, enable and jog: commissioning Stage B (8–10 minutes) Understand machine home, direction and travel checks, deliberate jog modes and the current operating-setup blocks. Prerequisites: Stage A satisfied; supervised physical setup Footage: Synchronised native screen and camera view of axis motion and homing. 06. Spindle, stopping and supporting equipment: Stage C (7–9 minutes) Distinguish requested RPM from feedback, confirm stopping, and inspect cooling/extraction where independent feedback is unavailable. Prerequisites: Preceding commissioning stages; authorised spindle procedure Footage: Actual spindle/VFD setup, stop verification and supporting equipment. 07. Stock, clamps and fixture placement (6–8 minutes) Describe stock and occupied fixture bounds, recognise travel and holder clearance, and identify the intended CAM origin. Prerequisites: Qualified machine setup; reviewed workholding plan Footage: Bench demonstration and matching stock/fixture entries in the native setup form. 08. Machine home, work zero and saved fixture datums (8–10 minutes) Understand MPos/WPos/WCO and G54–G59; save named fixture corners and distinguish selection from applying an offset. Prerequisites: Verified home and known fixture geometry Footage: Actual fixture-square inner corner, controller readback and saved-datum review. 09. Build a tool library and verify the fitted cutter (7–9 minutes) Distinguish supplier catalogue, owned tools and fitted geometry; check diameter, holder and measured stickout. Prerequisites: Known physical tool and holder Footage: Tool Manager, owned-tool entry and physical measurement. 10. Probe stock Z and work references: Stage D (9–12 minutes) Review probe contact state and checked approach, measure the intended reference and verify the resulting work zero. Prerequisites: Qualified preceding stages and a suitable commissioned probe setup Footage: Native probing workflow plus close camera view of the actual probe and workpiece. 11. Configure and calibrate a tool setter: Stage E (8–10 minutes) Record the installed sensor body and safe approach, calibrate a known reference and distinguish measured length from catalogue length. Prerequisites: Installed supported setter; preceding checks satisfied Footage: Setter geometry, calibration and readback; show the not-installed route separately. 12. Load CAM output and review units, tools and operations (6–8 minutes) Choose supported G-code, inspect units/WCS and bounds, understand operation boundaries and handle import failures. Prerequisites: Reviewed CAM output; lessons on datums and tools Footage: One original CAM file, successful analysis and a clearly labelled rejection example. 13. Toolpaths, stock carving and placement on the machine (7–9 minutes) Use JOB/MACHINE views, layers, Play/scrub, stock inputs and visual datum placement while recognising simulation limits. Prerequisites: Loaded practice file; lesson on datums Footage: Continuous offline capture showing both carving windows with the same source file. 14. Preflight, blocked Start and the air run: Stage F (9–12 minutes) Read blocking findings, review the exact source and geometry, and distinguish simulated inspection from a supervised spindle-off clearance run. Prerequisites: Current commissioned setup, tool, datum and stock checks Footage: Native path review, a resolved blocker and the actual clearance route on the machine. 15. First supervised cut and run controls: Stage G (8–12 minutes) Make a deliberate Start decision, observe progress, distinguish Pause/Resume/Software Stop from physical E-stop and verify completion. Prerequisites: All required preceding stages and current job approval Footage: Synchronous machine and native UI recording under the machine-specific acceptance procedure. 16. Guided measured tool changes: Stage H (8–10 minutes) Follow the measured changeover, safe position, standstill checks and fresh Z/length review before continuation. Prerequisites: Supported measured workflow and commissioned equipment Footage: A real supported changeover; mark unavailable capability honestly where not fitted. 17. Machine watch, warning lights and missing data (6–8 minutes) Read FAULT/CHECK/NO DATA, inspect signal details and distinguish reported conditions from simulated or unavailable sensing. Prerequisites: Basic interface knowledge Footage: Labelled virtual fault examples followed by real readback examples where available. 18. Recovery from an interruption: Stage I (10–14 minutes) Preserve the original source and journal, re-establish measured references, review correction/return/remainder, and continue only through the checked workflow. Prerequisites: Commissioned supported recovery setup and original source evidence Footage: A prescribed supervised interruption and complete recovery recording. Script against the actual installation before filming. 19. Recovery decision clinics (3–5 each minutes) Short separate cases for power/link loss, probe/limit blocks, tool slip or breakage, moved stock and wrong source/WCS; show when continuation must be abandoned. Prerequisites: Recovery foundation lesson Footage: Clearly labelled simulated cases; use physical evidence only where the scenario has been safely demonstrated. 20. History and repeat-job preparation (5–7 minutes) Locate completed/interrupted runs, inspect source identity and prepare a repeat job with fresh checks instead of reusing old approval. Prerequisites: Completed practice or supervised run Footage: Job History and the new preparation flow. 21. Console commands and controller readbacks (6–8 minutes) Use the supported-command reference and readbacks, understand fill-only examples/history and interpret rejected requests. Prerequisites: Known connection mode; commissioning for physical actions Footage: Start with virtual readbacks; physical command demonstrations remain subject to native checks. 22. Update machine and tool catalogues (6–8 minutes) Review catalogue revisions, import supplier libraries and separate directory products from owned/measured tools. Prerequisites: Dated backup; supported catalogue/library files Footage: Review/apply/rollback of a labelled training update and tool import results. 23. Backups, restore and software upgrades (8–10 minutes) Preserve application, tools and controller data separately, review replacement, and use a verified upgrade/rollback process. Prerequisites: Dated backups; validated target package Footage: Isolated restore exercises and version-specific clean install/upgrade evidence. 24. Arrange the workspace, second monitor and camera (6–8 minutes) Save layouts, restore panels, use Workshop/themes and a second display, and understand advisory camera/snapshot use. Prerequisites: Suitable display/camera; host permission where applicable Footage: Real display changes; camera footage labelled synthetic if it is a test source. 25. Diagnostics, flight recorder and the virtual Fault Lab (7–9 minutes) Collect useful source/state evidence, export diagnostics and practise fault interpretation without confusing a twin with hardware qualification. Prerequisites: Basic recovery knowledge; virtual environment for fault injection Footage: Diagnostic export, traffic/flight-recorder views and explicitly virtual fault scenarios.