Page 3 of 4 FirstFirst 1234 LastLast
  1. #21
    Quote Originally Posted by m_c View Post
    I suspect the problem with Mach and external motion controllers is to do with how oem/userDROs are allocated and updated.
    Not from my experience. It usually has to do with how the plugins work with macros. For instance, most chinese controllers do not support Mach3's GetVAR()function, which is usually used to find the trip point.

    Most plugins don't really on any specific DRO's.

    DRO conflicts between wizards and screens is a different issue, imo.
    Gerry
    ______________________________________________
    UCCNC 2017 Screenset

    Mach3 2010 Screenset

    JointCAM - CAM for Woodworking Joints

  2. #22
    m_c's Avatar
    Lives in East Lothian, United Kingdom. Last Activity: 15 Hours Ago Has been a member for 9-10 years. Has a total post count of 2,123. Received thanks 233 times, giving thanks to others 5 times.
    You probably are right, regardless I think it's safe to say beneath the surface, it was probably not top of the issue list with Mach 3.
    Avoiding the rubbish customer service from AluminiumWarehouse since July '13.

  3. #23
    Neale's Avatar
    Lives in Plymouth, United Kingdom. Last Activity: 5 Hours Ago Has been a member for 5-6 years. Has a total post count of 1,157. Received thanks 209 times, giving thanks to others 5 times.
    I came across a thread somewhere that had a lot of finger-pointing on the CSMIO/Mach3 compatibility issue. The gist of it seemed to be that because the Mach3 APIs were not particularly well documented, CS Labs worked it out as they went along and ended up using Mach3 functionality that they were not supposed to/should not have used. But it worked. Until Artsoft changed that bit of the code, which is why "updating" to an earlier Mach3 version fixes those particular issues. At the moment, at least, I don't seem to suffer from any of the problems that were presumably fixed in the later Mach3 releases.

    I agree that you have to be careful about user DROs, as some screensets use these to transfer values to associated macros. My own very trivial mod to the standard 1024 screenset does exactly that, and I spent quite a long while checking to make sure that it didn't interfere with anything else.

    I'm happy with what I have at the moment and it all works fine (apart from lack of support for proper two-motor homing) but I'm not sure that I would go the same way again. I keep looking at the UC300ETH, even though with a decent BOB it would work out to be a similar price to the IP/M. At least it has active support in place!

  4. #24
    Quote Originally Posted by Neale View Post
    However, there are a few odd things that can happen around M6 that aren't quite right if you are using a CSMIO-IP/M, and I wouldn't be surprised if it's not true for other CSMIO variants. For example, when I first started playing with tool height setting/resetting during an M6 tool change (i.e. between the calls to M6start and M6end), there were problems about losing X and Y position. The fix (in my case) was to "upgrade" to an earlier version of mach3. I'm currently using 3.043.028 which is not the latest version but can still be downloaded and installed. Remember to save any profile modifications in a custom machine profile and not mach3mill or any of the other out-of-the-box profiles or they will definitely be overwritten. The CSMIO compatibility thing is well-known and documented but you won't generally find it unless you go looking for it.
    Pretty certain I have run into this on my Bridgeport conversion, IIRC if you jog the table while in the M6 loop it will fault with ePid error.

    Any idea how i find the "well documented" info :)

  5. #25
    Neale's Avatar
    Lives in Plymouth, United Kingdom. Last Activity: 5 Hours Ago Has been a member for 5-6 years. Has a total post count of 1,157. Received thanks 209 times, giving thanks to others 5 times.
    Quote Originally Posted by Davek0974 View Post
    Pretty certain I have run into this on my Bridgeport conversion, IIRC if you jog the table while in the M6 loop it will fault with ePid error.

    Any idea how i find the "well documented" info :)
    Dave - take a look at this for starters. It has a couple of pointers to some general info on Mach3 internal architecture and at the bottom of the post a pointer to a pdf with a bit more specific info on the CSMIO problem. What it doesn't have is a "fix" as really there isn't a proper fix as such. However, I have found that .028 works fine (at least, I have had no problems with it on my machine) although it has a few other bugs which were fixed in later releases. I have a feeling that these were more lathe-related, though, so not something that worries me too much. I have seen another post that suggests version .022 as well.

    Maybe I overstated it a bit when I said "well-documented". The problem is well-documented in the sense that plenty of people have complained about it. In general, it shows up if you do any movement between an M6start and m6end. That rules out tool-height setting during a tool change, which is a bit of a bugger. The "solution" or work-around seems less well known but it does seem to work.

  6. The Following User Says Thank You to Neale For This Useful Post:


  7. #26
    Thanks,

    Quote Originally Posted by Neale View Post
    tool-height setting during a tool change, which is a bit of a bugger..
    THAT was the issue - was going to try that on the mill as it worked great on my mini-mill but that only had a UC100 controller on it. In the end i gave up and locked-out all the auto-set buttons on the screen-set for safety.

    It seems my idea will be ok as having the M6 macro move the Z axis works fine so having it also move the knee should be ok too.
    Last edited by Davek0974; 03-01-2018 at 12:38 PM.

  8. #27
    Thanks for that link, very interesting reading.

    As it seems to do with auto tool length and as i am not using that, it also seems to back up my hopes that my new ideas will actually function well for me.

  9. #28
    Neale's Avatar
    Lives in Plymouth, United Kingdom. Last Activity: 5 Hours Ago Has been a member for 5-6 years. Has a total post count of 1,157. Received thanks 209 times, giving thanks to others 5 times.
    I'm not sure if it's to do with TLO directly, or some of the stuff that gets done at the same time. I don't use TLO as I have the usual ER20 collet on my spindle, so no repeatable tool settings. I have modified some of the tool height setting macros that are often mentioned to work with my setup and controller (so it uses the CSMIO M31-type probing, for example) and I have the usual tool height, initial tool height for multi-tool operations, and second-tool setting macros. These all work fine with the m6 macros now, including various combinations of G28 and manual jogging while tool-changing. Seems pretty solid once I upgraded to the older Mach3!

    I'm also pretty confident that the probing and movement stuff works fine in X and Y as well, as I threw together some macros for X and Y probing while setting up the machine and they seemed OK. Not sure that I ever used them during an M6 sequence, though - that seems pretty unlikely. But at least they do work when needed, with the older Mach3 version.

    Still tempted every time someone mentions UC300ETH, though - seems to do pretty well everything the CSMIO/IP-M does, and in a supported package. If you buy an expensive BOB to go with it, anyway...
    Last edited by Neale; 03-01-2018 at 02:41 PM.

  10. #29
    Quote Originally Posted by Neale View Post
    Still tempted every time someone mentions UC300ETH, though - seems to do pretty well everything the CSMIO/IP-M does, and in a supported package. If you buy an expensive BOB to go with it, anyway...
    That looks ok, I'm a bit confused about the LPT part - if its ethernet, how can it be LPT??
    Anyways, the price difference will drop when you add in the cost of all the connectors/adaptors to get from the header sockets to real-world cable connectors etc. Still looks a good board though.

  11. #30
    UC300ETH + UB1 + UCCNC license = $380 US.

    Closer feature wise to the IP-S than the IP-M.
    And the macros always work.


    That looks ok, I'm a bit confused about the LPT part - if its ethernet, how can it be LPT??
    The LPT is just the way the pins are configured. They match a parallel port pinout, so that just about any breakout board will plug right into it.
    Gerry
    ______________________________________________
    UCCNC 2017 Screenset

    Mach3 2010 Screenset

    JointCAM - CAM for Woodworking Joints

Page 3 of 4 FirstFirst 1234 LastLast

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •