Rename Protocol tools to Commlabel

Hello user

This message I inform user that I rename Protocol tools to Commlabel .. this name currently was not used and registered, so I set that name to use, currently tools are supporting Rs232 and ethernet, please waiting our next version let you have abilities to handle and analytic code and command to make sure they are right and running ok. I will also write epCode Protocol to preform the device… When user have any problem or status , please mail me when you want to understand and requirement,

Ivan Perng in Hsinchu, Taiwan.

Middle-ware V01 & V02 , Different status !!

Hello all

Yesterday, I test large connections of file with EP-iLogic, I found a situation that Middle-ware V01 is not work at overload of register number (16bits). Remind user when the Middle-ware is set V01, please do not use register number over 65535. When It is over 65535 , The middle-ware will be wrong status of display line status, please change that middle-ware to Version 02 will be large than 65535. User know this status will be correctly on running middle-ware to application. So I changed to Middle-ware V02, and loadded large connections of project file was OK and stable to be preform. Our users, When you have any problems of EP iLogic or any status need to inform me, I shall be glad to listen and to hear from your inquire/project.

Ivan Perng in Hsin-chu.

Bug Report — 20191026 — Another the resolve

This resolve will be used in any FrameCount you set up in downloader of EP iLogic. 

[Another the resolve]
case 0x6A:
{    static int MaxInfoLen=0;
     unsigned char i,infolen;
     if( (pld->LgInfoPos+StartAddr*MaxInfoLen+infolen)>(EEP_SIZE+100) ) {
       *pSend = 0x82; pSend++; SendLen++;
     } else {
       *pSend = 0x80; pSend++; SendLen++;
     }
     *pSend = (StartAddr & 0xFF00) >> 8;    pSend++; SendLen++;
     *pSend = StartAddr;                    pSend++; SendLen++;
     infolen = *Code;  Code++;
     if( MaxInfoLen < infolen)  MaxInfoLen = infolen;
     for(i=0 ; i<infolen ; i++) {
       my_eeprom_write_byte( pld->LgInfoPos+  StartAddr*MaxInfoLen+i  ,*Code );  Code++;
     }
}
break;

Bug Report – 20191026

Hello all

The new version of 1.1.28 is not totally to match to middleware of TEPMWConponent, so Here I write this bug and tell everyone. This software source declared problem to notificate user to recovery.

Date:  20191026

File Project:  TEPMWComponent

FileName:  EPMWComponent.cpp

Problem Description:   FUNCs mismatch the line status.

[Code Original]

case 0x6A:
{
byte i,infolen;

if( (pld->LgInfoPos + StartAddr*128 + infolen)  > (FBufferSize + 100) ) {
*pSend = 0x82; pSend++; SendLen++;
} else {
*pSend = 0x80; pSend++; SendLen++;
}
*pSend = (StartAddr & 0xFF00) >> 8;    pSend++; SendLen++;
*pSend = StartAddr;                                pSend++; SendLen++;

infolen = *Code;  Code++;

for(i=0;i<infolen;i++) {
eeprom_write_byte(pld->LgInfoPos + StartAddr*128 + i , *Code );  Code++;  // MaxLogic
}}
break;

[Code Recovery]

case 0x6A:
{
byte i,infolen;

if( (pld->LgInfoPos + StartAddr*138 + infolen)  > (FBufferSize + 100) ) {
*pSend = 0x82; pSend++; SendLen++;
} else {
*pSend = 0x80; pSend++; SendLen++;
}
*pSend = (StartAddr & 0xFF00) >> 8;    pSend++; SendLen++;
*pSend = StartAddr;                                pSend++; SendLen++;

infolen = *Code;  Code++;

for(i=0;i<infolen;i++) {
eeprom_write_byte(pld->LgInfoPos + StartAddr*138 + i , *Code );  Code++;  // MaxLogic
}}
break;

 

[Notification]

   Please in Downloader use FrameCount 10. to match device’s middleware.