daviddein Posted January 8, 2021 Share Posted January 8, 2021 I am no wizard in C or delta tau language in general, but I included the ECATMap.h file in my bgcplc that had some nifty pshm pointers that I wanted to use. I had issues when trying to use the unique #defines concerning IOBuffer's, and I kept getting compile errors stating: expected ';' before 'pshm' looking at my ECATMap.h file: #define Slave_1003_EL1252_1003_1D09_16_SysTime (x) pshm->ECAT[0].IOBuffer[32 + x] removing the space before a '(x)' fixed my compile error #define Slave_1003_EL1252_1003_1D09_16_SysTime(x) pshm->ECAT[0].IOBuffer[32 + x] Is this an auto-generation bug? This is similarly occuring in the ECATMap.pmh file as well. Link to comment Share on other sites More sharing options...
steve.milici Posted January 8, 2021 Share Posted January 8, 2021 What is the IDE version? Link to comment Share on other sites More sharing options...
daviddein Posted January 11, 2021 Author Share Posted January 11, 2021 PowerPMAC Version 4.4.1.7 Link to comment Share on other sites More sharing options...
daviddein Posted January 28, 2021 Author Share Posted January 28, 2021 So, is this something I am setting up incorrectly (wrong checkbox or other), or is it a bug? I am doing some development work, and whenever I change the bus configuration I have to go in and manually fix all of these 'errors' in the auto-generated ecatconfig files so my project can compile correctly. Link to comment Share on other sites More sharing options...
steve.milici Posted January 28, 2021 Share Posted January 28, 2021 It may be a setting in the devices ESI file. Can you send the ESI file to support for review? Link to comment Share on other sites More sharing options...
daviddein Posted September 30, 2021 Author Share Posted September 30, 2021 Sorry for the much delayed response, but here is a copy of the ESI. This issue is still happening in the latest version of the IDE. Note: I had to change the file extension because it wouldn't let me upload xml.Copley_BEL_4.12_rev3.txt Link to comment Share on other sites More sharing options...
steve.milici Posted September 30, 2021 Share Posted September 30, 2021 Thanx - I will have the SW development team look at this. Link to comment Share on other sites More sharing options...
steve.milici Posted September 30, 2021 Share Posted September 30, 2021 The SW development team has determined this is a bug and will fix it in the next release. Thank-you for your patience. Link to comment Share on other sites More sharing options...
Recommended Posts