search

synthetos / TinyG

Affordable Industrial Grade Motion Control
https://github.com/synthetos/TinyG/wiki
890 stars 293 forks source link

Alarm message when limit switch is hit #104

Open dougle opened 9 years ago

dougle commented 9 years ago

Point 2 from https://github.com/synthetos/TinyG/issues/69 is still an issue.

"When testing my limit switches (All six) which are configured NC, I receive this msg from tinyg.

{"er":{"fb":414.03,"st":76,"msg":"Limit switch hit - Shutdown occurred"}} qr:28, qi:1, qo:1

I receive this identical msg regardless of which switch is fired......"

Both V8 boards: Version 0.96 {“er”:{“fb”:380.08,”st”:27,”msg”:”System alarmed”,”val”:0}} Which has a useful "val" attribute in the response json.

Version: 0.97 {“er”:{“fb”:435.10,”st”:204,”msg”:”Limit switch hit – Shutdown occurred”}} It is not possible to know from this which limit switch has triggered the alarm.

aldenhart commented 9 years ago

Taken as a feature request

dougle commented 9 years ago

I would count this more as a regression than a feature request

ril3y commented 9 years ago

We never put which switch was triggered in the code base. I agree this is is a new feature request. Regression would imply that this was at one point working. It was not.

Alden has been working in the whole IO system however. So he might have some more input. Hes in China this week however.

On Fri, Apr 3, 2015 at 12:39 PM, dougle notifications@github.com wrote:

I would count this more as a regression than a feature request

Reply to this email directly or view it on GitHub https://github.com/synthetos/TinyG/issues/104#issuecomment-89347304.

dougle commented 9 years ago

OK if "val" was accidentally and unintentionally revealing which switch was hit then this is a new feature.

ril3y commented 9 years ago

Yah I have wanted to get this in for awhile now too! I had a mis-wired switch a few years back and could not tell which one it was! But we are all on the same page on this one.

On Fri, Apr 3, 2015 at 4:18 PM, dougle notifications@github.com wrote:

OK if "st" was accidentally and unintentionally revealing which switch was hit then this is a new feature.

Reply to this email directly or view it on GitHub https://github.com/synthetos/TinyG/issues/104#issuecomment-89409757.

dougle commented 9 years ago

I'm keen to add a "limit auto backoff" feature to my gcode sender that will reset tinyg after an alarm, back the axis off in the correct direction, reset tinyg again and then back off a bit more depending on the controller settings. I was using "val" from 0.96 to work out which axis and direction to back off but no more.