If you have a massive project like mine you can avoid manually saving each POU by first set the Line IDs setting, and then changing the Write project version in file setting. This will change every POU in your project and save it, including fixing the line numbers, without you having to go to all of them
A Jakob Sagatowski video? A good day! The Line ID setting is spot on - huge annoyance that this isn't default. Of all the settings suggestions, this one is my favorite suggestions.
Nice! 4 out of 5 for me... I also check the "confirm moving of files" (or something similar): when I use the PC with just the trackpad sometimes I inadvertently move POUs around...
Great video Jakob. I was at a Siemens Scout workshop about six year ago and I asked how to deal with version control and working on projects with multiple users. Nobody including the teacher ever heard of the words 'version control'. Version control in Scout and TIA portal is a pain because you have to import and export files to readable files before doing a commit to be able to do diffs because the project itself is binary. I'm glad I'm working with TwinCAT now, much easier. But I see that if you are working with multiple people on a project you have to set some settings the same on all pc's because when someone adds a new io device it will be saved in the project again if that person did not change the file setting. I think this should be stored in the project. I also hope they can make the intellisense better. If type CASE .. OF then it will always show Off. Similar for other examples.
My understand is the Line IDs are needed for breakpoint usage. The Line ID basically tells the IDE which line to show when a given breakpoint is active
I used to fix all the whitespaces and tabs by hand as well. But then god had mercy with me and showed me the STweep plugin and since then I dont have to do it myself anymore🙏
Instead of 'End of line markers' much better option is: 0. Open any structured text file in TwinCAT 1. Edit -> Advanced -> View White Space 2. You can put button of this function on any toolbar (PPM -> Customize) 3. Use it in the same way as similar option in Word documents
hi Jakob: 1) Pin Version 2) Fixar versões das bibliotecas 3) Separar configurações em arquivos individuais 4) Manter links não restaurados (Keep Unrestored Links) 5) LinedID 6) Habilitar o Plugin do GIT
Hey, thanks for all your content you're amazing! We would like to unify our Twincat Versions. We would like to stay on 4024. Which version do you advise ? 4024.25 is the one we use but has some bugs. Thanks !
Great video - again! I already had a few of these settings so I guess you've mentioned a few of these in previous videos 🙂 But I have one question: is there any reason for using 4024.54 instead of the latest 4024.55 which is the latest (AFAIK) ?
Turning everything to on in file settings, can make your path very long if you have deeply nested IO hardware. Then git will complain/mallfunction because the path is too long and windows will complain as well (windows default is max 255 chars). You can/should enable long paths in windows and git as well. >>bad things will happen if a colleague without these settings tries to pull your commit...
If you have a massive project like mine you can avoid manually saving each POU by first set the Line IDs setting, and then changing the Write project version in file setting.
This will change every POU in your project and save it, including fixing the line numbers, without you having to go to all of them
Great suggestion!
A Jakob Sagatowski video? A good day!
The Line ID setting is spot on - huge annoyance that this isn't default. Of all the settings suggestions, this one is my favorite suggestions.
Glad you enjoyed it!
Nice! 4 out of 5 for me...
I also check the "confirm moving of files" (or something similar): when I use the PC with just the trackpad sometimes I inadvertently move POUs around...
Great video! End of line marker is a new one on me- I'll be adding that today. Thanks Jakob
Thanks Mark!
Great video Jakob.
I was at a Siemens Scout workshop about six year ago and I asked how to deal with version control and working on projects with multiple users. Nobody including the teacher ever heard of the words 'version control'. Version control in Scout and TIA portal is a pain because you have to import and export files to readable files before doing a commit to be able to do diffs because the project itself is binary. I'm glad I'm working with TwinCAT now, much easier.
But I see that if you are working with multiple people on a project you have to set some settings the same on all pc's because when someone adds a new io device it will be saved in the project again if that person did not change the file setting. I think this should be stored in the project.
I also hope they can make the intellisense better. If type CASE .. OF then it will always show Off. Similar for other examples.
Version control is vastly under-utilized in the industrial automation space! Thanks for feedback.
My understand is the Line IDs are needed for breakpoint usage.
The Line ID basically tells the IDE which line to show when a given breakpoint is active
Its friday and another awesome Jakob video is out! Weekend is saved!
I hope you have better stuff to do during the weekend than TwinCAT-programming! 😅
there is nothing better than TwinCat programming@@JakobSagatowski
For me the most annoying is "SmartCoding" -> "Declaring unknown variables automatically". I also set "Insert with namespace" to get more clear code.
Yes the smartcoding can really drive me crazy!
Jacob jesteś najlepszy. Tak trzymaj :)
Thanks for the generous donation!
"Maybe this is problem with me - with my OCD"
Hahaha. Perfect line. It's not just you. I feel the same way ... OCD is awful. Take care.
I used to fix all the whitespaces and tabs by hand as well. But then god had mercy with me and showed me the STweep plugin and since then I dont have to do it myself anymore🙏
Instead of 'End of line markers' much better option is:
0. Open any structured text file in TwinCAT
1. Edit -> Advanced -> View White Space
2. You can put button of this function on any toolbar (PPM -> Customize)
3. Use it in the same way as similar option in Word documents
great video.. Best regards from kiel
hi Jakob:
1) Pin Version
2) Fixar versões das bibliotecas
3) Separar configurações em arquivos individuais
4) Manter links não restaurados (Keep Unrestored Links)
5) LinedID
6) Habilitar o Plugin do GIT
Hey, thanks for all your content you're amazing!
We would like to unify our Twincat Versions. We would like to stay on 4024. Which version do you advise ? 4024.25 is the one we use but has some bugs.
Thanks !
Latest & greatest in 4024!
Great video - again! I already had a few of these settings so I guess you've mentioned a few of these in previous videos 🙂
But I have one question: is there any reason for using 4024.54 instead of the latest 4024.55 which is the latest (AFAIK) ?
Without release notes from Beckhoff, you never know what has been fixed or not.
I don't know why, but turning on the "Minimize ID changes in TwincCat files" tag turns off advanced parameters in the visualization
That's odd! I don't use the built-in (codesys) visualizations that much.
Do you also save the PLC projects as independent files? I find it a bit strange that TwinCAT saves them in an obscure path such as _Config\PLC\
Turning everything to on in file settings, can make your path very long if you have deeply nested IO hardware. Then git will complain/mallfunction because the path is too long and windows will complain as well (windows default is max 255 chars). You can/should enable long paths in windows and git as well. >>bad things will happen if a colleague without these settings tries to pull your commit...
that feeling when you switch on dark mode .... aaaahhhhhh