Mitsubishi TCP/IP MELSECQ Driver-Link Register variable tag Problem

Dear All,

 

We are going to upgrade old project with Citect version5.21 and MELSEC over TCP/IP (AJ71E71 card) based on Win98 to 2018R2 and Windows10.

After migration( changing driver from “MESLCQNA” to “MELSECQ”), there is no problem in communication, but I found “Link Register” variable tag does not work properly to change the status of “Link Relay” variable tag.

Here is the code:

-----------------------------------------------------------------------------------

"T1_CSET" variable tag address is: W13B0 (data type: INT)

"T1B_8" variable tag address is: B1208 (data type: DIGITAL)

----------------------------------------------------------------------------------

Here is the code:

 

Button: Input On Command ---------------------------

T1_CSET=0;

T1_CSET1=0;

T1_CSET_P=0;

iCNT=TimeCurrent();

T1_CSET=T1_CSET BITOR 0x4000;

SLEEP(3);

T1_CSET=0;

---------------------------------------------------------

Then “T1B_8” variable tag should be “true”.

----------------------------------------------------------

And:

 

Button: Input On Command --------------------------

T1_CSET=0;

T1_CSET1=0;

T1_CSET_P=0;

iCNT=TimeCurrent();

T1_CSET=T1_CSET BITOR 0x8000;

SLEEP(3);

T1_CSET=0;

---------------------------------------------------------

Then “T1B_8” variable tag should be “False”.

----------------------------------------------------------

 

Any help is highly appreciated.

 

Best Regards

 

Mahsa Rassoulzadeh

Hooshmand Tavan Afzar Co.

 

E-Mail: m.rassoulzadeh@hta.ir

Parents
  • Hi Mahsa,

    As far as I can see there is no relation between the two tags T1_CSET and T1B_8 based on the addresses of them, so I assume there is PLC logic to monitor the T1_CSET command tag and set/reset T1B_8 status tag accordingly.

    Have you tested if the T1_CSET tag is written properly to the PLC using TagDebug() or TagDebugForm() ?

    In newer Citect versions you HAVE to be logged in to be able to perform tagwrites. This gets overlooked sometimes when upgrading old applications.

    Best regards,

    Patrick

Reply
  • Hi Mahsa,

    As far as I can see there is no relation between the two tags T1_CSET and T1B_8 based on the addresses of them, so I assume there is PLC logic to monitor the T1_CSET command tag and set/reset T1B_8 status tag accordingly.

    Have you tested if the T1_CSET tag is written properly to the PLC using TagDebug() or TagDebugForm() ?

    In newer Citect versions you HAVE to be logged in to be able to perform tagwrites. This gets overlooked sometimes when upgrading old applications.

    Best regards,

    Patrick

Children