that’s a blown chip.
I don’t know a ton about electronics, I like learning. How can you see that it is blown? Thanks
that bump shows that the case is cracked from the pressure inside the chip, so
it’s blown
some chips can have a dot molded into them, but more frequently it’s a hole not
a projection.
As soon as you talked about a bump on the chip, that sounds wrong to everyone,
and looking at it, it’s very clear it’s not something molded into the chip.
1 Like
I see it now! Thanks David.
1 Like
@Arichards
Since you’ll be waiting for a new shield (contact @hannah), it could be a good time to take a look at your file.
On my simulating PC I’m estimating roughly around 30 hours for the code to complete.
You might want to consider splitting the gcode into 3 or 4 files at least.
One more thing to think about is some active cooling for the motor shield. Small cpu-fans can give the chips some heat relieve for marathon runs.
The file provided is a nice stress test for the FW and GC and so far vers. 1.10 is holding up well.
Off-topic except for running the gcode provided (likely not related to the cut error)
Interesting still.
Apologies for slightly high-jacking this post.
Running with FAKE_SERVO activated in the firmware and vlc screen recording, I caught a “One Machine Position Report Command Misread”
I stopped the cut and closed GC to look at the 13.5MB log file and what sticks out is a <Idle,MPos:100] that is unique for me.
The relevant lines of log:
G1 X-26.889 Y-0.704
<Idle,MPos:-26.89,-0.70,-0.35,WPos:0.000,0.000,0.000>
[PE:-0.54,-0.17,100]
ok
Sent: G1 X-26.839 Y1.051 F60
G1 X-26.839 Y-0.754 F60
ok
Sent: G3 X-26.8416 Y1.113 I-0.7626 J0
G1 X-26.839 Y1.051 F60
<Idle,MPos:100]
X-26.839 Y-0.754 F60
X-26.839 Y1.051 F60
dle,MPos:-26.84,-0.75,-0.35,WPos:0.000,0.000,0.000>
[PE:-0.45,0.20,127]
<Idle,MPos:-26.84,-0.66,-0.35,WPos:0.000,0.000,0.000>
[PE:0.65,0.37,92]
<Idle,MPos:-26.84,-0.57,-0.35,WPos:0.000,0.000,0.000>
[PE:0.69,0.39,92]
<Idle,MPos:-26.84,-0.47,-0.35,WPos:0.000,0.000,0.000>
[PE:0.70,0.39,92]
<Idle,MPos:-26.84,-0.38,-0.35,WPos:0.000,0.000,0.000>
[PE:0.70,0.39,92]
<Idle,MPos:-26.84,-0.29,-0.35,WPos:0.000,0.000,0.000>
[PE:0.69,0.39,92]
<Idle,MPos:-26.84,-0.20,-0.35,WPos:0.000,0.000,0.000>
2 Likes
It would seem to me that some sort of Maslow specific G-Code Parser might be a good idea to include in Ground Control.
Something that kicked out a ‘report’ noting any errors, un-executable lines, comments, etc. along with a summary of the cut: tools used, total execution time, total ‘cut’ time, total distance to move, total distance to cut, z-axis details/passes etc.
It would be handy to pre-flight as much as possible considering there are so many different sources of .nc file generators, and so many potential G-code outputs that are perfectly appropriate for ‘one size fits all’ CAM tools that are frankly unsuited for Maslow/GRBL.
It seems that there are tons of potential problems that could be eliminated by a more detailed pre-flight checklist/report along with simple warnings, ie: " Cut Time exceeds x Hours, please ensure that your Maslow Shield has appropriate cooling. Continue y/n" , “Z-Axis depth exceeds normal parameters. Continue y/n?”.
thoughts?
mrfugu
2 Likes
Thanks for all of your help. @hannah has a new shield on the way. Thanks! I will plan on additional cooling systems, though I would be surprised if that was a problem this time around. (I’ve been working in a 35 F degree barn).
Have any of you had any experience breaking a file into more manageable chunks that would allow a larger bit to do heavier lifting and then cutting the details with a 1/8? I just wouldn’t know the process for programming such a design.
And finally, yes, a few built in warnings for bad g code or other issues would be well received! I would have thought twice before tackling a 30 hour cut had I known before now. Especially as I had hoped for this to be cut 1 of 4 for these signs.
Thanks again!
2 Likes
What CAM program are you using? If makercam, you can select individual toolpaths and make gcode from them. For instance, the sun part could be selected and you make a gcode from just that… then repeat the process selecting the various text lines. That should break it into four more manageable pieces.
Thanks. I used MakerCam and did select individual paths in order to boost efficiency of the cut. However, I think I will experiment with doing larger areas with larger bits.
2 Likes