Ok here goes,
Not very good at social media but desperate times…
I have a cheap chinese T8 style cnc and my learning curve has been pretty steep.
I found Chilipeppr and thought all my troubles were behind me.
I wish.
Would someone help me out with what feels like proper dumb questions.
Do I have to set up my own workspace to use chilipeppre?
I have got it working with GRBL1.1 on the jpadie workspace. But my second project keeps getting replaced with the first project when I click on “send auto levelled gcode to workspace”. Am I missing something here? I’ve waited for probing to finish 3 or 4 times and then had project 2 replaced with project 1 upon sending - driving me mad.
Also how do I edit my workspaces? Cloud9 is no longer accepting new accounts as it has been absorbed into Amazons AWS. Ive tried using AWS but the code seems to have a lot of old cloud9 specific references. I don’t think the two are compatible. It seems to hang when pushing to GIT.
This is so frustrating as CP look just the job and once it performed perfectly. Any ideas gratefully received.
Hi Vincent, I’m not sure how your proj 2 is getting replaced by proj 1. Perhaps wipe your browser localstorage for http://chilipeppr.com because chilipeppr stores your recently loaded gcode files in localstorage. Maybe something got corrupted there and it’s messing with the code?
On the Cloud9 stuff, I got the widget-template in github to have the correct code for working inside of AWS’s version of cloud9. It’s the runme.js that I had to add a lot of logic to for detecting which environment it’s in. I don’t think I updated the workspace version of runme.js, but it’s almost identical of a codebase.
What I will say though is that you can fork and modify in any dev environment like on your local machine. The runme.js ultimately just generates the monolithic final HTML page, but it’s sort of a brainless merging where it just shoves the javascript and css into the HTML page. So, you don’t really need runme.js.
Well, something happened. I wish I could tell you what it was but it worked perfectly.
So now I am trying to cut another board and I’m having the same problem.
I have tried it on Chrome (freshly installed), firefox, and I even got desperate and tried Edge.
Same problem. The autolevel data isn’t being added to the original gcode.
The load probe data function doesn’t work. The gcode doesn’t have any offsets - or any z data (see photo)
Order of events
run probe. Get a nice 3d topology showing the warped surface.
2.click on “send autloevelled data” then I get the chilipepre logo, with the autolevel data still visible over it.
3 check gcode - no z offsets.
tried a different approach
the probe data looked ok (I guess) so I saved it in a file.
2 reloaded eagle file by drag and drop
3 ran the make gcode button. Got all the cutting paths - fine.
4 opened up auto level widget, pasted the previous auto level data and tried to upload it. Not sure if anything happed at this point. However I can see the probe data if I “view” it.
clicking on “send auto levelled data” I get no clear feedback anything is happening.
Looking the the auto levelled code I have no z adjustments.
Oh! I forgot, sometimes CP complains it cant tell if the gcode is inch or mm. You can see the g21 code in the photo.
By the way I’m still new to gcode so not sure what G0zNaN is but a quick google looks like it shouldn’t be there. I have several NaNs see photo.
My guess would that the NaN is the core problem. That means “Not a Number”. Does your original Gcode that the Eagle widget generates have the NaN’s in it? If so, I could see that throwing off the auto-level parser. Get your original Gcode to not have any NaN’s in it and then I think the auto-level will work. My best guess theory right now.
Nope!
Original Gcode as it is shown in eagle importer window looks fine.
Tried again this morning. (I only seem to be able to put one picture per post - so Ill put up a couple of posts) Below you can see a picture of a gcode file showing routes to be cut, an auto level matrix. On top you can see the Gcode with auto level displaying the CP logo gcode. (see next post)
It’s hard to tell from your screenshot, but my new guess would be that you’re not actually sending your Eagle BRD import Gcode to the workspace and then auto-levelling. I’m guessing your have the Eagle BRD import widget open, which shows a preview until you actually “send gcode to workspace”
