Hello Guest it is April 19, 2024, 01:15:43 AM

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - jderou

Pages: « 1 2 3 4 5 6
51
Time to start yanking wires!  One last look at it....


Mostly gutted...


I decided to mount the PC internally to try and keep things neater, wires shorter, etc.  I came across a touch screen at work, picked it up for a whole $20.


So the thinking is the motors are good and I will use them.  The existing power supply should power the motors just fine since they did with the original drives, right?  The original power supply is just 120v rectified with a large cap so 170vdc.  More on this later.

The drives are here, so time to get busy wiring.  Lots and lots of wires, and lots of reading material.  I had to fab some angle brackets to mount the drives card style.  This kept them directly over the existing fans.


At this point I was able to power up the drives and make some initial moves.  Servos were not tuned, but motion was still decent right out of the box.  This was very basic at this point, no limits, no servo enable, but I had motion.  I also ran into an issue.  I could not (or rarely could) turn the drive power on without tripping a breaker.  I even burnt out a contact on my power switch.  The current draw was way too high at startup.  If you look at the pic above I have a power resistor inline after the rectifier.  This allowed me to turn it on, but limited me on performance.
To fix this, I needed to add a relay that would pull the resistor out of the circuit after a delay.  Well I need a servo enable relay, a relay to bypass the resistor, and a timer.  At some point I planned on adding a PLC, because I plan on adding a toolchanger and who knows what else down the road.  So PLC added, two relays for servo enable, and limit wiring tied to enable relay.  The PLC is programmed to close the first relay then the second after a couple seconds.  It is also tied to Mach via modbus, and locks out the reset button when servos are not enabled.


So at this point it is functional, though the interface leaves much to be desired.  A simple touchscreen and keyboard will do for now, time to fabricate a real operator interface.





52
Finally getting around to documenting this, it has been a few months now since this project started.


This all started when I fried two of the original servo amplifiers (http://www.cnczone.com/forums/servo-motors-drives/244822-fry-servo-amplifiers.html).  This is a pretty large machine, travels are 20 x 40 x 20.  It was not meant to be in a garage, so replacement parts are priced accordingly.  A repair place quoted me $700 each to possibly repair the amps.  New price is $1400 each.  Not gonna happen, and I was sick cause I had parts to make.
Here is the machine at that time


I had long been dreaming of getting rid of the clunky dos-based control but there was one thing that kept me from doing it,...It worked and was very accurate.  Having been through Mach builds before I know sometimes things can be less than predictable (the windows based motion control anyway).
With the idea of it "working" out of the way, it was time to look for another solution.  As an aside, I make custom footboards for bass drum pedals  
Luckily I had several stocked up, but I needed to get the machine going again asap.
I had received a private message from Larry Kenny of Larken Automation (www.viperservo.com) several months earlier when I was researching the idea.  At the time it was between the Viper 200 and another drive CNC4PC carried.  They were the only reasonably priced drives that accepted step-direction and could handle the servo power requirement.  The servos are SEM 140v, 6.5A continous, 30A peak, 31in-lb.
After a phone conversation with Larry I was confident that the viper 200 was the way to go.  Larry was very helpful and support means a lot in this kind of project.  3 viper 200's and a BX7 breakout board on order...

53
Brains Development / Why did this work?! Modbus addressing
« on: January 31, 2014, 08:11:36 AM »
I now have Brains writing a integer from Mach to the holding register of a Micrologix 1200 PLC.  I can't understand how it is working though!

According to the manual, the holding register addressing should start at 40001.  I set the Address Modbus(Var) in the serial plugin to 40001, with 4 registers and Output-Holding.
The test Modbus worked fine, I was able to read write to these registers.

In Brains is where I struggled to write to the appropriate register through the Modbus output.  The information was going somewhere in the PLC, cause I was able to read it back through brains also, but I don't know where it was going.
I was, however, able to write to the correct register by using the Sendstring output.  This was not appropriate for sending an integer though.

So anyway, after most of a day, I changed the Address Modbus(Var) to 0 and that solved the problem.  I don't understand this though, and that bothers me!

How is it getting to the correct address? ???

Thanks,
Joe

54
General Mach Discussion / Re: What is wrong with my cutter comp!?!
« on: January 17, 2014, 07:58:30 AM »
Figured it out.  I turned the "advanced compensation analysis" back on.  It wasn't doing anything with the original toolpath, appears to be working now.  Thanks for the help.
Joe

55
General Mach Discussion / Re: What is wrong with my cutter comp!?!
« on: January 17, 2014, 07:49:43 AM »
Tried removing the G91, and added a perpendicular lead in.  No luck, still rotated like the picture above.  The toolpath is intended to be rectangular.  The rotation changes based on the tool diameter I enter.  Somehow it is like it is re-compensating on every line.
N100 G20
N102 G0 G17 G40 G49 G80 G90
N104 T1 M6
N106 G0 G90 G55 X-6.7 Y.0015 A0. S1069 M3
N108 G43 H1 Z.25
N110 Z.2
N112 G1 Z0. F25.
N114 G41 D1 X-6.1969
G1 Y.5015 F30.
N116 G3 X-6.6969 Y1.0015 I-.5 J0.
N118 G1 X-8.4952
N120 Y-3.0856
N122 X-4.8986
N124 Y1.0015
N126 X-6.6969
N128 G3 X-7.1969 Y.5015 I0. J-.5
N130 G1 G40 Y.0015
N132 Z.2 F40.
N134 G0 Z.25
N136 M5
N138 G28 Z0.
N140 G28 X0. Y0. A0.
N142 M30

56
General Mach Discussion / Re: What is wrong with my cutter comp!?!
« on: January 16, 2014, 09:05:25 PM »
Pretty sure Fanuc requires the G91, so force of habit.  Don't know what that has to do with the question though.

57
General Mach Discussion / What is wrong with my cutter comp!?!
« on: January 16, 2014, 10:08:21 AM »
Simple program, just a rectangle, with lead in/out line and arc just as I would do on a Fanuc control.  Most of my results have been that the control just stops, doesn't know what to do on the entry to compensation.  This one is really strange, it is like it is cancelling/applying compensation on every line. 
I have "advanced compensation analysis" in ports & pins unchecked.  With it checked no compensation happens.
Can't figure this one out, need help please!

%
O0000(CUTTER COMP)
(MATERIAL - ALUMINUM INCH - 2024)
( T1 |  1/2 FLAT ENDMILL | H1 | D1 | CONTROL COMP | TOOL DIA. - .5 )
N100 G20
N102 G0 G17 G40 G49 G80 G90
N104 T1 M6
N106 G0 G90 G55 X-6.1969 Y.0015 A0. S1069 M3
N108 G43 H1 Z.25
N110 Z.2
N112 G1 Z0. F25.
G90 G91.1
N114 G41 D1 Y.5015 F30.
N116 G3 X-6.6969 Y1.0015 I-.5 J0.
N118 G1 X-8.4952
N120 Y-3.0856
N122 X-4.8986
N124 Y1.0015
N126 X-6.6969
N128 G3 X-7.1969 Y.5015 I0. J-.5
N130 G1 G40 Y.0015
N132 Z.2 F40.
N134 G0 Z.25
N136 M5
N138 G91 G28 Z0.
N140 G28 X0. Y0. A0.
N142 M30
%

58
Brains Development / Re: Set modbus output in brain
« on: January 05, 2014, 09:45:14 AM »
Did you come up with a solution to this?  Having a similar problem.
Joe

59
PoKeys / Triggering Pokeys Pin status through Modbus via Brains
« on: January 04, 2014, 12:22:08 PM »
Hello,
I have a Pokeys 56e that I have setup with Modbus to mach3 pc.  I am having no problems bringing inputs from the board into mach3 brains.  I am having trouble setting pin states from brains.  Can anyone point me in the right direction?  Not sure whether the pin should be setup as input or output.
Thanks,
Joe

Pages: « 1 2 3 4 5 6