Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
blocks:app-note:isaac [2024-01-22 11:07] mattias |
blocks:app-note:isaac [2024-01-22 13:47] (current) mattias |
||
---|---|---|---|
Line 1: | Line 1: | ||
=====ISAAC integration===== | =====ISAAC integration===== | ||
- | This application note shows the steps involved in setting up Blocks to communicate with Smart Monkeys ISAAC A/V monitor and management system. | + | This application note shows the steps involved in setting up Blocks to communicate with [[https:// |
- | ===Setup the Issac device=== | + | ===The Isaac device=== |
Please follow the vendors documentation for the device setup. This documentation aims to explain the necessary steps to be taken in Blocks. | Please follow the vendors documentation for the device setup. This documentation aims to explain the necessary steps to be taken in Blocks. | ||
- | The Pixilab Blocks module must be loaded in Isaac. | + | |
===Make the driver available to the server=== | ===Make the driver available to the server=== | ||
- | Copy the driver files Isaac.js (driver) and Issac.ts (source code file) from the drivers-archive to the drivers directory in PIXILAB-Block-root/ | + | Copy the driver files Isaac.js (driver) and Isaac.ts (source code file) from the drivers-archive to the drivers directory in PIXILAB-Block-root/ |
- | ===Configure the driver | + | ===Configure the driver === |
- | Open the blocks editor and add the Issac system as a Network device. | + | Open the blocks editor and add the Issac system as a Network device. |
A typical example will look like this: | A typical example will look like this: | ||
+ | |||
< | < | ||
{ | { | ||
Line 18: | Line 19: | ||
" | " | ||
" | " | ||
- | " | + | " |
- | " | + | " |
} | } | ||
</ | </ | ||
+ | |||
Where: | Where: | ||
// | // | ||
- | //token// (optional, string) is passed in the issac-token header, only to be used in case Isaac is configured to use a token. | + | //token// (optional, string) is passed in the isaac-token header, only to be used in case Isaac is configured to use a token. |
// | // | ||
- | // | + | // |
+ | |||
+ | //events// (optional, string array) An array of tasks specified as name.group.task | ||
+ | |||
+ | |||
+ | ===Sending log messages from Blocks=== | ||
+ | |||
+ | The driver exposes a callable named //log// that can be used in task programming to log messages to ISAAC. | ||
+ | |||
+ | ===Steps in ISSAC=== | ||
+ | |||
+ | Register the Pixilab Blocks module under setup/ | ||
+ | The events and the variables specified in the driver will be added automatically. Please note, full-stop and commas are prohibited in the ISAAC scheduler so edit the name of the variables and events once discovered in ISAAC. | ||
+ | At this point it is possible to use the schedules in ISAAC to run any of the specified tasks by scheduling that event at a specific time. It is also possible to track any changes to specified | ||
- | //events// (optional, string array) An array of full paths to tasks exposed as Isaac events. | + | Please use the vendors documentation for any details on how to use ISAAC. |