So yesterday our TinyG-controller router started to misbehave. I'm still trying to figure out the details but I can say that on some jobs it just locks up before doing anything. On the Chilipeppr logo job it starts and then quickly begins to do moves that have nothing to do with the job (luckily, all in the X-Y plane). Interestingly, Chilipeppr show the bit moving off the expected path as well.
This all started yesterday. But it had been a couple of weeks since we ran a job.
Has anything changed with Chilipeppr? Is a new version of the firmware needed? Any other ideas as to what the problem might be.
So Chilipeppr now supports multiple hardware options (tinyg, grbl, etc.) when communicating with the SPJS. We had it set to "default". Apparently, the behavior of that option has changed, or maybe we had used "tinyg" in the past and somehow got set it to "default" recently. It turns out that won't work.
The best part is that Chilipeppr even has an attention getting blurb warning users of TinyG hardware to use the "tinyg" setting for the SPJS. I managed to avoid seeing while my panic built for about an hour. Did a head-slap when I actually read the warning. My face is red.
In any case, when we changed the option to "tinyg" everything began to work as expected. The cutting has resumed!
John also caught this right away on the Chilipeppr Google group. That fact really impressed the machine's owner, and myself, given my panicked description of the symptoms. One more believer in open source.
Details, details, details, so many details. of CP is in the way it manages the flow if data to, and status back, from tinyG .
Much of the power of CP is in the way it manages the flow of data to, and status back, from tinyG . All of that is enabled by the choice of SPJS engine handler, "tinyg".
If have not yet, upgrade to SPJS 1.82. Much faster/more efficient.
This topic is from the original forum (June 2015). Your reply starts a new discussion linked to it.