Skip to content

Commit

Permalink
Updated readme
Browse files Browse the repository at this point in the history
Changed the description of file loading/dumping
  • Loading branch information
frivolas authored Jun 8, 2017
1 parent 0f8632c commit 593f754
Showing 1 changed file with 13 additions and 3 deletions.
16 changes: 13 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,9 +2,13 @@
By Oscar Frias - September 2016
www.oscarfrias.com

__TinyTerm__, a quick script to create a terminal-like interface that allows the user to control a [tinyG](http://synthetos.myshopify.com/products/tinyg) connected via Serial to the computer. It provides a textArea to show the history of the communication between the tinyG and the computer, and a textfield to allow the user to inject GCode commands or tinyG commands to the tinyG on the fly.
__TinyTerm__, a quick [Processing](www.processing.org) script to create a terminal-like interface that allows the user to control a [tinyG](http://synthetos.myshopify.com/products/tinyg) connected via Serial to the computer. It provides a textArea to show the history of the communication between the tinyG and the computer, and a textfield to allow the user to inject GCode commands or tinyG commands to the tinyG on the fly.

TinyTerm starts by loading an init.json file from the /data folder. This JSON file contains all the desired init settings for the tinyG. For a complete list of commands and settings, please take a look at the [tinyG Wiki](https://github.com/synthetos/TinyG/wiki/TinyG-Configuration-for-Firmware-Version-0.97). The JSON file needs to have a JSONArray named _"commands"_ contained in a JSONObject:
TinyTerm allows to load and dump files into the tinyG in either text or JSON format. TinyTerm looks for the file extension and determnies if the file is a JSON or any other format.

If a JSON, TinyTerm will try to parse it following Pensa's schema for init files. Otherwise, if not a JSON, TinyTerm will treat it as a plain text file and dump all the contents to the tinyG.

An initialization, config, or _init_ file could be created containing all the desired init settings for the tinyG. For a complete list of commands and settings, please take a look at the [tinyG Wiki](https://github.com/synthetos/TinyG/wiki/TinyG-Configuration-for-Firmware-Version-0.97). Such file should be in JSON format and in the schema, have a JSONArray named _"commands"_ contained in a JSONObject:

```css
{
Expand All @@ -16,7 +20,13 @@ TinyTerm starts by loading an init.json file from the /data folder. This JSON fi
}
```

You can have as many commands as necessary. Some of our init files have dozens of commands. It all depends on how many axes and inputs you want to initialize with this file. Just make sure the JSON file is clean, and valid. Make liberal use of the [JSON lint](http://jsonlint.com).
You could have as many commands as necessary (some of our init files have dozens of commands!), all depending on how many axes and inputs you want to initialize with this file. Just make sure the JSON file is clean, and valid. Make liberal use of the [JSON lint](http://jsonlint.com).

To run GCode scripts on your tinyG, just save them as text files (.txt, .cnc, .nc, etc) and load them with TinyTerm.

Once a file has been loaded, a "Re-dump file" button will appear, allowing for quick re-running of the script.

TinyTerm will wait and look for a serial device to be plugged on a USB port and hold the interface until something is connected (not checking specifically for a tinyG, though). Once a connection has been established, the interface can be used.

The GUI is created with the [ControlP5](http://www.sojamo.de/libraries/controlP5/) library by [Sojamo](https://github.com/sojamo), so make sure you have this library installed before running this script.

Expand Down

0 comments on commit 593f754

Please sign in to comment.