MID_FAT_VOLUME_FULL error
Hello,
When I attempt to configure an cifX50re Ethercat Master card using an ethercat.xml file I receive a MID_FAT_VOLUME_FULL error. The xml file was generated from SYCON and contains a network description for 1 cifX50 + 24 comX slaves. Other, smaller (16 slave) configurations seem to download fine. How can I download a larger ethercat.xml file?
-Pete-
Thanks Johnny,
I am indeed exceeding the 1MB limit. My generated ethercat.xml is far larger than yours (1.1MB). I don't know how to account for such a large difference in sizes. I used Sycon.net and generated the ethercat.xml from 1 CIFX ECM (Master) + 24 comX ECS (v2.0). Would it be helpful if I sent you my .xml?
-Pete-
Hello Pete,
I guess this is a misunderstanding of the Sycon interface. I tried several different comX Slave device description files, the resulting ethercat.xml was always about 100 till 200 kb.
There are two ways to receive the "ethercat.xml" file:
1.) directly download it from sycon.net to the hardware (and maybe upload afterwards)
2.) select "addtional>export>DBM/NXD (!!!!)" and save it on your hard disk.
If you select "addtional>export>XML" you will receive an XML file with a "signal table". In this case I get a file which exceeds 1 Megabyte. This file is for a customer application, not for the netX.
So it is a known problem in the Sycon interface, that the menu entry is labeled wrong.
Please confirm this.
Johnny
Johnny
Hello Pete,
I tried to confirm your problem. I created a Sycon.net project with 24 comX slaves and 1 cifx slave. (Maybe I have a different version of the slave description files then you).
The generated file "ethercat.xml" is 192kb big. It is downloaded successfully to the netX.
Background: in the cifx EtherCAT Master is a Ramdisk with 1 Megabyte space. So the "ethercat.xml" must be smaller than 1 Megabyte. I assume, that you have one ore more additional files already in the ramdisk. Please confirm this (e.g. with cifxTest->File Explorer). For the EtherCAT Master is NO reason to have additional files. The firmware file itself is NOT located in the ramdisk.
Johnny