For a full-fledged Press Brake GUI
- NWE
- Away
- Premium Member
-
Less
More
- Posts: 80
- Thank you received: 23
15 Jan 2026 03:40 #341409
by NWE
For a full-fledged Press Brake GUI was created by NWE
I'm working on a press brake retrofit and need a GUI for it. This is going to be a full fledged GUI hopefully somewhat universal in hopes of making future press brake retrofits much easier. My goal is to come up with a couple example configs that could be packaged with LinuxCNC. I think I will create it using FlexGUI. My big problem is, I have little experience actually operating press brakes and will need some guideance on what features are required and which ones will just waste screen space.
Any offers to help with the coding will also be appreciated, however, I am willing to jump in myself and see what I can do with it.
I assume it will need at least:
0. Touchscreen freindly.
1. A "status" ribbon across the top displaying current operational status, including color-coding; like red for errors, yellow for warnings, green or blue otherwise.
2. DRO displaying position of movable beam (the die). How about also displaying positions of all axis? I performed service work on a 12 axis press brake a year or two ago, it had Y1, Y2 (left and right side of upper beam). The backstop consisted of two independant 3-axis stops: R1, R2, X1, X2, Z1, Z2. Crowning was 9th axis. Variable width bottom die was 10th axis. Sheet lifter in front of press had height and angle (axis 11-12)...
3. Program bends table. The program will need to contain various parameters for each 'bend' in the part. The table on the 'Run' screen hardly needs to display every fine detail. I'm thinking maybe 4 columns: 'Bend Number', 'Length', 'Angle', 'Notes'.
4. Tonnage control: how visible does this want/need to be for the operator? Least visible = just set it in the programming screen, or more visible, say a big guage displaying tonnage live?
5. Editting the 'part program' should probably be done on a separate tab or screen.
5.a My first version of the editor will be basic: enter the go-to positions for each axis to configure that specific bend.
5.b My goal for a 'real' editor is one where you can select dies, enter tab lengths and bend angles, and it produces the parameters for the bending program. This editor should have a 2D display of dies and plate and can possibly be a separate app.
Am I overlooking anything?
I will start drawing the ui...
Any offers to help with the coding will also be appreciated, however, I am willing to jump in myself and see what I can do with it.
I assume it will need at least:
0. Touchscreen freindly.
1. A "status" ribbon across the top displaying current operational status, including color-coding; like red for errors, yellow for warnings, green or blue otherwise.
2. DRO displaying position of movable beam (the die). How about also displaying positions of all axis? I performed service work on a 12 axis press brake a year or two ago, it had Y1, Y2 (left and right side of upper beam). The backstop consisted of two independant 3-axis stops: R1, R2, X1, X2, Z1, Z2. Crowning was 9th axis. Variable width bottom die was 10th axis. Sheet lifter in front of press had height and angle (axis 11-12)...
3. Program bends table. The program will need to contain various parameters for each 'bend' in the part. The table on the 'Run' screen hardly needs to display every fine detail. I'm thinking maybe 4 columns: 'Bend Number', 'Length', 'Angle', 'Notes'.
4. Tonnage control: how visible does this want/need to be for the operator? Least visible = just set it in the programming screen, or more visible, say a big guage displaying tonnage live?
5. Editting the 'part program' should probably be done on a separate tab or screen.
5.a My first version of the editor will be basic: enter the go-to positions for each axis to configure that specific bend.
5.b My goal for a 'real' editor is one where you can select dies, enter tab lengths and bend angles, and it produces the parameters for the bending program. This editor should have a 2D display of dies and plate and can possibly be a separate app.
Am I overlooking anything?
I will start drawing the ui...
Please Log in or Create an account to join the conversation.
Time to create page: 0.053 seconds