I have send it over PM multiple times, now I will post it here:

This is Zip of  zap13, TIA13 archeive file. I have compiled it from v11, VAL_STRG, does not allow to be called directly in SCL, so there is one another function that calls VAL_STRG in LAD.

Dear Marko,

thanks for sharing this app with us.

I make the steps you described and i succesfull connect with Heidi to mySQL database.

I make the same table as your and i check the telegrams with the wireshark.

Everything its fine until now. 

I run the project on my CPU and when i set the connect bit to "1" after 2-3 seconds the Error bit get TRUE and the Status take value = 3.

I checked the SQL code and i found in line 247 that i have "authentication failed" status.

It seems strange because with Wireshark there is no telegram from CPU to mySQL server PC. The only telegrams are between CPU and TIA Portal PC (used for status program).

Is there any details i can check?

When i open the Mysql_DB to check the parameters you told me i saw that the user,pass has not updated with my new data. This happens because there are some warnings when i compile the MySQL FB. I delete the instance db and recreated it and WORKS!!! 

I think the easiest way is to rapresent octets from DB on HMI as numbers (byte 0-255), you can change freely and settings will remain in DB as all data are retained, of course you need to reboot the connection.

There are some limitations, non resolved problems:

The entire sequence of connection/disconnection has to be redone (from lines 120-330 is OK), at the time I was writing there were very little known about TCON TDISCON TRECV TSEND, therefore it could hang somewhere if the connection breaks. I have found that instead sending a command CMD_QUIT to the server you can simply, disconnect this eases the sequence a little bit. 

Further, if I remember the client connects, sends data and then disconnects (not sure on that) from server. This is not needed if you want constant connection once is established.

If you use TIA v13 SP1, you can uncomment this line and comment the next line, as VAL_STRG was found to be reintegrated in TIA V13 SP1 (it was working in TIA v11, but not in v12 and v13)

 //  TIAv11 worked, v13 not  VAL_STRG(IN:=#real_temp, SIZE:=13, PREC:=6, FORMAT:=W#16#6, P:=1, OUT=>#text_temp); //encode real number to ascii with user format
             // TIA v13:
                        "VAL_STRG_TIA13"(InReal := #real_temp,
                                         OutStrg => #text_temp);

Marko Bursic

I think the easiest way is to rapresent octets from DB on HMI as numbers (byte 0-255), you can change freely and settings will remain in DB as all data are retained, of course you need to reboot the connection.

There are some limitations, non resolved problems:

The entire sequence of connection/disconnection has to be redone (from lines 120-330 is OK), at the time I was writing there were very little known about TCON TDISCON TRECV TSEND, therefore it could hang somewhere if the connection breaks. I have found that instead sending a command CMD_QUIT to the server you can simply, disconnect this eases the sequence a little bit. 

Further, if I remember the client connects, sends data and then disconnects (not sure on that) from server. This is not needed if you want constant connection once is established.

If you use TIA v13 SP1, you can uncomment this line and comment the next line, as VAL_STRG was found to be reintegrated in TIA V13 SP1 (it was working in TIA v11, but not in v12 and v13)

 //  TIAv11 worked, v13 not  VAL_STRG(IN:=#real_temp, SIZE:=13, PREC:=6, FORMAT:=W#16#6, P:=1, OUT=>#text_temp); //encode real number to ascii with user format
             // TIA v13:
                        "VAL_STRG_TIA13"(InReal := #real_temp,
                                         OutStrg => #text_temp);

 i make the changes for VAL_STRG and its ok.

As regards the behavior i noticed that the first time you make a connection there is no Error and the Step goes from 9 to 7 which is normal. After you can send data normally.

If you disconnect and connect again (2nd time) then Error activated but the Step goes from 9 to 7 normally and you can send data although to mySQL without problem. I make a debug to see what is the errror. see the attached screenshot. 

As stated, the disconnection, error behaviour isn't 100%. But if you have time you can improve all that. Anyway, you're the first one that has sent some feedback information about this. I have never used it latter, I did just some piece of code because some of my clienet wanted some cheap variant to store data on SQL, that latter changed his mind.

There are some parts of program, that they don't need to be changed at all. SHA1 function, strictly you have nothing to change, because it is complicated and well optimized. Then handshaking, encoding,...its a huge work and it works, you are the whitness that has logged in.

From line 276 to 328 you can change as it suits your demand, you can even delete SQLExe command if you like to send data for logging on the server.

The lines I don't like are 1 to 85 and 365->

Also I have found that you can remove copy: array[0..19] of byte and rtu :int, this because a line

                 MOVE_BLK(IN:=#Pwd.Bytes[0],COUNT:=#Pwd.Len,OUT=>#copy[0]);
                            #rtu:=#Pwd.Len;

does nothing (it does: consumes plc time), it is a residual from earlier versions.

Good day!

great job, thank you.I would like to ask, can there be a project for MSSQL?

Ahtyng

Good day!

great job, thank you.I would like to ask, can there be a project for MSSQL?

No, because MSSQL is not open source. The authentication method is keep secret, you can only get precompiled .dll from MS.

This client was made from source of the native MySQL client .dll