Advanced Search

I can assure you a VNC of any kind is not included in the distribution ISO.

I don't think there is a prebuilt Probe Basic for the Pi. You would need to build from source

Just recompile it.

The whole idea of a more industrial gui is difficult to implement/deploy on linuxCNC since theres not really a premade unit with a unified set of controls. Everyone is going to have different physical setups. I think lots can be done in hal already but some stuff is hard to do, like the ability to not need a mouse by default. Axis is already pretty close to technically not needing a mouse to operate, but it lacks features. The peripherals needed to run axis (file manager, tool editor, gcode editor) kill the whole thing also.


second for the parameter page, I made an attempt to make a parameter display for axis, based on qtvcp code, but I am stuck on how to change them.
github.com/cakeslob/regularmac_800/tree/offset
Ive made good progress making the axis gui more fanuc like, PhilC has helped me a lot, and I use lots of stuff from qtvcp because it has all the features I want. I post this to show its not all gui whining but computers are hard.

 
 

by computer gui standards, its pretty shit, and its hard as all hell to do stuff, and this is the "new", they went with a dark mode.
But Cnc workflow wise, its very fast, stable and safe, with very little screwing around. Its annoying compared to the LinuxCNC guis, but the workflow is less clumsy.
they always blast me for this in irc
 

Wow that was simple lol. Thank you I also added M50 to the preamble to allow adaptive feed. Just to be sure but working great now. Thank you

alexandrap wrote:

Yes, it is still disconnected because I am waiting for the installation of the fast overvoltage electronic efuse TPS2596

To the 5V Mesa power?
I do not think any fuse is faster than silicium/silicone inside the chips.
Put a switch on the primary side of the power supply.

Are you sure the drives are in velocity mode?

If they are in torque mode, the tuning is completely different.

In velocity mode, the motors should strongly resist any attempt
to rotate the shaft (even with P=0)

cmorley wrote:

What would be a short list of requirements for an industrial screen?
No axis movement without START button?
No graphics?
Mostly text styles or more modern graphical elements?
Multi function soft keys? Hardware only keys.
What target monitor size?
Etc.

My preferences are very similar to @cakeslob's post.  I think Gmoccapy is the closest current GUI available, although there are quite a few changes I'd make if I were handed a magic wand.

• General Layout
  • 4:3 or 1:1, although it looks like I have to walk back my previous statement about commercial controls never using 16:9.  Siemens, Fanuc, Okuma and others appear to have 16:9 options on their latest controls.
• General concepts/restrictions
  • No on-screen controls can cause movement or spindle activation
    • This includes probing and tool-change functions
  • No axis movement (besides jogging & homing) unless cycle start is pressed.
    • i.e. for MDI you have to enter the command and then press cycle start
  • Icons/cartoons for function keys optional
    • Ideally, a GUI config page would be accessible where each softkey button could be named or have an icon assigned by the user.
    • Default to text in the desired language.
• Navigation
  • Option 1 - softkeys on bottom & side
  • Option 2 - softkeys on bottom, and external hardware buttons or selector switch for different screens/modes (i.e. 840d)
  • Option 3 - Haas arrow/page navigation
• Main screen
  • No backplot/preview
  • Large DRO - gmoccapy's DRO is excellent, although the "R/D" in lathe mode is annoying
    • User selects which axes are displayed, and gets to pick one of two 'sizes' to save some space.
  • Large G-code window
    • User-selectable font and size within window
    • No editing g-code inside main run screen
  • Spindle & override windows
    • No on-screen sliders/buttons. All adjustments made via external hardware.
    • No temperature bar for override % - a number is sufficient but a blinking/highlighted function is nice if not at 100%
    • Small temp bar for spindle load
    • Room enough for multiple spindles
• Jogging
  • External hardware only
  • Disabled unless jogging 'mode' is selected (i.e. as @cakeslob described)
• Auto
  • No run/stop or other motion via softkeys.
  • Part counter
  • Remaining time (estimate, of course) window/display
• Tool page
  • User settings page with checkboxes for which columns are displayed.  No digging in a yaml file needed.
  • User settings page has 'tool changer installed' checkbox along with number of slots
    • If selected, top of page has non-graphical array of the slot numbers plus spindle position, and empty boxes next to them which are automatically updated when a tool change is performed.
    • Although the Probe Basic graphics are impressive, I think they're unnecessary.  But a simplified display of what's in the tool changer or turret would be helpful.
• Parameters page
  • I'd like to see a page with realtime (or nearly) display of all parameters, at least the numbered ones.  I really miss this one in LCNC.

Sorry for rambling.

P=5-10 I=0 D=0
FF1 - 0.024 but still tweaking.
Deadband 0.00001

the servo will move but if the P value is much higher it will oscillate more and more untill it trips following error. the F error max limit is set at 50 currently which is ofcourse way to high for normal operations

Hi guys, the best way is to show so much detail that someone can pinpoint what's wrong.
Starting from lcec_configgen is often a good way for the ethercat-conf.xml
Servos and stepper motors almost always follow the CIA402 standard so there it is best to take the example from github.com/dbraun1981/hal-cia402/tree/main/example and mix that into the config. There are more nuances for drives but lets not go there unless needed.

I and others can help to see what's wrong with your config, you need to attach the errors and outputs from the linuxcnc startup. This output, together with the hal file and ethercat-conf.xml can be attached here.

Im at about the same step as you. Last night I used the XMLconfiggen to make an xml for the 3 servos i had plugged in at the time. seems reasonable at first glance but might need some edits. My Hal and Ini are based on Hakan's ethercat Rpi video/forum post. getting errors indicating my ini and hal are not up to snuff.
forum.linuxcnc.org/ethercat/42048-notes-...at-on-raspberry-pi-4

Tonight I will bash my head against the keyboard some more and see if I can get a servo to move.

Chris it worked ,thank you for your guidance.
For those learning to use qtvcp with hal, here is "Hello World"  example that turns on/off the embedded led in hal PushButton widget.

Start Qt Designer:
For a RIP install:
  Open a terminal and source the environment:
  $ source /home/YourPath/scripts/rip-environment
  $ designer -qt=5
For a package install:
  Open a terminal and type:
  $ designer -qt=5
Create MainWindow Widget
  Select MainWindow
Add the ScreenOptions Widget
  Drag and drop the ScreenOptions widget anywhere onto the MainWwindow widget
Add hal PushButton
  Drag and drop hal PushButton widget anywhere onto the MainWwindow widget
Save The .ui File
  Save the file as test.ui in a folder
Create a .hal file
  Open text editor and copy hal netlisting (see below), save the file as test.hal
  (make sure you save .hal file .ui file in the same folder)
At command prompt:
 $ halrun -I -f test.hal

Copy following into text file and save as  test.hal
# load realtime components
# load non-realtime programs
loadusr -Wn test qtvcp test.ui
# add components to thread
# connect pins
net connect test.mybutton test.mybutton-led 
# start thread
start

You can try pinning the IRQ to the last processor
(and using the appropriate isolcpus line in the kernel command line)

0.494 might be OK, probably need to try, worst case, you might
need to slow down the servo thread to say 1.5 or 2 ms
 

I found this thread so interesting. I'm slowly sketching the plan to build my own press brake and hydraulic system is giving me some headache. I'd like to avoid 700bar system due to the prices of elements. The only cheap thing @ 700bar is hydraulic cylinders. The rest is problematic. Going lower pressure i need to grow bigger cylinders (plan to achieve 40 or 50 tonnes using two cylinders) bur regular gear pumps and valves (from agro world) should be fine. Du you have more photos/videos showing the hydraulic side of you brake? Are you still using it?

Yes, it is still disconnected because I am waiting for the installation of the fast overvoltage electronic efuse TPS2596