P1 and P2 parkpositions

If you think you've found a bug post it here.

P1 and P2 parkpositions

Postby bhdavis » Sun Apr 11, 2021 8:17 pm

When I press the P1 and P2 park buttons on the main screen they both will bring up the axis calibration window. I have P1 for button 200 and P2 set for button 201.

I've attached screen shots of the Macros, the button settings and the resulting axis calibration window that pops up.

The machine does not travel to the park position.

Also I've created buttons and macros using 193 and 194 and copy/pasted the M200 text into those. Same thing happened.

If I type M200 or M201 into the MDI space the park feature works as it should.

In DEMO mode P1 yields an error message saying there are errors in the code but the axis configuration window does not come up.
In DEMO mode P2 works.

BH Davis
Attachments
M201.txt
(782 Bytes) Downloaded 418 times
M200.txt
(783 Bytes) Downloaded 411 times
P1_b.PNG
P1_a.PNG
bhdavis
 
Posts: 141
Joined: Tue Mar 23, 2021 7:36 pm

Re: P1 and P2 parkpositions

Postby ger21 » Sun Apr 11, 2021 8:57 pm

See the document "Buttons by Number" in UCCNC\Documentation

Park 1 is button number 193, and Park 2 is button 194.

200 and 201 are axis calibration.
Gerry
UCCNC 2022 Screenset - http://www.thecncwoodworker.com/2022.html
ger21
 
Posts: 2714
Joined: Sat Sep 03, 2016 2:17 am

Re: P1 and P2 parkpositions

Postby bhdavis » Sun Apr 11, 2021 9:04 pm

That was an error. Done some more testing and both P1 and P2 work in DEMO mode as long as I // out the Z-axis lines. But they still bring up the Z-axis calibration window when running the router.
BH
bhdavis
 
Posts: 141
Joined: Tue Mar 23, 2021 7:36 pm

Re: P1 and P2 parkpositions

Postby bhdavis » Sun Apr 11, 2021 9:27 pm

ger21 wrote:See the document "Buttons by Number" in UCCNC\Documentation

Park 1 is button number 193, and Park 2 is button 194.

200 and 201 are axis calibration.



Gerry,

Ahhh........... I see my confusion. It's BUTTON 193 but it's running MACRO 200. Somewhere along the line I got the idea that the button number ALWAYS matched the macro number. That obviously is not the case !!

Thanks,
Bernie
bhdavis
 
Posts: 141
Joined: Tue Mar 23, 2021 7:36 pm


Return to Report a bug

Who is online

Users browsing this forum: No registered users and 10 guests