-Ted,
Just to comment on the pressbrake setup Andy Pugh helped me set
up.https://forum.linuxcnc.org/30-cnc-machines/42100-pressbrake-cnc-control-setup-questions?start=100#228476.
Interesting that your pressbrake also is a 25 ton Accupress.
It is working good for ram control, set end depth, bend repeat.
The backstop works, but because of homing not working it is not
convenient to setup.
- Andy,
Having never used a CNC press brake it was all a bit of a guess, and
mainly an exercise in making a LinuxCNC system that was table-driven
rather than G-code driven.
Did a great job without experience running a press brake!
But, it does bender-specific motion, including allowing the operator
to nudge the brake a bit further if it has under-bent before moving on
to the next bend.
This option works good, we use it a lot for getting the first bend depth!
I have noticed on developer mailing list work is being done on a custom
homing module. home.comp
https://github.com/LinuxCNC/linuxcnc/commits/dgarr/homebase
Is this something I could utilize with my existing setup?
Would my GladeVCP still work if I do any updates, since the switch to
python3?
(I am using 2.9 master, before the python3 updates.)
One thing I learned from that is that I probably would use motion if I
was doing it again.
-Andy,
Would you use motion and setup the joints and axis in the hal file,
instead of using simple_tp ?
A combination of motion.comp, home.com, and a custom press.com?
Thanks,
Earl
*************************
**Earl Weaver
**************************
On 4/24/2022 12:21 PM, Ted wrote:
Subject: Re: [Emc-users] Variables for instantaneous transit vector
from python? (long)
Message-ID:
<CALQw8iOGM9jTV7Gh8Ps63vA0=_arcsedzkudzibbkyu0uln...@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Hey I won't be much help but I would love to see how you did a break
press
gui!
Andrew - I really do need to put together an entry for the wiki on
this - we haven't quite given it the "full wrap" yet; it got the the
point of daily supervised testing but stalled at that point (date: Dec
2018, I bet you can guess why) - however I did upload a screen cap
from it at: https://pasteboard.co/nyWk9elvzxj7.png if it's of
interest. The main points were to emulate the existing nomenclature of
the press, so the vertical ram is "Y" (not R or X, for instance), and
the two back-gauges (X and Z, also by those names originally) were
servo driven. The Ram itself in this application was hydraulic with a
Vickers proportional valve (0-10v control) and a glass scale attached
- so it turned into a servo axis as well. We initially shied-away from
trying to drive the valve in that tight of a loop, because we thought
the system might cavitate, but it responds really really well that
way. Way better than simply up-fast/down-fast/slam-stop!
This project had about a dozen different (less than successful)
approaches but the production version uses a more streamlined custom
component that handles only safety and logic rather than motion
control. (Our first attempt was to build a comp with full motion
control, but it turned out to be too jumpy) - so the motion is
actually controlled by triggering a couple of g-code files. Jogging or
manual single bends are straightforward jog implementations,
semi-automatic is the daily-use feature that the operator sets
waypoints and times - so we have ngc files for ram down, ram dwell and
ram retract that reflect that. Although there is a plan for full-auto,
we haven't bothered to implement the fully-auto feature, which due to
the change in our comp file got simplified to just plain old g-code
that they would write. We skipped on that due to operators not being
interested in that level of complexity. They also didn't seem
interested in wizards for taking material, knowledgebases, k-factors,
tooling details, and building numbers - they just wanted to run the
ram down to the number they set and keep repeating. Still a very
hands-on type of process for them.
We took graphic and layout concepts from the original operators of the
machine (it was an Accurpress 25 ton unit with a win98 control), as
well as other shop operators using the current generation control on a
larger unit but intentionally not wanting to copy it verbatim - as it
turns out a number of the operators liked our different layout.
Ted
_______________________________________________
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users
