Anyone using Mach3 on a TinyG, CNCx? Possible?

Anyone using Mach3 on a TinyG, CNCx? Possible?

I am not sure how it would work, since MACH3 runs g-code itself, would they not compete with each other??

I don’t believe that you use Mach as GUI for the TinyG, If you wan to use the tiny G with gui you may want to look into Chilipepper for a gui.

This is what I was wondering as well. Reason in asking, yesterday I had a cut going I really needed to finish. Internet (Comcast) went out, called, they said there was an outage. Chilipepprs out. Back to the unfaithful tgFX. I don’t run endstops, after the fourth warning and stop of my CNC for an endstop warning I was done.

I really need a back up. Something I can plant on a machine and it just work.

Is it the visualization you want to have? I know you can run gcode sender locally, and it has a visualizer built-in; you really need the end-stops or a very organized workflow where you get the zeros sent before each effort though. At least that way, you are not dependent on the internet being up. That is the beauty of my mach3 build, but the shortfall is having to have parallel port computers to drive it.

@Bruce_Lunde ​, I’m pretty sure Mach3 can drive USB hardware also. Not to mention adding one or more parallel ports to a desktop is a reasonably easy, inexpensive affair.

@Kyle_Kerr I understand they (USB) are out there, but I have not heard from anyone how stable they are…I agree, I can maintain what I have with parallel ports, just looking to the future since XP is outdated and Win7 and parallel ports and MACH3 are non-functional to the best of my knowledge.

Visualization is not all that important to me. I’ve looked at a few options, but really seems kind of limited. Suppose I need to research more. Have plenty of machines laying around but all are windows 7 and up.

End stops. I played with them but really do fine without. I’m on a CNC router and have plenty of room to play and lay my work piece in various places. I design most my parts so I know the stock size needed and limits of travel. When I first started cutting I needed them but have not needed any in a long time. I set my zero between every cut based on where I need it. I ditched them as tgFX always triggered falsely due to surges and spikes…

Brandon, there is some work to get chilipeppr locally. Once chilipeppr load, you don’t need to reload it though. Did the Internet go out before you start chilipeppr?

Hey Dat, I’m looking into that as well. Internet dropped midway through the job and I only had a few lines loaded in the buffer.

I scanned the github page for chilipeppr. Getting it running locally is a job in and of itself.

I agree with @Dat_Chu after chilipeppr has loaded in the browser it is all local JS you are running so internet outages should not matter. Very curious what caused your issues. Perhaps @jlauer can chime in.

I’m wondering if its the websocket to Serial Port JSON Server that disconnected and that’s what is being referred to here, not that the Internet was disconnected. That would mean this issue has nothing to do with an offline version. Just a guess.

I haven’t seen the websocket being disconnected on chillipeppr. @jlauer , what steps would prompt such an occurrence.

I’ve seen the websocket disconnect in cases when the user’s machine is slow enough that the browser can’t keep up with all the processing. This can be more likely when it’s a Gcode file with lots of tiny moves. For each gcode line out, there’s going to be 4 events back and 4 browser UI updates per event, so 16 callbacks. (Gcode widget checkmark and auto-scroll, 3D viewer toolhead move, Axes widget update, Serial Port Console update). On my laptop I see about a 20% CPU load. On really slow machines you could get to 100% and then the websocket decides to give up.

Hmm, this reminds me to not change my old desktop for a Raspberry Pi as the json server machine any time soon :).

No, Dat, that’s not the case. It’s when the machine running ChiliPeppr is slow. The Serial Port JSON Server never has problems and can run on super slow/old hardware without any issue. It’s the desktop running the browser that can be the issue.

Oh nevermind me then :-). I generally don’t leave the chilipeppr web browser open once I have buffered the commands. I do like that I can resume the status at any point though.

@jlauer that may very well be the case. I have 3 laptops I run Chilipeppr on. One is decrepit and outdated, well sorta is a windows 7 32 but loaded to the gills, so I am never surprised when it just stops running code. The second is a fresh wipe, fresh windows 7 32 I can get about 3 hours of cutting done and it will just stop, no errors, not locked up, just stop…it is an old machine though. The last is a fresh windows 8.1 64, it’s a hot machine, typically runs Chilipeppr without issue, this is the machine that stopped when the connection stopped and I’m running a 1000 to 10000 in the buffer. I will note these are 5-8 hour cuts I’m making though.
It is a fantastic product and I would never complain. I was just trying to see if there were options running around.

@Brandon_Satterfield ​ your scenario is not chilipeppr in my experience. It’s tinyg not sending a r:{} response randomly after 1000s of lines. In that case all you have to do is hit ~ cycle start and everything keeps going without issue. Is that consistent with what you’ve seen? Meaning you did NOT get a websocket disconnect?