So I keep having Chilipeppr freeze on me at random mid-job. I’ve lost numerous bits and quite a bit of material. It’s starting to cost me a decent amount of money so I’m considering a switch to something else if I can’t figure this out. Basically, it will glitch out about 20-30 mins into the job, sometimes randomly switching itself to mm instead of inches, it’ll loose zero, doesn’t seem to follow the virtual toolhead accurately. Other times, it will just freeze altogether and re-zero itself where it stands. When this happens I am unable to do anything. I have to close everything out and try again. Any advice? Not sure what else to do here.
Are you grbl or tinyg?
Also screenshots help as they tell us all your versions of everything
I’m tinyg. Will try to get some screenshots next time the issue occurs. Sorry, none as of right now. I did download the newest version of the JSON server a month or two ago though.
Also, running Linux Mint and I’m connected directly via USB.
@tlgrimmy check your gcode for arc moves g02 or g03. I have had many issues with tinyg and arcs locking up the controller. Unless of course its the web browser that’s locking up that would firmly be a chilipeppr issue.
My suggestion is to record the process on a web cam and at the same time start cp in verbose mode and capture the output.
@jlauer is there a switch for sjps to have it log to a file as well as stdout?
My gut is G2/G3 arcs as well. That’s why firmware version is key info.
For logging you could use OS tools like on Linux just routing stdout to a file “> log.txt”. There’s nothing in SPJS itself.
Thanks for the replies everybody. I’ve been running shorter jobs to avoid the issue, but just ran into again when I ran a longer job (45 mins). I got a screenshot, but I’ll try to figure out the logging option you mentioned next time around. Apparently, I was connected through my raspberry pi. I’ll try it direct to the laptop as well just in case. I’m running firmware version 1.94. I looked for g2/g3 codes in the console, but it didn’t show all of the code and couldn’t find any g2/g3 codes in what was there.
missing/deleted image from Google+
I’m not very familiar with Linux commands. I tried googling how folks redirect the stdout to a file, but all of the commands I found didn’t work. I created a log.txt file, put it on the desktop, and tried the commands I found using the log.txt file name I created, but no dice. Anyone know how I can do this?
Your state says “end” in tinyg widget which means you may have an m30 in line 75192 which would be odd to have in the middle of your gcode rather than as the last line.
Like this
From the terminal in the directory with sjps in it.
echo “”> http://log.txt
./sjps -v > ./http://log.txt
Yeah, is is. When it freezes the virtual toolhead continues through the gcode, while the actual router is stationary.
If you truly do have m30 in middle of gcode what cam are you using? Never heard of that
I don’t think that was in the middle, but could be wrong. This file was done with jscut
Thanks for the responses again. I didn’t see Justin’s suggestion until today. The latest update is that I looked through the gcode and didn’t see any code with G2 or G3 in it. It’s continually freezing still, but will sometimes work. Also, the computer randomly shuts down (sometimes repeatedly) midway through the job. It continues to cut, so if I restart it quickly enough, I can click “restore” on the google browser and things keep moving along, but sometimes immediately shuts off again. The performance settings are all set to never shut off, and it doesn’t unless I’m running a job in chilipeppr. Also, I paid a bit closer attention and during a freeze, chilipeppr resets itself to mm instead of inches (gcode in inches), continues to show the virtual tool head moving as normal, but there is no movement at the CNC.
I haven’t tried the terminal log deal yet. I’m assuming I just open a terminal and type in those commands? I have spjs running on a Raspberry Pi because Linux constantly disallows permissions to the USB jack and disconnects from the CNC. Do I have to reference it’s location on the raspberry pi in the code somehow? Whew! I wish I could just have one issue at a time instead of this mess I’m dealing with;).
It sounds like the computer shutting down in the middle of the job is the core problem. ChiliPeppr slowly feeds lines of Gcode to SPJS. If your computer shuts down and it only fed 30% of the lines, then even when you reconnect ChiliPeppr has no idea how many lines were sent and what you want to do and won’t send anymore lines to your CNC. So, of course, your run stops in the middle of the job when it completes executing the 30% of the lines you sent. It’s doing what it should.
One solution is for you to change the upload settings in the Gcode widget to pre-upload a much larger block and to upload faster intervals and more lines. However, SPJS can only handle about 200k lines in it’s memory buffer so don’t overdo it either.
The best solution is never let your computer shut down when running a job.
Totally, the computer issue is just one of the things going on at the moment that I can’t figure out. Even when it’s not shutting down, I continually have freezes mid-job, but not every time. It’s about 60/40, freezing a little over half the time. if the job is over 20 minutes though, it freezes at some point every time, but in different spots. That’s what’s so confusing; it doesn’t seem to be isolated to a particular area within the gcode.
Irq conflicts sometimes causing kernel errors?
The system logs will (or may) have useful info.
Hi Justin, I’m pretty clueless in the coding/programming area. If I just put the SPJS directly on the desktop, what would I have to put in a terminal to accomplish this? Thanks again for your help!