Version 4.14 - Issues to Report, Please post them here

[cnckeith]

would be nice to see the entire screen when it stops..i'd like to see all of the buttons on the VCP.

i'm am running the g code file provided on my machine here and i've already passed the line number that yours stopped on.

[cnckeith]

"I also noticed that a couple of my gcode files that I was using just prior to the upgrade now will not work and I get a popup that says there is an invalid character in the first line. They worked fine with the older version. Anyone have any ideas what to look for ?"

provide the g code file(s) and what line number cnc12 was complaining about and i'll be glad to comment.

[cnckeith]

There isn’t any. The screen shots are what it shows when it has stopped. It just stops moving. Leaves the spindle running and the gcode just stops scrolling. I got aggravated and needed to get some work done so I uninstalled the new version and reinstalled the older and using the same gcode, it ran fine.

Hello. i ran the provided g code program (coaster vcarve badge.cnc) two times from start to finished with no issues, once with my machine configured with your provided report.zip and once with it configured with defaults.
I did notice that the last run g code program in the report.zip (coaser vcarve.cnc) and seen in the screen shots provided does not match the one posted in the thread (coaster vcarve badge.cnc). so for a valid test i would need the exact same program that was used in the screen shots.

[bmilam]

Sorry about the file. When I kept having the issue, I redid the vcarve program and created all new guides for the file to try that. That was the other file but they both did the same thing just at a different point. One was a little under 3 minutes in and the other was almost 5. Since I reverted back to the older version of software, the file is cutting completely thru.

As far as the control panel, i know positively that nothing got clicked on by accident. I Did try to pause the program and then continue but it had no effect. There was no tool change either but the z axis never retracted, all axis just stopped.

I don’t think that it is in the gcode since it runs fine in the other version and you say it ran thru for you. I don’t think it is the machine since that also works fine before and after. I followed the instructions for the install and it worked good other than on this particular project. I think maybe when it installed, something didn’t instal correctly and I am going to attempt to download a new file then reinstall it fresh. Hopefully it was just a computer glitch and that will correct it.
If it continues I will post again with a new report and new photos of the screen.
Thanks for responding.

[cbb1962]

I had a weird issue today. I had a Z-Axis motor fault, no big deal, I re-homed everything and it homed correctly. I went to the VCP to jog the Z-axis down and it wouldn't move. I ran the ClearPath Motor Setup Program to see if I could jog the Z down with that program. No problems moved up/down - no issues at all.

I restarted CNC12, I could jog up - but still couldn't jog down. On a whim I turned on the wireless MPG to see if I could move the Z, It moved up/down no issues at all. I rebooted the PC and Acorn. I went back to the VCP and I had movement up, but not down. The MPG worked, Homing worked, MDI worked, so I started my program, after the program completed I tried the VCP, and it worked perfectly. Weird.

report_38D2695C8301-0122180576_2019-05-03_19-40-41.zip

(255.15 KiB) Downloaded 97 times

(In the error logs the issue happened about 14:10 today.)

[martyscncgarage]

I had a weird issue today. I had a Z-Axis motor fault, no big deal, I re-homed everything and it homed correctly. I went to the VCP to jog the Z-axis down and it wouldn't move. I ran the ClearPath Motor Setup Program to see if I could jog the Z down with that program. No problems moved up/down - no issues at all.

I restarted CNC12, I could jog up - but still couldn't jog down. On a whim I turned on the wireless MPG to see if I could move the Z, It moved up/down no issues at all. I rebooted the PC and Acorn. I went back to the VCP and I had movement up, but not down. The MPG worked, Homing worked, MDI worked, so I started my program, after the program completed I tried the VCP, and it worked perfectly. Weird.

report_38D2695C8301-0122180576_2019-05-03_19-40-41.zip

(In the error logs the issue happened about 14:10 today.)

There are probe tripped messages in you log file. Check the probe input

[martyscncgarage]

Sorry about the file. When I kept having the issue, I redid the vcarve program and created all new guides for the file to try that. That was the other file but they both did the same thing just at a different point. One was a little under 3 minutes in and the other was almost 5. Since I reverted back to the older version of software, the file is cutting completely thru.

As far as the control panel, i know positively that nothing got clicked on by accident. I Did try to pause the program and then continue but it had no effect. There was no tool change either but the z axis never retracted, all axis just stopped.

I don’t think that it is in the gcode since it runs fine in the other version and you say it ran thru for you. I don’t think it is the machine since that also works fine before and after. I followed the instructions for the install and it worked good other than on this particular project. I think maybe when it installed, something didn’t instal correctly and I am going to attempt to download a new file then reinstall it fresh. Hopefully it was just a computer glitch and that will correct it.
If it continues I will post again with a new report and new photos of the screen.
Thanks for responding.

Well you reverted to previous software.
Did it stop on the exact same line each time?
You can run both versions of software, but you have to rename the directories

[cbb1962]

There are probe tripped messages in you log file. Check the probe input

Which file did you see the probe tripped messages??

thanks,
Clint

[martyscncgarage]

There are probe tripped messages in you log file. Check the probe input

Which file did you see the probe tripped messages??

thanks,
Clint

Open your report.zip file. Go find Urf zip. Open it, look at the msg log

[bmilam]

Well you reverted to previous software.
Did it stop on the exact same line each time?
You can run both versions of software, but you have to rename the directories
[/quote]

I was not aware that I could run both versions.
No, when I reverted back to the older version, it runs the entire program without stopping.

I believe the probe tripped was the tool touchoff. I was using the M6func macro from the tech tip section. When I started having issues, I tried removing that macro and manually touching off the tools but that did not seem to help.

So far the older program is working just as it did before my upgrade with any file that I run, no issues.