Archive for category Soapbox Snap
With more users come more bug reports (thanks Reza!) so this release includes two useful bug fixes:
- A few people have been complaining about an error when compiling the ArduinoFirmware.ino sketch about the timerISR function. It only showed up on some computers. This version fixes that bug.
- There’s a bug where, if you link an output to an internal coil, and then delete the internal coil, the saved file can’t be opened again. This version provides a work-around where it breaks the link upon opening it, which at least lets you get to your program and fix the problem.
I’ve also added a new Up/Down Counter instruction. This instruction works a bit differently than the Count Up and Down Down timers. It counts up on the rising edge of the rung-in condition. It has a separate Count Down input which causes the internal count to decrement by 1 with each rising edge. It also has a Reset input, which sets the internal count back to zero (and it’s reset-dominant, so as long as Reset is on, it ignores the Count Up and Count Down pulses). The rung-out (or output coil) is on when the internal counter is zero, and false otherwise.
You can download the new version over at the SoapBox Snap Project Page.
Traditional PLCs let you peek and poke at memory addresses directly with commands like MOVE, etc. In SoapBox Snap, the ladder language is designed around a more strict Functional Programming model, but that doesn’t mean you can’t conditionally latch a number into a memory location.
Let’s examine the case where you have an analog input (A0) and you want to capture the value of A0 on the rising edge of one of the discrete inputs (pin2). The Choose Number instruction acts like a memory register if you set the second numeric input to itself:
Take a look at how the Choose Number instruction selects value A0 when the input turns on, but otherwise chooses its own value. This creates a form of internal state, similar to a sealed in coil.
Happy New Year!
An astute SoapBox Snap user pointed out a problem with the counter function blocks in the Arduino Runtime over the holidays (thanks Miguel!) and I tracked down the bug and fixed it. The bug was there all along but only seems to cause problems on newer versions of the Arduino compiler.
Please download version 2016.01.03 of SoapBox Snap and make sure you download the Arduino Sketch to your board to get the fix. You can get the latest download on the SoapBox Snap product page.
This version also fixes a bug in the new Export Signal Table function of the Arduino Runtime.
SoapBox Snap version 2015.11.01 has just been released, with a bug fix (dragging and dropping an instruction to the left of itself could cause an editor crash) and a new feature: the ability to export a lookup table of signals and addresses to a CSV file (for the Arduino Runtime).
If you’re using the Arduino Runtime for SoapBox Snap and you want to hook it up to something over the serial port, you’ll need to be able to read and write signal values. Due to space limitations in the Arduino, storing the lookup table between signal name and address is just too costly, so there was no easy way to figure out which address your coil signal was in. This release adds an Export Signal Table feature to solve this problem.
Go to Tools -> Options… and find the SoapBox Snap Arduino Runtime options page. Check the box called Export Signal Table, and enter a (fully qualified) directory where you want the table exported to. Now every time you do a download of your program to the Arduino, Snap will create a CSV file listing the address, signal type, signal name, and the comment. Now you can lookup which address corresponds to which signal name.
SoapBox Snap version 2015.01.11 has just been released! You can download it from over at the SoapBox Snap Project Page.
This version adds support for the Arduino Mega, meaning you can now have a whopping 16 analog inputs and use all the way up to pin 53 on the Mega board. The Mega also supports almost 5 times as much space for your ladder logic program and more memory for discrete and numeric (i.e. analog) signals.
Additionally I’ve added support for analog outputs (for the Uno, Nano, and Mega). On the Uno and Nano boards, pins 3, 5, 6, 9, 10, and 11 are configurable as “PWM” (i.e. pulse width modulated) outputs. On the Mega board you can use pins 2 to 12 and 44 to 46. SoapBox Snap now supports configuring these pins as PWM outputs (using the new config-pwm command) which will make the pins show up under the Analog Outputs list rather than the Discrete Outputs list. In your ladder program, you can control these analog outputs by connecting a signal and driving it with any value from 0 to 255, and the output will vary accordingly.
I’ve updated the SoapBox Snap Arduino Tutorial.
SoapBox Snap version 2014.07.06 has just been released! You can download it from over at the SoapBox Snap Project Page.
This version adds an Arduino runtime, meaning you can now download SoapBox Snap ladder logic programs to an Arduino and use your Arduino like a PLC. Currently it’s compatible with the Arduino UNO and Nano boards (R3). The SoapBox Snap download includes a firmware sketch (written in C++) which you’ll have to upload to the Arduino in the normal way.
To get you started, I’ve written a complete SoapBox Snap Arduino Tutorial.
As usual, SoapBox Snap, and the SoapBox Snap Arduino Runtime code, is released as open source.
Note that this version of SoapBox Snap no longer has the Game Controllers module in it (due to installer issues). That means the original soft runtime won’t support joysticks and other game controllers.
Here’s a sneak peek of the next SoapBox Automation project: adding an Arduino runtime for SoapBox Snap. That means you can use an Arduino just like a PLC, including forcing I/O and online debugging. Here’s a picture of the ladder diagram while online with the Arduino:
…and here’s the Arduino test circuit:
The initial version will have support for the UNO (R3) and the Nano (R3) versions of the Arduino boards. The ladder logic is stored in the internal EEPROM of the chip.
As always, all of the source code, including the Arduino sketch that allows it to act like a PLC, will be released as open source under a GPLv3 license. More will be coming soon.
If you tried SoapBox Snap with a 64-bit operation system and had a problem, we apologize. If you try the new download, it should work better for you.
We’ve just put a new version of SoapBox Snap up for download (version 2011.03.01). This version adds a new I/O driver for DirectX compatible game controllers.
If you have an old joystick, racing wheel, or game pad for your PC lying around, you can now use it to drive discrete and analog inputs in your SoapBox Snap ladder logic program. SoapBox Snap will automatically detect your game controllers the same way it auto-detects Phidgets devices:
- Connect to the runtime
- Under the runtime node, right click on Device Configuration
- Click the Read Configuration option
That forces you to disconnect from the runtime after reading the configuration. You can just re-connect and choose to download your application if you want to try it out right away. You will be able to see the discrete inputs light up when you press the buttons on your controller. To see the analog inputs (axes) working, you’ll need to use those somewhere in your logic.
What’s next? New drivers for even more I/O hardware… stay tuned!
Version 2010.11.15 of SoapBox Snap is now available for download. It includes 11 new Math and Comparison operators for the ladder logic module. This fills in most of the missing functionality you need to make good use of the NUMBER type in your applications.
Let’s step back and talk about types for a minute. SoapBox Snap only has 3 types:
That’s a really lean type system compared to most PLCs (but of course, “Snap is not a PLC”). If you’ve done much traditional PLC programming, you would expect to see a dozen different numeric types, like BYTE, INT, UINT, DINT, UDINT, not to mention SINGLE, and DOUBLE precision floating point numbers, and various BCD numbers if you’re really lucky. At first when I was writing SoapBox Snap, I planned to support every data type in the IEC-61131-3 standard, but I realized all those types only existed because traditional PLCs are so memory constrained that you had to take memory usage and low level memory management into account when you use them. One of the goals of SoapBox Snap is to remove the burden of memory management from the programmer. That’s why there’s only one NUMBER type and it can represent any number.
SoapBox Snap already used the NUMBER type in the Counter and Timer instructions that shipped with the first version. The counters expose a Count output that you can access just like any other signal. Likewise, the timers expose an Elapsed output (in milliseconds). Of course, all analog inputs in your Device Configuration also expose NUMBER type signals, and all analog outputs consume NUMBER type signals, so now you can manipulate all of these signals with the new instructions below.
The new math instructions carry out your four basic mathematical operations: add, subtract, multiply, and divide. Each takes two NUMBER inputs, and produces a single NUMBER output. Since a result is generated, all of these instructions are considered “right hand” instructions (that is, they show up on the right hand side of the rung). They all use the rung-in condition to enable the operation. If the rung condition feeding the instruction is false, the result stays the same as it was during the previous scan. If the rung condition is true, the result is overwritten with the new result of applying the operation to the two inputs.
There is one exception: if the second input to the divide instruction is zero, it disables the instruction from executing, so the result will stay the same as the last scan. There are various alternative ways it could handle a divide-by-zero condition (throwing an error, setting the result to zero or infinity, etc.), but I thought that holding the last “good” value was the most reasonable thing to do.
These are your basic comparison operators. They are all “left hand” instructions, so they go on the left side of the rung, where you normally use contacts. Each one takes two NUMBER inputs, just like a Math instruction, but doesn’t generate an output, other than the rung-out condition. If the rung-in condition is false, the rung-out condition will always be false. If the rung-in condition is true, the instruction will read both inputs, apply the comparison, and set the rung-out condition to the result of the comparison. Therefore you can chain these comparison operators together on the same rung (for instance to say A > 250 and A < 750).
Similar to the Math instructions (in that it has two NUMBER inputs and one NUMBER result) is the new Choose Number instruction. This instruction copies the first input to the result if the rung-in condition is true, and otherwise it copies the second input to the result. If you use this instruction in combination with a Greater Than instruction, then you can easily implement a Maximum instruction. That is, if A > B, return A, else return B.
There are some small features we’re going to be adding to SoapBox Core shortly. After that we’ll come back to adding some new features to SoapBox Snap, so keep watching this space for updates. Remember, contact us if you have any questions, or post a question on the support site. Most of you like to email me directly, which is just fine. 🙂