CANtap Studio tutorials: Hardware and channels 🎬

Is everything really wired the way you think it is? A test that fails because a cable sits on the wrong port, or a channel runs at the wrong bitrate, costs an afternoon and proves nothing about the ECU. This chapter connects CANtap Studio to the bus and shows how it tells you, in plain words, whether the wiring is what you expect. Boards belong to your computer: you add each PTW CANtap once, and it is known by its serial number, so it is found again even when it comes back on a different USB port. Channels belong to the project: "channel 1 is the ECU's bus, 500 kbit/s, active". Hardware → Channels joins the two: which board, and which of its two ports, serves each bus on your desk. In this 4-minute video: ▸ Devices: the port list shows only CANtap boards, never the computer's other serial devices ▸ Channels: bitrate and mode, the split termination centre tap, and CAN FD with its own data bitrate ▸ Start: every board opened at once and set as the project says, with one line per board on what was applied ▸ The Bench setup tab: where every frame comes from and where it goes, with live frames per second ▸ Test Devices: firmware, bus state, the bitrate and mode actually applied, and errors by kind, each with what to do about it ▸ The frame test: each channel sends one probe, and you see who hears whom ▸ Self-test and Scan bitrate: one port checked on its own, and the traffic's rate found by listening only, safe on a vehicle ▸ The Device Console: commands to one board by hand, a single frame by id and data, and a remote reboot The video runs on two simulated boards so every step is easy to follow. The dialogs are the real ones, and they work the same with real PTW CANtap boards. Next chapter: databases, the Monitor and the Trace. #CANtap #CANtapStudio #CANbus #CANFD #AutomotiveTesting #TestAutomation #EmbeddedSystems #Python #HIL #ECU #UDS #VehicleDiagnostics #ProTektWar