I monitor all my prints in the Terminal as they run.

Basically I sliced from Matter Control, copied the G-code to the SD-card, put that in the printer and loaded it. I start printing, get 3-4 layers in, and the printer stops. Scroll back through terminal it's stuck in a loop UNKNOWN COMMAND (numbers) ""

Only does that from the SD card, and only from the Linux version. Windows it worked great, we used it on large parts.

For the sake of troubleshooting I did test it with three different cards and multiple files. All sliced from Matter Control, all loaded onto the SD card... loaded into the printer, then launched from Matter Control.

I'm wondering if the slicing itself is bad, and if that isn't what is causing these blow-ups? If the slicing engine is generating gibberish-code that would cause all kinds of exceptions, loops and failures. I am going to try getting Cura up and running on here so I can slice some files as a test, then feed them to Matter Control and see if that makes any difference.

Happens at random, usually during a longer print.

I can get smaller prints to work just fine. I can get smaller prints to work off of the SD card. I cannot however get anything over about 10K to print from either the SD card or Matter Control on Linux.

Worked JUST GREAT under Windows, never had a lick of trouble.

Now... the problem is we are without a Windows computer for at LEAST six weeks possibly longer. We are counting on our Robo R1 to continue to fulfill orders during this time. If I don't get the orders out we don't get paid and so on so forth.

Where I am having a major issue here, I was told flat out that Matter Control was fully developed and deployed on Linux, that it worked flawlessly and that there would be zero issues running under Ubuntu. Now I am finding out this is not the case? The program is not in fact in a stable configuration and there is no plan currently to work through the issues? Am I understanding this correctly?

If this is in fact the case this is a huge blow to our business. I do not have enough Matter Control Touch tablets to keep everything running, and those are just as buggy, just as prone to "blowing up" mid-print for no detectable reason. ESPECIALLY on longer prints.

We need a solution. We do not have the cash-flow to fix our Windows computer at the moment, we are stuck using Linux.

I am open to suggestions that do not involve spending money that we simply do not have, or involve pirating software.

Unhandled Exception:
System.NullReferenceException: Object reference not set to an instance of an object
at System.Windows.Forms.XEventQueue+PaintQueue.Dequeue () <0x412f0920 + 0x000ed> in <filename unknown>:0
at System.Windows.Forms.XplatUIX11.GetMessage (System.Object queue_id, System.Windows.Forms.MSG& msg, IntPtr handle, Int32 wFilterMin, Int32 wFilterMax) <0x412e3280 + 0x003f7> in <filename unknown>:0
at System.Windows.Forms.XplatUI.GetMessage (System.Object queue_id, System.Windows.Forms.MSG& msg, IntPtr hWnd, Int32 wFilterMin, Int32 wFilterMax) <0x412e3230 + 0x00047> in <filename unknown>:0
at System.Windows.Forms.Application.RunLoop (Boolean Modal, System.Windows.Forms.ApplicationContext context) <0x412e1340 + 0x00e4b> in <filename unknown>:0
at System.Windows.Forms.Application.Run (System.Windows.Forms.ApplicationContext context) <0x412e1290 + 0x00057> in <filename unknown>:0
at System.Windows.Forms.Application.Run (System.Windows.Forms.Form mainForm) <0x412c0fc0 + 0x00033> in <filename unknown>:0
at MatterHackers.Agg.UI.WidgetForWindowsFormsAbstract.Run () <0x412cd5d0 + 0x0001f> in <filename unknown>:0
at MatterHackers.Agg.UI.WidgetForWindowsFormsOpenGL.Run () <0x412cd5b0 + 0x0000f> in <filename unknown>:0
at MatterHackers.Agg.SystemWindowCreator_WindowsForms.ShowSystemWindow (MatterHackers.Agg.UI.SystemWindow systemWindow) <0x412035e0 + 0x00391> in <filename unknown>:0
at MatterHackers.Agg.UI.SystemWindow.ShowAsSystemWindow () <0x41203570 + 0x0002a> in <filename unknown>:0
at MatterHackers.MatterControl.MatterControlApplication.get_Instance () <0x41086460 + 0x0004b> in <filename unknown>:0
at MatterHackers.MatterControl.MatterControlApplication.Main () <0x4101dea0 + 0x0020f> in <filename unknown>:0
[ERROR] FATAL UNHANDLED EXCEPTION: System.NullReferenceException: Object reference not set to an instance of an object
at System.Windows.Forms.XEventQueue+PaintQueue.Dequeue () <0x412f0920 + 0x000ed> in <filename unknown>:0
at System.Windows.Forms.XplatUIX11.GetMessage (System.Object queue_id, System.Windows.Forms.MSG& msg, IntPtr handle, Int32 wFilterMin, Int32 wFilterMax) <0x412e3280 + 0x003f7> in <filename unknown>:0
at System.Windows.Forms.XplatUI.GetMessage (System.Object queue_id, System.Windows.Forms.MSG& msg, IntPtr hWnd, Int32 wFilterMin, Int32 wFilterMax) <0x412e3230 + 0x00047> in <filename unknown>:0
at System.Windows.Forms.Application.RunLoop (Boolean Modal, System.Windows.Forms.ApplicationContext context) <0x412e1340 + 0x00e4b> in <filename unknown>:0
at System.Windows.Forms.Application.Run (System.Windows.Forms.ApplicationContext context) <0x412e1290 + 0x00057> in <filename unknown>:0
at System.Windows.Forms.Application.Run (System.Windows.Forms.Form mainForm) <0x412c0fc0 + 0x00033> in <filename unknown>:0
at MatterHackers.Agg.UI.WidgetForWindowsFormsAbstract.Run () <0x412cd5d0 + 0x0001f> in <filename unknown>:0
at MatterHackers.Agg.UI.WidgetForWindowsFormsOpenGL.Run () <0x412cd5b0 + 0x0000f> in <filename unknown>:0
at MatterHackers.Agg.SystemWindowCreator_WindowsForms.ShowSystemWindow (MatterHackers.Agg.UI.SystemWindow systemWindow) <0x412035e0 + 0x00391> in <filename unknown>:0
at MatterHackers.Agg.UI.SystemWindow.ShowAsSystemWindow () <0x41203570 + 0x0002a> in <filename unknown>:0
at MatterHackers.MatterControl.MatterControlApplication.get_Instance () <0x41086460 + 0x0004b> in <filename unknown>:0
at MatterHackers.MatterControl.MatterControlApplication.Main () <0x4101dea0 + 0x0020f> in <filename unknown>:0

Ok thanks for your reply!

First, I popped the hood and forced Mono to update, I had some really out-of-date components that installed with CAE Linux. Turns out that Mono doesn't update as part of the normal cycle because it uses it's own repositories... which had to be enabled manually. I was able to get three entire prints out without a crash. Aside from the usual ABS-warp-in-one-spot issues the parts came out excellent. THAT problem is caused by uneven heat coming up from the heat-bed... I will be troubleshooting that once I get the software working. This is less of a priority because I normally run PLA, seldom run ABS parts larger than a half-dollar. When I do, I get warpage in the exact same spot every time regardless of orientation.

Anyway we'll see. Thank you for the logging commands. I'll run a couple of test prints this evening after work and see how we do.

Ok that actually tells me quite a bit, I'll look at "mono" and see what is going on there.

Linux has left me behind, I was "down with it" back in 2007-2010.... it's really matured, especially Ubuntu.

If I had some kind of output (error messages or the like) I could begin working on it in my spare time. Hopefully someone comes along that is more up-to-date than I am.

@LordRichard I also seem to be having forum issues, apparently the forum software doesn't play nice with my browser.

I am running CAE Linux, which is an Ubuntu-based engineering build. I am also running the latest most up-to-date version of Ubuntu. Running Matter Control on this laptop is problematic. The software vanishes at random without any message or any event logging,

causing the printer to stop.

Sometimes I can finish a print, more often than not I waste a significant amount of material. Nothing else is running, just Matter Control. I have four gig of RAM on here, I don't see any signs of memory leak meaning I am not suddenly running out of memory. I suspect that the problem is the INTEL Graphic crap, however the Linux version doesn't seem to accept the force software rendering argument. I tried it and I still get random crashes.

Right now as it stands I cannot run Matter Control from this laptop which is a setback for us. I was told that MC was sufficiently stable under Linux to be considered reliable. This is not the case.

First step is overcoming the problem caused by the Intel chip-set. How do I force it like Windows? Second, where is the program logging events? In order to troubleshoot this I need a crash log or event log so I can figure out if this is my build, my laptop, or the software causing this.

A few weeks back I ordered a Robo with MC-Touch (sounds like a pedophile rap-star doesn't it?!). They sent the MC-Touch on ahead of the Robo box... so I unpacked it and hooked it up to my most troublesome machine -- my CTC. Within an hour I had every problem I ever had with that hunk of junk under control. That easy. I tried it on my HICTOP Prussia -- great steaming bowls of mac-and-cheese what an improvement over Rep-G. When the ROBO arrived I reluctantly hooked it up to that machine. Wow. Aside from a minor mechanical glitch the ROBO took off right out of box.

I am a big believer in MC-Touch at this point, however I found the following shortcomings that need to be address. Perhaps in a Touch II or Touch Advanced format.

1) First of all the tablet is prone to overheating and stalling. 99% of my glitches happen when the tablet gets very warm to the touch. Provision needs to be made to cool the tablet better.

2) Connections: Lets look at where all the wires connect and devise a way to spread them out so they give us better mounting flexibility.

3) Larger screen: Put the program on a much larger easier to use tablet. It can be challenging typing on this thing! I don't see any provision to hook up a Bluetooth keyboard, though I haven't really poked behind the Matter Control shell very much. I went into Settings to change my security options that was it.

4) EMI Shielding: The remaining glitches come from transients in the power-line and EMI in my shop. The simple act of turning on the box-fan under the work-station stalled the tablet. As did firing up my mill across the room. Either the power-supply is passing transients through to the tablet, or the boards themselves are picking up EM spikes. Regardless, this needs to be fixed.

5) General Improvements: Clean up the UI a bit, make the buttons more responsive, and allow me to customize my experience (sounds, colors, layouts) and we'll be perfect. There are a few other improvements I'd like in the software, but I'll wait until I have more experience with the package before I detail them.

When it is all said and done, we're almost there -- it's almost perfect. Address these concerns and you'll blow all other control schemes out of the water. Will be buying a second unit as budget allows.