Small victory in the war against the Cincinnati cinturn 12u

More
08 Dec 2022 01:05 #258859 by andypugh

that matches my documentation. so set it to binary in the hal ?

For numbers < 10 BCD and binary are identical. 
(at least for the type of BCD that carousel understands) 
 

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

More
08 Dec 2022 01:23 #258862 by smc.collins
well, then there is a problem, because I am getting carousel failure to align errors. and the position of the turret is random. I'm open to suggestion on remedy's, but I need a bit of hep in the how to debug department. running my generator to spin the turret is getting expensive

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

More
08 Dec 2022 01:44 #258863 by andypugh
I assume that RANDOM_TOOLCHANGER isn't in the INI?
(This isn't a joke, much as it might look like one)

What is the exact error message? Is it from your NGC file? Which line of the NGC file?

Halscope the strobe and the carousel.0.current-position (along with ready and motor-fwd). Also, to be sure, carousel.0.pocket-number to check that is being correctly set.

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

More
08 Dec 2022 02:31 #258867 by smc.collins
No, I checked all of the files in the machine, and nowhere, even using search can i find RANDOM_TOOLCHANGER.

the error message is from my NGC file afaict, I just get a warning in axis,

failed to align carousel

I can do the scope tests tomorrow, how do I check the carousel.0.pocket number ? against what ? or to verify it with ? I can scope it and screen shot it tomorrow.

on a good note, the rest of the functions appear to be correct. I can grab the files off the Lathe and post them tomorrow afternoon

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

More
08 Dec 2022 16:48 - 08 Dec 2022 16:48 #258899 by andypugh

the error message is from my NGC file afaict, I just get a warning in axis,

failed to align carousel


OK, this is from your NGC routine and is if the wait-on-input for carousel-ready fails.

This could be because the carousel never believes itself to be at the correct position. Which could be either because it is reading the position incorrectly, or because the M6 (or T) command is picking a pocket > 6 or < 1.

I can do the scope tests tomorrow, how do I check the carousel.0.pocket number ? against what ?

Against the selected pocket number. Which should be the pocket number from the tool table of the tool you have chosen when starting the tool change.
Last edit: 08 Dec 2022 16:48 by andypugh.
The following user(s) said Thank You: smc.collins

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

More
08 Dec 2022 22:33 - 08 Dec 2022 23:01 #258919 by smc.collins
screen shots from scope, I am not sure about the behavior of Tloop, it just goes up 1 div and then drops right down, as if it is basically just sending a triggering signal. the car-pos-32 seems to be working at it is reporting position properly. So this looks like a issue with Tloop. I attached my hal files. 


this is currently in my main cinturn12u.hal I assume this is the problem 

net T-loop iocontrol.0.tool-prepare => iocontrol.0.tool-prepared

whereas this is commented out in my toolchangerBCD.hal

#net tool-prep-loop   iocontrol.0.tool-prepare iocontrol.0.tool-prepared

So is it safe to assume that this needs to be edited to and placed in either my main cintrun12u.hal or my toolchangerbcd.hal. I'd prefer to use the later if it makes no difference, because then ALL of my toolchange config exists outside of my primary hal file. Also, my brain is very smooth today, I hate german car engineers sometimes, I wish they would buy their electrical systems from GM and or Delphi 







      
Attachments:
Last edit: 08 Dec 2022 23:01 by smc.collins.

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

More
08 Dec 2022 23:08 #258927 by smc.collins
MGM attached his carousel file and I find myself confused about the behavior of the t loop now


this is in his file. it appears he might have a turret of some sort like mine

net T-loop iocontrol.0.tool-prepare => iocontrol.0.tool-prepared
#net tool-change-finished carousel.0.ready => iocontrol.0.tool-changed

#net tool-change-loop iocontrol.0.tool-change iocontrol.0.tool-changed
#net start-tool-change iocontrol.0.tool-change => carousel.0.enable

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

More
09 Dec 2022 00:02 #258940 by andypugh
This ought to work, but is a bit inconsistent in format:
net carousel.0.in    	 carousel.0.strobe
net car-locked             motion.digital-in-01
net car-lock 			motion.digital-out-01



#Digital  inputs
net bit0   carousel.0.sense-0 <= hm2_5i25.0.7i77.0.0.input-04
net bit1   carousel.0.sense-1 <= hm2_5i25.0.7i77.0.0.input-05
net bit2   carousel.0.sense-2 <= hm2_5i25.0.7i77.0.0.input-06
net        carousel.0.in 	  <= hm2_5i25.0.7i77.0.0.input-03

Could be
net car-locked             motion.digital-in-01
net car-lock 			motion.digital-out-01



#Digital  inputs
net bit0     carousel.0.sense-0 <= hm2_5i25.0.7i77.0.0.input-04
net bit1     carousel.0.sense-1 <= hm2_5i25.0.7i77.0.0.input-05
net bit2     carousel.0.sense-2 <= hm2_5i25.0.7i77.0.0.input-06
net strobe carousel.0.strobe    <= hm2_5i25.0.7i77.0.0.input-03

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

More
09 Dec 2022 00:12 #258942 by andypugh
I don't think that T-loop is a major problem.

Personally I would leave the changer in the middle of that loop, so that "change" starts the process and "changed" is signalled at the end, but doing it your way does mean that the system can do other things while waiting for the carousel. (of course you might not want to do that...)

But, you you don't seem to have logged the channels I asked for.

carousel.0.strobe
carousel.0.current-position
carousel.0.ready
carousel.0.motor-fwd
carousel.0.pocket-number

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

Moderators: piasdom
Time to create page: 0.105 seconds
Powered by Kunena Forum