I've seen this issue in other forums, and I can reproduce it reliably, auto-level prob

if I press the 'send final gcode to workdesk' <a target="_blank" rel="noopener nor

<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clip

Autolevel unreliable, does not go past the first step about widget-autolevel HOT 12 CLOSED

chilipeppr commented on September 17, 2024

Autolevel unreliable, does not go past the first step

from widget-autolevel.

Comments (12)

dgtlmoon commented on September 17, 2024

It seems to be entering a paused state after each check, if i hit "pause" button twice, it will move onto the next step... where i have to hit the pause button twice..

from widget-autolevel.

dgtlmoon commented on September 17, 2024

https://discuss.inventables.com/t/chilipeppr-auto-level-stopping/19811

If anyone else runs up against this, it appears from the chilipeppr forums that this is a new bug introduced in the last few days. It's apparently been fixed in the TinyG version already, but hasn't been fixed over in the GRBL version yet... However there is a fork that someone built that does have the fix we can use. Seems to be a moving target, so please reference the chilipeppr G+ community for the latest forked version until they get it fixed officially...

Is this still the case? that's from feb 2016

from widget-autolevel.

dgtlmoon commented on September 17, 2024

if I press the 'send final gcode to workdesk'

button then re-run the autolevel by pressing the play button it works?

from widget-autolevel.

chilipeppr commented on September 17, 2024

Somebody else mentioned that if they didn't open the Eagle BRD widget it worked ok. Do you see that? Also, what Javascript debug console errors do you see if any? If you turn off the funnel icon in serial port console, do you see any errors back from TinyG?

…

On Thu, Feb 23, 2017 at 8:19 AM, dgtlmoon ***@***.***> wrote: if I press the 'send final gcode to workdesk' [image: screenshot_2017-02-23_17-17-34] <https://cloud.githubusercontent.com/assets/275001/23267811/2510f22c-f9ec-11e6-922c-0a9bfb2193c0.png> button then re-run the autolevel by pressing the play button it works? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#3 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AHidbR6RrdgMWrJRIQMQLjgNJDZnEh2wks5rfbF7gaJpZM4MJ2O-> .

from widget-autolevel.

dgtlmoon commented on September 17, 2024

{"Lbs":87}
{"r":{},"f":[1,0,32,133]}
G0 Z1.5
{"Lbs":77}
{"r":{},"f":[1,0,8,4401]}
{"sr":{"posz":1.998,"vel":24.09,"stat":5,"mpoz":1.998}}
{"qr":31}
G0 X-1 Y-1
{"Lbs":73}
{"r":{},"f":[1,0,11,70]}
{"sr":{"posz":1.974,"vel":202.51,"mpoz":1.974}}
{"qr":30}
G0 Z0.5
{"Lbs":63}
{"r":{},"f":[1,0,8,4401]}
{"sr":{"posz":1.907,"vel":476.09,"mpoz":1.859}}
{"qr":29}
{"qr":30}
{"qr":31}
{"sr":{"posx":-1.000,"posy":-1.000,"posz":0.508,"vel":180.98,"mpox":-1.000,"mpoy":-1.000,"mpoz":0.502}}
{"sr":{"posz":0.500,"vel":0.00,"stat":3,"mpoz":0.500}}
{"qr":32}
 G38.2 Z-10 F25
{"Lbs":74}
{"r":{},"f":[1,0,15,74]}
{"sr":{"stat":7,"coor":0}}
{"qr":32}
{"qr":31}
{"sr":{"posz":0.399,"vel":25.00,"momo":1,"mpoz":0.399}}
{"sr":{"posz":0.297,"mpoz":0.297}}
{"sr":{"posz":0.195,"mpoz":0.195}}
{"sr":{"posz":0.093,"mpoz":0.093}}
{"sr":{"posz":0.008,"vel":2.49,"mpoz":0.008}}
{"Lbs":42}
{"sr":{"vel":0.00,"stat":3,"coor":1,"momo":4}}
{"qr":32}

ah yes I see errors, no difference if the eagleboard widget is open/closed (off)

from widget-autolevel.

chilipeppr commented on September 17, 2024

I'm hearing reports that the fix to the fadeOutUserObject that I published yesterday fixed the problem. Try to reload ChiliPeppr in your browser and see if you're good now. When seeing this email I was worried the publish broke something further for you, but I've seen reports since then that the fix worked.

…

On Fri, Feb 24, 2017 at 2:27 AM, dgtlmoon ***@***.***> wrote: {"Lbs":87} {"r":{},"f":[1,0,32,133]} G0 Z1.5 {"Lbs":77} {"r":{},"f":[1,0,8,4401]} {"sr":{"posz":1.998,"vel":24.09,"stat":5,"mpoz":1.998}} {"qr":31} G0 X-1 Y-1 {"Lbs":73} {"r":{},"f":[1,0,11,70]} {"sr":{"posz":1.974,"vel":202.51,"mpoz":1.974}} {"qr":30} G0 Z0.5 {"Lbs":63} {"r":{},"f":[1,0,8,4401]} {"sr":{"posz":1.907,"vel":476.09,"mpoz":1.859}} {"qr":29} {"qr":30} {"qr":31} {"sr":{"posx":-1.000,"posy":-1.000,"posz":0.508,"vel":180.98,"mpox":-1.000,"mpoy":-1.000,"mpoz":0.502}} {"sr":{"posz":0.500,"vel":0.00,"stat":3,"mpoz":0.500}} {"qr":32} G38.2 Z-10 F25 {"Lbs":74} {"r":{},"f":[1,0,15,74]} {"sr":{"stat":7,"coor":0}} {"qr":32} {"qr":31} {"sr":{"posz":0.399,"vel":25.00,"momo":1,"mpoz":0.399}} {"sr":{"posz":0.297,"mpoz":0.297}} {"sr":{"posz":0.195,"mpoz":0.195}} {"sr":{"posz":0.093,"mpoz":0.093}} {"sr":{"posz":0.008,"vel":2.49,"mpoz":0.008}} {"Lbs":42} {"sr":{"vel":0.00,"stat":3,"coor":1,"momo":4}} {"qr":32} ah yes I see errors, no difference if the eagleboard widget is open/closed (off) [image: screenshot_2017-02-24_11-25-51] <https://cloud.githubusercontent.com/assets/275001/23300014/0756197c-fa84-11e6-9209-7047cbb8cf80.png> — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#3 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AHidbZCAkgnBjb285iT3UiZF-WL2H-EVks5rfrB7gaJpZM4MJ2O-> .

from widget-autolevel.

treib commented on September 17, 2024

I'm getting the error that "fadeOutUserObject" is not found. Looking at the latest commit, I see only a "fadeOutUserObjectOld" and a "fadeOutUserObjectJustinVersion".

Same end result: the probe stops when contact is made but doesn't continue on probing other locations.

Here's the console error in Chrome:

Uncaught TypeError: this.fadeOutUserObject is not a function
    at Object.showProbeMatrix (eval at globalEval (jquery-2.1.0.min.js:2), <anonymous>:285:26)
    at Object.toggleShowMatrix (eval at globalEval (jquery-2.1.0.min.js:2), <anonymous>:268:26)
    at Object.callback (eval at globalEval (jquery-2.1.0.min.js:2), <anonymous>:1339:30)
    at publish (amplify.js:35)
    at Object.publish (app.js:167)
    at Object.onWsMessage (eval at globalEval (jquery-2.1.0.min.js:2), <anonymous>:1533:40)
    at Object.eval (eval at globalEval (jquery-2.1.0.min.js:2), <anonymous>:232:22)
    at publish (amplify.js:35)
    at Object.publish (app.js:167)
    at Object.publishMsg (eval at globalEval (jquery-2.1.0.min.js:2), <anonymous>:1420:24)

from widget-autolevel.

chilipeppr commented on September 17, 2024

Uh oh. That would be my mistake. Just fixed it and republished from the hotel in Barcelona. That's the danger of launching code without getting to test it.

…

On Sat, Feb 25, 2017 at 3:39 PM, Phil Treib ***@***.***> wrote: I'm getting the error that "fadeOutUserObject" is not found. Looking at the latest commit, I see only a "fadeOutUserObjectOld" and a " fadeOutUserObjectJustinVersion". Same end result: the probe stops when contact is made but doesn't continue on probing other locations. Here's the console error in Chrome: Uncaught TypeError: this.fadeOutUserObject is not a function at Object.showProbeMatrix (eval at globalEval (jquery-2.1.0.min.js:2), <anonymous>:285:26) at Object.toggleShowMatrix (eval at globalEval (jquery-2.1.0.min.js:2), <anonymous>:268:26) at Object.callback (eval at globalEval (jquery-2.1.0.min.js:2), <anonymous>:1339:30) at publish (amplify.js:35) at Object.publish (app.js:167) at Object.onWsMessage (eval at globalEval (jquery-2.1.0.min.js:2), <anonymous>:1533:40) at Object.eval (eval at globalEval (jquery-2.1.0.min.js:2), <anonymous>:232:22) at publish (amplify.js:35) at Object.publish (app.js:167) at Object.publishMsg (eval at globalEval (jquery-2.1.0.min.js:2), <anonymous>:1420:24) — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#3 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AHidbXZXpwiIJhU4gN4cCzjsgbsIfqSoks5rgLvIgaJpZM4MJ2O-> .

from widget-autolevel.

dgtlmoon commented on September 17, 2024

Thanks John! I'll retest tomorrow once I'm back in the office.

Kind of (un)related - the commit message Made some changes to ChiliPeppr widget using Cloud9, so cloud9 is committing somewhere else then you're pushing to github as a remote, or is it just a lazy commit message and it can support proper commit messages?

from widget-autolevel.

chilipeppr commented on September 17, 2024

All ChiliPeppr widgets and workspace Github repos have a runme.js script that you can run to create the final HTML file that contains all Javascript, CSS, and HTML for the widget or workspace. That runme.js script also uploads to Github and does so with a default message. You can add a custom git commit message, but if you're being lazy you just reload the runme and you're done. So, yes, it's just being lazy.

…

On Sun, Feb 26, 2017 at 1:39 AM, dgtlmoon ***@***.***> wrote: Thanks John! I'll retest tomorrow once I'm back in the office. Kind of (un)related - the commit message Made some changes to ChiliPeppr widget using Cloud9, so cloud9 is committing somewhere else then you're pushing to github as a remote, or is it just a lazy commit message and it can support proper commit messages? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#3 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AHidbTjrp9JnEZXzGSZlfVPhMvURAQV1ks5rgUg7gaJpZM4MJ2O-> .

from widget-autolevel.

dgtlmoon commented on September 17, 2024

ahuh cool! ok, some very interesting architecture there, i'll have to read more into it.

ok, so I'm still seeing an error in the console but it does appear to be working reliably...

serial port console output

{"Lbs":0}
{"r":{},"f":[1,0,16,75]}
{"sr":{"stat":7,"coor":0}}
{"qr":32}
{"qr":31}
{"sr":{"posz":0.170,"vel":32.00,"momo":1,"mpoz":0.170}}
{"sr":{"posz":0.040,"mpoz":0.040}}
{"sr":{"posz":-0.058,"vel":3.19,"mpoz":-0.058}}
{"r":{"prb":{"e":1,"x":4.500,"y":19.500,"z":-0.058,"a":0.000,"b":0.000,"c":0.000}},"f":[1,0,0,9833]}
{"sr":{"vel":0.00,"stat":3,"coor":1,"momo":4}}
{"qr":32}
 G0 Z1.0
 G0 X4.5 Y14.5
 G0 Z0.3
G0 Z1.0
{"Lbs":22}
{"r":{},"f":[1,0,8,4401]}
{"sr":{"posz":-0.057,"vel":17.96,"stat":5,"momo":0,"mpoz":-0.057}}
{"qr":31}
G0 X4.5 Y14.5
{"Lbs":8}
{"r":{},"f":[1,0,14,73]}
{"sr":{"posz":-0.038,"vel":170.28,"mpoz":-0.038}}
{"qr":30}
G0 Z0.3
{"Lbs":0}
{"r":{},"f":[1,0,8,4401]}
{"sr":{"posz":0.075,"vel":646.26,"mpoz":0.075}}
{"qr":29}
{"qr":30}
{"sr":{"posy":16.724,"posz":1.000,"vel":1200.00,"mpoy":16.724,"mpoz":1.000}}
{"qr":31}
{"sr":{"posy":14.500,"posz":0.300,"vel":0.00,"stat":3,"mpoy":14.500,"mpoz":0.300}}
{"qr":32}
 G38.2 Z-1.5 F32
{"Lbs":0}
{"r":{},"f":[1,0,16,75]}
{"sr":{"stat":7,"coor":0}}
{"qr":32}
{"qr":31}
{"sr":{"posz":0.170,"vel":32.00,"momo":1,"mpoz":0.170}}
{"sr":{"posz":0.040,"mpoz":0.037}}
{"sr":{"posz":-0.045,"vel":3.19,"mpoz":-0.045}}
{"r":{"prb":{"e":1,"x":4.500,"y":14.500,"z":-0.045,"a":0.000,"b":0.000,"c":0.000}},"f":[1,0,0,3136]}
{"sr":{"vel":0.00,"stat":3,"coor":1,"momo":4}}
{"qr":32}

.. could be that G38? I get one set of those errors in the console on every 'step' of the check

from widget-autolevel.

dgtlmoon commented on September 17, 2024

I might close this issue for now, seems to be working reliably but with that above errors which I'm not sure is todo with this issue directly, thanks a bunch!

from widget-autolevel.

Autolevel unreliable, does not go past the first step about widget-autolevel HOT 12 CLOSED

Comments (12)

Related Issues (4)

Recommend Projects

React

Vue.js

Typescript

TensorFlow

Django

Laravel

D3

Recommend Topics

javascript

web

server

Machine learning

Visualization

Game

Recommend Org

Facebook

Microsoft

Google

Alibaba

D3

Tencent