https://forge.codesys.com/forge/talk/Engineering/thread/23f23119a7/2025-10-07T09:05:10.382000ZRecent posts to IECStringUtils.FormatDateTime2025-10-07T09:05:10.382000Z2025-10-07T09:05:10.382000Zhteichhttps://forge.codesys.com/u/hteich/https://forge.codesys.com57b80b01c17ad0694254d6e2883c25ea59e4f247

<div class="markdown_content"><p>Does that actually work, though? Where do you put in the actual Date_Time value??</p></div>

2025-07-29T08:11:30.040000Z2025-07-29T08:11:30.040000ZTimvHhttps://forge.codesys.com/u/timvh/https://forge.codesys.comeb92278892360290ba71e7a38f9b7420adb78915

<div class="markdown_content"><p>There has been a fix in SP21. I tried it in this version with the option "Use unicodestring" enabled in the Visualization Manager and it worked if the variables used for the function are declared as WSTRING variables</p> <div class="codehilite"><pre><span></span><code><span class="w"> </span><span class="nt">wsFormat</span><span class="w"> </span><span class="o">:</span><span class="w"> </span><span class="nt">WSTRING</span><span class="w"> </span><span class="o">:=</span><span class="w"> </span><span class="s2">"%t</span><span class="cp">[</span><span class="nx">HH</span><span class="p">:</span><span class="nx">mm</span><span class="p">:</span><span class="nx">ss</span><span class="w"> </span><span class="nx">dd.MM.yyyy</span><span class="cp">]</span><span class="s2">"</span><span class="o">;</span> <span class="w"> </span><span class="nt">wsTime</span><span class="w"> </span><span class="o">:</span><span class="w"> </span><span class="nt">WSTRING</span><span class="o">;</span> </code></pre></div> <div class="codehilite"><pre><span></span><code><span class="nv">IECStringUtils</span><span class="o">.</span><span class="nf">FormatDateTime</span><span class="p">(</span><span class="nv">cbpResult</span><span class="w"> </span><span class="o">:=</span><span class="w"> </span><span class="nf">ADR</span><span class="p">(</span><span class="nv">wsTime</span><span class="p">),</span><span class="w"> </span><span class="nv">uiResultCapacity</span><span class="w"> </span><span class="o">:=</span><span class="w"> </span><span class="nf">SIZEOF</span><span class="p">(</span><span class="nv">wsTime</span><span class="p">),</span><span class="w"> </span><span class="nv">cbpFormat</span><span class="w"> </span><span class="o">:=</span><span class="w"> </span><span class="nf">ADR</span><span class="p">(</span><span class="nv">wsFormat</span><span class="p">));</span> </code></pre></div> </div>

2025-07-25T18:54:35.343000Z2025-07-25T18:54:35.343000Zbnewmanhttps://forge.codesys.com/u/bnewman/https://forge.codesys.com3d95458cd4b0c8e3cf65c38e656eb9cd931d7a69

<div class="markdown_content"><p>Update as of 2025:</p> <p>This function (IECStringUtils.FormatDateTime) doesn't make any sense there isn't any parameter that accepts a Date_Time value.</p> <p>I have no idea what's purpose even is.</p> <p>I am going to use StuSprintf from the StringUtils library for this purpose.</p></div>

2022-05-30T15:03:52.914000Z2022-05-30T15:03:52.914000Zlukashttps://forge.codesys.com/u/lukas/https://forge.codesys.com9568ee218b35e4425144b1cb5c64fb2f6736eeb9

<div class="markdown_content"><p>Hello all,<br/> there is lib IECStringUtils in Codesys that contains FormatDateTime function.</p> <p>It works just fine.</p> <div class="codehilite"><pre><span></span><span class="err">sFormat := '%t[HH:mm:ss dd. MM. yyyy]';</span> <span class="err">sTime := DWORD_TO_STRING(dwTimeDateLocal);</span> <span class="err">xFormatDateTimeOK := FormatDateTime(cbpResult := ADR(sTime), uiResultCapacity := SIZEOF(sTime), cbpFormat := ADR(sFormat));</span> </pre></div> <p>sTime then contains 16:40:00 30. 05. 2022, so exactly what i wanted.</p> <p>But, when I set in Visualization Manager - General Settings - checkbox Use unicodestrings, this function returns in sTime undecoded number. Is this a bug?</p> <p>I know I can use '%t<span>[HH:mm:ss dd. MM. yyyy]</span>' directly in visu (it works ok in there), but I need date and time string for creating a filename.</p> <p>xFormatDateTimeOK is still FALSE (with or without "Use unicodestring" checked) - bug as well or i'm missing something?</p> <p>Thanks for reply, Lukas.</p></div>