Testing function of WebIDE is used to visualize and control testing.
Attached is source of the project and testing file.
Testing file works with project option. Copy testing file to sub folder testing in your local project folder. Project and testing needs to be activated in options. You will find links to tours for project and testing there too.
Some short explanation about alarms in processing units.
In technical plants you often have a board which reflects actual status of the unit. Usually there are meters and lot of lamps. These lamps can be grouped to
alarm, something bad happened like temperatur too high
warning, somebody should take a look like flow is below 35%
status, pump is running
Usually alarms are blinking(red) and stay blinking until pushing reset.
Warnings do the same but have a different reset button.
After reset alarm- and warning-lamps are on, until alarm or warning is off.
Status lamps only show actual status and are on or off.
Common question is "which alarm came first". Imagine having a water pump.
This pump should not run dry, to avoid damages. And pump should not be too hot for same reason. Therefore pump shuts off if temp is too high or no flow is detected.
This happens very fast, and you would see 3 alarms, Temp too high, no Flow and Pump off. All are comin in at same time, at least for your eyes.
For root cause analysis you would need to know the sequence of alarms.
All of this is available in attached source. There are some more explanations in source.
During testing I found a bug in WebIDE(sorry, my fault), its already fixed in Github by Gordon. For now you need to use actual version from github until next rollout which may also have 1st version of compiling in, hopefully ...
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
My new project is an alarming unit for Espruino.
Testing function of WebIDE is used to visualize and control testing.
Attached is source of the project and testing file.
Testing file works with project option. Copy testing file to sub folder testing in your local project folder. Project and testing needs to be activated in options. You will find links to tours for project and testing there too.
Some short explanation about alarms in processing units.
In technical plants you often have a board which reflects actual status of the unit. Usually there are meters and lot of lamps. These lamps can be grouped to
Usually alarms are blinking(red) and stay blinking until pushing reset.
Warnings do the same but have a different reset button.
After reset alarm- and warning-lamps are on, until alarm or warning is off.
Status lamps only show actual status and are on or off.
Common question is "which alarm came first". Imagine having a water pump.
This pump should not run dry, to avoid damages. And pump should not be too hot for same reason. Therefore pump shuts off if temp is too high or no flow is detected.
This happens very fast, and you would see 3 alarms, Temp too high, no Flow and Pump off. All are comin in at same time, at least for your eyes.
For root cause analysis you would need to know the sequence of alarms.
All of this is available in attached source. There are some more explanations in source.
During testing I found a bug in WebIDE(sorry, my fault), its already fixed in Github by Gordon. For now you need to use actual version from github until next rollout which may also have 1st version of compiling in, hopefully ...
1 Attachment