and then posting it to the appropriate
slave+service FSM, rather than leaving it up to the individual service FSMs
to explicitly post datagrams to check and read data.
From: Jeroen Van den Keybus [mailto:jeroen.vandenkey...@gmail.com]
Sent: Wednesday, 20 November 2013 09:52
To: Gavin Lambert
Cc: etherlab
Mere moments ago, quoth I:
Did you see my other patch specifically for FoE busy? My slave is
working fine for busy reads with both of my patches applied. (There was
a third patch included in the same email as the busy patch, but that's
optional and just increases debug logging.)
My patch
Quoth Koch Daniel:
Everytime I try to reset a slave-error on a BoschRexroth Servo-Drive by
sendig a SoE-Message (S-0-0099) via ecrt_master_write_idn, i am facing a
kernel issue (see below) on my rtai-system (version 3.6.1 on a patched
linux 2.6.24 with ethercat-master 1.5.2). Has anybody ever
.
Regards,
Gavin Lambert
From: etherlab-dev-boun...@etherlab.org
[mailto:etherlab-dev-boun...@etherlab.org] On Behalf Of Knud Baastrup
Sent: Tuesday, 1 April 2014 03:57
To: etherlab-dev@etherlab.org
Subject: [etherlab-dev] Missing mailbox handler
Hi
I often get below SDO: Input
.
Regards,
Gavin Lambert
lib-deactivate.patch
Description: Binary data
___
etherlab-dev mailing list
etherlab-dev@etherlab.org
http://lists.etherlab.org/mailman/listinfo/etherlab-dev
Quoth Frank Heckenbach:
Perhaps you can at least make sure they compile with the new version.
Ultimately, Florian will have to integrate the patches into the
development sources, or not.
Well, they won't all merge/compile cleanly without some changes. (Also
there's a few cases where variables
On 13 June 2014, quoth I:
Ah. I found a spot in ec_master_queue_datagram where I had incorrectly
applied patch 11 (and jiffies_sent would have been 0). I've been
sidetracked a little and haven't had a chance to re-test this, but I
expect it will solve the issue; thanks for the hint!
A few days ago, quoth I:
I'm planning to set up a forked repository on SF consisting of the
current 1.5.2 plus several of the patches I've submitted in the past,
in the hopes that maybe it'll be easier for IgH to do an hg pull
rather than applying a patch from a mailing list
I've been
On 25 June 2014, quoth taotao:
I try to build ethercat on ubuntu. Now Ethercat host master has been
successfully established.
These sorts of questions really belong on the users list.
Q1: How can i find slave's alias and position(ec_slave_config_t)?
i try to use command /opt/xxx/ethercat sl
On 27 June 2014, quoth Frank Heckenbach:
The issues regarding io_sem (#18, #19, #20) apply to all code, RTAI or
not.
True, but like I said the current 1.5.2 locking code appears quite different
and I wasn't sure how to integrate it properly, so it seemed safest to leave
it alone for now and let
bear in mind that it'll trigger a rescan if
the network is disrupted at all). Sometimes you don't get away with it though
and you'll get unexpected response errors and other issues.
Regards,
Gavin Lambert
___
etherlab-dev mailing list
etherlab-dev
datagram,
which again might not be the right way to do it but does seem to be a
common need.
Regards,
Gavin Lambert
coe-finish.patch
Description: Binary data
___
etherlab-dev mailing list
etherlab-dev@etherlab.org
http://lists.etherlab.org/mailman/listinfo
mailbox). This
involves a register write to 0x080E, but I haven't looked too closely at the
specifics, or how likely slaves are to implement it.
Regards,
Gavin Lambert
___
etherlab-dev mailing list
etherlab-dev@etherlab.org
http://lists.etherlab.org
scan completed,
unless this was made less monolithic. One advantage of Frank's locking patch
over this is that it would still allow other requests [except
create_sdo_requests, unless they were moved to fsm_slave] to interleave with
dictionary scanning, albeit at a slower rate.)
Regards,
Gavin
be better] is that it could still try [and
fail] to transfer while the slave is in INIT, in the case when the app is
started too soon after the master, so #1 or #2 may be needed anyway.)
Regards,
Gavin Lambert
___
etherlab-dev mailing list
etherlab-dev
On 3 February 2015 13:38, quoth Graeme Foot:
Sent: Tuesday, 3 February 2015 13:38
To: Gavin Lambert; 'Knud Baastrup'
Cc: etherlab-dev@etherlab.org
Subject: RE: [etherlab-dev] Multiple mailbox protocols and other issues
From: etherlab-dev [mailto:etherlab-dev-boun...@etherlab.org] On Behalf
On 2 February 2015 20:18, quoth Knud Baastrup:
16_improved_ethercat_rescan_performance.patch:
The SII data and PDOs will now be stored when the EtherCAT master is in
its
operation phase. The stored SII data and PDOs will be detached from the
slaves prior to a scanning and re-attached during
On 3 February 2015 20:08, quoth Knud Baastrup:
Yes, I decided not to use the alias as matching criteria for the slave
data
due to the tree points intended use of aliases. Currently we do not use
aliases on our modules, but we are planning to introduce this in the near
future to prevent that
On 13 February 2015 03:30, quoth Knud Baastrup:
I have attached a new set of patches (now by using git format-patch, which
also imply that the patch names are given by the commit text).
I believe that I have addressed the issues you highlighted in prior mails
including the alias support that
On 13 February 2015 21:39, quoth Knud Baastrup:
Nice! Although there still seem to be some funny things going on with
the
whitespace, eg. see patch 0013's master/fsm_slave_config.c's second hunk
(ec_fsm_slave_config_enter_mbox_sync).
I guess I need more help to figure this out. I cannot
On 13 March 2015 16:12, quoth I:
gavinl-1011-e1000e_watchdog:
This resolves an issue with the e1000e driver that I mentioned earlier
--
when wired for cable redundancy, the second port didn't establish link
until
the network broke, causing an unacceptable delay in failover to the
redundant
Attached two more patches, one of which is the missing one from the prior
message (despite the numbers, they can basically be applied in any order,
but that's the minimum-fuzz locations).
gavinl-1005-quick_op_watchdog:
When some kind of comms error occurs and a slave watchdogs back to
On 3 March 2015 01:49, quoth Knud Baastrup:
Thanks, attached updated patches. See inline comments.
Looks good, as far as I can see. :)
Although speaking of syslog spam, I'm getting quite a lot of Busy -
processing internal SDO request! now.
Although speaking of the EC_REGALIAS code, if that's
No, the original code is correct.
EtherCAT slaves can be addressed in one of two ways:
1. 0, abs_ring_pos = where abs_ring_pos is the absolute position in the
virtual ring (0 is the first slave).
2. alias, rel_ring_pos = where alias is the alias of some slave and
a look at ETG1000.6 6.4.1.4.
-Original Message-
From: Knud Baastrup [mailto:k...@deif.com]
Sent: Thursday, 6 August 2015 20:26
To: Gavin Lambert gavin.lamb...@compacsort.com
Cc: etherlab-dev@etherlab.org
Subject: RE: [etherlab-dev] [PATCH] My patchset roundup July 2015
for this that I'm unaware of?
Regards,
Gavin Lambert
___
etherlab-dev mailing list
etherlab-dev@etherlab.org
http://lists.etherlab.org/mailman/listinfo/etherlab-dev
,
Gavin Lambert
-Original Message-
From: Knud Baastrup [mailto:k...@deif.com]
Sent: Thursday, 6 August 2015 19:05
To: Gavin Lambert
Cc: etherlab-dev@etherlab.org
Subject: RE: [etherlab-dev] [PATCH] My patchset roundup July 2015
Hi Gavin,
I look forward to try out
On 13 July 2015 10:20, quoth Graeme Foot:
Re: gavinl-2004-sdo_write_size.
What I have been doing to allow one SDO Request object for all data sizes
is
to call ecrt_sdo_request_read() every time before calling
ecrt_sdo_request_write(). This sets the size specific to the object you
are
about
com]
Sent: Wednesday, 15 June 2016 00:51
To: Gavin Lambert <gavin.lamb...@compacsort.com>; Florian Pose <f...@igh.de>;
'David Page' <dave.p...@gleeble.com>
Cc: etherlab-dev@etherlab.org
Subject: RE: [PATCH] Default branch patchset re-applied on 5a70ff
Gavin, we really appreciate the
On 3 February 2016 21:02, quoth Tillman, Scott:
> Since you brought up the typical process cycle: I have been using a process
> similar the second one you describe. I was very surprised when I was doing my
> initial development that the output frame and the return frame were overlaid,
> requiring
.f...@touchcut.com]
> Sent: Thursday, 4 February 2016 12:21
> To: Gavin Lambert <gavin.lamb...@compacsort.com>; 'Tillman, Scott'
> <scott.till...@bhemail.com>; Dr.-Ing. Matthias Schöpfer
> <schoep...@robolab.de>; etherlab-dev@etherlab.org
> Subject: RE: [etherlab-dev] Pos
On Wednesday, 6 July 2016 22:04, quoth Christoph Permes:
> After checking the e1000e code I noticed that there has been a change in the
> original driver between kernel 3.8 and 3.10 affecting link detection in the
> e1000_watchdog function (the change has been reverted in kernel 3.16).
> With
On 25 January 2017 10:55, quoth Rusu Valerian:
> Is AoE supported by IgH EtherCAT Master or is there a work around? E.g if it
> is
> not supported is it possible to get the card configured in a different setup
> that
> supports AoE then use it with IgH EtherCAT Master in my setup?
AoE is not
On 20 January 2017 04:29, quoth Christoph Schroeder:
> On 01/19/2017 01:09 AM, Gavin Lambert wrote:
> > Try the following changes (sorry, can't generate a patch right now):
> >
> >* voe_handler.c:372: "mbox_coe_data" should be "mbox_voe_data&qu
On 29 September 2016 03:07 quoth Christoph Schröder,
> #1.)
> Starting with the tarball release 1.5.2 and encountered a problem with
> ecrt_master_reference_clock_time which led to a segmentation fault. My
> DC config here is basically the same as in the rtai_rtdm_dc example with
> minor fixes
ts support this, though I'm not sure about HG patchsets.
(FYI, I've already made a note of the patch updates Knud Baastrup submitted
in December, and a few other patches posted to the list since then, though I
haven't integrated them yet.)
Regards,
Gav
On 26 May 2017 19:02, quoth Gregor Beck:
> reading and writing SDO's from userspace while an EoE interface is up (but
> otherwise unused) occasionally failed with:
>
> Failed to execute SDO upload: Input/output error
[...]
> Skimming the documentation suggests using ecrt_master_callbacks() but it
On 7 May 2017 20:33, quoth Graeme Foot:
> I don't use ec_master_set_send_interval() or --enable-hrtimer since my
masters operational thread
> has always run at 10ms (100Hz) anyway. (I probably should so will look at
adding that in at some
> stage.) My Linux kernel is configured to run at 100Hz
On 28 April 2017 11:59, quoth Graeme Foot:
> First off, I also prefer #3. I use buildroot to create my Linux
environment and
> buildroot applies patches in alphabetical order (at least in my version
which is
> now pretty old), so the number at the front is important. Buildroot also
> requires
Mere moments ago, quoth I:
> On 28 April 2017 11:59, quoth Graeme Foot:
> > 2) Your 0054 patch successfully moved the slave sdo request processing
> > from the master fsm's idle state to be called every cycle of the master
> > thread.
> > However, I have my Linux environment set to run at 100Hz,
The size in ecrt_slave_config_create_voe_handler specifies the maximum size of
the VoE request/reply, which is different from (but must be equal or smaller
than) the actual mailbox size.
The mailbox size itself is specified by the slave's SII data, as read from its
EEPROM during the INIT ->
...@amat.com]
Sent: Friday, 15 September 2017 12:07
To: Gavin Lambert <gavin.lamb...@compacsort.com>; etherlab-dev@etherlab.org
Subject: RE: foe_write result
Hi Gavin,
Thanks for your advices and I really appreciated. I still get several
questions that I want to double check wi
I've just pushed a new update to the unofficial patchset; it is now at
version 20170914 and is based on the latest upstream default (33b922 at this
moment).
https://sourceforge.net/u/uecasm/etherlab-patches/ci/default/tree/#readme
Feedback is welcomed.
Notable changes:
* Now ahead
The "foe_write" ethercat command will print an error on stderr and return a
non-zero exit code in case of error. It's intended to be used interactively
by whoever is commissioning the system, although it can be used in a script.
Alternatively if you want to call it programmatically you could
On 29 November 2017 10:10, quoth Matthieu Bec:
> I have an application that requires uniquely identifying all our slaves
(~180
> that are essentially one same model) in the fieldbus.
> Using "configured station alias" seems it could work, since it means
updating
> all the SII individually.
> Those
On 29 November 2017 12:33, quoth Matthieu Bec:
> in my use case the devices are all the same and serviceable. We'd like to
> avoid reprogramming IDs if a device fails and gets swapped by another, so
> we intend to use an ID from an EEPROM dongle (that will be permanently
> mounted) rather than SII
Hi all,
I've just updated the unofficial patchset to version 20171102. It is still
based on the same upstream default commit as before: 33b922.
https://sourceforge.net/u/uecasm/etherlab-patches/ci/default/tree/#readme
Notable changes since the last release:
* I've added a new "stable"
They are not the same. The "p/etherlabmaster" repository is the mainline
repository, while the "u/uecasm/etherlab-patches" repository contains
unofficial patches not yet in mainline.
However, that particular patch is included in the mainline default branch, just
not in the stable-1.5 branch.
Note that this sort of question belongs on the users list, not the dev list.
When you are commissioning a particular network, you first run "ethercat
slaves" to view the list of existing slaves on the network. This will show
both their position-based address and their alias-based address.
You
Hi all,
I've just updated the unofficial patchset to version 20180622. It is still
based on the same upstream default commit as before: 33b922.
https://sourceforge.net/u/uecasm/etherlab-patches/ci/default/tree/#readme
Notable changes since the last release (20171108):
* Refreshed
The documentation is not entirely up to date, so it can be misleading at
times.
Returning 1 does not indicate success or failure, it indicates whether the
datagram has been populated and needs to be sent (and thus whether the state
machine needs to continue). Success or failure of the request
On 2 May 2018 17:34, quoth Joye Laurent:
> I'm using the code from etherlabmaster (default branch) + your own patches
> (Patchset 20171108 based on default branch 33b922ec1871).
>
> I'm trying to compile a kernel 4.14 with rtmutex enabled at configure time.
> The compilation fails because an
The unofficial patchset
(https://sourceforge.net/u/uecasm/etherlab-patches/ci/default/tree/#readme)
contains driver and other patches to let it build on kernel 4.14. I haven’t
personally tried anything newer than this.
Usually it’s better to stick to one of the supported versions (which tend
On 5 March 2018 22:58, quoth Esben Haabendal:
> The multiple process world can be different though. You basically end up
> with a new EtherCAT API. A combination of the etherlabmaster API and a
> custom named semaphore API. Without this, applications will not work
> properly together. Why not
want to use IGB, rather than trying to patch just
this one thing.
I think this addresses all patches sent to myself or to the mailing lists since
the last patchset release. There was a period where I wasn't receiving
messages from the list, however, so if I've missed one then I apologise.
Note that the standard distribution of the Etherlab master does not support
kernel 4.19. You can either downgrade your kernel or try using the unofficial
patchset, which includes some compatibility patches for 4.19.
Gavin Lambert
Senior Software Developer
[cid:logo_compac_5dcf97ef-52f5-498c
56 matches
Mail list logo
