Messages

41

CS-Lab / Re: Problem with index homing

« on: September 23, 2015, 12:23:05 PM »

Okay, here is CS Labs' response concerning the index homing problem.

Dear sir,
 
CSMIO/IP-A has security that watch over correct homing on index signal.
It's about the index signal can't show up too close or too far from homing switch signal.
More precisely  - homing failed if index signal shows up:
- closer to the switch than 1/24 of pulses entered into  "Config\Config PlugIns\Config\Index Homing\Encoder Pulses/Rev" window,
- further from the switch than 1/1 of pulses entered in to "Config\Config PlugIns\Config\Index Homing\Encoder Pulses/Rev" window.
 
In the mentioned window there must be entered an encoder pulses number with all edges incl. electronic gear of a servo drive if used.
 
If you set all like I described and the problem still exists then you will have to move the homing switch or turn the encoder so the index signal will appear in the safe range (between 1/24 and 1/1)
 
You can see the distance between the index signal and the homing switch signal shown impulses in the "PluginControl\Debug" window "Index Distances" area.
It would be great if the value is close to half of the value entered in "Config\Config PlugIns\Config\Index Homing\Encoder Pulses/Rev"
If the distance is displayed in red then it means that the index signal isn't in the safe range.
 
 

42

CS-Lab / Re: Problem with index homing

« on: September 22, 2015, 06:07:05 PM »

Hey Hood,

  Sorry for the delayed response. I've been buried under a few other projects for the past few weeks. I did get around to working with the mill yesterday.

As far as steps per unit of distance, I have worked out the pitch of the ball screws and gearing and encoder pulses per revolution.  I have been using the mill with index homing disabled and it moves and cuts accurately. I am sending off an email to the cs labs guys today and including the address to this thread. Hopefully it will be something simple that I missed.

43

CS-Lab / Re: Problem with index homing

« on: September 09, 2015, 12:25:38 PM »

Thanks for checking on that, Hood. I upped my input signals filer to 60ms and still no change. Thank you for the suggestion though. You may be right about the limit switches, Hood. Although I have triggered them with the mpg and found that once triggered, the machine has to back off past the trigger point for the contacts to open. It's as if there is 'spring' to the switches. Essentially, they don't open and close at the same point I wonder if this would have something to do with it. However, I tested the system by depressing the switches manually while the machine was indexing the axis (z in this case) and wether or not the error was triggered seemed time dependant. If I released it imediately, the error was triggered. If I held it for a little longer than what it would normally take for the macHine to back off the switch, the error would not be triggered. If I held it for even longer, it would send the error again. This leads me to believe that there is a window of oportunity on the encoder wheel during which the limit switch signal must go low otherwise the error is triggered. This is very odd indeed. I'm thinking of trying to contact cs labs direct  in the hopes that they can help resolve the issue. This machine is very accurate for its age, so I'd really like to have the ability to index home. Thanks for everyone's help thus far. I am truly grateful for the community on this forum and especially you, Hood. Your input has been indispensable on this project. I only wish we were on the same continent so I could pay you a proper visit and thank you in person!
Jonathon

44

CS-Lab / Re: Problem with index homing

« on: September 08, 2015, 11:18:48 PM »

In other news, I've gotten the tool changer to work beautifully with the DL06 PLC. I've posted a video under the 'posts your video here' section

45

CS-Lab / Re: Problem with index homing

« on: September 08, 2015, 11:17:50 PM »

Unfortunately, no. I think the problem is this-   The machine runs over the limit switch, then reverses to find the next index signal. If the machine find the next index signal before it completely backs off the homing limit, it sends the error. This is the reason that the error is triggered about 80% of the time. I did some tests and I found that if I slowed the machine to an unbearable crawl (2 to 5 inches a minute) it wont send the error. I think the macro should be modified such that the machine triggers the limit switch, then backs off the limit switch completely, then moves to the limit switch again at a much reduced rate. Only then will index homing work on this machine. Unfortunately, I don't know enough visual basic to modify the CS labs macro. Oh well.

Jonathon

46

Brains Development / DL06 tool change safety brain

« on: September 04, 2015, 02:23:15 AM »

Hi guys,

    I need help designing a brain that is based off the state of a single input (tool change limit switch) that will prevent Mach3 from moving or attempting to start the spindle in the event that the limit is not active. The 16 carrousel tool changer is under the direction of a DL06 plc. The PLC and mach3 communicate via modbus upon activation of the M6 macro.  I have the tool changer working at this time, but I want to implement a few safety measures in the system. I'm imagining a scenario where an inattentive operator triggers manual tool change movements when the spindle is active or the axis are moving. I'm also paranoid that of mach sending the Z axis crashing down through the changer while the carrousel is  in the extended position and linked up with a tool.  Basically, I don't want Mach3 to so much as twitch if the carrousel or the spindle dog move from their resting state limit switches. But I also don't want to send a stop command to Mach3 whenever the switches go low. This would stop the program. Where could I send the command in brains without disrupting the M6 macro or the program in general?

I'll also be designing a brain that will cut power to the relays controlling the pneumatic solenoids whenever the machine axis are moving or mach3 is actively sending a run command to the spindle. I think I have a handle on this brain though. I'll simply create a brain that will set the output controlling the relay power to low if the axis velocity DROs have a non 0 value or if the spindle is active in mach.

Thanks for any and all help!

Jonathon

47

*****VIDEOS***** / Re: PLC tool change running!

« on: September 04, 2015, 01:03:54 AM »

LOL! Thanks! I tell you what, that Scotsman has been more help than you can imagine! Still have a few more kinks to work out but home plate is in sight!

48

CS-Lab / Re: Problem with index homing

« on: September 03, 2015, 08:08:44 PM »

Those were my numbers as well. The window to which I am referring can be found by going to the top right of the menu bar in mach3 and clicking plugin control. There select CSMIO I think and the widow appears. Its the plugin window where you can see how much voltage is going to each drive and which inputs and outputs are active. I'm not at the shop currently, so I don't have it in front of me, otherwise I would take a picture.

jonathon

49

CS-Lab / Re: Problem with index homing

« on: September 03, 2015, 07:10:39 PM »

Oh lord, I'm so sorry hood. I wrote off that last reply about the gearing in a hurry on my phone and I didn't proofread. What I meant to write is as follows:
The gearing is 24 teeth on the x and y servos which mesh with  40 teeth gear on the ball screws.
On the z axis the gear on the servos is 24 teeth as well, but it meshes with a 40 tooh gear which in turn drives the 60 tooth gear on the ball screws. I think my math is correct.



Also, should I even pay attention to the encoder pulse count in the CSMIO plugin window? Will that tell me how many pulses per revolution the encoders have?

50

CS-Lab / Re: Problem with index homing

« on: September 03, 2015, 03:06:00 PM »

I did try 8000. I even tried 10000 and it still would give the same error. 'Index distance not within allowed limit'