Hello Guest it is October 11, 2024, 12:02:35 PM

Author Topic: Mach4 Printer Port Discussions  (Read 1363834 times)

0 Members and 1 Guest are viewing this topic.

Offline ART

*
  • *
  •  1,702 1,702
  • Tough as soggy paper.
Re: Mach4 Printer Port Discussions
« Reply #530 on: October 07, 2014, 09:18:43 PM »
Note:

 Theres a workaround I found for a lockup error when configing Darwin under MachGUI.. close the Mach4 dialog while Darwins config is still open. Youll find it all works well then. If you dont close M4's selection dialog first it can lock up..

Art
Re: Mach4 Printer Port Discussions
« Reply #531 on: October 07, 2014, 10:03:52 PM »
Art,  the lockup I was referring to happens when configuring M4 and selecting the motion controller tab.  Darwin is not in configuration mode at that time.

Peter
Re: Mach4 Printer Port Discussions
« Reply #532 on: October 07, 2014, 10:04:38 PM »
Art,

It looks like Mach 4 build 2030 and Darwin 2035 (both licensed) is work exceptionally well.  The stutter I use to observe when jogging in Mach 4 has disappeared.  I'm running Darwin at 40,000 with no problems.  


-Freeman
I'm not a complete idiot...
    there are some parts missing.

Offline ART

*
  • *
  •  1,702 1,702
  • Tough as soggy paper.
Re: Mach4 Printer Port Discussions
« Reply #533 on: October 07, 2014, 10:09:09 PM »
Peter:

   You might want to drop that one in the bug report system, I havent seen it.

Freeman, thx, great to hear. Im runnign 40K as well with no touble on my laser.

Art
Re: Mach4 Printer Port Discussions
« Reply #534 on: October 07, 2014, 11:39:11 PM »
Hello Art,
 Got my license changed and Mach4 now shows 2030 licensed. I tried Darwin 2030, 2035, and 2038 and none of the inputs and outputs work. if I disconect the charge pump I can jog both axises.

Dave

Offline ART

*
  • *
  •  1,702 1,702
  • Tough as soggy paper.
Re: Mach4 Printer Port Discussions
« Reply #535 on: October 08, 2014, 07:33:50 AM »
Hi Dave:

  That means the license isnt working. At present theres no indication to you that it is or isnt, the only way youd know is
if the outputs dont work...and motion shuts down after 30 minutes or so.

  Check with the license guys to see if a new license is necessary for your ID.. I know they changed some...

Art
Re: Mach4 Printer Port Discussions
« Reply #536 on: October 09, 2014, 01:51:13 AM »
Sorry for the probably dumb question but How do you get a license? was it just for the early birds? i only see the demo download and not mention of licensing available yet

Offline ART

*
  • *
  •  1,702 1,702
  • Tough as soggy paper.
Re: Mach4 Printer Port Discussions
« Reply #537 on: October 09, 2014, 07:21:41 AM »
I think you just contact licensing.. theres supposed to be a link on the site for Darwin licenses..

Art
Re: Mach4 Printer Port Discussions
« Reply #538 on: October 09, 2014, 04:14:50 PM »
Hello Art

Since Mach 4 2038 is up on the website. Will Darwin 2030 work with this release or do i need to wait for Darwin 2030 to be updated to 2038. 

Eric
Re: Mach4 Printer Port Discussions
« Reply #539 on: October 09, 2014, 04:30:32 PM »
I've been unable to jog in M4 for a couple of revs now.  I uninstalled and then installed M4 2038 and Darwin 2038.  Motors jog in Darwin but not in M4.  One symptom is that when I enable Darwin and return to M4, the lower status line shows a stream of inputs from MPG1 and MPG3.  I do not have any MPGs installed.  I do have encoders but they are not moving to cause this.  With M4 2038, the history log no longer seems to be capturing events but with the previous version (2030) the log was full of MPG1 and MPG3 input events.  Disabling Darwin stops this stream.

Regarding encoders, I did find a minor bug in Darwin.  My encoder #0 channels A and B are connected to port2, pins 2 and 3 respectively.  The default channel A pin is 2 so I did not change this.  The encoder count would only alternate between 0 and 1.  Channel A input was being ignored.  If I change it to another pin then back to 2, everything is okay.  I suspect the pins are not loaded with the defaults shown (pin 2).

Thanks

Peter