Bug? advanced TDMS on sbRIO9636

Hi everyone,
the problem comes from a sbRIO system using VxWorks. If I want to log the measurement data on a USB storage, it takes to long to sue the normal TDMS VIs, as it take much time for saving the file. So I decided to use advanced TDMS VI to save measurement data. This is how I did on sbRIO:
It doesn't bring any problem if I have 533 data pro channel. However, if the number of data more than 534, the channels in the TDMS data is not arranged correctly. You may find out how it looks like from my attachment. I have also tried the interleaved data layout and it works, but not comparable with the speed of the non-interleaved data layout.
So far Ihave no better idea how I can save data (20000 Simples x16 Chn) on a VxWork system correctly. Any suggestions will be welcome!
I've posted the situation in another post from my last question, so I just want to explain the situation better in this way.
Wilbur
Solved!
Go to Solution.
Attachments:
non_interleaved_sb_RIO.zip ‏201 KB

Hi,
Your advanced TDMS VI is correct. You can verify this by running your VI on your Windows(not the VxWorks target), the VI creates it 4 channels which has 8000 values each, it should be working just as what you've programmed.
But I also found the "non_interleaved_sb_RIO.tdms" file from your attachment is un-readable/corrupted, I cannot read the 4 channels' values successfully from your file.
I understand that your VI should generate equivalent files on both Windows and VxWorks, but the corruption make me think whether your were writing the file on some bad sectors in your USB storage. Could you please try writing the tdms file to other partition(e.g., the tmp folder on VxWorks) ?

Similar Messages

"End of File" error 4 when trying to use Advanced TDMS Palette to create a circular file buffer

I'm using the Advanced TDMS palette to create an on-disk circular buffer. I was able to successfully implement the buffer for a single channel of data.
However, when I try to write multiple channels of data, I continuously get "End of File Encountered" error 4. I am pre-allocating 60,000 data points for each channel using the "TDMS Set Channel Information" function.
I am able to (1) Set Next Write Position and (2) perform an Asynchronous Write to the first channel. But when I try to Set Next Write Position to the second channel, I immediately get an error 4.
The examples have not been helpful as none of them write to different channels in sequence.
Attached is an example project of what I'm trying to do, coded in 2013SP1.
Sorry about the file hierarchy, the project is located in the ZIP file here:
Workspaces\V12000\_V12000 Common Labview Code\Named WF Array\Named WF Array.lvproj
http://linkd.in/mikele
Attachments:
Named WF Array Project.zip ‏1500 KB

I looked into your project and found that the error comes from Set Next Write Position because the "offset" passed in is out of range. In fact, for continueous logging, you don't need to put the Set Next Write Position in front of the write. Remove this function and you will find your VI can run successfully without throwing out any errors.

Advanced TDMS, Set Channel Information

Hello,
I have a problem with scaling in and TDMS File. I´ll try to explain what i want to do.
I work on a system that streams data from 2 PXIe 5122 via peer to peer streaming to 2 NI 7962R FPGA FlexRIO cards. After that I want to stream my measurement data from the FPGA cards to an NI 8260 hdd array via the advanced TDMS API using the "TDMS Advanced Asynchronous Write (Data Ref).vi"
This works fine, but i have a big problem trying to scale my raw data. When using the "TDMS Set Channel Information.vi" I can decide to split my measurement data into two groups, Digitizer 1 and 2 with 2 channels each digitizer. When doing so, the API sets 2 Properties to the groups called "NI_Scale[0]_Scale_Type == AdvancedAPI" and "NI_Scaling_Status==scaled". When the API Sets these 2 properties i don´t have any chance to scale my raw data directly with the "TDMS Create Scaling Information.vi" because this vi sets the scaling information to each channel. The properties were set, but TDMS viewer and also DIADEM ignores these properties cause the group properties from the Advanced API were set.
When taking all 4 channels from both digitizers into one group, the group properties "NI_Scale[0]_Scale_Type == AdvancedAPI" and "NI_Scaling_Status==scaled" won´t be set to the group. But i can´t write the data directly to the TDMS file over the data reference, because i have 2 data references from each digitizer, and the API has a problem deciding what sample belongs to which channel.
So the only thing that worked is to create one group and set channel informations for 2 measurement channels, then get the data reference that contains these two channels and write them to TDMS, then set the other two channels informations and get the second data reference and write them to TDMS.
But the problem is, that i have to do that in a loop. When setting always the channel informations before getting the datareference and write the raw values to TDMS file this slows the performance of my system.
I think the right way shoul be that i can use 2 groups for each digitizer and set channel informations for each without getting these two group properties into my TDMS file. Anyone has an idea how i can solve the problem?

Thanks for your reply,
i know that the scaling vi works when using one group. It also works when using 2 groups. But you put the scaling infos for the whole group. when using an digitizer you can´t do this because every channel has a little bit different scaling values. so u must set the scaling values to each channel. this is done properly, but when using 2 groups tdms viewer and diadem ignore these scaling values because the Groups have the properties as stated in my first post.
Here is a little screenshot of what im trying to do.
Attachments:
TDMS Advanced.png ‏53 KB

BUG: Advanced Actions duplicated when creating NEW PROJECTS FROM TEMPLATE using Adobe Captivate 8.

Need: CREATE NEW PROJECTS FROM TEMPLATE using Adobe Captivate 8.
Problem: NEW PROJECT (.cptx) duplicates the Advanced Actions originally configured within TEMPLATE FILE (.cpt.).
For example: Template file (.cptl) advanced action "_initializeModule" gets duplicated as "_initializeModule1", "_initializeModule2", "_initializeModule3" within NEW PROJECT. FYI, the original "_initializeModule" advanced action still appears.
MAJOR BUG, what the heck is going on?!?!!! Planning to deploy this template file to use for multiple courses with multiple users, this WILL cause epic confusion across the board.

Similar problem, think they are working on it as well: when dragging a shared action from an external library to a slide or object event, and that action is using a parameter that was already created for another shared action, there will be a new parameter created which really screws up the shared action contrary to this problem. Tip: for the moment do not drag shared actions from an external library immediately to an event, but drag them first to the Library: Reuse Shared Actions in other Projects - Captivate 7 vs. 8 - Captivate blog

How to configure tdms advanced read

Hi
I am trying to read a tdms file using advanced TDMS VIs to get a faster reading speed but when I disable the system buffering then I get error -2544 which says that "the array sizes and file positions must be integer multiple of the disk sector size". My disk's sector size is 512 and I am using a buffer of 256 samples with I16 data type which is an integer multiple of the sector size. I have attached the code snippet.
If I use the example VI "TDMS Advanced - Finite Asynchronously Read.vi" it works fine with the file created for the example VI but it doesn't work with my file which has data in I16 format. I am also attaching the example VI.
What could be the reason? please help me out
thanks!
Mani
Solved!
Go to Solution.
Attachments:
TDMS Asynchronous Read.png ‏48 KB
TDMS Advanced - Finite Asynchronously Read.vi ‏22 KB

According to error -2544, either array sizes or file positions is not disk sector size aligned. In your case, since the error is thrown by "Set Next Read Position", probably the target file position is not disk sector size aligned. Is your TDMS file created by TDMS Standard API or Advanced API ? In the latter case, each TDMS head (which contains meta information) is 4K aligned thus easily to set to a sector size aligned position. If it's created by "TDMS File Write", the sample position you want to read from is probably not sector aligned, thus returns error -2544.

TDMS Get Property bug

I found a bug with tdms get property (in LV 8.5) basically if the Property Value output isn't wired then the Found Output may not return true when it should. I've attached an example, just probe the found output, and it'll return false if property value isn't wired and true if it is (you can just attach it to the case structure). Oddly if I attach an indicator to found and wire Property Value, then run it, I can remove the property value wire, and it'll work until I open the vi again.
Matt W.
Attachments:
Bug.zip ‏12 KB

That indeed is a bug. CAR # 4DRIL6WJ. Good thing there's a workaround.
Thanks for letting us know,
Herbert

TDMS error -2503. Is seemingly corrupted file able to be recovered?

We performed a rather expensive test with multiple instruments and gauges on a specimen and recorded the data to a TDMS file. Before we performed the test, we recorded to a "dummy" tdms file for a few minutes and then reviewed the file to confirm that we were recording all the gauges properly. Everything was fine and we knew we were ready to test.
We then recorded during the test and the TDMS file ended up being about 400 Mb. After recording we attempted to open the file and recieved the following error:
"Error -2503
Possible reason(s):
LabVIEW: Specified file does not comply with TDMS file format standards."
There is no record of this error on the forums or anywhere on the website. The data is there, the file is huge. We just need to figure out how to recover it. This data is very important to us. Is there any way to analyze the tdms file and recover the data?
Any time we attempt to open the file in any way we receive the same error. We have tried opening it with the TDMS Excel Importer, Open TDMS file.vi, TDMS Defragment. No luck. The error seems to be occurring in the open tdms file.vi.
The file is very large or I would post it here. Please help
[will work for kudos]
Solved!
Go to Solution.

I solved the problem.
I was trying to figure out which part of the tdms file was corrupt. I was preparing for a long day of altering bits/bytes to fix the corruption, which I have done in the past and is never fun, but it wasn't necessary. Using a file analyzer (http://www.safer-networking.org/en/filealyzer/index.html) I could see that the data was there and the headers were correct throughout the data in the tdms file. There didn't appear to be any wierdness in the beginning or end of the file. This told me that the problem was probably in the index file. I had been reviewing the new advanced tdms VIs in LabView 2010 and was looking for something that could help me. The Advanced TDMS Open.vi mentioned that it deleted the index file and opened the tdms file. I thought perhaps it would recreate the index file. It didn't. The tdms index file was automatically recreated when I opened the the TDMS file and it recreated it properly. The data is there. The file opens properly this time. All is well. It definately leaves me wondering what created the corruption in the first place and how to prevent it in the future.
Solution:
Delete the tdms index file. The TDMS Excel Importer will recreate the index file properly when you open the file. The file opened with no errors for me.
[will work for kudos]

Memory growth in TDMS write

I have tried all the turnarounds as I can find from the NI website, such as
1) Setting the NI-MinimumBufferSize to 10,000, or
2) Using the TDMS Advanced Synchronous Write along with other Advanced TDMS functions instead of standard TDMS write
However, the RT free memory still diminishes gradually when a DMS file is written. It is also noted that the drive space available on the /C/ is reduced as well. Due to the reduced free RT memory, a FPGA memory Full error occurs after recording 4~5 several large TDMS files (100 to 200 MB). Can anyone help on this issue?
More details on the system and the program I am working on:
1) LabVIEW 2014 Professional Developement
2) cRIO 9068 + 2 NI 9234 modules for triggered Sound & Vibration measuement
3) 8 Channels at 51200 S/s
4) FPGA buffer size 8191
5) RT buffer depth 5*8*51200
6) LabVIEW Code is simply beased on the LabVIEW sample project: LabVIEW FPGA Wavefrom Acquisition and Logging on CompactRIO
Regards,
JJDFRD

Hi Kyle,
Thank you for the work you've done on this.
I'm not 100% sure where we should be putting the TDMS Flush function? I've attached a modified cRIO Waveform Acquisition and Logging on CompactRIO Sample project based on a cRIO 9068 and 9234 as JJDFRD is using, and I still see the physcial memory declining with each TDMS write until it gets down to about 4M (reserved for the system) - Funnily enough it seems to work fine and continue to log and write even after it reaches this bottom threshold. If I change the Free Space constant to delete files when the disk space reaches say 30% rather thean the default value of 70%, I can see the Physcial Memory bounces back after a TDMS write and older tdms files are deleted.
If you could pelase confirm where we should put the TDMS Flush function this would be very helpful, and JJDFRD can try this out to see if it fixes his problem.
Kind Regards,
Stuart Little
Applications Engineering

Multiple TDMS Questions

I haev a few questions on TDMS.
1. Is it true that TDMS file is a LabVIEW specific binary, and you can't read it without using LabVIEW?
2. I was able to read the TDMS file in excel. Howcome I can do that? Is excel supposed to be able to read TDMS?
3. Is it true that TDMS is smaller than a regular ASCII file, given the same data? It seems so.
4. If 3 is true, I don't understand why, since I was able to look at the raw data of the TDMS directly in excel, i assume that the data is stored as ASCII and not binary inside the TDMS file.
5. It seeems like TDMS comes in pair, a tdms file and a tdms_index file. Can the tdms be accessed with only the tdms file without the tdms_index and vice versa?
Thanks!
Kudos and Accepted as Solution are welcome!

And I suppose it should be mentioned that there are a few CAR's pertaining to some of the behavior of if you use the Advanced TDMS functions (which you only really need to use if you need to overwrite or replace data in an existing TDMS file).
And if you acquire data one point at a time, make sure you don't put the points in one at the time in the TDMS file as you will create a huge file consisting mostly of duplicated header information (which you can then use the TDMS defrag to fix). It can be better to collect the points in a software/memory array and only push them to the TDMS file once every xx samples.
I find that I enjoy working with TDMS files for my project, but of course my data is awesome for TDMS too, I get my data in "traces" so each logical unit (channel) comes pre-packaged as an array of thusands of points, so my TDMS files tend to be very "efficient".
Here is a copy paste of one of the Advanced issues I ran into:
I have done some more research on the first issue you reported. (Error:
-2529 in [Adv] [TDMS Set Channel Information])
Issue/Feature A) Flush required after channel property writes:
Create some file level properties and write and over-write them.
Create a group and add and overwrite some properties Create a channel in the
group, add a property then try to do a synchronous write. You will get an
error message. Either do a flush between the property write OR write the
channel data first then do the channel property writes.
As it turns out, there is already a Corrective Action Report (CAR) filed
with the LabVIEW Development Team. Here is the CAR#310023 You can look for
this number in the future releases of LabVIEW.
QFang
CLD LabVIEW 7.1 to 2013

TDMS & Config Files Comparison

Hello,
I'm not really new to the community since I had many queries that have already been asked before and I found an answer here, until now. I've been studying up on TDMS (File>Group>Channel) and its conceptual heirarchy seems to be very similar to Config Files (File>Section>Key). Now, I think it's possible to use the TDMS template for config files as well aside from measurement results but I thought I should ask...
What are the advantages and disadvantages of TDMS vs Config (*.ini) Files?
I haven't found any form of comparison between the two so far. I would personally excempt the Notepad accessibility of the Config File as an advantage since it would be better to limit the access to the system settings from non-authorized users.
Solved!
Go to Solution.

For your addon question - this is why it's important to have proper error handling and a proper shutdown routine in your application.
If you have any LabVIEW errors in your application you should handle these properly and if it's deemed to be an unrecoverable error then you tell your application to exit.
You should handle your application being closed correctly to make sure that whenever possible you shut down gracefully and close all of your references (e.g. hardware, file references etc.) before your application exits. There's some good information about that on a recent thread here: http://forums.ni.com/t5/LabVIEW/Best-Practices-for-Gracefull-Application-exit-close/m-p/3094973#M885...
Of course, there is always the possibility that you might get a fatal application crash or you might have a power cut or something - in that case you could periodically flush the TDMS buffer but there is also OS and disk-level caching to consider.
If you look at the Advanced TDMS VIs - you can disable buffering and according to the help "buffering does not occur at any layer".
Certified LabVIEW Architect, Certified TestStand Developer
NI Days (and A&DF): 2010, 2011, 2013, 2014
NI Week: 2012, 2014
Knowledgeable in all things Giant Tetris and WebSockets

Files comparison

how can i compare files (same content's type) with iFS API ?

For your addon question - this is why it's important to have proper error handling and a proper shutdown routine in your application.
If you have any LabVIEW errors in your application you should handle these properly and if it's deemed to be an unrecoverable error then you tell your application to exit.
You should handle your application being closed correctly to make sure that whenever possible you shut down gracefully and close all of your references (e.g. hardware, file references etc.) before your application exits. There's some good information about that on a recent thread here: http://forums.ni.com/t5/LabVIEW/Best-Practices-for-Gracefull-Application-exit-close/m-p/3094973#M885...
Of course, there is always the possibility that you might get a fatal application crash or you might have a power cut or something - in that case you could periodically flush the TDMS buffer but there is also OS and disk-level caching to consider.
If you look at the Advanced TDMS VIs - you can disable buffering and according to the help "buffering does not occur at any layer".
Certified LabVIEW Architect, Certified TestStand Developer
NI Days (and A&DF): 2010, 2011, 2013, 2014
NI Week: 2012, 2014
Knowledgeable in all things Giant Tetris and WebSockets

Too many digits of precision in imported data

I store some data in a TDMS file that has four digits of precision. When I recall the data in DIAdem or import it into Excel there are many more digits there than I want. Do I just have to live with that or is there a way to limit the number of digits to just what I want?
George

Hi George,
Are you saving the TDMS file with LabVIEW or DIAdem? In LabVIEW, you wire a data array of a particular data type to be written to the TDMS file, so the precision used on disk will match that of the data type. So if you're currently wiring a DBL type, converting that array to a SGL type prior to writing the array to TDMS will reduce the precision (and the disk footprint), though it may not reduce it enough for your taste. If you are wiring waveforms to the TDMS file, I believe you are stuck with DBL precision.
If you are saving the TDMS file in DIAdem, and if you have DIAdem 10.1, then you have the option of using the new ChnQuantize() function to limit the resolution of the data both inside of DIAdem and when you save it to disk. Unfortunately, DIAdem 10.1 has a bug for TDMS output when using custom quantization, though this will be fixed in the upcoming DIAdem 10.1 SP1. Still, this doesn't necessarily reduce the number of displayed digits, it just reduces the accuracy so that similar values can be saved in a smaller binary footprint. So this may not be what you're after.
Regardless of the resolution of the saved binary data, DIAdem loads all channel values as DBLs in the Data Portal, and it displays all the digits of precision corresponding to the DBL value it has in memory. However, you can always change the displayed format of a channel value in a VIEW or REPORT table by changing that column's format string. Try "d.ddd" or "d.ddde" for instance.
Ask if you have further questions,
Brad Turpin
DIAdem Product Support Engineer
National Instruments

FileDlgShow Undefined Error

I can't seem to get the FileDlgShow to work. I get an error "Variable is undefined: 'FileDlgShow' whenever I try to use it.
I am using version 10.2. The below is straight from Excercise 5-1 in the Diadem Advanced Course Manual.
Option Explicit
Call DataDelAll(1)
DlgState = FileDlgShow("C:\Excercises\DIAdem Advanced\","*.tdm")
If (DlgState = "IDOk") Then
Call DataFileLoad(FileDlgNameList(0),",")
Call ChnSmooth("[1]/[2]","/Smoothed",12,"maxNumber")
Call ChnPeakFind("[1]/[1]","[1]/Smoothed","/PeakX","/PeakY",5,"Max.Peaks","Amplitude")
Call DataFileSave("Results.tdm","TDM")
Call PicLoad("Smooth_2")
Call PicUpdate(0)
Else
Call MsgBoxDisp("Data loading has been aborted!")
End If
Solved!
Go to Solution.

Hello!
The FileDlgShow command is not part of DIAdem 10.2. It was implemented later in Version 11. You have to use the bulky FileNameGet command instead.
Matthias
Matthias Alleweldt
Project Engineer / Projektingenieur
Twigeater?

T60 Embedded Controller - hangs or crash at power-up

Lenovo ThinkPad T60
Model 200772U
BIOS 79ETE7WW (2.27 )
EC 79HT50WW-1.07
With a dead battery, the T60 will not power-up. With the battery removed, the T60 will sometimes, or often, also not power-up. The problem seems to be buggy embedded controller software, which "hangs" or "crashes" at power-up, perhaps similar to the problem described at:
http://forums.lenovo.com/t5/T61-and-prior-T-series-ThinkPad/T61P-Graphic-problems-random-shut-down-B...
Applying power, the "plug" and "battery" icons light, then the "battery" icon goes dark, where there is no battery attached. Pressing the power button, the "plug" icon then goes dark, and the system "hangs". Pulling the power connector will reset the system. Repeated attempts to start the system, while performing various superstitious rituals of pressing buttons and detaching peripherals, the system powers-up normally again, and runs normally until "sleep" or power-down.
"Searching", this appears to be a common problem, which also occurs across several Thinkpad models.
Also, in a possibly related bug, there is described a "Bug: Advanced battery query causes EC hang" at
http://www.thinkwiki.org/wiki/Embedded_Controller_Firmware
All together, it seems clear that the EC start-up software "tests" are too severe, or just plain broken. Are all Lenovo Thinkpad products this "flakey"? At-end-of-warranty failures are usually more of an HP specialty, in my experience.
Any chance of an Embedded Controller software upgrade from Lenovo? Where are EC software bugs supposed to be reported?
Has anyone found a _consistant_and_reliable_ work-around?
Thanks
James

thx1138 wrote:
Has anyone found a _consistant_and_reliable_ work-around?
Thanks
James
Yes.
Replace the battery with a working genuine one and report back.
Cheers,
George
In daily use: R60F, R500F, T61, T410
Collecting dust: T60
Enjoying retirement: A31p, T42p,
Non-ThinkPads: Panasonic CF-31 & CF-52, HP 8760W
Starting Thursday, 08/14/2014 I'll be away from the forums until further notice. Please do NOT send private messages since I won't be able to read them. Thank you.

E52 bug list for advanced users

I wanted to start the compilation of a bug list for advanced users. Here is my first suggestion:
1. SMS Functionality:
When trying to send SMS to a distribution list, the phone interface will ask you to choose between number and email addresses, even though the phone does understand that this is a SMS and not an email ("Text Message" appering on top)
This happens even when the contact has one phone number only (and an email address) in the phonebook
This does not happen when you use PC Suite to do the same task
2. Mail for Exchange client:
I will not go through the many -most already reported- bugs and general instability of the client. However, I will mention two that I have not seen reported anywhere so far:
When forwarding emails, only the header (From/To/Date/Subject) is forwarded. The rest of the text, as well as possible atachments are not forwarded. This is happening -to my epxerience- every time you try to forward an email
The client doesn't provide information (like the previous, installable client for devices such as E51, E71, etc.) as to when was the last time that sync took place, while it also doesn't show a real-time progress like the previous one. These two functionalities were very useful for controlling the Mail for Exchange process and understanding proactively if there was an issue. I consider these a must for any Business user (going through the log files to understand the same thing is obviously utterly impractical)
The client doesn't synchronise the "Deleted Items" folder from the mail server but only locally (which means it includes emails that were deleted only from the device itself).
The synchronization of the folders other than "Inbox" should be happening ad-hoc whenever the user is accessing these folders and requesting a sunchronization. Otherwise, we see the phenomenon of extremely lengthy synchronizations
3. Screen/Display:
It would be nice, when using the smallest font, to also accordingly compress the menu choices, in order to be able to fit more on the screen. Otherwise, with the present implementation, the fonts get smaller, but the relevant menu icons are not, resulting in an assymetrical look
4. Ovi suite:
As a general comment, I would like to mention that -apart from totally unknown NOKIA policy with regards to Ovi vis-a-vis PC Suite- it is not appropriate for Ovi to contain less functionality than PC Suite (I am referring to SMS presentation, etc.). In general, I find Ovi much clunkier and more clumsy than PC Suite which has actually evolved well over the years as the absolute PC phone tool (and still a differentiator for Nokia). So, NOKIA, please do not screw up PC Suite for something that may be "hype" accoridng to you, but is used as a tool by many of your customers.
5. Log:
As in previous phones/firmware versions, when setting the Log to 30 days, only 7 or ten days are actually retained. Maybe related to phone memory, but in any case it is a nuissance
6. SMS/VMs/Missed calls notifications:
This is not a bug, but at least personally, I preffered the way the SMS/VMs/Missed calls notifications were displayed in the previous devices (E51, etc.), just below the active stand-by applications "ribbon", instead of at the bottom of the screen. The new implementation makes it harder to access these items than before (at least for me)
I appeal to NOKIA to consider and fix these issues in the next firmware release(s).
Timos Tsokanis

@Timos , great compilation. I hope Nokia will work to resolve these quickly.
I have been using phone since last 2-3 days and find few things in Email client really annoying.
Also I want to understand few settings in Email client (version 2.1.0). They have made settings too complicated.
1)Any folder except Inbox doesn't show unread email count in brackets next to folder names.
i.e. If i delete or move 2 emails which I have not read to any folder(Deleted etc) , then deleted folder should be like Deleted(2). But right now it doesnt show anything. Strange.
I have checked with E72 and this bug is not there.
2) I have Gmail, Hotmail and Ovi mail as part of Nokia Messaging. But only Gmail and Hotmail actually show up when I open Messaging. All 3 show up if I open Email.
3)What does "Download Notification" under Global settings do? Notification icon control?
4) Why my Name field in Mailbox setting is picked from account at email.nokia.com, also even though secure connection is Yes under server settings in email.nokia.com, for same email its No in email client.
5) Why I am not allowed to change settings in "What to sync" , e.g. Hide email older than
6) what do settings "synchronise new updates" , "timed sync" do? No explaining in help.
7) Setting ->Gmail(or any other)->Account settings->Account Info, why number is blank? Also please make this work with destinations support. Also connectivity setting should be in global settings.
Best Regards,
Suyog

Bug? advanced TDMS on sbRIO9636

Similar Messages

Maybe you are looking for