EtherCAT Explorer Activity
Graphical explorer for EtherCAT network
Status: Beta
Brought to you by:
fchaxel
Activity for EtherCAT Explorer
-
Marco S. posted a comment on discussion General Discussion
Ok, I missed something. Marco
-
EtherCAT Explorer updated /SetupEtherCATExplorer_0.5.exe
-
F. Chaxel committed [r32]
WriteEEProm progressbar patch
-
Marco, The read back is between Pause and Resume in this code. Line 250 is OK to take into account the write and the read process. I've made a mistake at the line 276 where the code should be : progress.Value += 128; Update will be done today, and also with a Setup with this version. Thank you very much. Have a good week-end. Bye.
-
Hi, I appreciate your solution to avoid modifying the SOEM lib. Everything works now, but with one mistery left: I don't understand why the "EEPROM read" needs Pause and Resume to work properly, but the read back I added, that does exactly the same, doesn't need Pause and Resume. Can you see a reason for that? By the way, in my opinion the read back is necessary because ec_readeepromAP successful, means that the communication between the master and the ESC and between the ESC and the EEPROM was ok,...
-
Hi Marco, Great job. Sure the flow to and from the EEProm through the I2C ou SPI bus is too slow compare to Ethernet 100 Mbs. So if data are not queued in the device it's a problem. I really dislike modifying a lib from a third party. As I understand it, a read is OK with Pause & Resume, but a Write is not OK. ec_writeeepromAP function return >0 if it's OK so I've modfiy only the code in EEprom_Write (SoemWrapper.c) to loop 4 times (see line 214) rather than a modification in ethercatmain.c. ec_readeepromAP...
-
Some progress to Read/Write EEprom
-
Hi, from the WireShark trace, captured during programming, (see attachement) we can see that there are many "EEPROM command error". This is not unusual as it happen if the EEPROM interface, and the EEPROM itself , is not fast enought to cope with the master requestes. This is explained in the Beckhoff documentation as follows: 11.2.1.1 Missing Acknowledge Missing acknowledges from the EEPROM chip are a common issue, especially if a fast PDI uses the EEPROM interface. E.g., a write access to the EEPROM...
-
Hi, some wrong bytes randomly. I am trying to track down what happen using WireSharK. Bye Marco
-
Hi Marco, What is wrong ? Nothing written, some bad bytes ? Bye
-
Hi, ok for the restored patch in the wrapper, but the EEPROM write still fails. It failed also in R29, also programming the EEPROM in one shot (in my previous post I was wrong). The only way I found to make it work is to disable the cyclic slave polling, commenting out line 242 in MainDialog.cs. The added functions Pause and Resume actually stop and restart the slave polling but this has a good effect on the EEPROM read but not on the EEPROM write. I don't know why ... Regards Marco
-
Hi, ok for the restored patch in the wrapper, but the EEPROM write still fails. It failed also in R29, also programming the EEPROM in one shot (in my previous post I was wrong). The only way I found to make it work is to disable the cyclic slave polling, commenting out line 242 in MainDialog.cs. The added functions Pause and Resume actually stop and restart the slave polling but this has a good effect on the EEPROM read but not on the EEPROM write. I don't know why ... Regards Marco P.S. A minor...
-
Hi, Houps, Yes some wrong files manipulations. Maybe now it will be fine. Thanks for your help. Bye
-
EEPromWrite, some news
-
Hi, the last revision (r29) works only if I write the data to the EEPROM in only one shot (without the progress bar) because you forgot to put my latest patch into the wrapper. uint16 data = ((uint16)buf[i]) & 0x00FF; data |= ((uint16)buf[i + 1]) << 8; Anyway Pause and Resume the cyclical activity do their job. Good night. Marco
-
Thank you Marco. I've just update the source code both for the Interrop code & Explorer. I've added a way to Pause and Resume the cyclical activity, and I've use it during the read and write operations. Can you test it ? Bye.
-
Pause & Resume RTthread
-
Hi, I tested the write EEPROM function with your last code, and it fails with many wrong bytes. This is due to the interference between the cyclic slave polling (10mS sample time) and the programming process. I disabled the cyclic slave polling, in a very crude way, commenting out line 242 in MainDialog.cs // SoemInterrop.Run(); In this way the programming operation succeeds Please note that also the read EEPROM function fails if the cyclic slave polling is running. You can check this executing several...
-
WriteEEprom with progress bar
-
Hi, Some very interested EtherCAT shields sold by this society. Maybe I will try to buy some. Bye.
-
Hi, thanks, I will get back to you when I have some useful result. No problem for the risk of bricking my EtherCAT board. I use this EtherCAT shield for Arduino and I have the capability of restore the EEPROM in any situation. https://www.bausano.net/en/hardware/ethercat-e-arduino/easycat.html Bye Marco
-
Hi, Code updated. Absolutly not tested. Let me know if it's OK or not ... take care with your devices, Wrong EEprom write can be a problem ... maybe up to factory return. Bye
-
Bug fix : ReadEEProm alway in device 1 & Fix by Marco S.
-
Hi, I realize now that my patch is wrong. It works with my application because I write the EEPROM in just one chunk, and then starting from 0. The patch must be: uint16 data = ((uint16)buf[i]) & 0x00FF; // Marco new data |= ((uint16)buf[i + 1]) << 8; // " and not: uint16 data = ((uint16)buf[start + i]) & 0x00FF; // Marco wrong data |= ((uint16)buf[start + i + 1]) << 8; // " Good night Marco
-
Fine. I will update the code tomorow, I've see some wrong code for read/write EEprom. But I do not have device now to test it. So please wait a day or two, then get the source code and check it. Bye.
-
Hi, I tested my patch only using the wrapper with my application and I though that the EterCAT Explorer included all the necessary to program the EEPROM. I will try to add the missing code and, if I will succeed, I will get back to you. Regards Marco
-
Hi, Yes the version number as not been updated. Since I've never tested Write eeprom the menu should be enabled by setting the option EEPromWriteEnable to true. But no code is inside. Somedoby should program it and test it : The code as to be replaced. MessageBox.Show("Not yet implemented", "EtherCAT Explorer", MessageBoxButtons.OK, MessageBoxIcon.Information);
-
Hi, Yes the version number as not been updated. Since I've never tested Write eeprom the menu should be enabled by setting the option EEPromWriteEnable to true.
-
Hi, I downloaded the release 0.5 but I see that the "write memory" function is still disabled. Further the release version in the "about" is still stuck to 0.3. Please see attachements. Regards Marco
-
Thanks for your feedback ! :-) Marco
-
EEprom_write fixed by Marco S.
-
-
Hi, Thank you. I see your message with some delay. I will update the source code and build a release of the EXE. Bye.
-
I use the EtherCAT explorer with satisfaction but I have seen that the EEprom_Write function doesn't work propely. I worked to fix the issue and, after some debug, I replaced line 210 in the SoemWrapper.c file: uint16 data=buf[start]+(((uint16)buf[start+1])<<8); with: uint16 data = ((uint16)buf[start + i]) & 0x00FF; data |= ((uint16)buf[start + i + 1]) << 8; Now the EEprom_Write works fine, and I hope somobody can take advantage of this. Marco
-
Download snapshot information
-
-
Somes dots
-
-
Usage of the WapperDll in release mode
-
some dots
-
64 bits dll version
-
Printf remove in soem code & Read PDO sample in...
-
One dot.
-
Missing files
-
Interfaces list for Java
-
Java Master code sample
-
Preparation for Java
-
-
Version beta 0.3
-
Minor modifications
-
Small changes
-
-
EEPROM operation
-
Improvement, start of Read EEprom, changes in u...
-
Array decoding
-
Version alpha 0.2 - Boot state, Acknowledge
-
Acyclic console code sample. PDO simple fields ...
-
Add SimpleMaster console code
-
Read device XML description file
-
Slave state management & Acyclic Read/Write PDO
-
First functional version
-
-
First update
1