# GroundControl Crash on File Opening

**URL:** <https://forums.maslowcnc.com/t/groundcontrol-crash-on-file-opening/2969>\
**Category:** Troubleshooting\
**Created:** [March 28, 2018, 2:02pm UTC](https://forums.maslowcnc.com/t/groundcontrol-crash-on-file-opening/2969 "2018-03-28T14:02:25Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![Papa](https://avatars.discourse-cdn.com/v4/letter/p/9d8465/32.png) [@Papa](https://forums.maslowcnc.com/u/Papa)\
**Post date:** [March 28, 2018, 2:02pm UTC](https://forums.maslowcnc.com/t/groundcontrol-crash-on-file-opening/2969/1 "2018-03-28T14:02:25Z")

</div>

Hi there!

My Ground Control sometimes crashes when I try to open a G-Code file.  
I create them all with Fusion 360.  
Some work fine and some don’t.  
Is there an Error log somewhere or can Fusion write Code, that CroundControl can\*t handle?

Laptop with WIn 7  
GC 1.09 and Firmware 1.09

I would add the File, but I’m not allowed to…

---

<div class="post-metadata">

**Author:** ![bar](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/bar/32/10_2.png) [@bar](https://forums.maslowcnc.com/u/bar)\
**Post date:** [March 28, 2018, 2:35pm UTC](https://forums.maslowcnc.com/t/groundcontrol-crash-on-file-opening/2969/2 "2018-03-28T14:35:11Z")

</div>

Hmmm having the file would help me to figure out what’s going on.

There isn’t a log of what works and what doesnt, but the general policy is that if you find something which doesn’t work and send me the file I will make it work in the next release.

Using the Maslow post processor is a good idea if you are not

---

<div class="post-metadata">

**Author:** ![blurfl](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/blurfl/32/9_2.png) [@blurfl](https://forums.maslowcnc.com/u/blurfl)\
**Post date:** [March 28, 2018, 2:41pm UTC](https://forums.maslowcnc.com/t/groundcontrol-crash-on-file-opening/2969/3 "2018-03-28T14:41:42Z")

</div>

There is a log named ‘log.txt’. The location depends on the operating system:  
Linux: in the GroundControl folder that you run from  
Windows: in the ‘GroundControl-Windows.Portable.v1.xx\GroundControl\’ folder  
OSX: in Finder, in the Applications folder, find the groundcontrol app, right-click on it and ‘Show Package Contents’ to open a window that lets you navigate to the right place. The GroundControl log file is in the ‘Contents/Resources/yourapp/’ folder.

I’m not sure of the restrictions, I think that new accounts are restricted from uploading for one day, but it could be less. Only some file types are allowed, you could try zipping it, the .zip file is allowed. I think .txt and .nc are allowed as well.

Which operating system are you using? I’ve not used Fusion to create a gcode file, but others here have. If I remember right, choosing the ‘grbl’ post processor from the list made files that worked. Which one did you use?

---

<div class="post-metadata">

**Author:** ![bar](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/bar/32/10_2.png) [@bar](https://forums.maslowcnc.com/u/bar)\
**Post date:** [March 28, 2018, 4:16pm UTC](https://forums.maslowcnc.com/t/groundcontrol-crash-on-file-opening/2969/4 "2018-03-28T16:16:45Z")

</div>

Here’s a way to find out more. If you can replace the “Launch Ground Control” file with the one in this zip file[Pauseoncrash.zip](https://canada1.discourse-cdn.com/flex031/uploads/maslowcnc/original/2X/8/84f6cd2595484837398a6d9404455258bcb752db.zip) (178 Bytes) Ground Control will pause after crashing so we can see what the error message is!

---

<div class="post-metadata">

**Author:** ![Papa](https://avatars.discourse-cdn.com/v4/letter/p/9d8465/32.png) [@Papa](https://forums.maslowcnc.com/u/Papa)\
**Post date:** [May 12, 2018, 9:41am UTC](https://forums.maslowcnc.com/t/groundcontrol-crash-on-file-opening/2969/5 "2018-05-12T09:41:14Z")

</div>

I finally fount the time to check back on my (not really) broken G-Code and - Man, do I feel stupid now!-  
Fount out, Ground Control doesn’t like blank spaces in filenames…  
So, problem solved!  
Thanks for the suggestions anyways!

---

<div class="post-metadata">

**Author:** ![bar](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/bar/32/10_2.png) [@bar](https://forums.maslowcnc.com/u/bar)\
**Post date:** [May 12, 2018, 4:39pm UTC](https://forums.maslowcnc.com/t/groundcontrol-crash-on-file-opening/2969/6 "2018-05-12T16:39:57Z")

</div>

That still sounds like a bug to me!

Would you be willing to post the file which was giving you trouble so I can fix the issue? I’d like for Ground Control to not crash ever 😁

I tried just adding spaces to a file name and I couldn’t make it crash that way

---

<div class="post-metadata">

**Author:** ![Gero](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/gero/32/17487_2.png) [@Gero](https://forums.maslowcnc.com/u/Gero)\
**Post date:** [May 12, 2018, 5:15pm UTC](https://forums.maslowcnc.com/t/groundcontrol-crash-on-file-opening/2969/7 "2018-05-12T17:15:46Z")

</div>

> [@bar](#):
>
> adding spaces to a file name and I couldn’t make it crash

Bar, the OS would be nice 😉  
On Ubuntu Mate 18.04 LTS

> [@Papa](#):
>
> blank spaces in filenames

do not cause GC1.12 to crash.  
Edit: FW/GC 1.13 is also fine with blanks.

---

<div class="post-metadata">

**Author:** ![bar](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/bar/32/10_2.png) [@bar](https://forums.maslowcnc.com/u/bar)\
**Post date:** [May 12, 2018, 5:17pm UTC](https://forums.maslowcnc.com/t/groundcontrol-crash-on-file-opening/2969/8 "2018-05-12T17:17:15Z")

</div>

Great point @gero this was on Windows 10

---

<div class="post-metadata">

**Author:** ![blurfl](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/blurfl/32/9_2.png) [@blurfl](https://forums.maslowcnc.com/u/blurfl)\
**Post date:** [May 12, 2018, 8:20pm UTC](https://forums.maslowcnc.com/t/groundcontrol-crash-on-file-opening/2969/9 "2018-05-12T20:20:35Z")

</div>

OSX HighSierra works OK on an .nc file with a space in the name for me.

GC _does_ crash if I put a space in _its_ name, though…

---

<div class="post-metadata">

**Author:** ![Papa](https://avatars.discourse-cdn.com/v4/letter/p/9d8465/32.png) [@Papa](https://forums.maslowcnc.com/u/Papa)\
**Post date:** [May 14, 2018, 7:03pm UTC](https://forums.maslowcnc.com/t/groundcontrol-crash-on-file-opening/2969/10 "2018-05-14T19:03:47Z")

</div>

I’m not sure, if the Filename was the problem, and right now I’m completely unable to check because about 1 hour after my last post, the whole crappy AEG-Router went up in flames!  
It took my Z-Axis Motor and its cable with it. So bye bye CNC for now…  
But I can at least attach the File here:  
[Untersetzer 6mm-8mm Fräser-Ohne Bohrung.nc](https://canada1.discourse-cdn.com/flex031/uploads/maslowcnc/original/2X/2/21e6d7be8c06a266a0055fa5e34da838051ea07a.nc) (800 Bytes)

---

<div class="post-metadata">

**Author:** ![bar](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/bar/32/10_2.png) [@bar](https://forums.maslowcnc.com/u/bar)\
**Post date:** [May 14, 2018, 7:15pm UTC](https://forums.maslowcnc.com/t/groundcontrol-crash-on-file-opening/2969/11 "2018-05-14T19:15:32Z")

</div>

Wow! That is quite frightening! Are you sure that the router was the issue? What happened?

---

<div class="post-metadata">

**Author:** ![Papa](https://avatars.discourse-cdn.com/v4/letter/p/9d8465/32.png) [@Papa](https://forums.maslowcnc.com/u/Papa)\
**Post date:** [May 14, 2018, 7:37pm UTC](https://forums.maslowcnc.com/t/groundcontrol-crash-on-file-opening/2969/12 "2018-05-14T19:37:31Z")

</div>

I can’t think of anything else.  
The machine was running and I went into the house to help my daughter who has a broken Arm at the moment.  
A bit later I was surprised that it was so quiet in the shop, went out and the whole sled was already gone…  
Unplugged everything and got the garden hose (hope, that’s the right Word)…

I add some Photos:

 ![CNC%20Fire%201](https://canada1.discourse-cdn.com/flex031/uploads/maslowcnc/original/2X/f/f802370a249b1f5132fffe91f0e6de12bc3571f4.jpg) ![CNC%20Fire%202](https://canada1.discourse-cdn.com/flex031/uploads/maslowcnc/original/2X/a/ac4c6fe9675b9e1fa480972ef5e0c601886f1f6c.jpg)

---

<div class="post-metadata">

**Author:** ![bar](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/bar/32/10_2.png) [@bar](https://forums.maslowcnc.com/u/bar)\
**Post date:** [May 14, 2018, 7:47pm UTC](https://forums.maslowcnc.com/t/groundcontrol-crash-on-file-opening/2969/13 "2018-05-14T19:47:49Z")

</div>

WOW. That’s a real fire.

I’m really glad you caught it so quickly.

My instinct wouldn’t be to blame the router. An electric motor is not very likely to catch fire and they are very well tested. The router bit against the wood would be my guess. The friction of a dull bit against the wood, or if the bit is not moving can create friction and heat which can start a fire.

Would it be OK if we use your pictures in the next newsletter to remind folks to never leaver the machine running untended?

---

<div class="post-metadata">

**Author:** ![dlang](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/dlang/32/859_2.png) [@dlang](https://forums.maslowcnc.com/u/dlang)\
**Post date:** [May 14, 2018, 7:51pm UTC](https://forums.maslowcnc.com/t/groundcontrol-crash-on-file-opening/2969/14 "2018-05-14T19:51:42Z")

</div>

It’s possible that the router stopped moving (for whatever reason) and the  
friction of the spinning bit against the wood ignited the chips/sawdust.

This is more likely than the router itself catching on fire.

looking at the picture, the router is mostly damaged at the base, while the part  
of the router that has power and could start a fire is at the top.

So I would say this is FAR more likely to be a matter of the bit friction  
triggering a fire.

---

<div class="post-metadata">

**Author:** ![Papa](https://avatars.discourse-cdn.com/v4/letter/p/9d8465/32.png) [@Papa](https://forums.maslowcnc.com/u/Papa)\
**Post date:** [May 14, 2018, 7:54pm UTC](https://forums.maslowcnc.com/t/groundcontrol-crash-on-file-opening/2969/15 "2018-05-14T19:54:12Z")

</div>

> [@bar](#):
>
> Would it be OK if we use your pictures in the next newsletter to remind folks to never leaver the machine running untended?

Feel free to use the pictures!

---

<div class="post-metadata">

**Author:** ![Gero](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/gero/32/17487_2.png) [@Gero](https://forums.maslowcnc.com/u/Gero)\
**Post date:** [May 14, 2018, 8:09pm UTC](https://forums.maslowcnc.com/t/groundcontrol-crash-on-file-opening/2969/16 "2018-05-14T20:09:44Z")

</div>

😱🔥  
Shock!

I was suspecting the → ä ← in the filename, but on ubuntu it does not crash GC.  
The Bier-Untersetzer file runs well on my GC Maslow simulator. Prost!

---

<div class="post-metadata">

**Author:** ![Jayster](https://avatars.discourse-cdn.com/v4/letter/j/d78d45/32.png) [@Jayster](https://forums.maslowcnc.com/u/Jayster)\
**Post date:** [May 14, 2018, 8:13pm UTC](https://forums.maslowcnc.com/t/groundcontrol-crash-on-file-opening/2969/17 "2018-05-14T20:13:04Z")

</div>

If I remember right when you get the lost USB connection error the machine just freezes (with the bit still embedded). Would be nice if certain error codes forced the Z-axis to the safety height.

---

<div class="post-metadata">

**Author:** ![Papa](https://avatars.discourse-cdn.com/v4/letter/p/9d8465/32.png) [@Papa](https://forums.maslowcnc.com/u/Papa)\
**Post date:** [May 14, 2018, 8:14pm UTC](https://forums.maslowcnc.com/t/groundcontrol-crash-on-file-opening/2969/18 "2018-05-14T20:14:05Z")

</div>

I only tried on Windows machines.  
Win 7 and GC 1.09  
Win 10 and GC 1.13  
No luck on both Computers.

---

<div class="post-metadata">

**Author:** ![Gero](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/gero/32/17487_2.png) [@Gero](https://forums.maslowcnc.com/u/Gero)\
**Post date:** [May 14, 2018, 8:46pm UTC](https://forums.maslowcnc.com/t/groundcontrol-crash-on-file-opening/2969/19 "2018-05-14T20:46:06Z")

</div>

I got it to crash! 😂🤣😂🤣😂  
It is the → ä ←

Python error: UnicodeEncodeError: ‘ascii’ codec can’t encode character u’\xe4’ in position 54: ordinal not in range(128)

Surprising for me is that it did not crash the first time

---

<div class="post-metadata">

**Author:** ![blurfl](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/blurfl/32/9_2.png) [@blurfl](https://forums.maslowcnc.com/u/blurfl)\
**Post date:** [May 14, 2018, 8:50pm UTC](https://forums.maslowcnc.com/t/groundcontrol-crash-on-file-opening/2969/20 "2018-05-14T20:50:10Z")

</div>

Very sorry about your troubles.

Kivy on OSX doesn’t like the “Ã¤” character combination. The OS and most applicatins seem to accept it, but Kivy posts this error:

```auto
   File "/Applications/groundcontrol.app/Contents/Resources/yourapp/UIElements/viewMenu.py", line 92, in load
     self.data.config.set('Maslow Settings', 'openFile', str(self.data.gcodeFile))
 UnicodeEncodeError: 'ascii' codec can't encode characters in position 58-59: ordinal not in range(128)

```

[Next page](https://forums.maslowcnc.com/t/groundcontrol-crash-on-file-opening/2969.md?page=2)
