Hello Guest it is June 12, 2024, 11:06:22 AM

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Tony Bullard

Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 »
1
Mach4 General Discussion / Re: Mach4 Trace not generating tool path
« on: May 12, 2024, 03:43:48 PM »
Thanks for the extra effort. I hope ArtSoft sees your post.

2
Mach4 General Discussion / Re: Mach4 Trace not generating tool path
« on: May 12, 2024, 11:37:26 AM »
Thank you, Graham. I do appreciate your help. Hopefully it will work in future versions. I had a plasma application where the trace function could have been a quick help.


3
Mach4 General Discussion / Re: Mach4 Trace not generating tool path
« on: May 12, 2024, 10:07:45 AM »
I'm still unable to use the Mach4 Trace feature. See above. Will someone try to do a simple trace and see it it works for them? It shouldn't have to be done on the working machine. It should work in software only I would think. Thank you for any help.

4
Mach4 General Discussion / Re: Mach4 Trace not generating tool path
« on: November 02, 2023, 07:47:10 AM »
It seems unusual to have the same problem with four machines. Will someone try to run this Mach4 Trace and see it it works on their machine. Thank you.

5
Mach4 General Discussion / Mach4 Trace not generating tool path
« on: November 01, 2023, 09:03:02 AM »
I’m trying to use Mach4 Trace on a Windows 7 Mach4 Hobby licensed machine. I’ve also tried it on another Windows 7 and two Windows 10 computers.

Mach4 Hobby Version 4.2.0.5036 Build 5036
Profile Mach4Mill WX4.set

For a test I am tracing a 1” square with origin X0.0 Y0.0.

The path is X1.0 Y0, X1 Y1, X0 Y1, X0 Y0.

The process:
Enable and home the machine.
Set X Y and Z G54 Zero
Open the Trace Tab.
Click trace.
Except the three default pop up screens: Trace Start, Feed Rate For GCode and Trace Start X0 Y0.
Jog to X1 and click Line End Point.
Jog to Y1 and click Line End Point.
Jog to X0 and click Line End Point.
Jog to Y0 and click Line End Point.
Click End Trace and save GCode file.

The path is not generated in the Tool Path Window when Line End Point is clicked and the path is not in the GCode file. Attached are two of the error messages I get in the process.

Attached are the error logs and gcode file.

Any help with these errors would be appreciated.

Eddit: I can't post anymore attachments.

7
PoKeys / Re: Mach4 Pokeys 57E with FRO
« on: January 03, 2023, 07:36:57 AM »
The 3 volt battery slot if for the RTC, real time clock. I suggest you read the Pokeys 57 user manual. https://www.poscope.com/wp-content/uploads/downloads/Pokeys/Manuals/PoKeys%20user%20manual%20(19.8.2017).pdf

If you have too much signal noise use a digital encoder for FRO as mentioned above.

8
PoKeys / Re: Mach4 Pokeys 57E with FRO
« on: January 02, 2023, 07:52:33 AM »
"To do some tests on the fly I took these 5 volts from a PC USB socket (cut a common USB cable and use the red and black wires).
The board is normally powered with LED lighting." So you're powering the board with 5 volts?

"I connect a potentiometer following the instructions...etc etc"  Is it connected to the boards 3.3v and board GND as stated in the Pokeys 57 user manual? Or is it connected to 5 volts from a PC USB socket? The analog input is not 5 volt tolerant and the 57E is not grounded to the PC.

"the potentiometer values start to oscillate" Read the Pokeys 57 user manual for low-pass filtering for analog inputs signal noise. There is an easy "slider" adjustment for it.

9
PoKeys / Re: Mach4 Pokeys 57E with FRO
« on: January 01, 2023, 09:00:38 AM »
This is not what you asked for but there is an easier way to do it now. Set your Pokeys analog input pin, pot pin,  as shown on page 33 of Pokeys Mach4plugin_manual.pdf That's on Pokeys Device configuration / Pokeys pin mapping. Next enable Feedrate override and set its pin # and % of override on / Special functions. That's it. It works! See attachments. I think?

10
Thank you Craig and that explains it well to to me.

It lead me to Axis Override. I setup a button to test the OB6 axis override of  the Z axis. It woks well with this code:
Code: [Select]
                --in button script
--left button down script

local inst = mc.mcGetInstance()

-- Set the axis 6 to be the override axis for the Z axis.
mc.mcAxisSetOverrideAxis(inst, mc.AXIS6, mc.AXIS2);

-- Set the Z axis jog accel percentage to 25%.
rc = mc.mcJogSetAccel(inst, mc.AXIS6, 25);

-- Set the jog rate to 20% of the Z axis maximum velocity.
        rc = mc.mcJogSetRate(inst, mc.AXIS6,20)

        -- Start Z axis jogging in positive direction
rc = mc.mcJogVelocityStart(inst, mc.AXIS6, 1);


--in button script
--left button up script

local inst = mc.mcGetInstance()
mc.mcJogVelocityStop(inst, mc.AXIS6); -- Stop the axis.
-- Remove axis 6 from the Z axis.
mc.mcAxisRemoveOverrideAxis( inst, mc.AXIS6, mc.AXIS2 );


You are a great asset to this forum. Thank you again.
Tony

Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 »