Advanced Search

mesaboard is on 2. enp8s0 (see alsö static inet/inet6 addresses) It does show no carrier when unplugged.

eno1 (internet) has automatic connection method.

wlan has been turned off in order not to get confused.

I changed lan cables and now it behaves as it should mesact/machine finds the board and readhmid provides the information as expected.(mesact and terminal)
I wasnt aware of that since I did have acces to the internet anyhow(???).

so thank you very much for the moment This particular problem is solved.


Have nice days

geebee

please find attached 3 screenshots - left side are all the pins for cia402 component (they did all fit in screen) and right side is list of lcec pins in terminal. do you have any idea, which of these is "enable" pin? lcec.0.state-preop, lcec.0.state-safeop and lcec.0.state-op seem suspicious to me but then I do not understand why would 3 pins be needed. I would appreciate some hints on which pins should I try for enabling the drive and which would be most suitable candidate for making the motor spin. cia402.0.velocity-cmd would seem like most obvious candidate but is there anything else to add (so far in my experience it would have been 2 pins - one sets velocity, the other would be a bit output for "run/stop")
BTW cia402.0.controlword has value 4, which seem to match instructions in manual to set the parameter 50.04 to 4 (which means that reference is speed). does that help in any way? and since the manual says this:"Ensure the drive profile parameter 51.02 is set to CiA402 (0)" I would like to think that it's all good regarding the suspicion about needing different mode rather than cia402.
could you please share some link where I could see some cia402 templates that you mentioned?

I just try to set the card to work.

For the beginning, I want it to get a single stepper motor to turn with nothing else connected to it. For this, I need to configure some hal and ini files. I can use mesact but not pncconf for this.Later, I will analyze and try to understand these first files according to linuxcnc docs. What i intend to do is retrofitting a lathe to cnc (two, maybe three axes) , an additional axe for an attached lathe and on for a dividing head and some encoders /DRO This is all I might need in the (far) future.

Right now, I would just be happy to get linuxcnc, mesact ,board and stepper (driver) "Talk to one another".

cheers

geebee

OK so the next question is which Ethernet interface is the 7I95T connected to?
(enp8s0 or eno1)

(quick way to check is unplug the 7I95T RJ45 cable and see which interface shows "NO-CARRIER"

copy from terminal :

eebee@debian:~$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host noprefixroute
valid_lft forever preferred_lft forever
2: enp8s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 9c:53:22:48:4a:55 brd ff:ff:ff:ff:ff:ff
altname enx9c5322484a55
inet 10.10.10.1/24 brd 10.10.10.255 scope global noprefixroute enp8s0
valid_lft forever preferred_lft forever
inet6 2003:ca:745:4b0:8af0:56c3:81dc:59d1/64 scope global dynamic noprefixroute
valid_lft 172796sec preferred_lft 86396sec
inet6 fe80::1f98:abff:6d07:69fe/64 scope link noprefixroute
valid_lft forever preferred_lft forever
3: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 50:46:5d:6f:50:7c brd ff:ff:ff:ff:ff:ff
altname enp0s25
altname enx50465d6f507c
4: wlp7s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 6a:9d:f2:44:dc:7d brd ff:ff:ff:ff:ff:ff permaddr 64:70:02:18:5d:b8
altname wlx647002185db8
geebee@debian:~$

Sorry, i forgot to ask, why would you flash the 7i95T ?

JT wrote:

IMHO GUI's should not be included in the main repo except for Axis so as to not drag in a huge amount of dependencies for nothing.

If anyone asked me to decide what way to go, i would be very hard pressed to decide as i see benefits on both sides.
Should i elaborate?

Hi FOrum!

i have a Foxconn A74 Mainboard with 4GB DDR3_Ram, AMD Athlon X2 250 3Ghz.
I tried to upgrade to a graphicscard, i bought an Asus Radeon R7 240 with 2GB of DDR3 Vram.

Now my problems.. The latency overall is the same as with the onboardgraphics, bit i have massive spikes, up to 600000..

I tried: 

1.  Grub "radeon.dpm=0"
no luck, LinuxCNC greets me with a Readerror.

2. Grub "radeon.si_support=0 amdgpu.si_support=1 amdgpu.dpm=0"
no luck, LinuxCNC greets me with a Readerror. I checked which driver is used, it was amdgpu, but no luck.

As far as i can tell, the version without any kerneltweaks worked the best for me.

I have 1 Core isolated for LinuxCNC, nothing fancy in grub customized. 
Is there anything i can try to get the graphicscard to work properly?

Thank in advance, greets, TOm

Ich freue mich auch sehr darüber das NativCAM eine aktuelle Überarbeitung bekommt und bin allen dankbar die daran arbeiten.
Ich bin jemand der auf einer CNC umgebauten Langlochbohrmaschine Kleinigkeiten bearbeitet. Das was halt so in einer Tischlerei anfällt...
Hierzu ist NativCAM ein top Programm dafür.
So ähnlich wie WoodWop für eine Homag Maschine. Hier wird auch vieles an der Maschine programmiert.
Ich bin mir sicher, das dieses Programm künftig noch viele Möglichkeiten bietet. Ich werde mir mal die neue Version installieren und mich damit intensiver beschäftigen. Die derzeit installierte Version läuft leider etwas labil.

Danke an alle die diese Software am leben erhalten....

geebee wrote:

board adress changed to 10.10.10.11 and ping to 10.10.10.10 gives destination host unreachable. Ping to 10.10.10.11 is successful.

Are you changing the board IP or computer IP? Board address is changed using mesaflash, and there is never any reason to do it.
Computers address should be changed depending on the Mesa jumper setting, be it for 192.168.n.n (default) or for 10.n.n.n if you change the jumper as per the manual.

geebee wrote:

I remember rumours different regions or countries might require specific ip addresses in order for this to work

That is not true, both subnets used by Mesa (10.n.n.n and 192.168.n.n) are non routable IP addresses so they do not go out of the local network, hence have nothing to do with region or localisation.

geebee wrote:

The procedure you suggest in this thread does not work for me.

It always, always works if you follow it properly, so what does PCW's advice return?

What does the command:

ip a

return?
 

thanks, forgot to mention I already tried these hints also.

I repeated them anyway

board adress changed to 10.10.10.11 and ping to 10.10.10.10 gives destination host unreachable. Ping to 10.10.10.11 is successful.

Netmask for board connection reads 24,( I entered 255.255.255.0 )

I checked " use this connection only for resources on its network" in routes
Nothing shows in this window "Editing ipv4 routes for 7i95t" under Address. Netmask, Gateway and Metric. 7i95t is the name I gave to this connection. I did not add anything here since I have not (yet) been advised to.

For both addresses (10.10.10.10 and 10.10.10.11) mesaflash answers no board found.I am in germany. I remember rumours different regions or countries might require specific ip addresses in order for this to work

The procedure you suggest in this thread does not work for me.
Further aid will be appreciated

thx and best regards

geebee

forum.linuxcnc.org/27-driver-boards/3559...ethernet-mesa-boards

rodw wrote:

I don't like using backports. Never have used them.
 

"I don't use it" and "I don't like it" are not substantive arguments.
The problem is that there are newer versions of the libraries in the newer release. First of all, it is about Python, in which the authors constantly change or remove something, so even relatively new programs (from a year or two ago) do not want to run, or some of their functions do not work.
However, backports repositories are optional, you can activate them, install only what you need and then turn them off again.