Advanced Search

Not sure this is the correct topic, or where to start figuring out this problem.

I have a new build LCNC 2.9 from disto, EtherCAT, AC Servos with/ 23-bit absolute encoders, using ProbeBasic I have attached a screenshot with the issue show the Z-axis

"Sometimes" the "zero" will not display as zero, most of the time it works and will display as zero.  On the screen, it will show a non-zero value (-0.297), and a G0Z0 does not move.  If I move off that value and G0Z0 MDI, it moves back to the same non-value, also "zeroing" the Z-axis does not set the value to zero.  I have seen this on all the axes, not just the Z, but the same issue.  I have not seen a pattern yet, or what triggers it.

I am looking for an idea to explore the issue further.
Thanks!!!!!
 

What do you think about these values, and if they are good, are there any other tests you can recommend for this PC before I go all-in?

They are OK, the 0.494 is not great

Did you change the host static IP address to say 10.10.10.100 when you tested the 7I94T at 10.10.10.10?

You can check the EEPROM IP address with:

mesaflash --device ethernet --addr 192.168.1.121 --verbose

You should get something similar to this:

---

snip
  [space 2] Ethernet eeprom:
    mac address: 00:60:1B:16:08:00
    ip address: 10.10.10.10
    board name: 7I96S
    user leds: Hostmot2

 

Hello,

According to today's update of Linux CNC 2.10, the comment in the INI is still not recognized as such.
This modest entry is already sufficient.

WL_POS_X = 6.934 #

Without a comment, everything works normally.

It would be nice if someone could see over the knowers.

Thanks and best regards, Frank.

Perhaps his ethernet is just really, really speedy.

Not physically possible with a 100BT link 

100 Mbits/sec is 12.5 bytes/usec = ~5 usec for a minimum size packet
since packets need to be sent and echoed that's ~10 usec absolute
minimum for the smallest  (64 byte) packet (ignoring overhead and response time)

I tried to get the Mesa card on 10.10.10.10, but I never got that to work. I tried mesaflash --device 7i94t --addr 192.168.1.121 --set ip=10.10.10.10 before, but that didn't seem to change the boards IP address.

I ran the test again an now the values are probably more realistic:
What do you think about these values, and if they are good, are there any other tests you can recommend for this PC before I go all-in?

The discussion ot touchscreens missed out a third tech, Surface Acoustic Wave. I actually delibearately seek these out, as they have a hard glass front panel for scratch resistance, but are not as easily false-triggered as capacitive.

I use Touchy + jogwheel on both my machines, it suits me. The MDI tab is rather neat.

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.  

Perhaps his ethernet is just really, really speedy.

I love how the Linux and FreeBSD versions of ping show the actual numbers down to 3 decimal places, the Windows version rounds to the "nearest" millisecond.


Maybe try netplan for network config.

I use it for my Ubuntu server. It's weird but it works well and can configure anything however you like.

You can have multiple addresses for one interface, have static and dynamic IPs simultaneously, and much, much more.

It does not connect to the internet over Bell Wi-Fi for some reason tho, despite being able to communicate with other devices on the network.

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

forum.linuxcnc.org/30-cnc-machines/47066...ndles-jobs-jomach-32

Perhaps Archive.org is your friend.

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)

The problem with 12V is the wiring has to be quite thick due to the low voltage and high required amperage.

240W (average efficient PC) needs 20A at 12V.

With 20V, 240W only draws 12A, which requires less copper.

What power supply do you use?