What technologies can/should I potentially explore?
What issues could I be faced with?
What have I not considered/overlooked?
Is the Tin Can (xAPI) a solution in this instance?
Can Lectora recieve Tin Can statements from an LRS (I know it can submit)?
The choice of technology depends on a number of factors. How far is the “push button” from the Lectora course? Is the button some ready-made device or you have access to it and can e.g. solder something in? Does it have to be wired or wireless? Where is the course running (PC, tablet, kiosk, smth else)? Should the course communicate back to the button somehow (to e.g. buzz / vibrate / light up)?
If you provide a bit more information on the exact scenario, I’ll be happy to help find suitable tech to make it happen.
Im glad to have caught your interest. Yes projects like this is what keeps us going, pushing the boundaries helps us stay ahead of the industry.
The game plan is to have course running on a touchscreen next to the device. Both the device as well and the screen will be running from the same system.
Picture a touchscreen sitting above an external device with 4 switches with integrated LED’s and maybe even a gauge. This device is already fully functional and can pass values of each switches state to an external file. If we can find a common communication channel that Lectora can read/write to then these switches states can change as well. Therefore giving us a flexible solution that will allow both Lectora content to control the device and the device to control Lectora content.
Alternatively, you can wire your buttons to a HID USB controller so they act like a normal keyboard. You can then intercept keystrokes using normal Lectora functionality.