Probe Basic - ATC sim parameter question

More
21 Jul 2022 22:30 #247992 by spumco
yes #5189 was just a numbered variable used to store data in the macro

Thanks for the confirmation.  And yes, I can see where someone with a 24 tool changer would run out of contiguous numbers.

Speaking of which... have you (or other qtpyvcp/PB devs) looked at the new LCNC tool dabase yet?  I've read the manual page, but I cant see if there's a UI somewhere to explore the features.

I'm wondering if it would make quite a lot of the remap/ngc gymnastics I've found in just about every toolchanger example moot.
keep going its nice having more eyes finding things at the scrutiny level you are employing!

Nothing is ever easy and I have to be persistent to digest any of this...

Please Log in or Create an account to join the conversation.

More
23 Jul 2022 02:35 #248093 by Lcvette
TurBoss has been actively working on the tool database and has it sorting image files for tooling, it's pretty slick. But i haven't played with it yet.

Please Log in or Create an account to join the conversation.

More
23 Jul 2022 05:35 #248094 by spumco
I did find the axis-sim with a tool.db sidepanel - a little difficult for meto follow.

In other news...

Both M11 and M12 have #<_my_current_pocket> = #5170 at the end.  But I can't find #<_my_current_pocket> referenced anywhere.

Only thing close is global parameter #<_current_pocket> (from the tool table).

Is this another parameter for testing that didn't get incorporated?

 

Please Log in or Create an account to join the conversation.

More
23 Jul 2022 15:19 #248125 by Lcvette
it appears it may be redundant in this scenario, but it has stored the current pocket to numbered parameter #5170, it may be precautionary in the event the if statement fails to complete, but even then im not sure it would be needed. however it may be used in the sim code somewhere but i have not looked at that yet to see. in any event it is available globally as written so could be useful. I will leave in the distribution subroutines for future use.
The following user(s) said Thank You: spumco

Please Log in or Create an account to join the conversation.

More
14 Aug 2022 21:23 #249736 by spumco
Lcvette,

I'm back on the ATCproject afer some life distractions, trying to wrap up everything.

I've got everything moving properly.  Last issue (I think) is synchronizing the ATC widget with the carousel.  When I start up LCNC and reference the carousel using the screen button (M13), my physical carousel homes to pocket #1 and the spindle orients properly.

Problem is that the ATC widget doesn't move during homing, and it initializes with pocket #1 on the left.  I get the "REFERENCING" on screen message, but the ATC stays oriented with pocket #10 to the right (3 o'clock).

I've tried manually 'moving' the widget using (DEBUG, EVAL...rotate...) and the widget moves.  Problem is that PB still thinks that pocket #10 is the currently aligned pocket.  If I put a tool in the spindle away, the widget doesn't rotate and the tool icon pops up in pocket #10 (which is now on the left - 9 o'clock).

Also tried editing M13 to rotate the widget during the referencing/homing sequence, but the same thing results.

I've not modified M13 other than adding my spindle orient M-code and carousel enable/homing commands as well as changin the number of pockets.

Other than that, the ATC widget moves as expected during tool changes and spindle load/unload.  It's just not synch'ed up with the physical ATC.

Any thoughts?

 

Please Log in or Create an account to join the conversation.

More
16 Aug 2022 05:16 #249853 by Lcvette
I saw this not too long ago on the sim,  but I can't remember the fix.  Try running an update on qtpyvcp and probe basic, I think that may have been the solution.   

Please Log in or Create an account to join the conversation.

More
16 Aug 2022 11:37 #249884 by spumco
Thanks.  I'm on qtpyvcp master and PB python3, LCNC-RIP
  • navigate to \probe_basic
  • git checkout python3
  • git pull

Is that the procedure?

Please Log in or Create an account to join the conversation.

More
17 Aug 2022 14:48 #249951 by Lcvette
I use gitkraken, so i just checkout the latest, but i would assume if doing via terminal it would be as you described, gotkraken has spoiled me.. lol

Please Log in or Create an account to join the conversation.

Moderators: KCJLcvette
Time to create page: 0.114 seconds
Powered by Kunena Forum