Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TinyG reported an error reading '{"clr":null}' #8

Open
brettdaman opened this issue Nov 2, 2017 · 0 comments
Open

TinyG reported an error reading '{"clr":null}' #8

brettdaman opened this issue Nov 2, 2017 · 0 comments

Comments

@brettdaman
Copy link

When I open tinyG in node on my rpi3 I immediately get 2 errors thrown from the tinyG.

error { [TinyGResponseError: TinyG reported an error reading '{"clr":null}': 100 (based on 13 bytes read)] name: 'TinyGResponseError', message: 'TinyG reported an error reading \'{"clr":null}\': 100 (based on 13 bytes read)', data: { r: { clr: null }, f: [ 1, 100, 13, 4451 ] } } error { [TinyGResponseError: TinyG reported an error reading '{"clr":null}': 100 (based on 13 bytes read)] name: 'TinyGResponseError', message: 'TinyG reported an error reading \'{"clr":null}\': 100 (based on 13 bytes read)', data: { r: { clr: null }, f: [ 1, 100, 13, 4451 ] } }

my code looks like this

` g.removeAllListeners();
g.on('error', function (error) {
console.log('error ');
console.log(error);

});
 g.open('/dev/ttyUSB0');`

So it is already from the first connection and after pressing the RESET button. I dont have the idea that it is doing something wrong but i would like to know what causes this and how to resolve

Kind regards and thx for this awesome project.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant