Turn software update?

[Robertspark]

I always thought that the Mach3 install was rather simple {i.e. it did not install any DLL's in any other directories other than the C:\Mach3 folder, and it did not fiddle with the registry {much}}

hence I am surprised that it would cause problems with the overall installation of windows or allowing it to boot.

Threading on Mach3 lathe or turn I believe was always complex / problematic because of its use of a single pulse index (only) for spindle timing.

Hence UCCNC should be better allowing for the use of a proper multi-pulse per rev encoder.

The problem with mach3 and mach 4 is that it is just the planner software and it does not provide any hardware so there will always be hardware and software incompatibilities because of having 1 software developer (artsoft) and many hardware providers. Sure you have access to the api (as long as you have signed the NDA) but details of what changes between versions is always sketchy.

Hence uccnc is miles better as you have 1 hardware and software developer and they should be able to manage and control their code to just work with their hardware. Problem is you ae still reliant on whatever access they give you to the hardware or software and whatever features they see as being beneficial or developable.

Centroid is another hardware and software provided as an integrated system. I looked briefly at their system many years ago now. I thought it was rather expensive given you buy the hardware and then you have to unlock the software functionality. Also you just unlock it to run...... I don't believe you can modify anything about it (other than m-codes) i.e. no screenset editing, and no plugins etc etc. You get it as it is and it works as it is, like it or lump it. you are also limited to the hardware.

There are a few companies listed here who may be able to offer alternatives.
https://mellowpine.com/cnc/best-cnc-controllers/

There was a Canadian motion controller manufacturer that looked promising a while ago, I just cannot find or remember their name. They seemed similar to the Warp9 ESS, but did the software package too. I think they did turn.... {its going to bug me now}

Again the problem is turn seems to be quite limited in who can do it or wants to provide it because it seems such a small market compared to all the other linear axis (Cartesian plane?) motion machines (routers, mills, 3 d printers, laser cutters etc etc).

[rodrigjup@gmail.com]

Hi Dazp1976,

That would be interesting to see if it works on Mach3 or Mach4 even. My plant tonight is to install Mach4 on machine and see if lathe function will work.

[rodrigjup@gmail.com]

@Robert

I thought so to, was surprised when the 62 version failed and after rebooting and reinstalling 66 had same errors. I knew that it has a kernel thread somewhere and eventually found it and removed it from system, Still no luck. Restoring it back to end of June windows backup didnt even sort it out so it must have some code that messes with windows at kernel level to prevent interrupt and other delays. I need to look for a win7 version windows to reinstall it.

Agree UCCNC looks the better product and shows promise but should'nt boast Mach3 compatibility if it cant support the claim. Only reason I am fiddling with Mach's is because UCNC has no lathe profile.


Had a look and am swinging between two decisions; (At the risk of swapping one set of risks for another)
1. Go for a decent compact all in one unit and ditch UC300eth/UCCNC - MASSO G3 USD 760, Centroid Acorn USD 660 as you suggest
2. Get Smoothstepper and run Mach3/4 until UCCNC release lathe profile. ESS-MB3 USD 414 plus Mach4 hobby license USD 200
https://www.masso.com.au/product/mill-r ... roller-g3/
https://www.centroidcnc.com/centroid_di ... rwQAvD_BwE
https://cncroom.com/en/product/ess-mb3/

Lets see what happens tonight.

Thank you

[cncdrive]

Our motion controllers are compatible with mach3 and mach4, however these softwares are very complex so ofcourse not 100% of the features are supported.
I think there is no motion controller on the market today which supports these softwares 100%.
We will test the mach3 lathe mode problem though what you reported, but we will need some time to get to it.
Lathe mode should work with3, if it does not then it could be a bug in the plugin version you running.
But I can tell you more after my collegues will test and debug it.

Our motion controllers do not support lathe mode with mach4, so there is no point for you to test that.

[Robertspark]

cncdrive are developing a turn application for uccnc. when it will be released I am not sure and how long before it becomes stable and has a selection of features (wizards etc) I am not sure. It was mentioned to be issued as a first release in the next development release or maybe the one after that but I believe that they are actively working on it.

I started off with the ESS (actually it was the USBSS/USS.... then switched to the ESS). I would not go back there as that was just a pile of development promises and "its on the lists" etc. encoder threading was asked for probably 2010, and I suspect its still on the list on the forum given the occasional poke and ask followed by the "within the next year / 6m etc". I always said it was a nice piece of hardware using a very fast FPGA....... however that was before I found MESA hardware..... and I learnt how to use the sourcecode to change the pin configs from whatever to whatever.

cncdrive are correct that there are no hardware which is 100% compatible with mach3 or even mach4. you tend to find that they are compatible with a specific version or release because subsequent "bug fix" releases break something else..... that required another plugin update etc etc etc.

MASSO was an interesting piece of equipment. bit expensive for me and I was not keen on everything on an all in one controller solution. but that is just me as I use 1 control box to control plasma, lathe, mill, routerx2 sharing 7 stepper drives between machines and having standard configs from inputs and outputs via plug in interfaces. not optimum but it works for me and my hobby setup.

where are you in the world?

[CL_MotoTech]

I have been holding off on my lathe conversion because I don't have a solid plan on a control. I have most of the parts, the ballscrews, steppers, drivers, etc.. But without a known control I don't want to actually convert.

I have a Mach 3 license, and I could buy an ESS (had one years ago) and go that route, but I had enough issues with Mach and the ESS on my mill that I'd rather not go back to getting tortured again. Yes, I made parts, many parts in fact. However, there were times where the software did weird stuff and it drove me crazy. I am told Mach is more reliable in turn than mill, but who knows?

I have used LinuxCNC and find it reliable, but I find myself tired of dealing with Linux. I have three computers sitting on a shelf that would all run it just fine, but it would be a chore to deal with drivers and what not, I am sure.

So here I wait on the UCCNC turn profile. I rarely encounter issues with it on my mill, and I'd like to continue down that path my lathe.

I looked heavily at Acorn, but I agree it is too pricey and locked down.

[Robertspark]

what do you find wrong with Linux or linuxcnc?

I appreciate the learning curve is steep but once you get a working config it just works

I used to be one of those guys who wanted a newer looking GUI with better "features" then saw the light of the simplicity of AXIS.... it just works and can be tweaked for other things (wrong forum I know but I'm always keen to learn others experience .... I may come back to uccnc if it develops beyond linuxcnc which is possible)

[rodrigjup@gmail.com]

@cncdrive

How do I got about getting a warranty replacement ?

A comms errors bombing out the application is not a feature error, its a "not fit for release" error or a hardware error.

The auto install and manual install software on UC300eth website install different versions of plugins on same computer as far as I can tell. Already a sign of trouble imo.

I have been in IT (studied electronic engineer) for over 15 years involved in technical and software divisions and I can honestly say that the last time I had the kind of experience I am having now with UC300eth/Mach3 was in the 90's. The problem isn't so much only with the error but the lack of support for clients like me who may pick up a bug or mistake. It is superficial and almost non existent both on semi live interactions like email and, on technical documentation. The people on this forum not withstanding. I appreciated their help a lot.

I am pretty sure that I am not the first person who experiences a "UC300ETH not respond!" error and strange that no-one can tell me exactly what triggers the error in the software in order to establish some insight as to what may be wrong (comms speed, buffer sizes, CRC etc.) . I have exhausted numerous computers, windows versions, LAN cables, LAN hubs, and even got a windows 7 server to test.

Despite this I have managed to right my first G-code and setup Mach3 to work properly on my Lathe/mill system. But I can't keep resetting the UC300 board every 4 minutes to keep the system functional after "comms errors" !

I am 85% sure UC300ETH is NOT compatible with MACH3 and would suggest that anyone else avoids falling into the same trap I have. Has anyone actually got a UC300ETH to work with Mach3 Lathe yet ? Maybe start from there.

Here is previous email sent to support with some of the plugin versions tested;
""" Hi,

As per conversation below, I have now been a week into trying to get UC300Eth controller to work properly on Mach3 Turn. Being an IT guy, thought this would be straight forward. Followed Manual instructions and always end up with a UC300eth comms error. On some configs it will work for a while and eventually display UC300eth comms error.

Used two different laptops with different versions of windows as well. Pings fine initially but ends up comms lost error. Reinstalled the Mach3 software a number of times and used both the auto UCNC plugin utility off the UCCNC website and the manual one but no avail. Eventually found clue in controller blue light which appears to go off indicating firmware issue.

I noted the following;

1. Default plugin versions -------------- > Blue light on, Plugin version 1.022, BL 1.00, FW 1.017 HW id 002 = UC300ETH comms error.
2. If I do auto plugin update from your website then I get -------------- > Blue light on, Plugin version 1.022, BL 1.00, FW 1.037 HW id 002 = UC300ETH comms error.
3. If I do Manual plug in update from your website the I get -------------- > Blue light on, Plugin version 1.013, BL 1.00, FW 1.017 HW id 002 = UC300ETH comms error.
4. If I use Mach3 config menu to update plug then I get -------------- > Blue light on, Plugin version 1.013, BL 1.00, FW 1.017 HW id 002 = UC300ETH comms error.

Its now apparent that the plugin firmware is the problem and depending on which update method you pick, you end up with different settings particularly the Firmware version.

Can you kindly indicate;
1. Which are the correct plugin, firmware, BL, etc version that will work on Mach 3 (particularly turn profile) ?
2. Where can I get them and installation procedure.

IP configs for PC and Controller are 10.0.0.59 /33 subnet 255.255.255.0, IP gateway 10.0.0.0 or empty, NO DHCP as I am using a direct link
"""""""
And the reply telling me that plugins are not a problem (((:

""""""
Dear JP,

Thank you for your email.
The firmware is packed in the plugin and so the firmware required for the plugin to run automatically updates if nessessary.
You do not have to download any firmware, figure out which one is correct for your plugin etc. this is all done automatically by the plugins.

Blue light going off does not indicate firmware issue. The blue light shows active communication between the controller and the PC.
Firmware error is indicated with the green LED blinking on the UC300ETH, but firmware is corrected automatically by the plugin on the next plugin run.

How is your UC300ETH connected to the computer? Direct connection or via network router/switch?
If via router, then try it with direct connection.
Also verify your ethernet cable, possibly try another cable.

--
Best Regards,
Balazs
""""""""""""""""""""""""""""""""""""

I can only see a board replacement being a last desperate option.


Sorry but I am being honest and above is a pretty mild version of what my thoughts are in this regard. Apologies for long write up.

[rodrigjup@gmail.com]

@Cl_Mototech;

I am also keen on UCCNC but can't wait for a lathe profile. I suggest you be careful as not all is as simple as it is suggested. Despite that I am really excited at getting the lathe to work this far and if it wasn't for the risk of falling into another trap, I would have bought something else whilst I waited for UCCNC lathe profile. Although unplanned, I have invested a lot of time in Mach3 so would prefer to use that and avoid learning a new utility from scratch. I am now Mach and UCCNC capable at configuring and basic lathe level.

I suspect the UC300Eth comms error should be relatively easy to resolve via the plugin but the root issue with me is lack of depth and effort in the after sales support.

I imagine the new UCCNC lathe profile release will have a number of bugs and the speed and depth of support will be important.

I have contacted ESS supplier for quote, was not sure which BOB to use but you and Robertspark are scaring me. Can't handle another "misfire".

We should stay in touch once we get Lathes working, should be fun. If I get it working, will share info no problem.

Rgds

[rodrigjup@gmail.com]

@Robertspark;

I stay in South Africa.

A friend and I are building a small engineering service to design and build small prototypes for mining metallurgy and some sailing gear for small racing dinghies at our club.
He is almost finished with a 3mx3m router (calls it RotorusMaximus ,lol) and does fibreglass/carbon moulding etc. I do the CAD (fusion) and 3D printing part, Lathe, mill part.

You ?


Rgds
JP