Messages

1

Finished Screens / Re: Mach3 2010 Screenset - Now available

« on: August 18, 2018, 11:00:04 PM »

Thank you!

2

Finished Screens / Re: Mach3 2010 Screenset - Now available

« on: August 18, 2018, 09:14:48 AM »

I too have a Chinese USB controller.
Could you post the special macros here?
That would be awesome!

3

General Mach Discussion / Re: Mach3 Windows 10 update -- don't do it

« on: May 16, 2018, 10:18:10 PM »

I thought Mach3 3.043.066 was the latest version??

4

VB and the development of wizards / Re: M10P1 NOT WORK USB MOTION CARD :o

« on: May 02, 2018, 06:17:55 PM »

From another thread here:
The technique here is to edit the existing GCode so that the +Z moves are just one step (in my case +0.002) and the –Z moves are also just one step (-0.002) then set the Z axis direction pin to the laser trigger pin allocation. The time delay between the Z axis completing the two virtual steps and the laser switching is so small that it can almost be considered instantaneous and when I return to engraving the fine line in a soft wood there is no longer a dot at each end of the line.

An alternative option, which is also worth investigating, is the B axis direction pin. This is probably much easier to implement where the B axis ‘steps per’ are set to 1 and the B axis direction pin is mapped to the laser trigger (pin 16 in my case) then any GCode is edited to replace the Z axis moves with B1 to turn the laser on and B0 to turn it off. Again this command can almost be considered as instantaneous and tests have shown it to have equal results to when the Z axis direction pin was used.

I have the USB XHC MachIV controller (Rev 5) and at this point can't get the M11/M10 working. Understood per this current thread. My controller is 4-axis and I'm using the JTechPhotonics driver and their Pic-Convert (DAC) board which takes signals from the A-axis. Since M11/M10 aren't working and of course I'm getting delays and burning at endpoints, I'm intrigued with the above comments about using the B-axis (or C) but I'm confused as to how to set up the triggering with the dummy axis and how it comes into play regarding GCode.

An example of GCode might help me understand the difference between:
1. Switching an output utilizing a macro that contains the "ActivateSignal(Output 5)" for output 5
2. An M3 call.
3. Or using a dummy drive, i.e., how does that make things faster than options 1 or 2?

Also, I don't understand the part about using/mapping the B-Axis direction pin to trigger something?

5

General Mach Discussion / Re: m11 and m10 commands

« on: April 22, 2018, 09:47:05 PM »

I have the XHC MK-IV v5 and haven't been successful yet but I have an email to their tech support.

6

Third party software and hardware support forums. / XHC-MKX-IV Rev 5 issue controlling laser, JTechPhotonics Driver and PicConvert

« on: April 11, 2018, 05:35:51 PM »

The boards are all successfully talking to each other, well sorta.

I have an oddity with the XHC and the spindle output controlling the on/off of the laser itself. As a safety feature of the PicConvert board, I've wired from the XHC's Spindle Output#1 to the PicConvert Board input for enabling the laser only when a call is made from within the Gcode for an M03. I just happened to discover that issuing an M03 (normal start of the spindle) actually turns the laser OFF instead of ON. And M05 (normal stop) actually does the opposite.

I'm using Mach3 and I've unchecked and checked active low / active high for Spindle Output, OutPut #1, etc. to no avail.

For now I've swapped the M03 with an M05 at the start of the GCode and vice versa at the end of the file. Terrible workaround!

This means I have to make sure the spindle start command has been invoked BEFORE I turn on the laser. The Spindle has been removed and I've built a drop in laser attachment in its place. This way I can carve as needed then remove the spindle and start laser engraving the work-piece.

I haven't crossed swapped the wiring and don't want to do that, i.e., positive to negative. I have the positive out from the XHC going to the positive in to the PicConvert.

I tried other outputs on the XHC and made matching changes in Mach3 for those outputs on the spindle setup tab. I was unable to measure any appreciable voltage changes on those outputs when calling for an M03 or M05. Only Output #1 will work. However, I also discovered that I need to have power switched on to the VFD for the output #1 to enable the PicConvert to send signal to the laser via the JTechPhotonics driver.

The issue lies in the XHC-MKX-IV Rev5 board.

Has anyone seen this before or could give suggestions on how to make it more conventional?
I haven't even gotten to the M11P1 (ON) and M10P1 (OFF) yet.

The image below is in regards to voltages taken at Output #1.


I'm wondering if I need some sort of pull-up resistor.

I appreciate you all looking at this.

7

General Mach Discussion / Re: 3040T Chinese router, Y axis not working

« on: January 05, 2018, 10:08:55 PM »

Attach your xml file for others to look at.

Also, does the Y-axis work using the MDI or the pop up onscreen MPG pendant (press tab key on keyboard)?

8

General Mach Discussion / Re: Issue with XHC USB Controller and axes direction

« on: January 05, 2018, 06:55:27 PM »

All working!

The codes for all the moves in the shipped macros were for metric! I finally studied them closely and came to realize that the first axis (Z) was trying to drive down 5 inches after touching off and crashing. I don't have that kind of room on the 6040Z. After I picked myself up off the floor from smacking myself in the head, I got it sorted out. Man, it was kicking my rear end.

Anyway, I had to massage the AutoTool script as well to slow things down a bit. It was traveling like a bat out of Hades. Now smooth.

But there's more to the story. The plugin for the pod showed a pull-off of 5 for the X, Y and Z in the Homing Pulloff area near the bottom of the dialog box for the configuration of the pod plugin. I had no idea what the pull off was for. Time, distance, etc. but it is for distance.

Another point worth noting, even though I had set the units to Inch from the drop down menu, I discovered my warm-up code was extremely small in accordance with the foot print and table outline on screen. Going to the Settings tab I discovered in the bottom right hand corner that the units of metric was still selected. Once I set it to Inches and did a Regen of the toolpath, things looked much better.

I hope this helps someone in the future.

Been a long intriguing day in my inner sanctum.
Peace and quiet and lack of interruptions can be your friend when it comes to sorting out the obvious. Ha!

9

General Mach Discussion / Re: Issue with XHC USB Controller and axes direction

« on: January 05, 2018, 04:07:34 PM »

Moving forward! (and backward)

Turns out I had to remove the jumper wire and actually put an additional wire for the +5. So now I have 4 wires to the M542 stepper driver from the controller. The gantry moves in both directions for each axis as it should.

I've also determined that the PE wire needed to be connected to a 0v pin. I used one of the pins associated within the "24v-Power Out" area closest to the Input area.  So I now have the E-Stop working and the Probe!

New issue is I can't get the Reference All Home to work. The axis moves, reaches Home, switch triggers as indicated on Diagnostics tab, axis reverses and goes completely to the other end and crams until I hit the Esc key. When I do hit the ESC key the axis reverses again (like a double touch off) but once it hits the trigger it reverses yet again. It takes two ESC and a Reset to get out of the whole referencing loop.

I'm still playing around with settings but getting nowhere. I been using Mach3 with a parallel port for years. This USB Controller is nice, but worthless if I can't get the Referencing to work.

My shop is warm with a nice wood stove, but the wood pile is dwindling along with my days off from work.

Anybody?

10

General Mach Discussion / Re: Reference not stopping

« on: January 05, 2018, 01:05:04 PM »

I'm having the same issue. I had a 3-axis XHC version IV controller which worked fine for homing and probe. Swapped it for a 4-axis version V and am struggling to get everything sorted out.

Interested in your findings.