Advanced Search

I always stuck in error I can`t resolve by myself for now.

1. It's usually a good idea to attach any error messages you get.
2. Share your config folder (compress and attach here)

Here is my current attempt to have a fanuc like gui
github.com/cakeslob/regularmac_800

I dont have all the controls mapped to the Tab/arrow keys yet, or a softkey menu

Cmo 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.

Fanuc has a nice workflow because you dont have to screw around with a mouse and find buttons and stuff like that.

- Not everything needs to be on the screen at the same time.
- I dont think people have a problem with graphics, most stuff is crude text shortforms.

- It uses a combo of hard keys for each menu -(some multi press buttons, ie press offset for tool, press offset again for work offset) and soft keys that change with each menu

- you can load/setup/run the program with like 5 buttons(some soft) + arrow keys

- some modes (ie edit/MDI/Jog/pendant/auto) disable other features , so you cant run a program from edit mode, you can edit a program in MDI mode, you cant jog in auto, etc

-the whole gui is bacically controlled by pg up/down, arrow keys, and function keys

- monitor aspect is usually 1:1 square, but thats uncommon in consumer stuff, so 4:3 is closest

- no axis movement until start button. so any probe routines or toolsets, you need to press cycle start.

Aciera wrote:

Not sure what GUI you are using but it seems to me that you might not have given the existing GUIs much consideration other then the fact that it does not look and feel like the controls you are used to.
External buttons can be implemented with most GUIs. Start/stop/pause, jogging, overrides, homing, etc. with physical buttons, encoders and potentiometers. This has been possible for a long time.
None of my machine refits use screen jogging buttons and _certainly_ no keyboard shortcuts.
Also tool and work offsets pages have been around for years.

As an example, Gmoccapy which I use, but there are others:
linuxcnc.org/docs/html/gui/gmoccapy.html#_hal_pins

I have tested out every gui to find the most similar one. All the GUI could be made to be like fanuc style, The cloest ones to fanuc style workflow were keystick and mini, but its been a long time since I was able to use those so maybe its nostalgia. Qtdragon or the smaller one could be made to work like fanuc style with not to much changes, but it would be more python backend behavior for keyboard behavior/navigation (no mouse needed), and softkey stuff than actual GUI organization, the layout of the small one (woodpecker?) is pretty close to what fanuc stuff looks like .

I figured it could be tested with a normal rotary encoder by setting the "home" detection 
index interval to the CPR of the encoder, so 2 index detection's with the proper delta
would arm LinuxCNC's index search.

I guess a fancier scheme would use it as an absolute scale ( generate the correct absolute
position after any  two index detection's  and a table lookup ) but I think that would need
a new homing routine rather than just a hal component.  

I'm not sure what you mean PCW,

Your initial ping statistics had 3 and 4 usec times which are not
possible unless you are pinging the host.

Also the address range of enp3s0 overlaps enp2s0
 
This is why it's suggested to use the FPGA cards 10.10.10.10 address.
( as it will not overlap a local network DHCP range )
 

The N100DC draws no more than ~20 W...
Basically a laptop CPU in a Mini-ITX format

It would be easier with a starting hal/ini file set because
while the Mesa and LinuxCNC pin names are known,
the specific signal names used are configuration dependent.

(signal names are arbitrary and everyone uses different ones)