TwinCAT 4026.3 - The final(?) beta
ฝัง
- เผยแพร่เมื่อ 24 ก.ค. 2024
- Beckhoff have released a third version of the TwinCAT 4026 beta. Could this be the final beta before release of TwinCAT 4026, and what more news do Beckhoff provide in 4026?
Let's find out in the (hopefully) last video about the 4026 beta!
Visit our sponsor → sase.space/
SASE is a growing community of peers that are at the intersection of automation and software engineering. Whatever platform you use, if you consider your controls programming work to be software engineering, you’ll find a welcome home at SASE.
Please support this channel by either:
- A donation by using the "Thanks" button under the video
- A donation through PayPal → www.paypal.com/donate/?hosted...
- Becoming a Patron → / sagatowski
Need help with your automation project? I'm offering consultancy and programming services through my company → www.sagatowski.com
Subscribe so you don't miss new videos → th-cam.com/users/jakobsagatows...
#TwinCAT #Beckhoff #plcprogramming
0:00 Introduction
1:31 __POUNAME()
8:14 Write LineIDs
10:30 Library parameters
12:15 Library links
13:09 LDate...
15:20 VS2022 transparency
18:02 Runtime? - วิทยาศาสตร์และเทคโนโลยี
Love that thumbnail. Clean style.
Glad you liked it buddy. Learned from the best ❤️
Hi ! Where we can find the link for download the last update ? Or for accessing to a beta?
Do we know how eariler versions of the compiler are going to be handled in the package manager? i.e. the old Remote Manager deployments.
My understanding is that 4024 will be managed through separate packages.
Can you check your dpi settings? Do you use "advanced scaling settings"? With default scaling settings up to 175% there is no issue with library manager.
So who's gonna be brave enough to use the initial release of 4026 on an actual project? Personally I'll be waiting for the first patch. I remember the last big update lol
I agree. Probably wouldn't want to run the first one or two versions on a real production machine. Usually not an issue though as it anyway takes some time to do development of a brand new machine and Beckhoff usually do a few releases until machine goes into production.
@@JakobSagatowski with the way my company manages projects, 4028 will be out before some of our current machines leave 😭😅
I downloaded and installed the TwinCAT/BSD today, it say it's 4026 after the installation.
Have you tested TC/BSD 4026?
I sure have! I have some videos about it here on my TH-cam!
POUNANE is far better than the old version with the pragma. An obvious exrension of it now is the ability to form hyperlinks in ADS writes. Imagine you have a debug message rhat writes to the ads log in XAE. The message has a hyperkink you can click, and the XAE will automatically open the page. This is something that exists in more traditional IDEs, im hoping we see it in TC
hello,
New Operators:
VAR
sPouName : STRING;
sPositionImpl1 : STRING;
sPositionImpl2 : STRING;
END_VAR
sPouName := __POUNAME();
sPositionImpl1 := __POSITION();
sPositionImpl2 := __POSITION();
Those are great too! Thanks Victor!
The __POUName is not really anything new, this could already be done in earlier versions using Attribute 'instance-path', although you needed to create a function block for that (but then you had also the possibility to use solution name, project name, etc.). This is not really a game changer. What bothers me most though is that it is 2024, the new version of Twincat is almost ready, and still no dark theme working in POUs. That is kinda lame on Beckhoff part :)
In the usecase I showed using TcUnit TEST() it's a larger amount of boilerplate code using attribute 'instance-path' compared to __POUNAME(), which is just a cleaner way in this particular example. I use instance-path for many other reasons (logging for example), but for test-cases I think this is perfect.
Am I correct in that the instance-path attribute didn't cover method names, while __POUName does?
That's correct! The instance-path attribute can't be applied to methods.
*Promo sm* 🔥