Just wondering if anyone managed to get V-Carve/JSCut working? I’m trying to vcarve a 14mb file and chilipeppr freezes up!
Originally shared by Matt Herrera
V-carve in chilipeppr not working…
So I’ve tried a few times to get V-carve to work in chilipeppr and it never loads. I use Jscut to produce my Gcode and drop that into chilipeppr. Other files load just fine. Is there a trick to this? Is the v-carve file too large for chilipeppr? I’d appreciate any feedback. Has anyone else been successful loading v-carve Gcode from Jscut into chilipeppr?
Too big. Sad but Chilipeppr is limited to much less and it may never get the programming rewrite it needs to fix this very serious limitation. We had to switch to MACH3 for a new table we are upgrading because the client wants to do some 2.5d reliefs for full 4’ x 8’ panels, which we have done very easily on our other Mach3 build. The Chilipeppr machines we built are smaller but I still run into this limit when doing deep reliefs even at relatively small sizes. China CNC zone is making a nice 5 axis 6040 that I would have loved to use with Chilipeppr but I cannot “upgrade” them to Tinyg and Chilipeppr when it does LESS than what they ship with.
@Steve_Anken I’ve been thinking seriously about starting a new gcode server code base. I’d like something that can queue both 3d printing and CNC jobs. I envision a frontend (probably web based) that would render a compiled down tool path. I don’t think we could ever get large gcode files parsed in JavaScript efficiently.
Thank you for the response 
@Steve_Anken you should see if my workspace helps at all. I’ve done a lot to try and optimize the 3d viewer and stop it from nuking the rest of chilipeppr when a job is running
Daniel I have tried it before this latest post of yours but I suddenly have a problem with the FTDI driver not installing so I can’t run my machine until I fix this. Weird, I did an update of Windows that has made everything a bit unstable lately and the driver not working is making me think I should just back up and reinstall everything from scratch. I really do not like how frustrating it is to get solid device to computer communication. It should not be this hard but it says I need to use the Component Services administrative tool to fix it… yeah right…
@Brian_Poland try using cncjs instead. It has a few less bells and whistles but has no issues with really large files. I’ve run 20mb gcode though it no problem at all.
@Daniel_Chote it’s not JavaScript at fault here. Cncjs is also just based and has no issues like this. It’s an issue specific to the way chilipeppr was built not a technology choice problem.
@Ben_Delarre Thanks Ben will give it a try -
@Ben_Delarre I think I’ll go take a look at cncjs and see how they do their gcode parsing and see if I can engineer chilipeppr to do the same.