SiePortal

The integrated platform for your product selection, buying and support workflow - bringing together Industry Mall and Online Support.

Products & Services
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
Support Support
{{(apiData.Support | filter:{'rank':1}:true)[0].title}} Support
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
MySiePortal MySiePortal
{{(apiData.MySiePortal | filter:{'rank':1}:true)[0].title}} MySiePortal
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
Cart ({{apiData.CartCount}})

Navigation

Simple Sample and TIPs - STEP 7 - long-term trace

12/30/2024 10:07 AM	Rate (0)
Denilson Pegaia Diamond Expert Joined: 9/23/2005 Last visit: 1/19/2026 Posts: 4449 Rating: (1487)	Hi As from TIA V20, the long-term trace and long-term project trace’s recording is saved to a DAT file instead of a CSV file. TIP Saving as dat takes up less space (in some testes I get a order was > 2x, but there is no guaranty that it is a rule). Although saved as DAT, the trace can still be exported as CSV. By default, the folder to save the files is pointed to the project's own folder. When the project is migrated, this pointer to save the logs is not changed, regardless of whether it is default or not. This means that a migrated project can point a long-term trace to the original project's directory. Therefore, after migration, I suggest checking the archive folder for these logs. Sample project (archived from TIA Portal as .zap20 and after that compacted in .zip format to be uploaded here) user= User, all password = Password1! Attachment LongTermTrace.zip (107 Downloads)
	Denilson Pegaia Siemens Industry Sector Technical Support
Suggestion To thank Quote Answer
This contribution was helpful to 3 thankful Users Towome Moderator_Lan CaOd