This widget shows smoothie specific controls and current status information.
All ChiliPeppr widgets/elements are defined using cpdefine() which is a method that mimics require.js. Each defined object must have a unique ID so it does not conflict with other ChiliPeppr widgets.
| Item | Value |
|---|---|
| ID | com-chilipeppr-widget-Smoothie |
| Name | Widget / Smoothieboard |
| Description | This widget shows smoothie specific controls and current status information. |
| chilipeppr.load() URL | http://raw.githubusercontent.com/https://master/auto-generated-widget.html |
| Edit URL | http://ide.c9.io/jarretluft/widget-smoothie |
| Github URL | http://github.com/https:/ |
| Test URL | https://preview.c9users.io/jarretluft/widget-smoothie/widget.html |
You can use the code below as a starting point for instantiating this widget inside a workspace or from another widget. The key is that you need to load your widget inlined into a div so the DOM can parse your HTML, CSS, and Javascript. Then you use cprequire() to find your widget's Javascript and get back the instance of it.
// Inject new div to contain widget or use an existing div with an ID
$("body").append('<' + 'div id="myDivWidgetSmoothie"><' + '/div>');
chilipeppr.load(
"#myDivWidgetSmoothie",
"http://raw.githubusercontent.com/https://master/auto-generated-widget.html",
function() {
// Callback after widget loaded into #myDivWidgetSmoothie
// Now use require.js to get reference to instantiated widget
cprequire(
["inline:com-chilipeppr-widget-Smoothie"], // the id you gave your widget
function(myObjWidgetSmoothie) {
// Callback that is passed reference to the newly loaded widget
console.log("Widget / Smoothieboard just got loaded.", myObjWidgetSmoothie);
myObjWidgetSmoothie.init();
}
);
}
);This widget/element publishes the following signals. These signals are owned by this widget/element and are published to all objects inside the ChiliPeppr environment that listen to them via the chilipeppr.subscribe(signal, callback) method. To better understand how ChiliPeppr's subscribe() method works see amplify.js's documentation at http://amplifyjs.com/api/pubsub/
| Signal | Description |
|---|---|
| /com-chilipeppr-widget-Smoothie/com-chilipeppr-interface-cnccontroller/feedhold | Feedhold (Emergency Stop). This signal is published when user hits the Feedhold button for an emergency stop of the Smoothie. Other widgets should see this and stop sending all commands such that even when the plannerresume signal is received when the user clears the queue or cycle starts again, they have to manually start sending code again. So, for example, a Gcode sender widget should place a pause on the sending but allow user to unpause. |
| /com-chilipeppr-widget-Smoothie/com-chilipeppr-interface-cnccontroller/plannerpause | This widget will publish this signal when it determines that the planner buffer is too full on the Smoothie and all other elements/widgets need to stop sending data. You will be sent a /plannerresume when this widget determines you can start sending again. The Smoothie has a buffer of 28 slots for data. You want to fill it up with around 12 commands to give the planner enough data to work on for optimizing velocities of movement. However, you can't overfill the Smoothie or it will go nuts with buffer overflows. This signal helps you fire off your data and not worry about it, but simply pause the sending of the data when you see this signal. This signal does rely on the Smoothie being in {qv:2} mode which means it will auto-send us a report on the planner every time it changes. This widget watches for those changes to generate the signal. The default setting is when we hit 12 remaining planner buffer slots we will publish this signal. |
| /com-chilipeppr-widget-Smoothie/com-chilipeppr-interface-cnccontroller/plannerresume | This widget will send this signal when it is ok to send data to the Smoothie again. This widget watches the {qr:[val]} status report from the Smoothie to determine when the planner buffer has enough room in it to send more data. You may not always get a 1 to 1 /plannerresume for every /plannerpause sent because we will keep sending /plannerpause signals if we're below threshold, but once back above threshold we'll only send you one /plannerresume. The default setting is to send this signal when we get back to 16 available planner buffer slots. |
| /com-chilipeppr-widget-Smoothie/com-chilipeppr-interface-cnccontroller/axes | This widget will normalize the Smoothie status report of axis coordinates to send off to other widgets like the XYZ widget. The axes publish payload contains {x:float, y:float, z:float, a:float} If a different CNC controller is implemented, it should normalize the coordinate status reports like this model. The goal of this is to abstract away the specific controller implementation from generic CNC widgets. |
| /com-chilipeppr-widget-Smoothie/com-chilipeppr-interface-cnccontroller/units | This widget will normalize the Smoothie units to the interface object of units {units: "mm"} or {units: "inch"}. This signal will be published on load or when this widget detects a change in units so other widgets like the XYZ widget can display the units for the coordinates it is displaying. |
| /com-chilipeppr-widget-Smoothie/com-chilipeppr-interface-cnccontroller/proberesponse | Publish a probe response with the coordinates triggered during probing, or an alarm state if the probe does not contact a surface |
| /com-chilipeppr-widget-Smoothie/com-chilipeppr-interface-cnccontroller/status | Publish a signal each time the Smoothie status changes |
This widget/element subscribes to the following signals. These signals are owned by this widget/element. Other objects inside the ChiliPeppr environment can publish to these signals via the chilipeppr.publish(signal, data) method. To better understand how ChiliPeppr's publish() method works see amplify.js's documentation at http://amplifyjs.com/api/pubsub/
| Signal | Description |
|---|---|
| /com-chilipeppr-widget-Smoothie/com-chilipeppr-interface-cnccontroller/jogdone | We subscribe to a jogdone event so that we can fire off an exclamation point (!) to the Smoothie to force it to drop all planner buffer items to stop the jog immediately. |
| /com-chilipeppr-widget-Smoothie/com-chilipeppr-interface-cnccontroller/recvgcode | Subscribe to receive gcode from other widgets for processing and passing on to serial port |
This widget/element publishes to the following signals that are owned by other objects. To better understand how ChiliPeppr's subscribe() method works see amplify.js's documentation at http://amplifyjs.com/api/pubsub/
| Signal | Description |
|---|---|
| /com-chilipeppr-widget-Smoothie/com-chilipeppr-widget-serialport/send | We send to the serial port certain commands like the initial configuration commands for the Smoothie to be in the correct mode and to get initial statuses like planner buffers and XYZ coords. We also send the Emergency Stop and Resume of ! and ~ |
This widget/element publishes to the following signals that are owned by other objects. To better understand how ChiliPeppr's publish() method works see amplify.js's documentation at http://amplifyjs.com/api/pubsub/
| Signal | Description |
|---|---|
| /com-chilipeppr-widget-Smoothie/com-chilipeppr-widget-serialport/ws/onconnect | When we see a new connect, query for status. |
| /com-chilipeppr-widget-Smoothie/com-chilipeppr-widget-serialport/recvline | When we get a dataline from serialport, process it and fire off generic CNC controller signals to the /com-chilipeppr-interface-cnccontroller channel. |
| /com-chilipeppr-widget-Smoothie/com-chilipeppr-widget-serialport/send | Subscribe to serial send and override so no other subscriptions receive command. |
The table below shows, in order, the methods and properties inside the widget/element.
| Method / Property | Type | Description |
|---|---|---|
| id | string | "com-chilipeppr-widget-Smoothie" The ID of the widget. You must define this and make it unique. |
| name | string | "Widget / Smoothieboard" |
| desc | string | "This widget shows smoothie specific controls and current status information." |
| url | string | "http://raw.githubusercontent.com/https://master/auto-generated-widget.html" |
| fiddleurl | string | "http://ide.c9.io/jarretluft/widget-smoothie" |
| githuburl | string | "http://github.com/https:/" |
| testurl | string | "http://widget-smoothie-jarretluft.c9users.io/widget.html" |
| publish | object | Please see docs above. Define the publish signals that this widget/element owns or defines so that other widgets know how to subscribe to them and what they do. |
| subscribe | object | Please see docs above. Define the subscribe signals that this widget/element owns or defines so that other widgets know how to subscribe to them and what they do. |
| foreignPublish | object | Please see docs above. Document the foreign publish signals, i.e. signals owned by other widgets or elements, that this widget/element publishes to. |
| foreignSubscribe | object | Please see docs above. Document the foreign subscribe signals, i.e. signals owned by other widgets or elements, that this widget/element subscribes to. |
| config | object | All widgets should have an init method. It should be run by the instantiating code like a workspace or a different widget. |
| err_log | object | |
| buffer_name | string | |
| report_mode | number | |
| work_mode | number | |
| controller_units | object | |
| status | string | "Offline" |
| version | string | |
| q_count | number | |
| alarm | boolean | |
| offsets | object | |
| last_work | object | |
| last_machine | object | |
| g_status_reports | object | |
| gcode_lookup | object | |
| init | function | function () |
| btnSetup | function | function () Call this method from init to setup all the buttons when this widget is first loaded. This basically attaches click events to your buttons. It also turns on all the bootstrap popovers by scanning the entire DOM of the widget. |
| updateWorkUnits | function | function (units) |
| updateReportUnits | function | function () |
| openController | function | function (isWithDelay) |
| closeController | function | function (isWithDelay) |
| getControllerInfo | function | function () |
| trackGcodeLines | function | function () |
| restartStatusInterval | function | function () |
| SmoothieResponse | function | function (recvline) |
| sendCode | function | function (sendline) |
| clearBuffer | function | function () |
| publishAxisStatus | function | function (axes) |
| plannerLastEvent | string | "resume" |
| publishPlannerPause | function | function () |
| publishPlannerResume | function | function () |
| toInch | function | function (mm) |
| toMM | function | function (inch) |
| addError | function | function (line, msg) |
| options | object | User options are available in this property for reference by your methods. If any change is made on these options, please call saveOptionsLocalStorage() |
| setupUiFromLocalStorage | function | function () Call this method on init to setup the UI by reading the user's stored settings from localStorage and then adjust the UI to reflect what the user wants. |
| saveOptionsLocalStorage | function | function () When a user changes a value that is stored as an option setting, you should call this method immediately so that on next load the value is correctly set. |
| showBody | function | function (evt) Show the body of the panel. evt ({jquery_event}) - If you pass the event parameter in, we know it was clicked by the user and thus we store it for the next load so we can reset the user's preference. If you don't pass this value in we don't store the preference because it was likely code that sent in the param. |
| hideBody | function | function (evt) Hide the body of the panel. evt ({jquery_event}) - If you pass the event parameter in, we know it was clicked by the user and thus we store it for the next load so we can reset the user's preference. If you don't pass this value in we don't store the preference because it was likely code that sent in the param. |
| forkSetup | function | function () This method loads the pubsubviewer widget which attaches to our upper right corner triangle menu and generates 3 menu items like Pubsub Viewer, View Standalone, and Fork Widget. It also enables the modal dialog that shows the documentation for this widget. By using chilipeppr.load() we can ensure that the pubsubviewer widget is only loaded and inlined once into the final ChiliPeppr workspace. We are given back a reference to the instantiated singleton so its not instantiated more than once. Then we call it's attachTo method which creates the full pulldown menu for us and attaches the click events. |
| uiHover | function | function () |
ChiliPeppr is a hardware fiddle, meaning it is a website that lets you easily create a workspace to fiddle with your hardware from software. ChiliPeppr provides a Serial Port JSON Server that you run locally on your computer, or remotely on another computer, to connect to the serial port of your hardware like an Arduino or other microcontroller.
You then create a workspace at ChiliPeppr.com that connects to your hardware by starting from scratch or forking somebody else's workspace that is close to what you are after. Then you write widgets in Javascript that interact with your hardware by forking the base template widget or forking another widget that is similar to what you are trying to build.
ChiliPeppr is massively capable such that the workspaces for TinyG and Grbl CNC controllers have become full-fledged CNC machine management software used by tens of thousands.
ChiliPeppr has inspired many people in the hardware/software world to use the browser and Javascript as the foundation for interacting with hardware. The Arduino team in Italy caught wind of ChiliPeppr and now ChiliPeppr's Serial Port JSON Server is the basis for the Arduino's new web IDE. If the Arduino team is excited about building on top of ChiliPeppr, what will you build on top of it?