LaserWeb / deprecated-LaserWeb2

Deprecated: use http://github.com/openhardwarecoza/LaserWeb3 instead
41 stars 21 forks source link

Comms module: TinyG #36

Closed Cinezaster closed 8 years ago

Cinezaster commented 8 years ago

Creating the communication layer between laserweb2 and TinyG - TinyG2

ghost commented 8 years ago

Don't know if this would help but @giseburt wrote https://www.npmjs.com/package/tinyg which could contain some value

Cinezaster commented 8 years ago

It is mainly for the serial connection and it is a low level implementation it doesn't abstract the communication from the tinyG into interpretable data.
Nicely written library, he put in a lot of work into it and not only in the code but also the documentation.

Cinezaster commented 8 years ago

On connecting with the device we need a command we can send to recognize which device is connected. TinyG2 is silent on connect.

This command must be a unique command for tinyG and/or TinyG2 (their behaviour seems the same). I suggest: {sys:n} this returns the system group of TinyG

ghost commented 8 years ago

Since the user has to select the Buffer for Serial Port Json Server already, we could use that as an 'assumption' that it is a tinyg?

In laserweb1 I did this https://github.com/openhardwarecoza/LaserWeb/blob/master/server.js#L174-L177

Chilipeppr also checks for $fb (firmware build) On 3 May 2016 08:28, "Cinezaster" notifications@github.com wrote:

On connecting with the device we need a command we can send to recognize which device is connected. TinyG2 is silent on connect.

This command must be a unique command for tinyG and/or TinyG2 (their behaviour seems the same). I suggest: {sys:n} this returns the system group of TinyG https://github.com/synthetos/g2/wiki/Configuration-for-Firmware-Version-0.98#system-group

— You are receiving this because you commented. Reply to this email directly or view it on GitHub https://github.com/openhardwarecoza/LaserWeb2/issues/36#issuecomment-216448499

Cinezaster commented 8 years ago

The buffer select could indeed be the solution.

Never the less, I like to import all data from the device into laserweb. For later use The $fb command returns a less parseable response compared to the {fb:n} command which returns json.

I found a Arduino Due and flashed it with TinyG2. Would be great if someone could send me a list of all the settings of a realistic machine. Don't want to spend time configuring one.

ghost commented 8 years ago

I'll nudge the guys on Google Plus again...

PS: no objection against $fb vs $fb:n