For schools and colleges
A robotics lab that runs on the computers your lab already has. Students wire real components, write real Arduino code, and it is compiled by the real toolchain and run on a simulated AVR chip. Nothing to order, nothing to replace, nothing to store.
The first levels are free, for as many students as you like. No purchase order needed to put a class through them. A person reads the email and replies — there is no form and no queue.
The hard part of teaching electronics is rarely the electronics. It is thirty students, one cupboard, and forty minutes.
One kit between two or three, so most of the class watches somebody else wire it.
One bench per student. Thirty students, thirty circuits, all running at once.
A loose jumper wire looks exactly like a bug in the code, and eats the period.
The circuit names its own faults. A student reads the cause instead of hunting for it.
Parts go missing, come back bent, or quietly stop working halfway through a term.
Nothing wears out. A wrong connection costs nothing — undo it and go again.
Handing out and packing away takes the first and last ten minutes of the lesson.
The lesson opens in a browser tab. Sign in, and the wiring is where they left it.
A student who misses the practical has missed it.
The seat belongs to the student, not the machine. It works from home too.
A course that runs from a blinking LED to a robot that follows a line. Every level is graded on what the circuit actually did, not on whether a box was ticked. New levels are added to the same seat.
A seat is one student, for the length of your licence. You buy a number of them; we attach them to the accounts you name.
One per student in the classes that will use it. A seat you have not handed out is a seat you can still hand out later in the term.
They sign in with Google or GitHub. Nothing for you to create, no passwords to reset, no accounts to hand back at the end of the year.
We give you a join code. A student signs in, types it, and the seat attaches to that account — nothing for you to import and no accounts for you to create. Codes can be capped and switched off, and a code is not access: the seat count is still the ceiling.
We revoke that seat and it goes to the next student. Access is a grant we can withdraw, not a password that has escaped.
The free levels need no seat and no payment. Put a whole class through them and decide afterwards.
Every submission is stored, per student and per level: whether it compiled, the compiler error if it did not, which of the level’s checks passed, and the wiring and code that produced that result. “Who is stuck, and on what” is a question the data answers.
Some of that reaches the student first. A circuit that will not work says why, in words, while they are still looking at it:
The ULN2003 board has no power on VCC (+). Wire it to 5V.
That is a real message from the simulator. A dead motor names its own cause, so the student is not queueing at your desk to find out why nothing moved.
Be clear about the shape of this. There is a live roster — who has joined, how far each one has got, and who has not opened it in a week — and that is the screen you will use on a Monday. Reading an individual submission back, attempt by attempt, is still a report we run for you.
The seat is the cost. There is nothing per student on top of it.
No components to replace, no batteries, no jumper wires, no breadboards that stop gripping. Nothing is bought twice.
It runs in a browser on the machines you already have. No boards, no USB drivers, no software to install, no administrator rights to request.
Nothing to lock in a cupboard, count at the end of term, or replace when it walks off.
A student cannot damage anything by wiring it wrongly, so a broken bench is never on somebody’s repair list.
Per seat, per year — talk to us. It depends on how many seats and how long a term you want, and we would rather quote you honestly than put a number here that we would then argue about. What the lab needs on top: computers with a current browser, and working internet, because the compile happens on our servers.
You would find all of this out in the first week. Better here.
Tell us the size of the group and when your term starts, and we will tell you what it would cost and what it would take to set up. If it is not right for your lab, we will say so.
Email info@abilityfusion.comIt goes to an inbox a person reads, and a person replies. There is no form, no ticket number and no sales sequence.