LabVIEW MilliSecs support manager function and Tick Count block diagram object

Is the output of the support manager function MilliSecs (used in a CIN) directly comparable with the time returned by the Tick Count (ms) block diagram object? i.e. if they have the same value then it is the 'same' time allowing for OS specific time resolution

> Is the output of the support manager function MilliSecs (used in a
> CIN) directly comparable with the time returned by the Tick Count (ms)
> block diagram object? i.e. if they have the same value then it is the
> 'same' time allowing for OS specific time resolution
The LV diagram node is built upon the MilliSecs() function, which is
built upon various OS specific functions. It is safe to treat them as
though they are the same function and represent the same clock.
Greg McKaskle

Similar Messages

How can I open a vi and show the block diagram?

Hi,
I am opening an vi using "Open VI Reference" and "Invoke Methodpen FP", but I want to open the vi and show the block diagram, but I haven´t found any method (Invoke Method) to do that and any property.
Any idea?
Thanks!
Gracinda

OK, I can come up with a reason. I have written a program that will search the entire VI Hierarchy of a program and update all of the descriptions for all VIs with the top level program part #, the name of the top level program that the VI is used in, the company copyright info, the ITAR notice, company address, the name of the engineer performing the update, along with the date and time. This will also place as a background image on all the VIs, a watermark of the company name, legality stuff and the copyright. It works very slick in that if there are thousands of sub-vis, such as what I'm working on now, it goes through all of them, makes sure the data is there as per company policy without having to open every one of them look at them and update or not whichever the case may be. The one portion that is tough is that the program will detect if there is a description written about what funtion the VI performs and if there is not a description, then it pops up a dialog requesting the user to write a description. The problem is that without looking at the block diagram for the VI, it can be nearly impossible to write a description for the functionality of the VI. So is there a way to programmatically open a VI, show its block diagram (this would only be in the case of a missing description) and then upon completion of the updates, close the block diagram? (I already open and close the VI programmatically in order to read the VI DESC and update as needed, but that is in the background and of course you can't see the block diagram).
Thanks,
Dan

Member function and member procedure inside an object type in Oracle.

Hi All,
Please do have a look at these codes and help me understand. I have no idea about this member function and member procedure. How do they work? Please explain me about this.
Regards,
BS2012
create type foo_type as object (
foo number,
member procedure proc(p in number),
member function func(p in number) return number
create type body foo_type as
member procedure proc(p in number) is begin
    foo := p*2;
end proc;
member function func(p in number) return number is begin
    return foo/p;
end func;
end;
/

Methods are just like functions or procedures in a package, except they're not in a package, their part of an object type.
The object has attributes (which are the variables declared in it).
To use such an object you would do things like this...
SQL> set serverout on
SQL>
SQL> declare
2    v_foo foo_type;
3    v_val number;
4 begin
5    v_foo := foo_type(20); -- instantiate the object and initialize the object attributes
6    v_foo.proc(20); -- call the object method (proc)
7    v_val := v_foo.func(4); -- call the object method (func)
8    dbms_output.put_line(v_val);
9 end;
10 /
10
PL/SQL procedure successfully completed.The Type definition you've declared creates the object class, but not actually an object itself.
To actually have an object you need to declare a variable of that object class type, and then instantiate it. When you instantiate the object you need to initialize all the attributes (generally you can pass null if required for each of them to initialize them).
Once you have your object instantiated, you can call the methods within that object as demonstrated above, a bit like calling functions and procedures in a package, except they are methods within the object type itself, and therefore called directly by referencing them from the variable.
The documentation goes into a lot more detail of objects if you look it up.

Print Problem : Print description and tips from structures, nodes and loops from block diagram

Hello,
I've just completed the entire documentation of my VI and I did describe some Case structures and Formula Nodes. Now I want to print the VI with the VI printer and when I select ''Description'' in the custom printer manager, it doesn't select the description from most functions in the block diagram such as Formula Node, Case Structure,etc.
Is there a way to get these descriptions in the printed version VI ?
Thanks a lot !
Solved!
Go to Solution.

Hi Weepet,
After some investigation, it turns out that this behavior is expected behavior. Please see the following help topic
http://zone.ni.com/reference/en-XX/help/371361G-01/lvhowto/creating_vi_and_object_de/
Essentially, Context Help will only display the description for controls, indicators, and constants. At the same time, the descriptions will only print if that description is available in context help. LabVIEW primitives will always use the description from the documentation, and will not display your custom "Description and Tips". So, for primitives like case structures and formula nodes, we cannot get that information to print. The behavior that you're seeing is expected.
Perhaps you can just use comments to document these functions? You can double click on a blank area of the block diagram and provide comments.
Regards,
Che T.
Applications Engineer
National Instruments

LabView application hangs up when scrolling the block diagram

Hi all.
I attached you "Main.vi" that is part of my LabView project. I don't know what's going on, but when I scroll the block diagram to the maximum right, the LabView application hangs up. There are a lot of things in this block diagram because is an outline yet. My plan was to make it more structural, but now I can't do anything because this error don't allow me to edit the diagram.
Please, try to open it (ignore all the dependencies) and check if it hangs up also in your computer.
If it does, is there any way to recover it? It's really important for me because I don't have any backups since two weeks ago...
Regards,
Francisc
Hi all.
I attached you "Main.vi" that is part of my LabView project. I don't know what's going on, but when I scroll the block diagram to the maximum right, the LabView application hangs up. There are a lot of things in this block diagram because is an outline yet. My plan was to make it more structural, but now I can't do anything because this error don't allow me to edit the diagram.
Please, try to open it (ignore all the dependencies) and check if it hangs up also in your computer.
If it does, is there any way to recover it? It's really important for me because I don't have any backups since two weeks ago...
Regards,
Francisco
Attachments:
Main (v3.1).vi ‏257 KB

It didn't hang up on my computer, but it did make me nauseous, luckily I keep a bucket by my desk.
You might have video card issues. Try this: open the VI, and hit Auto Cleanup, then save. Close LabVIEW, reopen. If that does not work, try to get to the far right side by going to the Front Panel, and double clicking something that will take you there. If you get there successfully, use the disable structure to disable ~ 1/8 or more of the diagram on that side. Save, reopen.
Richard

LabView causes system to lock up when editing block diagram of large application

I am attempting to go through a large application which was written for on a different machine with I/O attached. I am looking at it on a plain PC with no attached hardware. The application loads, I can get into the block diagram, but after viewing it for just a short time the display freezes (including the taskmanager), then the keyboard locks up. The only way out is to cycle the power on the PC. This is running W2K on a 550Mhz pentium III processor with 256MB RAM and a new installation of Win2K with all updates applied. This is with LabView 7.1. I can run smaller subvi's with no problem.
I am new at LabView, so any help is appreciated.
- George

Hi George
what kind of Hardware - IO do you use in the app? are there any DAQ-channel- or VISA-Connection-constants in your diagramm? maybe the problem is not the size of your code but the missing hardware...
best regards
chris
Best regards
chris
CL(A)Dly bending G-Force with LabVIEW
famous last words: "oh my god, it is full of stars!"

Determine which vi is executing at runtime and read its block diagram

I have a time-critical loop. Within this loop, one of a set of
known VI's is chosen in a case statement. Within each of those
VI's, data is decoded in a specific way. I cannot modify these
VI's to make the information I need available, because it would
increase the amount of execution time of the tight loop.
What I need to do is write a new VI which will "read" the components of
the block diagram, so I can determine dynamically what code is being
run. For example, if there are three blocks in the running VI
that extract an array element, I need to be able to determine the index
of the array elements being extracted.
I could re-encode all of this information in a new VI, but that would
generate a maintenance headache, because the decoding algorithms would
have to be kept identical for every incremental change.
Is it possible to "read" the contents of a VI from another VI without reverse-engineering the VI file binary format?

Actually, no. I'm probably not being very clear. I'm not
interested in looking at the values within the VI, I want to be able to
see what the VI is doing. I don't want to see the result of
ExtractDataFromArray() (which I know is not a real function -- it was
just an example), that is, I DON'T want to see the values on a "wire"
during execution.
Rather, I want to know how many instances of a certain kind of sub-VI
are in a VI, I want to know how many instances of constants there are,
and which sub-VI's they are wired to.
I want to be able to find this information, essentially:
    In FOO.VI:
       bar.vi is called seven times, each time, the INPUT1 is wired to terminal 1,
        and for the 7 various instances, the values "1," "3," "12," "17," "23," "35," and "71" are wired to terminal 2.
In C-speak, I don't want to know the result of the calls to the imaginary function ExtractDataFromArray(),
rather, I want to know that it was called seven times, with the
arguments (&input1, 1), (&input1, 3), (&input1, 12), ...
And I don't care what was in &input1 when it was called, just THAT it was called.
Essentially, I want to be able to have one VI analyze another and determine what it does.

Why is the Tick Count function slow when used with a .dll but fine with normal lab view code?

when using the Tick Count millisecond timer with a .dll I've written in C, I'm getting some odd timing issues.
When I code the function I want (I'll explain it below in case it helps) in LV and run it as a subVI, feeding it the Tick count as an argument, the function runs quickly, but not quite as quickly as I would like. When I feed this same subVI just an integer constant rather than the Tick Count, it takes about the same amount of time, maybe a tiny bit more on average.
When I bring in my function from a .dll, however, I start to run into problems. When I feed my function an integer constant, it is much faster than my subVI written in LV. When I feel my .dll the Tick Count, however, it slows down tremendously. I'm including a table with the times below:
             | Clock   |   Constant   |
SubVi:   | 450ms | 465ms       |
.dll         | 4900ms| 75ms         |
This is running the function 100,000 times. The function basically shifts the contents of a 2-dimensional array one place. For this function, it probably won't be a huge deal for me, but I plan on moving some of my other code out of LV and into C to speed it up, so I'd really like to figure this out.
Thanks,
Aaron

Hi Aaron,
Thanks for posting the code -- that made things a lot clearer for me. I believe I know what's going on here, and the good news is that it's easy to correct! (You shouldn't apologize for this though, as even an experienced LabVIEW programmer could run into a similar situation.) Let me explain...
When you set your Call Library Function Node to run in the UI Thread you're telling LabVIEW that your DLL is not Thread-safe -- this means that under no circumstances should the DLL be called from more than one place at a time. Since LabVIEW itself is inherently multithreaded the way to work with a "thread-unsafe" DLL is to run it in a dedicated thread -- in this case, the UI thread. This safety comes at a price, however, as your program will have to constantly thread-swap to call the DLL and then execute block diagram code. This thread-swapping can come with a performance hit, which is what you're seeing in your application.
The reason your "MSTick fine behavior.vi" works is that it isn't swapping threads with each iteration of the for loop -- same with the "MSTick bad behavior.vi" without the Tick Count function. When you introduce the Tick Count Function in the for loop, LabVIEW now has to swap threads every single iteration -- this is where your performance issues originate. In fact, you could reproduce the same behavior with any function (not just TIck Count) or any DLL. You could even make your "MSTick fine behavior.vi" misbehave by placing a control property node in the for loop. (Property nodes are also executed in the UI thread).
So what's the solution? If your DLL is thread-safe, configure the call library function node to be "reentrant." You should see a pretty drastic reduction in the amount of time it takes your code to execute. In general, you can tell if your DLL is thread-safe when:
The code is thread safe when it does not store any global data, such as global variables, files on disk, and so on.
The code is thread safe when it does not access any hardware. In other words, the code does not contain register-level programming.
The code is thread safe when it does not make any calls to any functions, shared libraries, or drivers that are not thread safe.
The code is thread safe when it uses semaphores or mutexes to protect access to global resources.
The code is thread safe when it is called by only one non-reentrant VI.
There are also a few documents on the website that you may want to take a look at, if you want some more details on this:
Configuring the Call Library Function Node
An Overview of Accessing DLLs or Shared Libraries from LabVIEW
VI Execution Speed
I hope this helps clear-up some confusion -- best of luck with your application!
Charlie S.
Visit ni.com/gettingstarted for step-by-step help in setting up your system

Why doesn't Tick count (ms) follow Dataflow ?

I have been taught basic examples of Labview data flow like multiple Add, Subtract.. blocks carry out execution at the same time and we can visually see the dataflow in Highlight execution mode.
In this example, I expect count ms to load its value the instant the first frame is run. However, in reality, count ms will only load its value to the right terminal after Search Replace string finishes (takes a long time). This means the time difference is zero !
Note that the integer constant loads the terminal the moment the frame starts, which is correct (unlike count ms)

zigbee1 wrote:
As a matter of fact, I have read papers that suggested splitting copies of code and wire them up at the same time hoping for "concurrent execution". This technique worked no doubt. But now I got to ask myself if they will really execute sequentially one block after another.
Concurrent execution is the normal case with code that doesn't have dataflow dependencies, but it's important to understand what that actually means. If you take the first article you linked to, it shows the transition from code, through the OS to two CPU cores:
This means that at most two instructions can actually execute in parallel. Because computers are really fast, this looks like they're doing many more things in parallel, but that's just because they're breaking them up into smaller chunks and going back and forth between them. This should give you the first clue as to what might be going on - what happens if there's a task which can't be broken up? You have a core which is stuck until that task is done. What happens if you have two such tasks at the same time? Now both cores are stuck and you can't do anything. That's why I said that LV doesn't guarantee parallel execution - it can't.
This problem doesn't actually happen at the CPU level, because operations there are relatively short and should actually have a fixed time, but it can happen at higher levels. Like I said, in this specific case, I'm guessing that the replace function does a DLL call to implement the regex functionality, and DLL calls block the thread they're in. This shouldn't apply to the majority of the primitives in LV, because I far as I know they directly generate machine code. The regex goes through a DLL because it's a standard implementation (PCRE) which isn't done by NI. Presumably other threads should keep running while this blocks.
So again, generally code which you write can execute in parallel (using at least some interpretation of the term. It might be true parallelism, it might be task-swapping), but there are cases where it won't happen. This doesn't change the functionality, but it can affect the actual execution. The reason it doesn't bother me is that it's not as common as you seem to now think it is. In fact, other than your post, I don't think I ran into something similar in quite some time.

[unixODBC][Driver Manager]Driver does not support this function {IM001}

Hello,
I start from the end and details show below - this error message i got in sql session:
SQL> select count(*) from EnergyType@ENERGOPLAN;
select count(*) from EnergyType@ENERGOPLAN
ERROR at line 1:
ORA-28500: connection from ORACLE to a non-Oracle system returned this message:
[unixODBC][Driver Manager]Driver does not support this function {IM001}
ORA-02063: preceding 2 lines from ENERGOPLAN
SQL>
First question - is Oracle Heterogeneous Services are licensed for standard edition ? I cant find this information, and my database - is SE 11.2.0.3.0 - 64bit.
If its ok and HS are licensed for SE, then please see details of my problem:
----OS and packages version
[oracle@aris_sv_db log]$ uname -a
Linux aris_sv_db 2.6.18-308.24.1.el5 #1 SMP Tue Dec 4 17:43:34 EST 2012 x86_64 x86_64 x86_64 GNU/Linux
[oracle@aris_sv_db log]$
[oracle@aris_sv_db log]$ rpm -qa | grep odbc
[oracle@aris_sv_db log]$ rpm -qa | grep unixodbc
[oracle@aris_sv_db log]$ rpm -qa | grep unixODBC
unixODBC-libs-2.2.11-10.el5
unixODBC-libs-2.2.11-10.el5
unixODBC-devel-2.2.11-10.el5
unixODBC-2.2.11-10.el5
unixODBC-devel-2.2.11-10.el5
[oracle@aris_sv_db log]$ rpm -qa | grep freetds
freetds-0.91-1.el5.rf
[oracle@aris_sv_db log]$
-----ODBC.INI, ODBCINST.INI and FREETDS.CONF
[oracle@aris_sv_db log]$ more /home/oracle/.odbc.ini
[ENERGOPLAN]
Driver = FreeTDS
Servername = ENERGOPLAN
Database = ess2
[oracle@aris_sv_db log]$
[oracle@aris_sv_db log]$ more /etc/odbcinst.ini
# Example driver definitions
[FreeTDS]
Description = MSSQL Driver
Driver = /usr/lib64/libtdsodbc.so.0
#Setup = /usr/lib64/libtdsodbc.so.0
#Driver = /usr/lib64/libodbc.so
#Driver = /usr/lib/libodbc.so
UsageCount = 1
Trace = Yes
TraceFile = /tmp/freetds.log
[ODBC]
DEBUG = 1
TraceFile = /tmp/sqltrace.log
Trace = Yes
[oracle@aris_sv_db log]$
[oracle@aris_sv_db log]$ more /etc/freetds.conf
# A typical Microsoft server
[ENERGOPLAN]
host = 192.168.10.64
port = 1433
tds version = 8.0
# client charset = UTF-8
client charset = cp1251
[oracle@aris_sv_db log]$
----CHECK CONNECT from ODBC
[oracle@aris_sv_db log]$ isql -v ENERGOPLAN user pass
| Connected! |
| |
| sql-statement |
| help [tablename] |
| quit |
| |
SQL> select count(*) from EnergyType;
| |
| 8 |
SQLRowCount returns 1
1 rows fetched
SQL> [oracle@aris_sv_db log]$ tsql -S ENERGOPLAN -U user -P pass
locale is "en_US.UTF-8"
locale charset is "UTF-8"
using default charset "cp1251"
1> select count(*) from EnergyType;
2> go
8
(1 row affected)
1> [oracle@aris_sv_db log]$
----LISTENER.ORA, TNSNAMES and initENERGOPLAN.ora
[oracle@aris_sv_db log]$ more /u01/app/oracle/product/11.2.0/dbhome_1/network/admin/listener.ora
# listener.ora Network Configuration File: /u01/app/oracle/product/11.2.0/dbhome_1/network/admin/listener.ora
# Generated by Oracle configuration tools.
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1521))
(ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 1521))
SID_LIST_ENERGOPLAN =
(SID_LIST =
(SID_DESC=
(SID_NAME=ENERGOPLAN)
(ORACLE_HOME=/u01/app/oracle/product/11.2.0/dbhome_1)
(PROGRAM=dg4odbc)
(ENVS="LD_LIBRARY_PATH=/usr/lib64:/u01/app/oracle/product/11.2.0/dbhome_1/lib")
ENERGOPLAN =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = IPC)(KEY = PNPKEY))
(ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.10.72)(PORT = 1523))
ADR_BASE_LISTENER = /u01/app/oracle
[oracle@aris_sv_db log]$ more /u01/app/oracle/product/11.2.0/dbhome_1/network/admin/tnsnames.ora
# tnsnames.ora Network Configuration File: /u01/app/oracle/product/11.2.0/dbhome_1/network/admin/tnsnames.ora
# Generated by Oracle configuration tools.
ORCL =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = orcl)
ENERGOPLAN =
(DESCRIPTION=
(ADDRESS=(PROTOCOL=tcp)(HOST=192.168.10.72)(PORT=1523))
(CONNECT_DATA=(SID=ENERGOPLAN))
(HS=OK)
[oracle@aris_sv_db log]$ more /u01/app/oracle/product/11.2.0/dbhome_1/hs/admin/initENERGOPLAN.ora
# This is a sample agent init file that contains the HS parameters that are
# needed for the Database Gateway for ODBC
# HS init parameters
HS_FDS_CONNECT_INFO = ENERGOPLAN
#HS_FDS_CONNECT_INFO = 192.168.0.199:1433//test
HS_FDS_TRACE_LEVEL = DEBUG
#HS_FDS_TRACE_FILE_NAME = /tmp/hs1.log
HS_FDS_TRACE_FILE_NAME = /u01/app/oracle/product/11.2.0/dbhome_1/hs/log/mytrace.log
HS_FDS_SHAREABLE_NAME = /usr/lib64/libodbc.so #/usr/lib64/libtdsodbc.so.0
#HS_FDS_SHAREABLE_NAME = /usr/lib64/libtdsodbc.so.0
#HS_FDS_SHAREABLE_NAME = /usr/lib/libodbc.so
#HS_LANGUAGE=american_america.we8iso8859p1
#HS_LANGUAGE=AMERICAN_AMERICA.AL32UTF8
#HS_LANGUAGE=AMERICAN_AMERICA.CL8MSWIN1251
#HS_LANGUAGE=RUSSIAN_RUSSIA.UTF8
#HS_LANGUAGE=Russian_CIS.AL32UTF-8
#HS_FDS_FETCH_ROWS=1
HS_NLS_NCHAR = UCS2
HS_FDS_SQLLEN_INTERPRETATION=32
# ODBC specific environment variables
set ODBCINI=/home/oracle/.odbc.ini
set ODBCINSTINI=/etc/odbcinst.ini
#HS_KEEP_REMOTE_COLUMN_SIZE=ALL
#HS_NLS_LENGTH_SEMANTICS=CHAR
#HS_FDS_SUPPORT_STATISTICS=FALSE
# Environment variables required for the non-Oracle system
#set <envvar>=<value>
[oracle@aris_sv_db log]$
[oracle@aris_sv_db log]$ tnsping ENERGOPLAN
TNS Ping Utility for Linux: Version 11.2.0.3.0 - Production on 01-APR-2013 16:27:49
Copyright (c) 1997, 2011, Oracle. All rights reserved.
Used parameter files:
/u01/app/oracle/product/11.2.0/dbhome_1/network/admin/sqlnet.ora
Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION= (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.10.72)(PORT=1523)) (CONNECT_DATA=(SID=ENERGOPLAN)) (HS=OK))
OK (0 msec)
[oracle@aris_sv_db log]$
----CREATE DBLINK and test from sqlplus
CREATE DATABASE LINK "ENERGOPLAN" CONNECT TO "user" IDENTIFIED BY "pass" USING 'ENERGOPLAN';
[oracle@aris_sv_db log]$ sqlplus / as sysdba
SQL*Plus: Release 11.2.0.3.0 Production on Mon Apr 1 16:30:14 2013
Copyright (c) 1982, 2011, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Release 11.2.0.3.0 - 64bit Production
SQL> select count(*) from EnergyType@ENERGOPLAN;
select count(*) from EnergyType@ENERGOPLAN
ERROR at line 1:
ORA-28500: connection from ORACLE to a non-Oracle system returned this message:
[unixODBC][Driver Manager]Driver does not support this function {IM001}
ORA-02063: preceding 2 lines from ENERGOPLAN
SQL>
----logs from hs and odbc
[oracle@aris_sv_db log]$ tail -50 ENERGOPLAN_agt_12117.trc
12 VARCHAR N 100 100 0/ 0 1000 0 200 ConsumptionYearCostUOM
3 DECIMAL N 24 24 9/ 3 0 0 0 ConsumptionYearFactorAmount
-7 BIT N 1 1 0/ 0 0 0 20 NeedToBeApprovedByREK
Exiting hgodtab, rc=0 at 2013/04/01-16:30:42
Entered hgodafr, cursor id 0 at 2013/04/01-16:30:42
Free hoada @ 0x14e5fd20
Exiting hgodafr, rc=0 at 2013/04/01-16:30:42
Entered hgopars, cursor id 1 at 2013/04/01-16:30:42
type:0
SQL text from hgopars, id=1, len=36 ...
00: 53454C45 43542043 4F554E54 282A2920 [SELECT COUNT(*) ]
10: 46524F4D 2022454E 45524759 54595045 [FROM "ENERGYTYPE]
20: 22204131 [" A1]
Exiting hgopars, rc=0 at 2013/04/01-16:30:42
Entered hgoopen, cursor id 1 at 2013/04/01-16:30:42
hgoopen, line 87: NO hoada to print
Deferred open until first fetch.
Exiting hgoopen, rc=0 at 2013/04/01-16:30:42
Entered hgodscr, cursor id 1 at 2013/04/01-16:30:42
Allocate hoada @ 0x14e5fd80
Entered hgodscr_process_sellist_description at 2013/04/01-16:30:42
Entered hgopcda at 2013/04/01-16:30:42
Column:1(): dtype:4 (INTEGER), prc/scl:10/0, nullbl:1, octet:0, sign:1, radix:0
Exiting hgopcda, rc=0 at 2013/04/01-16:30:42
Entered hgopoer at 2013/04/01-16:30:42
hgopoer, line 231: got native error 0 and sqlstate IM001; message follows...
[unixODBC][Driver Manager]Driver does not support this function {IM001}
Exiting hgopoer, rc=0 at 2013/04/01-16:30:42
hgodscr, line 407: calling SQLSetStmtAttr got sqlstate IM001
Free hoada @ 0x14e5fd80
hgodscr, line 464: NO hoada to print
Exiting hgodscr, rc=28500 at 2013/04/01-16:30:42 with error ptr FILE:hgodscr.c LINE:407 FUNCTION:hgodscr() ID:Set array fetch size
Entered hgoclse, cursor id 1 at 2013/04/01-16:31:24
Exiting hgoclse, rc=0 at 2013/04/01-16:31:24
Entered hgocomm at 2013/04/01-16:31:24
keepinfo:0, tflag:1
00: 4F52434C 2E343535 32623466 342E362E [ORCL.4552b4f4.6.]
10: 32322E37 363237 [22.7627]
tbid (len 20) is ...
00: 4F52434C 5B362E32 322E3736 32375D5B [ORCL[6.22.7627][]
10: 312E345D [1.4]]
cmt(0):
Entered hgocpctx at 2013/04/01-16:31:24
Exiting hgocpctx, rc=0 at 2013/04/01-16:31:24
Exiting hgocomm, rc=0 at 2013/04/01-16:31:24
Entered hgolgof at 2013/04/01-16:31:24
tflag:1
Exiting hgolgof, rc=0 at 2013/04/01-16:31:24
Entered hgoexit at 2013/04/01-16:31:24
Exiting hgoexit, rc=0
[oracle@aris_sv_db log]$
[oracle@aris_sv_db log]$ tail -50 /tmp/sqltrace.log
Native = 0x7fff6ca974f4
Message Text = 0x14e5f968
Buffer Length = 510
Text Len Ptr = 0x7fff6ca97750
[ODBC][12117][SQLGetDiagRecW.c][582]
Exit:[SQL_SUCCESS]
SQLState = IM001
Native = 0x7fff6ca974f4 -> 0
Message Text = [[unixODBC][Driver Manager]Driver does not support this function]
[ODBC][12117][SQLGetDiagRecW.c][540]
Entry:
Statement = 0x14e399f0
Rec Number = 2
SQLState = 0x7fff6ca97700
Native = 0x7fff6ca974f4
Message Text = 0x14e5f908
Buffer Length = 510
Text Len Ptr = 0x7fff6ca97750
[ODBC][12117][SQLGetDiagRecW.c][582]
Exit:[SQL_NO_DATA]
[ODBC][12117][SQLEndTran.c][315]
Entry:
Connection = 0x14dbd4b0
Completion Type = 0
[ODBC][12117][SQLGetInfo.c][214]
Entry:
Connection = 0x14dbd4b0
Info Type = SQL_CURSOR_COMMIT_BEHAVIOR (23)
Info Value = 0x7fff6ca9781e
Buffer Length = 8
StrLen = 0x7fff6ca9781c
[ODBC][12117][SQLGetInfo.c][528]
Exit:[SQL_SUCCESS]
[ODBC][12117][SQLEndTran.c][488]
Exit:[SQL_SUCCESS]
[ODBC][12117][SQLDisconnect.c][204]
Entry:
Connection = 0x14dbd4b0
[ODBC][12117][SQLDisconnect.c][341]
Exit:[SQL_SUCCESS]
[ODBC][12117][SQLFreeHandle.c][268]
Entry:
Handle Type = 2
Input Handle = 0x14dbd4b0
[ODBC][12117][SQLFreeHandle.c][317]
Exit:[SQL_SUCCESS]
[ODBC][12117][SQLFreeHandle.c][203]
Entry:
Handle Type = 1
Input Handle = 0x14dbb0c0
[oracle@aris_sv_db log]$

To see which ODBC function DG4ODBC is looking for and unixODBC isn't supporting it would be best to get an ODBC trace file. But as your unixODBC driver (unixODBC-2.2.11-10.el5) is outdated and these old drivers had a lot of issues when being used on 64bit operating systems (for example wrong sizeofint etc). So best would be to update the unixODBC Driver manager to release 2.3.x. More details can be found on the web site: www.unicodbc.org
- Klaus

How long does a tick last for the Tick Count (ms) VI in LabVIEW?

I'm trying to compare the timing performance between a VI implemented in LabVIEW and another VI implemented in LabVIEW FPGA module. If I use the Tick Count in both VIs (every one in their own module), I want to know how long does a tick last in LabVIEW standard (in the computer)?
Thanks

vitrion wrote:
I have this doubt because I read that a tick lasts 55ms in the following source:
http://books.google.com.mx/books?id=en1GKs2huTcC&pg=PA33&dq=tick+count+(ms)+labview+55+milliseconds&...
My tick count provides me better results than the hardware results, which is impossible because this is the same algorithm. If I consider the 55ms time, then the FPGA is really faster.
                          Hardware          Software with                  Software with
                              (ms)        1 ms Tick Count (ms)     55ms Tick Count (ms)
Algorithm 1          49.48                   1.5552                               84.535
Algorithm 2         0.8875                  0.032                                 1.87
Algorithm 3         0.1756                  0.0241                               1.43
Algorithm 4          0.27                     0.27                                   1.32
What's your opinion?
Thanks again
I think you are misunderstanding what the value of a "tick" is. From what I gathered from reading your link (which I couldn't get to from your post, but accidentally ran into on a search) a tick of the OS clock." Curiously, though - why 55ms? That was mentioned as the tick of a Win95/98 OS!
I guess you can say that the it returns the value of the next "tick" of the OS clock and returns that value in ms. So, the value of a tick varies from OS to OS. In Windows 95/98, for example, you can only look at the OS clock every 55ms or so, but it still returns a value that represents ms.
Bill
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.

I would like to put Dreamweaver 8 on a new computer. There is no "deactivate" function and the technical support person I chatted with recommended I come here. Can I just use the serial number again? How can I deactive? Has anyone else run into this?

There is no "deactivate" function and the technical support person I chatted with recommended I come here. Can I just use the serial number again? How can I deactive? Has anyone else run into this? How can I get Dreamweaver 8, which is no longer being activated by Adobe, on a new computer? Is it even worth doing or do I need to get a new version. What are the killer features I'm missing?

If you manage to get it installed on your current OS, don't forget to install the 8.02 update.
Adobe - Dreamweaver Support Center : Updaters
Nancy O.

Messaging Records Management: loss of functionality between Managed Folders and Retention Policy

In Exchange 2007 and 2010 you can use Managed Folders with Managed Content Settings to act on messages based on when they were moved into the folder. E.g.,
New-ManagedContentSettings -Name DeleteJunk -FolderName ManagedJunk -MessageClass * -RetentionEnabled $true -RetentionAction DeleteAndAllowRecovery -AgeLimitForRetention 30 -TriggerForRetention WhenMoved
will delete items 30 days after they're moved into the Junk E-Mail folder designated by the Folder Name "Managed Junk".
However, Exchange 2010 introduces Retention Policies as an alternative to Managed Folders, and Exchange 2013 drops Managed Folders entirely. With a Retention Policy, it's impossible to specify a TriggerForRetention. See http://technet.microsoft.com/en-us/library/dd335226%28v=exchg.141%29.aspx
and note that New-RetentionPolicyTag lacks -TriggerForRetention as a parameter. If you Get-RetentionPolicyTag | fl you can still see a TriggerForRetention value, but it's "WhenDelivered" and can't be changed.
Both http://technet.microsoft.com/en-us/library/bb430780%28v=exchg.141%29.aspx (Exchange 2010) and http://technet.microsoft.com/en-us/library/bb430780%28v=exchg.150%29.aspx (Exchange 2013) describe a rather convoluted method used to determine the age of
a message for retention purposes, but I don't know whether to believe those pages. It seems apparent, though, that basing a message's age on WhenDelivered can easily produce undesired results.
Consider a Retention Policy Tag placed on the Junk E-Mail folder which will perform DeleteAndAllowRecovery on items older than 30 days. A message arrives on 01/01/15 and is classified as Junk. It immediately starts aging based on the date 01/01/15. The user
find the message, which was misclassified, and moves it to another folder. Since there's no way to set a TriggerForRetention based on WhenMoved, the message continues to age from 01/01/15. 90 days later, while the user is reviewing their mail, the user accidentally
clicks the Junk button on the message. Because the message is more than 30 days old, it's deleted immediately.
1) Am I correct? Or is there a way to use Retention Policies so that messages are acted on based on how long they've resided in their current folder?
2) What do I have to do to get Microsoft to add the ability to change the TriggerForRetention on a Retention Policy Tag in Exchange 2013?
Note, I'm not the first person to raise this issue. It's been discussed in a number of places including TechNet. Here are a few:
http://social.technet.microsoft.com/Forums/exchange/en-US/82c01e6e-0184-4d25-b803-45a604ca0c68/retention-policy-tag-problem?forum=exchangesvrsecuremessaginglegacy
http://www.shudnow.net/2010/04/08/exchange-2010-sp1-retention-policies/
http://social.technet.microsoft.com/Forums/exchange/en-US/82c01e6e-0184-4d25-b803-45a604ca0c68/retention-policy-tag-problem

By default there is no property on a message to identify a message is moved from one folder to another.Managed folder used to stamp a new property Moveddate on the message when the ContentSetting on the target folder was set to WhenMoved.
WhenMoved functionality is not available with Retention Policy . You can raise your concern to make this functionality available by opening a ticket with support.

[ODBC Driver Manager] Driver does not support this function

HI every body
In Win Server 2008 R2 , I tried to retrieve data from my ODBC Driver
by Report Builder , my connection test is successful , but after any retrieve data by SQL Statement I encounter with this Error :
IM0001: [Microsoft] [ODBC Driver Manager] Driver does not support this function
I use Win Server 2008 R2 , and my ODBC Driver installed on :
%SystemRoot%\SysWOW64\odbcad32.exe
Can anyone help me to solve this problem, its realy urgent for me ,
PLEASE HELP ………………..

ODBC Driver name is PMSDK (32 bit) and installed by Primavera software
I use SQL Report Builder to connect the driver and try SQL Statement in it
Report Builder may be executing an ODBC function to retrieve meta data, and that function is not supported by the PMSDK driver. Are you using the latest version of the PMSDK driver? You might try turning on ODBC tracing to find out the problem
function.
Dan Guzman, SQL Server MVP, http://www.dbdelta.com

Message : "LabVIEW no longer supports this function..."

When you try to open a VI built in 7.1 using version 8. x and if it has a function like Open/Create/Replace file.vi or Write Characters to File.vi , you get a message that says LabVIEW no longer supports that VI and instead use of another VI is recommended.
Assuming I ignore this warning ( maybe there are too many replacements to be made ) and go ahead and build the VI with LV8.0, will something unforeseen happen ? Because despite the warning of not supporting the function, LV8.0 App. Builder still compiles and builds the EXE using those VIs. I do know that LabVIEW is quite forgiving and tolerates inefficient code but I don't want to compromise efficiency if I can avoid it..
There are many instances when you need to modify code built with previous versions and it may not be viable to spend time to replace functions just to make them compatible with the new version.
Can someone enlighten on this ?
Thanks
Raghunathan
Raghunathan
LV2012 to Automate Hydraulic Test rigs.

The thing that you need to do is save those lists of warnings and go through them to see the comments matter. Some of the unsupported functions could be because the function they performed is no longer needed due to other changes in the language. For example, in V1 you had special formatting VIs to prepare data for plotting. Starting with V2 you could just wire data to the graphs and the display would morph themselves to match the datatype wired to them.
But back to you main point, it used to be that the changes that happened between one version and the next were of the sort that the conversion code could fix on the fly during the conversion process. There were things live terminals were moved around or the datatype of a function was changed. When you saved your code in the new version LV would simply reestablish the connection to the new terminals or insert a type conversion routine so the existing code would continue working. And let me be clear, LV still does that in most cases.
The problem is that NI has started making changes to the way the language works that are not possible to fix automatically. For example, the decision of whether or not to display scrollbars on a subpanel used to be a property of the subpanel - now its a property of the window being inserted into the subpanel. Now you could make the argument that logically this is the way it should have been all along (and I'd agree with you), but the fact remains that this isn't something that LV can fix on the fly because there's no way it can know at compile-time what VIs you going to be inserting into the subpanel. In the end, NI is left to make the decision whether to fix something that was implemented incorrectly the first time or leave it alone for "compatibility reasons".
Of course this opens up the question of how much input from the user community NI gets before making changes - which is clearly not enough considering all the uproar over the interface changes with V8.x. But it also gives me some hope that someday they may drop stacked sequence structures from LV - something that has been there since day 1 and has never really belonged in the language.
Mike...
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

LabVIEW MilliSecs support manager function and Tick Count block diagram object

Similar Messages

Maybe you are looking for