REMAP M6 FOR GENEVA ATC
02 Nov 2018 13:39 #119814
by COlger81
Replied by COlger81 on topic REMAP M6 FOR GENEVA ATC
It does not update #5490. It does update #5400 with tool number.
The tool number is stored and recalled on startup. It is not storing and recalling the carousel current position though.
The tool number is stored and recalled on startup. It is not storing and recalling the carousel current position though.
Please Log in or Create an account to join the conversation.
02 Nov 2018 13:48 #119815
by COlger81
Replied by COlger81 on topic REMAP M6 FOR GENEVA ATC
EXAMPLE;
Shutting down at tool number 4.
After startup and before commanding the first M6, tool number shows 4.
Then if you command M6T8, it will move 8 pockets and show as tool number 8 which is actually at tool 12.
SOLUTION;
I need the CAROUSEL current position to pull the #5400 tool number persistent value on startup.
Shutting down at tool number 4.
After startup and before commanding the first M6, tool number shows 4.
Then if you command M6T8, it will move 8 pockets and show as tool number 8 which is actually at tool 12.
SOLUTION;
I need the CAROUSEL current position to pull the #5400 tool number persistent value on startup.
Please Log in or Create an account to join the conversation.
02 Nov 2018 13:59 #119816
by andypugh
Replied by andypugh on topic REMAP M6 FOR GENEVA ATC
No, I am afraid that I still don't understand the problem statement.
Are you using #5490 as the carousel position variable in the G-code?
Does #5490 get saved in to the vars file?
Are you using #5490 as the carousel position variable in the G-code?
Does #5490 get saved in to the vars file?
Please Log in or Create an account to join the conversation.
02 Nov 2018 14:09 #119817
by COlger81
Replied by COlger81 on topic REMAP M6 FOR GENEVA ATC
I think you just answered the question. It sounds like the carousel component does not by default save pocket position persistent or call from tool number value on startup.
Can you give me an example of G code line that would store a parameter from current pocket position?
Can you give me an example of G code line that would store a parameter from current pocket position?
Please Log in or Create an account to join the conversation.
02 Nov 2018 14:11 #119818
by andypugh
Replied by andypugh on topic REMAP M6 FOR GENEVA ATC
Why are you using "carousel"?
The fragment of G-code I gave you a number of posts back does all that carousel is doing in this case, and it should store the carousel position too.
The fragment of G-code I gave you a number of posts back does all that carousel is doing in this case, and it should store the carousel position too.
Please Log in or Create an account to join the conversation.
02 Nov 2018 14:21 #119819
by COlger81
Replied by COlger81 on topic REMAP M6 FOR GENEVA ATC
Using carousel component seemed like a nice and clean approach. It has everything i need built in, such as turret jogging and bidirectional mode. It works like a charm other than not saving and recalling the selected pocket. What is the benefit of not using the carousel?
Please Log in or Create an account to join the conversation.
02 Nov 2018 14:30 #119820
by andypugh
Replied by andypugh on topic REMAP M6 FOR GENEVA ATC
I admit I had forgotten about the jogging, if that is useful then carousel might be useful.
I normally think of "carousel" being mainly about decoding various types of carousel position encoders. (I wrote "carousel" but have never had a machine that needed it)
What I would suggest you do is to save the position from G-code after every tool change into a persistent variable (such as #5490). Then you need to subtract the number stored in #5490 from the required pocket position before sending it out to the carousel component. (In effect #5490 becomes a "home offset" for the carousel.)
I can think of neater ways, but most of those involve modifications to "carousel"
I normally think of "carousel" being mainly about decoding various types of carousel position encoders. (I wrote "carousel" but have never had a machine that needed it)
What I would suggest you do is to save the position from G-code after every tool change into a persistent variable (such as #5490). Then you need to subtract the number stored in #5490 from the required pocket position before sending it out to the carousel component. (In effect #5490 becomes a "home offset" for the carousel.)
I can think of neater ways, but most of those involve modifications to "carousel"
The following user(s) said Thank You: akb1212
Please Log in or Create an account to join the conversation.
02 Nov 2018 15:06 #119823
by COlger81
Replied by COlger81 on topic REMAP M6 FOR GENEVA ATC
Where can i find the carousel source code?
Please Log in or Create an account to join the conversation.
02 Nov 2018 15:17 #119827
by COlger81
Replied by COlger81 on topic REMAP M6 FOR GENEVA ATC
I'm definitely not scared of diving in and learning some code but by chance is there a line or 2 i could add to pull value from #5400 parameter (current tool) at startup?
Please Log in or Create an account to join the conversation.
Time to create page: 0.169 seconds