Re: [Emc-users] MESA 7i92H Saga
> I would get a USB <--> Ethernet or USB <--> WIFI dongle for internet,
> otherwise
> you are pretty much doing things the hard way
>
> You current (avahi etc) issues are basically because you have not setup the
> realtime Ethernet port with a static IP address as suggested in the hm2_eth
> man
> page
I thought I had set up a static IP. Although the odd thing is I can set the
mask to 255.255.255.0 and save it but when I get back into the dialog it shows
24. Go figure. I'll check the man page.
>
>
> Peter Wallace
> Mesa Electronics
>
> (\__/)
> (='.'=) This is Bunny. Copy and paste bunny into your
> (")_(") signature to help him gain world domination.
>
>
>
> ___
> Emc-users mailing list
> Emc-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-users
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users
Re: [Emc-users] MESA 7i92H Saga
On Sat, 17 Aug 2019, John Dammeyer wrote:
Date: Sat, 17 Aug 2019 14:15:14 -0700
From: John Dammeyer
Reply-To: "Enhanced Machine Controller (EMC)"
To: "'Enhanced Machine Controller (EMC)'"
Subject: Re: [Emc-users] MESA 7i92H Saga
Alright.
Installed the newest LiveCD Stretch version replacing the Wheezy in the office.
Has no problem interfacing to my 192.168.0.1 router. However using the
network tools dialogs adding a second IP like 192.168.1.125 doesn't work. On
my WIN-7 system I added a second IP group with a value 192.168.126 and it has
no trouble pinging the mesa card at 192.168.1.121. The mesa is plugged into one
of the network switches on the main network. This also worked on the Wheezy
system where I could select which network IP I wanted active and then I could
also ping the mesa from the LinuxCNC box.
Next step. Remove the network cable to the switch. Plug the mesa directly
into the now Stretch version LinuxCNC box. Reboot the LinuxCNC system. Now I
can ping the mesa from the LinuxCNC system. Of course I no longer have
internet access on that system. 8-(
But the MESA is alive!
Next step, run LinuxCNC selecting the MESA version.
Crap!
hm2_eth: ERROR: Failed to execute '/sbin/sysctl -q
net.ipv6.conf.eth0:avahi.disable_ipv6=1'
and then Debug info.
hm2_eth: ERROR: Failed to execute '/sbin/sysctl -q
net.ipv6.conf.eth0:avahi.disable_ipv6=1' Shutting down and cleaning up
LinuxCNC...
There are some major network issues with this box. That what is trivial in
WIN-7 for accessing both network groups doesn't work on the Stretch version.
That plugging in the ipv4 network causes complaints with the ipv6.
Oh and with the mesa plugged in, it does the usual timeout looking for the
network before it finishes booting.
What's the simple step by step configuration needed to make this work? What
other debugging information is required?
Thanks
John
I would get a USB <--> Ethernet or USB <--> WIFI dongle for internet, otherwise
you are pretty much doing things the hard way
You current (avahi etc) issues are basically because you have not setup the
realtime Ethernet port with a static IP address as suggested in the hm2_eth man
page
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users
Peter Wallace
Mesa Electronics
(\__/)
(='.'=) This is Bunny. Copy and paste bunny into your
(")_(") signature to help him gain world domination.
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users
Re: [Emc-users] MESA 7i92H Saga
Alright. Installed the newest LiveCD Stretch version replacing the Wheezy in the office. Has no problem interfacing to my 192.168.0.1 router. However using the network tools dialogs adding a second IP like 192.168.1.125 doesn't work. On my WIN-7 system I added a second IP group with a value 192.168.126 and it has no trouble pinging the mesa card at 192.168.1.121. The mesa is plugged into one of the network switches on the main network. This also worked on the Wheezy system where I could select which network IP I wanted active and then I could also ping the mesa from the LinuxCNC box. Next step. Remove the network cable to the switch. Plug the mesa directly into the now Stretch version LinuxCNC box. Reboot the LinuxCNC system. Now I can ping the mesa from the LinuxCNC system. Of course I no longer have internet access on that system. 8-( But the MESA is alive! Next step, run LinuxCNC selecting the MESA version. Crap! hm2_eth: ERROR: Failed to execute '/sbin/sysctl -q net.ipv6.conf.eth0:avahi.disable_ipv6=1' and then Debug info. hm2_eth: ERROR: Failed to execute '/sbin/sysctl -q net.ipv6.conf.eth0:avahi.disable_ipv6=1' Shutting down and cleaning up LinuxCNC... There are some major network issues with this box. That what is trivial in WIN-7 for accessing both network groups doesn't work on the Stretch version. That plugging in the ipv4 network causes complaints with the ipv6. Oh and with the mesa plugged in, it does the usual timeout looking for the network before it finishes booting. What's the simple step by step configuration needed to make this work? What other debugging information is required? Thanks John ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
Re: [Emc-users] Homing following error (was PID feed forward)
It is master as of a few days ago. The previous version which worked fine was master from a few months back. I'll get the results of linuxcnc_info tomorrow. I'll try 2.8 tomorrow. Les On 17/08/2019 20:16, Dewey Garrett wrote: I'm not clear on details of the install reporting this problem (commit or LinuxCNC version, os, kernel, etc). Posting the output from the command: $ linuxcnc_info would be helpful. If using the master branch, you should probably try 2.8 and report. The buildbot instructions at the bottom of the page: buildbot.linuxcnc.org don't seem to show 2.8 but you can browse http://buildbot.linuxcnc.org/dists/ to see if your OS and kernel (rtpreempt or rt(rtai)) have debs available for 2.8. For example, in the stretch directory, debs have names like: linuxcnc-uspace_2.8.0~pre1.5067gf178a1739_amd64.deb The hash following the 'g' is the commit (f178a1739) The f178a1739 is the most recent commit for the 2.8 branch (as of today 17aug19) as shown by commit listing at: https://github.com/LinuxCNC/linuxcnc/commits/2.8 If you find an appropriate deb, it can be installed by commands: $ wget the_deb ;# copy buildbot link $ sudo dpkg -i the_deb ;# install the deb ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
Re: [Emc-users] Homing following error (was PID feed forward)
I'm not clear on details of the install reporting this problem (commit or LinuxCNC version, os, kernel, etc). Posting the output from the command: $ linuxcnc_info would be helpful. If using the master branch, you should probably try 2.8 and report. The buildbot instructions at the bottom of the page: buildbot.linuxcnc.org don't seem to show 2.8 but you can browse http://buildbot.linuxcnc.org/dists/ to see if your OS and kernel (rtpreempt or rt(rtai)) have debs available for 2.8. For example, in the stretch directory, debs have names like: linuxcnc-uspace_2.8.0~pre1.5067gf178a1739_amd64.deb The hash following the 'g' is the commit (f178a1739) The f178a1739 is the most recent commit for the 2.8 branch (as of today 17aug19) as shown by commit listing at: https://github.com/LinuxCNC/linuxcnc/commits/2.8 If you find an appropriate deb, it can be installed by commands: $ wget the_deb ;# copy buildbot link $ sudo dpkg -i the_deb ;# install the deb -- Dewey Garrett ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
Re: [Emc-users] Homing following error (was PID feed forward)
From source I could just check out previous commits. The problem is that the router's computer is pretty slow and building LinuxCNC would take ages. Not good if I have to rebuild many times. Les On 17/08/2019 18:59, Peter C. Wallace wrote: I think this is what git bisect is for but that requires building from source ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
Re: [Emc-users] Homing following error (was PID feed forward)
On Sat, 17 Aug 2019, Les Newell wrote:
Date: Sat, 17 Aug 2019 18:45:39 +0100
From: Les Newell
Reply-To: "Enhanced Machine Controller (EMC)"
To: emc-users@lists.sourceforge.net
Subject: Re: [Emc-users] Homing following error (was PID feed forward)
Hi Peter,
I think this is pretty recent. I've been using joint-axis for quite a
while now. It's only recent buildbot builds that cause the problem. Is
there any way for me to go back though older builds to see where the
fault started?
Les
I think this is what git bisect is for but that requires building from source
On 17/08/2019 16:52, Peter C. Wallace wrote:
Ack! I thought this might be a simple PID related problem but it looks
like a error introduced to motion (by joints-axis?) The joint command
follows the joint feedback at the step on index but the ferror
calculation seems like its not in the correct place (CMD or FB off by
one sample time)
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users
Peter Wallace
Mesa Electronics
(\__/)
(='.'=) This is Bunny. Copy and paste bunny into your
(")_(") signature to help him gain world domination.
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users
Re: [Emc-users] Homing following error (was PID feed forward)
Hi Peter, I think this is pretty recent. I've been using joint-axis for quite a while now. It's only recent buildbot builds that cause the problem. Is there any way for me to go back though older builds to see where the fault started? Les On 17/08/2019 16:52, Peter C. Wallace wrote: Ack! I thought this might be a simple PID related problem but it looks like a error introduced to motion (by joints-axis?) The joint command follows the joint feedback at the step on index but the ferror calculation seems like its not in the correct place (CMD or FB off by one sample time) ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
Re: [Emc-users] Homing following error (was PID feed forward)
On Sat, 17 Aug 2019, Les Newell wrote:
Date: Sat, 17 Aug 2019 16:30:12 +0100
From: Les Newell
To: Peter C. Wallace
Subject: Re: [Emc-users] Homing following error (was PID feed forward)
Hi Peter,
Yes, it tripped a following error fault. I have attached a plot showing the
following error. As you can see there is a huge spike just as the index
signal drops.
Les
Ack! I thought this might be a simple PID related problem but it looks like a
error introduced to motion (by joints-axis?) The joint command follows
the joint feedback at the step on index but the ferror calculation seems like
its not in the correct place (CMD or FB off by one sample time)
I dont see anything wrong in the plot, did this particular plot generate a
following error? If so could you also plot the following error?
Peter Wallace
Mesa Electronics
Peter Wallace
Mesa Electronics
(\__/)
(='.'=) This is Bunny. Copy and paste bunny into your
(")_(") signature to help him gain world domination.
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users
Re: [Emc-users] Control theory book by "Michael Blösch", state space fee-forward control
On Wed, 22 May 2019 09:47:21 +0100 andy pugh wrote: > On Wed, 22 May 2019 at 08:43, Nicklas Karlsson > wrote: > > > the conclusion it is very unlikely to come > > from anything else than a book about control theory. > > > Why not send him an email? > I think that m.bloe...@imperial.ac.uk is very likely to work. No answer. I have checked other litterature on local University library and still feel I have a few unanswered question then it come to linear state space based control theory. Any suggestions? Nicklas Karlsson ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
Re: [Emc-users] Homing following error (was PID feed forward)
>I did notice that there didn't seem to be any the scope trace, so I added the additional debug. That made me think, as you suggested, that my thread function calls were in the wrong order, but that doesn't seem to be the case. That should read - I did notice that there didn't seem to be any errors the scope trace, so I added the additional debug. joint 0 following error 6.335277, cmd=0.139723, fb=6.475000 emc/task/taskintf.cc 947: Error on joint 0, command number 143 joint 0 following error where numbers are the following error, joint.pos-cmd, joint.pos-fb ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
