OpenEtherCATsociety / SOES

Simple Open Source EtherCAT Slave
Other
566 stars 247 forks source link

Using SOES or modifying the SOEM #84

Closed stevedanomodolor closed 3 years ago

stevedanomodolor commented 3 years ago

I am currently trying to use an old ethercat driver that initially was working with the old ros_ethercat_eml master implementation. I want to change and use soem. When using the slaveinfo to read the drive info, I get the following: The extra information I printed was to see at what stage the values were configured.

Slave 1: old EtherCat slave slave 2: new EtherCat slave slave 3: new EtherCat slave


SOEM (Simple Open EtherCAT Master)
Slaveinfo
Starting slaveinfo
ec_init on eth1 succeeded.
Number of slaves: 3
**********Debugging information(Before mapping configuration)**********

***********************************Slave 1 info***********************************
slave 1 ->Driver state 17
slave 1 ->Configured address: 1001
slave 1 ->output bit: 0
slave 1 ->output bytes:0
slave 1 ->startbit in first output byte 0
slave 1 -> input bit:0
slave 1 -> input bytes:0
slave 1 ->SM: 0: Start Address: 0x0
slave 1 ->SM: 0: Length: 0x0
slave 1 ->SM: 0: Flags: 0x0

slave 1 ->SM: 1: Start Address: 0x0
slave 1 ->SM: 1: Length: 0x0
slave 1 ->SM: 1: Flags: 0x0

slave 1 ->SM: 2: Start Address: 0x0
slave 1 ->SM: 2: Length: 0x0
slave 1 ->SM: 2: Flags: 0x0

slave 1 ->SM: 3: Start Address: 0x0
slave 1 ->SM: 3: Length: 0x0
slave 1 ->SM: 3: Flags: 0x0

slave 1 ->FMMU: 0:  Logical start address: 0x0
slave 1 ->FMMU: 0:  Logical length: 0x0
slave 1 ->FMMU: 0:  Logical StartBit: 0x0
slave 1 ->FMMU: 0:  Logical EndBit: 0x0
slave 1 ->FMMU: 0:  Physical start address: 0x0
slave 1 ->FMMU: 0:   Physical StartBit: 0x0
slave 1 ->FMMU: 0:  FMMUtype: 0x0
slave 1 ->FMMU: 0:  FMMUactive: 0x0
slave 1 ->FMMU: 0:  unused1: 0x0
slave 1 ->FMMU: 0:  unused1: 0x0

Slave 1: old EtherCat slave
slave 2: new EtherCat slave
slave 3: new EtherCat slave
**********Debugging information(Before mapping configuration)**********

***********************************Slave 1 info***********************************
slave 1 ->Driver state 17
slave 1 ->
slave 1 ->FMMU: 1:  Logical start address: 0x0
slave 1 ->FMMU: 1:  Logical length: 0x0
slave 1 ->FMMU: 1:  Logical StartBit: 0x0
slave 1 ->FMMU: 1:  Logical EndBit: 0x0
slave 1 ->FMMU: 1:  Physical start address: 0x0
slave 1 ->FMMU: 1:   Physical StartBit: 0x0
slave 1 ->FMMU: 1:  FMMUtype: 0x0
slave 1 ->FMMU: 1:  FMMUactive: 0x0
slave 1 ->FMMU: 1:  unused1: 0x0
slave 1 ->FMMU: 1:  unused1: 0x0

slave 1 -> FMMU0 function: 0
slave 1 ->FMMUslave function: 0
slave 1 ->FMMU2 function: 0
slave 1 ->FMMU3 function: 0
slave 1 ->length of write mailbox in bytes: 0
slave 1 ->length of read mailbox: 0x0
slave 1 ->mailbox supported protocols: 0x0
slave 1 ->Counter value of mailbox link layer protocol slave: 0
slave 1 ->CoE details: 0
slave 1 ->first unused FMMU: 0

***********************************Slave 2 info***********************************
slave 2 ->Driver state 1
slave 2 ->Configured address: 1002
slave 2 ->output bit: 0
slave 2 ->output bytes:0
slave 2 ->startbit in first output byte 0
slave 2 -> input bit:0
slave 2 -> input bytes:0
slave 2 ->SM: 0: Start Address: 0x1000
slave 2 ->SM: 0: Length: 0x80
slave 2 ->SM: 0: Flags: 0x10026

slave 2 ->SM: 1: Start Address: 0x1080
slave 2 ->SM: 1: Length: 0x80
slave 2 ->SM: 1: Flags: 0x10022

slave 2 ->SM: 2: Start Address: 0x1100
slave 2 ->SM: 2: Length: 0x0
slave 2 ->SM: 2: Flags: 0x10024

slave 2 ->SM: 3: Start Address: 0x1180
slave 2 ->SM: 3: Length: 0x0
slave 2 ->SM: 3: Flags: 0x10020

slave 2 ->FMMU: 0:  Logical start address: 0x0
slave 2 ->FMMU: 0:  Logical length: 0x0
slave 2 ->FMMU: 0:  Logical StartBit: 0x0
slave 2 ->FMMU: 0:  Logical EndBit: 0x0
slave 2 ->FMMU: 0:  Physical start address: 0x0
slave 2 ->FMMU: 0:   Physical StartBit: 0x0
slave 2 ->FMMU: 0:  FMMUtype: 0x0
slave 2 ->FMMU: 0:  FMMUactive: 0x0
slave 2 ->FMMU: 0:  unused1: 0x0
slave 2 ->FMMU: 0:  unused1: 0x0

slave 2 ->FMMU: 1:  Logical start address: 0x0
slave 2 ->FMMU: 1:  Logical length: 0x0
slave 2 ->FMMU: 1:  Logical StartBit: 0x0
slave 2 ->FMMU: 1:  Logical EndBit: 0x0
slave 2 ->FMMU: 1:  Physical start address: 0x0
slave 2 ->FMMU: 1:   Physical StartBit: 0x0
slave 2 ->FMMU: 1:  FMMUtype: 0x0
slave 2 ->FMMU: 1:  FMMUactive: 0x0
slave 2 ->FMMU: 1:  unused1: 0x0
slave 2 ->FMMU: 1:  unused1: 0x0

slave 2 -> FMMU0 function: 1
slave 2 ->FMMUslave function: 2
slave 2 ->FMMU2 function: 0
slave 2 ->FMMU3 function: 0
slave 2 ->length of write mailbox in bytes: 128
slave 2 ->length of read mailbox: 0x80
slave 2 ->mailbox supported protocols: 0xc
slave 2 ->Counter value of mailbox link layer protocol slave: 0
slave 2 ->CoE details: 23
slave 2 ->first unused FMMU: 0

***********************************Slave 3 info***********************************
slave 3 ->Driver state 1
slave 3 ->Configured address: 1003
slave 3 ->output bit: 0
slave 3 ->output bytes:0
slave 3 ->startbit in first output byte 0
slave 3 -> input bit:0
slave 3 -> input bytes:0
slave 3 ->SM: 0: Start Address: 0x1000
slave 3 ->SM: 0: Length: 0x80
slave 3 ->SM: 0: Flags: 0x10026

slave 3 ->SM: 1: Start Address: 0x1400
slave 3 ->SM: 1: Length: 0x80
slave 3 ->SM: 1: Flags: 0x10022

slave 3 ->SM: 2: Start Address: 0x1800
slave 3 ->SM: 2: Length: 0xb
slave 3 ->SM: 2: Flags: 0x10064

slave 3 ->SM: 3: Start Address: 0x1c00
slave 3 ->SM: 3: Length: 0xb
slave 3 ->SM: 3: Flags: 0x10020

slave 3 ->FMMU: 0:  Logical start address: 0x0
slave 3 ->FMMU: 0:  Logical length: 0x0
slave 3 ->FMMU: 0:  Logical StartBit: 0x0
slave 3 ->FMMU: 0:  Logical EndBit: 0x0
slave 3 ->FMMU: 0:  Physical start address: 0x0
slave 3 ->FMMU: 0:   Physical StartBit: 0x0
slave 3 ->FMMU: 0:  FMMUtype: 0x0
slave 3 ->FMMU: 0:  FMMUactive: 0x0
slave 3 ->FMMU: 0:  unused1: 0x0
slave 3 ->FMMU: 0:  unused1: 0x0

slave 3 ->FMMU: 1:  Logical start address: 0x0
slave 3 ->FMMU: 1:  Logical length: 0x0
slave 3 ->FMMU: 1:  Logical StartBit: 0x0
slave 3 ->FMMU: 1:  Logical EndBit: 0x0
slave 3 ->FMMU: 1:  Physical start address: 0x0
slave 3 ->FMMU: 1:   Physical StartBit: 0x0
slave 3 ->FMMU: 1:  FMMUtype: 0x0
slave 3 ->FMMU: 1:  FMMUactive: 0x0
slave 3 ->FMMU: 1:  unused1: 0x0
slave 3 ->FMMU: 1:  unused1: 0x0

slave 3 -> FMMU0 function: 1
slave 3 ->FMMUslave function: 2
slave 3 ->FMMU2 function: 3
slave 3 ->FMMU3 function: 0
slave 3 ->length of write mailbox in bytes: 128
slave 3 ->length of read mailbox: 0x80
slave 3 ->mailbox supported protocols: 0xe
slave 3 ->Counter value of mailbox link layer protocol slave: 0
slave 3 ->CoE details: 47
slave 3 ->first unused FMMU: 0

**********End of debugging(Before mapping configuration)**********

**********Debugging information(After mapping configuration)**********

***********************************Slave 1 info***********************************
slave 1 ->Driver state 18
slave 1 ->Configured address: 1001
slave 1 ->output bit: 0
slave 1 ->output bytes:0
slave 1 ->startbit in first output byte 0
slave 1 -> input bit:0
slave 1 -> input bytes:0
slave 1 ->SM: 0: Start Address: 0x0
slave 1 ->SM: 0: Length: 0x0
slave 1 ->SM: 0: Flags: 0x0

slave 1 ->SM: 1: Start Address: 0x0
slave 1 ->SM: 1: Length: 0x0
slave 1 ->SM: 1: Flags: 0x0

slave 1 ->SM: 2: Start Address: 0x0
slave 1 ->SM: 2: Length: 0x0
slave 1 ->SM: 2: Flags: 0x0

slave 1 ->SM: 3: Start Address: 0x0
slave 1 ->SM: 3: Length: 0x0
slave 1 ->SM: 3: Flags: 0x0

slave 1 ->FMMU: 0:  Logical start address: 0x0
slave 1 ->FMMU: 0:  Logical length: 0x0
slave 1 ->FMMU: 0:  Logical StartBit: 0x0
slave 1 ->FMMU: 0:  Logical EndBit: 0x0
slave 1 ->FMMU: 0:  Physical start address: 0x0
slave 1 ->FMMU: 0:   Physical StartBit: 0x0
slave 1 ->FMMU: 0:  FMMUtype: 0x0
slave 1 ->FMMU: 0:  FMMUactive: 0x0
slave 1 ->FMMU: 0:  unused1: 0x0
slave 1 ->FMMU: 0:  unused1: 0x0

slave 1 ->FMMU: 1:  Logical start address: 0x0
slave 1 ->FMMU: 1:  Logical length: 0x0
slave 1 ->FMMU: 1:  Logical StartBit: 0x0
slave 1 ->FMMU: 1:  Logical EndBit: 0x0
slave 1 ->FMMU: 1:  Physical start address: 0x0
slave 1 ->FMMU: 1:   Physical StartBit: 0x0
slave 1 ->FMMU: 1:  FMMUtype: 0x0
slave 1 ->FMMU: 1:  FMMUactive: 0x0
slave 1 ->FMMU: 1:  unused1: 0x0
slave 1 ->FMMU: 1:  unused1: 0x0

slave 1 -> FMMU0 function: 0
slave 1 ->FMMUslave function: 0
slave 1 ->FMMU2 function: 0
slave 1 ->FMMU3 function: 0
slave 1 ->length of write mailbox in bytes: 0
slave 1 ->length of read mailbox: 0x0
slave 1 ->mailbox supported protocols: 0x0
slave 1 ->Counter value of mailbox link layer protocol slave: 0
slave 1 ->CoE details: 0
slave 1 ->first unused FMMU: 0

***********************************Slave 2 info***********************************
slave 2 ->Driver state 2
slave 2 ->Configured address: 1002
slave 2 ->output bit: 50
slave 2 ->output bytes:a
slave 2 ->startbit in first output byte 0
slave 2 -> input bit:b8
slave 2 -> input bytes:17
slave 2 ->SM: 0: Start Address: 0x1000
slave 2 ->SM: 0: Length: 0x80
slave 2 ->SM: 0: Flags: 0x10026

slave 2 ->SM: 1: Start Address: 0x1080
slave 2 ->SM: 1: Length: 0x80
slave 2 ->SM: 1: Flags: 0x10022

slave 2 ->SM: 2: Start Address: 0x1100
slave 2 ->SM: 2: Length: 0xa
slave 2 ->SM: 2: Flags: 0x10024

slave 2 ->SM: 3: Start Address: 0x1180
slave 2 ->SM: 3: Length: 0x17
slave 2 ->SM: 3: Flags: 0x10020

slave 2 ->FMMU: 0:  Logical start address: 0x0
slave 2 ->FMMU: 0:  Logical length: 0xa
slave 2 ->FMMU: 0:  Logical StartBit: 0x0
slave 2 ->FMMU: 0:  Logical EndBit: 0x7
slave 2 ->FMMU: 0:  Physical start address: 0x1100
slave 2 ->FMMU: 0:   Physical StartBit: 0x0
slave 2 ->FMMU: 0:  FMMUtype: 0x2
slave 2 ->FMMU: 0:  FMMUactive: 0x1
slave 2 ->FMMU: 0:  unused1: 0x0
slave 2 ->FMMU: 0:  unused1: 0x0

slave 2 ->FMMU: 1:  Logical start address: 0x15
slave 2 ->FMMU: 1:  Logical length: 0x17
slave 2 ->FMMU: 1:  Logical StartBit: 0x0
slave 2 ->FMMU: 1:  Logical EndBit: 0x7
slave 2 ->FMMU: 1:  Physical start address: 0x1180
slave 2 ->FMMU: 1:   Physical StartBit: 0x0
slave 2 ->FMMU: 1:  FMMUtype: 0x1
slave 2 ->FMMU: 1:  FMMUactive: 0x1
slave 2 ->FMMU: 1:  unused1: 0x0
slave 2 ->FMMU: 1:  unused1: 0x0

slave 2 -> FMMU0 function: 1
slave 2 ->FMMUslave function: 2
slave 2 ->FMMU2 function: 0
slave 2 ->FMMU3 function: 0
slave 2 ->length of write mailbox in bytes: 128
slave 2 ->length of read mailbox: 0x80
slave 2 ->mailbox supported protocols: 0xc
slave 2 ->Counter value of mailbox link layer protocol slave: 2
slave 2 ->CoE details: 23
slave 2 ->first unused FMMU: 2

***********************************Slave 3 info***********************************
slave 3 ->Driver state 2
slave 3 ->Configured address: 1003
slave 3 ->output bit: 58
slave 3 ->output bytes:b
slave 3 ->startbit in first output byte 0
slave 3 -> input bit:58
slave 3 -> input bytes:b
slave 3 ->SM: 0: Start Address: 0x1000
slave 3 ->SM: 0: Length: 0x80
slave 3 ->SM: 0: Flags: 0x10026

slave 3 ->SM: 1: Start Address: 0x1400
slave 3 ->SM: 1: Length: 0x80
slave 3 ->SM: 1: Flags: 0x10022

slave 3 ->SM: 2: Start Address: 0x1800
slave 3 ->SM: 2: Length: 0xb
slave 3 ->SM: 2: Flags: 0x10064

slave 3 ->SM: 3: Start Address: 0x1c00
slave 3 ->SM: 3: Length: 0xb
slave 3 ->SM: 3: Flags: 0x10020

slave 3 ->FMMU: 0:  Logical start address: 0xa
slave 3 ->FMMU: 0:  Logical length: 0xb
slave 3 ->FMMU: 0:  Logical StartBit: 0x0
slave 3 ->FMMU: 0:  Logical EndBit: 0x7
slave 3 ->FMMU: 0:  Physical start address: 0x1800
slave 3 ->FMMU: 0:   Physical StartBit: 0x0
slave 3 ->FMMU: 0:  FMMUtype: 0x2
slave 3 ->FMMU: 0:  FMMUactive: 0x1
slave 3 ->FMMU: 0:  unused1: 0x0
slave 3 ->FMMU: 0:  unused1: 0x0

slave 3 ->FMMU: 1:  Logical start address: 0x2c
slave 3 ->FMMU: 1:  Logical length: 0xb
slave 3 ->FMMU: 1:  Logical StartBit: 0x0
slave 3 ->FMMU: 1:  Logical EndBit: 0x7
slave 3 ->FMMU: 1:  Physical start address: 0x1c00
slave 3 ->FMMU: 1:   Physical StartBit: 0x0
slave 3 ->FMMU: 1:  FMMUtype: 0x1
slave 3 ->FMMU: 1:  FMMUactive: 0x1
slave 3 ->FMMU: 1:  unused1: 0x0
slave 3 ->FMMU: 1:  unused1: 0x0

slave 3 -> FMMU0 function: 1
slave 3 ->FMMUslave function: 2
slave 3 ->FMMU2 function: 3
slave 3 ->FMMU3 function: 0
slave 3 ->length of write mailbox in bytes: 128
slave 3 ->length of read mailbox: 0x80
slave 3 ->mailbox supported protocols: 0xe
slave 3 ->Counter value of mailbox link layer protocol slave: 5
slave 3 ->CoE details: 47
slave 3 ->first unused FMMU: 2

**********End of debugging(After mapping configuration)**********

3 slaves found and configured.
Calculated workcounter 6

Slave:1
 Name:? M:0000eeee I:0067d60d
 Output size: 0bits
 Input size: 0bits
 State: 4
 Delay: 0[ns]
 Has DC: 1
 DCParentport:0
 Activeports:1.1.0.0
 Configured address: 1001
 Man: 0000eeee ID: 0067d60d Rev: 06020115
 FMMUfunc 0:0 1:0 2:0 3:0
 MBX length wr: 0 rd: 0 MBX protocols : 00
 CoE details: 00 FoE details: 00 EoE details: 00 SoE details: 00
 Ebus current: 0[mA]
 only LRD/LWR:0

Slave:2
 Name:E/BOX
 Output size: 80bits
 Input size: 184bits
 State: 4
 Delay: 600[ns]
 Has DC: 1
 DCParentport:1
 Activeports:1.1.0.0
 Configured address: 1002
 Man: 00000500 ID: 01107001 Rev: 00000004
 SM0 A:1000 L: 128 F:00010026 Type:1
 SM1 A:1080 L: 128 F:00010022 Type:2
 SM2 A:1100 L:  10 F:00010024 Type:3
 SM3 A:1180 L:  23 F:00010020 Type:4
 FMMU0 Ls:00000000 Ll:  10 Lsb:0 Leb:7 Ps:1100 Psb:0 Ty:02 Act:01
 FMMU1 Ls:00000015 Ll:  23 Lsb:0 Leb:7 Ps:1180 Psb:0 Ty:01 Act:01
 FMMUfunc 0:1 1:2 2:0 3:0
 MBX length wr: 128 rd: 128 MBX protocols : 0c
 CoE details: 17 FoE details: 01 EoE details: 00 SoE details: 00
 Ebus current: 0[mA]
 only LRD/LWR:0

Slave:3
 Name:Servo Drives
 Output size: 88bits
 Input size: 88bits
 State: 4
 Delay: 1460[ns]
 Has DC: 1
 DCParentport:1
 Activeports:1.0.0.0
 Configured address: 1003
 Man: 0000029c ID: 02c30001 Rev: 00000003
 SM0 A:1000 L: 128 F:00010026 Type:1
 SM1 A:1400 L: 128 F:00010022 Type:2
 SM2 A:1800 L:  11 F:00010064 Type:3
 SM3 A:1c00 L:  11 F:00010020 Type:4
 FMMU0 Ls:0000000a Ll:  11 Lsb:0 Leb:7 Ps:1800 Psb:0 Ty:02 Act:01
 FMMU1 Ls:0000002c Ll:  11 Lsb:0 Leb:7 Ps:1c00 Psb:0 Ty:01 Act:01
 FMMUfunc 0:1 1:2 2:3 3:0
 MBX length wr: 128 rd: 128 MBX protocols : 0e
 CoE details: 2f FoE details: 01 EoE details: 01 SoE details: 00
 Ebus current: 0[mA]
 only LRD/LWR:0
End slaveinfo, close socket
End program

The old code of this particular drive seem to hard code this addresses and configure them manually. 
Is it possible to set the addresses of the fmmu, sm, object list with soes or is it better to modify SOEM during the configuration stage and assign this addresses manually because SOEM is not able to read them.

An example of this is shown below 
Configuration of the FFMU and SM 

EtherCAT_FMMU_Config fmmu = new EtherCAT_FMMU_Config(2); //ROS_DEBUG("device %d, command 0x%X = 0x10000+%d", (int)sh->get_ring_position(), start_address, start_address-0x10000); (fmmu)[0] = EC_FMMU(start_address, // Logical start address commandsize,// Logical length 0x00, // Logical StartBit 0x07, // Logical EndBit COMMAND_PHY_ADDR, // Physical Start address 0x00, // Physical StartBit false, // Read Enable true, // Write Enable true); // Enable

start_address += commandsize;

//ROS_DEBUG("device %d, status 0x%X = 0x10000+%d", (int)sh->get_ring_position(), start_address, start_address-0x10000); (*fmmu)[1] = EC_FMMU(start_address, // Logical start address base_status, // Logical length 0x00, // Logical StartBit 0x07, // Logical EndBit STATUS_PHY_ADDR, // Physical Start address 0x00, // Physical StartBit true, // Read Enable false, // Write Enable true); // Enable

start_address += base_status;

sh->set_fmmu_config(fmmu);

EtherCAT_PD_Config *pd = new EtherCAT_PD_Config(4);

// Sync managers (pd)[0] = EC_SyncMan(COMMAND_PHY_ADDR, commandsize, EC_BUFFERED, EC_WRITTEN_FROM_MASTER); (pd)[0].ChannelEnable = true; (*pd)[0].ALEventEnable = true;

(pd)[1] = EC_SyncMan(STATUS_PHY_ADDR, base_status); (pd)[1].ChannelEnable = true;

(pd)[2] = EC_SyncMan(WGMailbox::MBX_COMMAND_PHY_ADDR, WGMailbox::MBX_COMMAND_SIZE, EC_QUEUED, EC_WRITTEN_FROM_MASTER); (pd)[2].ChannelEnable = true; (*pd)[2].ALEventEnable = true;

(pd)[3] = EC_SyncMan(WGMailbox::MBX_STATUS_PHY_ADDR, WGMailbox::MBX_STATUS_SIZE, EC_QUEUED); (pd)[3].ChannelEnable = true;

sh->set_pd_config(pd);

nakarlsson commented 3 years ago

Is "Slave 1: old EtherCat slave" a SOES slave? Anyway, it seems it is not implemented to be conformant, seems to be missing the EEPROM data hence the need to manually configure it from the eml master. SOEM rely on having the EEPROM data.

So you have 2 options.

Fix the SOES(?) slave Or Port the manual configuration steps from the eml master to SOEM, the closest available in SOEM is using the configlist that handle missing/erroneous data.

stevedanomodolor commented 3 years ago

It is one of the drivers from the old pr2 robot. I think it is not a soes slave and it was configured differently. Is it still possible to use soes to configure the eeprom data and fix the slave?

When you mean configlist, you are referring to this right? https://github.com/OpenEtherCATsociety/SOEM/blob/master/soem/ethercatconfiglist.h, we have to input the configuration data here right?

On Tue, Sep 1, 2020, 08:19 nakarlsson notifications@github.com wrote:

Is "Slave 1: old EtherCat slave" a SOES slave? Anyway, it seems it is not implemented to be conformant, seems to be missing the EEPROM data hence the need to manually configure it from the eml master. SOEM rely on having the EEPROM data.

So you have 2 options.

Fix the SOES(?) slave Or Port the manual configuration steps from the eml master to SOEM, the closest available in SOEM is using the configlist that handle missing/erroneous data.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/OpenEtherCATsociety/SOES/issues/84#issuecomment-684427629, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOU65DJVXGURX5JC3GZNQIDSDSHAVANCNFSM4QOEOMNA .

nakarlsson commented 3 years ago

Yes, that configlist.

stevedanomodolor commented 3 years ago

Thank you for your response,

On Tue, Sep 1, 2020, 10:41 nakarlsson notifications@github.com wrote:

Yes, that configlist.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/OpenEtherCATsociety/SOES/issues/84#issuecomment-684585561, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOU65DKHQTMGHYAF2MK66ULSDSXVFANCNFSM4QOEOMNA .

nakarlsson commented 3 years ago

@stevedanomodolor , can we close this?

stevedanomodolor commented 3 years ago

Yes, THANK YOU

On Wed, Sep 23, 2020, 08:00 nakarlsson notifications@github.com wrote:

@stevedanomodolor https://github.com/stevedanomodolor , can we close this?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/OpenEtherCATsociety/SOES/issues/84#issuecomment-697151666, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOU65DK7S7ZEPQOBCR7WHA3SHGFIRANCNFSM4QOEOMNA .