UTF-16 in labview 8.5

hi,
some body help me, i want to use 16 bit character set in labview.Actully i want to send a wild character which code is above 8 bit means greater then 255.
After too many search ,i could not find any vision to use unicode character like theta in my vi to send my instrument.
so please if some body have an idea to view and also send a character like theta with a string to an instrument as a command get me the solution.
thanx

Hi veerv,
If you are looking for ways to send 'theta' to your instrument i suggest you look for the code for 'theta' that your instrument understands (which should be a number).
Here's a link from where you can find the codes for theta.
http://www.fileformat.info/info/unicode/char/03d1/index.htm
There are ways to display unicode characters on your front panel but i guess this is not what you want.
Hope this helps.
Regards,
Ujjval

Similar Messages

Why does my LabVIEW occasionally display in Chinese?

Windows Vista and LabVIEW 9.01.
Occassionally when working in LabVIEW, different parts will suddenly begin displaying in ( presumed ) Chinese characters - see attached screen shot. I do not speak Chinese and have never had any of my OS regional settings configured for Chinese. Usually, if I just close LabVIEW and reopen, everything goes back to normal; although there was one instance where it happened in a VI which I accidentally saved in that form and could not get the characters to go back. Its more an annoyance than anything else, but it has happened multiple times is a single day and is becoming very aggrevating. Has anybody else ever seen this, or am I just lucky like that?
-A. Marks
Attachments:
LabVIEW Chinese.jpg ‏147 KB

I'm going to take an educated stab at your problem: your LabVIEW.ini file at some point had the key UseUnicode=True, or you are actively developing using UTF-16 Unicode on your front panels. From my experience, this is OS independent (I've been Unicoded on WinXP, Vista, and 7) and LabVIEW version independent (at least, between versions 8.2.1 and 2009)... it's linked simply to an unreproduceable, intermittent bug in the IDE's handling of 1-byte versus 2-byte string.
All of the "Chinese" characters you are describing are 1-byte ASCII strings that are being interpreted and displayed by the IDE as fixed 2-byte MBCS, or UTF-16. Take a look at all of the characters... there will be exactly half as many (or half minus one) characters of the "Chinese" string compared to the English ASCII string.
Take a look here where I have described the same issue.
a.lia-user-name-link[href="/t5/user/viewprofilepage/user-id/88938"] {color: black;} a.lia-user-name-link[href="/t5/user/viewprofilepage/user-id/88938"]:after {content: '';} .jrd-sig {height: 80px; overflow: visible;} .jrd-sig-deploy {float:left; opacity:0.2;} .jrd-sig-img {float:right; opacity:0.2;} .jrd-sig-img:hover {opacity:0.8;} .jrd-sig-deploy:hover {opacity:0.8;}

How does LabVIEW convert string to char* when passing them to a Call Library Node?

I have a program which calls C++-based libraries which themself use external libraries (Qt). I pass strings to my library through the Call Library Node, and was wondering how the formatting goes? I have to interpret the char* according to Latin1, UTF-8, UTF-16, ... to convert them to a string which the Qt libraries understand. I need to use char* instead of LV strings, because the library is indepent of LabVIEW.
It seems that interpreting the char* as Latin1 (default) does not work on Korean systems (for one of our customers), which is understandable when you know that the Latin character set does not know Korean signs. Anyone knows how the char* should be interpreted then? In other words, for non-Latin languages, what exactly is passed to the DLL?

I don't think that we reinterpret your string in anyway, just reformat the data so that it can be passed to your dll.
So assuming you are getting text from, say, keyboard editing, the text should be in the ANSI codepage that the system is running under. That is, if you are running Windows using an English locale, it will be codepage 1252 (Windows Western, Latin 1), if you are running Windows with a Korean codepage iirc it will be codepage 949, Unified Hangul code.
If you are filling the string with data that you get from an instrument or some other fashion, it could really be anything.
Here is a list of the codepages that Windows knows about
http://msdn2.microsoft.com/en-us/library/ms776446(VS.85).aspx
I do have some experience with Qt as well, and I think that the function you are looking for to create, say, a QString from this is:
QString::fromLocal8Bit
but I am not 100% certain about this as I am not a Qt expert.
Jeff Peters
LabVIEW R & D
Message Edited by jpeters on 04-02-2008 12:38 PM

Read/Write file in Unicode (UTF-16)

Hi, I have some issue to write a file in Unicode (UTF-16)
I have to read a file with LabView, change some parameters and write the new data into the same file. The file uses Unicode UTF-16.
I downloaded some library here: https://decibel.ni.com/content/docs/DOC-10153
I can read the file, convert the data to UNI/ASCII/UNI, and then write the file. But when I open the new file with an editor like Notepad++ there are some unexpected characters at the end of the line.
Even reading the file and writing exactly the same data doesn'not work.
I attached an example.
Thanks for you kind support.
Solved!
Go to Solution.
Attachments:
TEST.zip ‏7 KB

Right-click on your Read and Write Text File functions. There is an option to "Convert End Of Line". Turn that off on both functions.
As a side not, you don't need the Close File functions. The Read and Write Text File functions will close the file if the file reference output is not wired.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

Reporting success or failure of labview command line build

We've set up a nightly build for our project, using a batch file for compiling the C++ code in our project on Windows. Thanks to some other posts on this subject, we've gotten the command-line build to work in Labview 8.2. I'd like to add the Labview build command to same batch file as the C++ build. We found how to check within Labview if the project built or failed; however, I didn't see a way to report the success or failure status of the build from the Labview environment back up into the calling batch file (as/just before Labview exits).
One option is to have the batch file check for the existence of the Labview output executable file(s). Does anyone have a more elegant solution?
Thanks,
Adam

Hello Adam,
Based on what you have described, your method seems to be the simplest way to do it. You can not only check whether the executable files were created, but you can also check to see the modification dates to make sure that they are from the latest build.
body { margin: 0 0 0 0; padding:0 0 0 0 }
td,div { font-family:Arial;font-size:10pt;vertical-align:top }
body { margin: 0 0 0 0; padding:0 0 0 0 }
.transcript { background-color:#d2d2d2; }
.messageBlock { margin-left:4px; margin-bottom:3px }
.message { margin-left:100px; word-wrap:break-word; white-space:-moz-pre-wrap; _white-spacere; }
.messageCont { margin-left:100px; word-wrap:break-word; white-space:-moz-pre-wrap; _white-spacere;}
.other { color:#39577a;vertical-align:top;font-weight:bold;font-style:normal;float:left; width:95px; }
.myself { color:#da8103;font-style:normal;font-weight:bold;font-style:normal;float:left; width:95px; }
.otherCont { font-size:8px;text-align:right; color:#39577a;font-family:Arial,Lucida Grande;font-style:normal;vertical-align:top;font-weight:bold;float:left; width:95px; }
.myselfCont { font-size:8px;text-align:right; color:#da8103;font-family:Arial,Lucida Grande;font-style:normal;vertical-align:top;font-weight:bold;float:left; width:95px; }
.system { margin-left:4px; word-wrap:break-word;color:#da8103;font-style:normal;font-weight:normal; white-space:-moz-pre-wrap; _white-spacere; }
.showTimestamp { margin-right:3px; float:right; color:#999999;font-style:normal;font-weight:normal; }
.other1 { color:#ac2000;vertical-align:top;font-weight:bold;font-style:normal;float:left; width:95px; }
.otherCont1 { font-size:8px;text-align:right; color:#ac2000;font-family:Arial,Lucida Grande;font-style:normal;vertical-align:top;font-weight:bold;float:left; width:95px; }
.other2 { color:#3c9fa8;vertical-align:top;font-weight:bold;font-style:normal;float:left; width:95px; }
.otherCont2 { font-size:8px;text-align:right; color:#3c9fa8;font-family:Arial,Lucida Grande;font-style:normal;vertical-align:top;font-weight:bold;float:left; width:95px; }
.other3 { color:#e25614;vertical-align:top;font-weight:bold;font-style:normal;float:left; width:95px; }
.otherCont3 { font-size:8px;text-align:right; color:#e25614;font-family:Arial,Lucida Grande;font-style:normal;vertical-align:top;font-weight:bold;float:left; width:95px; }
.other4 { color:#0b6ac8;vertical-align:top;font-weight:bold;font-style:normal;float:left; width:95px; }
.otherCont4 { font-size:8px;text-align:right; color:#0b6ac8;font-family:Arial,Lucida Grande;font-style:normal;vertical-align:top;font-weight:bold;float:left; width:95px; }
.other5 { color:#b23290;vertical-align:top;font-weight:bold;font-style:normal;float:left; width:95px; }
.otherCont5 { font-size:8px;text-align:right; color:#b23290;font-family:Arial,Lucida Grande;font-style:normal;vertical-align:top;font-weight:bold;float:left; width:95px; }
.other6 { color:#02e7c7;vertical-align:top;font-weight:bold;font-style:normal;float:left; width:95px; }
.otherCont6 { font-size:8px;text-align:right; color:#02e7c7;font-family:Arial,Lucida Grande;font-style:normal;vertical-align:top;font-weight:bold;float:left; width:95px; }
.other7 { color:#5b3284;vertical-align:top;font-weight:bold;font-style:normal;float:left; width:95px; }
.otherCont7 { font-size:8px;text-align:right; color:#5b3284;font-family:Arial,Lucida Grande;font-style:normal;vertical-align:top;font-weight:bold;float:left; width:95px; }
.tsDisplay { display:block }To check if they exist, you can use the following batch command to check if a file exists:
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
IF EXIST some.txt DOSOMETHING
Good luck!
Kameralina
Ask NI (ni.com/ask)
Search The KnowledgeBase
NI Developer Zone
Measure It. Fix It. ni.com/greenengineering/
NI Vision ni.com/vision/

Parsing a non-standard (LabVIEW) xml file

I inherited an xml file which does not use the normal LabVIEW schema, where the types would be defined for each value and the number of elements would be defined for an array. Although a schema file xsl is listed in the xml header, no such file exists.
Below is a example of the file's contents. It is a much much shorter version of the actual file. As I look at the file and start to implement code to support it, I am wondering if I am creating an oversized monster better known as Rube Goldberg code for this task. Below is the snippet for the latest attempt that I started (obviously unfinished). It is obvious that I am not an expert at dealing with xml files, which is why I posted this thread. In other words, I am seeking advice on the appropriate approach to extract values from an exl file that contains code similar to that below.
The LabVIEW code will need to do 2 things:
1. parse the file and populate clusters with the data (I am trying to avoid a giant cluster)
2. allow to edit the values and write them back to the xml file, while retaining the original format (this is where it becomes tricky).
I have tried a couple of other approaches that I was not happy with. Below is the snippet for the latest code that I just started. I'm trying to avoid falling into the rabbit hole.
<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type="text/xsl" href="myschema.xsl"?>
<calibration>
<header>
    <hash>bogus123</hash>
    <version>15</version>
    <date>Dec-2-2014</date>
    <author>Me</author>
    <description>Calibration data.</description>
    <comments>new auto-generation</comments>
<unit-serial-number>007</unit-serial-number>
<unit-assembly-number>A01.00</unit-assembly-number>
<base-serial-number>533</base-serial-number>
<module-serial-number>788</module-serial-number>
<di-serial-number>001</di-serial-number>
<di-assy-number>123-01</di-assy-number>
</header>
<content>
    <data>
      <name>Power</name>
      <description>Output power vs Frequency</description>
      <params>
        <param name="RFFlag">TRUE</param>
         <param name="Temperature">38</param>
        <param name="BaudRate">115200</param>
      </params>
      <table>
        <params>
          <param name="Frequency">5551212</param>
        </params>
        <header>Pout (dBm), RF_GAIN</header>
        <rows>
<row>0,0x05</row>
<row>0.5,0x08</row>
<row>1,0x0A</row>
<row>1.5,0x0C</row>
<row>2,0x1F</row>
<row>2.5,0x12</row>
<row>3,0x16</row>
<row>3.5,0x1A</row>
<row>4,0x1E</row>
<row>4.5,0x23</row>
<row>5,0x28</row>
<row>5.5,0x2D</row>
        </rows>
      </table>
      <table>
        <params>
          <param name="Frequency">9993333</param>
        </params>
        <header>Pout (dBm), RF_GAIN</header>
        <rows>
<row>0,0x05</row>
<row>0.5,0x08</row>
<row>1,0x0A</row>
<row>1.5,0x0C</row>
<row>2,0x1F</row>
<row>2.5,0x12</row>
<row>3,0x16</row>
<row>3.5,0x1A</row>
<row>4,0x1E</row>
<row>4.5,0x23</row>
<row>5,0x28</row>
<row>5.5,0x2D</row>
        </rows>
      </table>
    </data>
    <data>
      <name>Loss</name>
      <description>loss vs frequency</description>
      <params>
        <param name="Temperature">34</param>
      </params>
      <table>
        <header>Frequency, Loss</header>
        <rows>
          <row>5551212,0.8</row>
          <row>6661313,0.8</row>
          <row>7771414,0.8</row>
        </rows>
      </table>
    </data>
      <name>Attenuation</name>
      <description>RF vs attenuation</description>
      <table>
        <header>index, DAC</header>
        <rows>
          <row>1, 0xCCC</row>
          <row>2, 0xCCC</row>
          <row>3, 0xCCC</row>
          <row>4, 0xCCC</row>
          <row>5, 0xCCC</row>
          <row>6, 0xCCC</row>
          <row>7, 0xCCC</row>
        </rows>
      </table>
    </data>
    <data>
      <name>Current</name>
      <description>current vs Pout</description>
      <table>
        <header>ADC, current</header>
        <rows>
          <row>0x2, 0x66</row>
          <row>0x2, 0x66</row>
          <row>0x2, 0x66</row>
          <row>0x2, 0x66</row>
          <row>0x2, 0x66</row>
          <row>0x2, 0x66</row>
          <row>0x2, 0x66</row>
          <row>0x2, 0x66</row>
          <row>0x2, 0x66</row>
          <row>0x2, 0x66</row>
          <row>0x2, 0x66</row>
          <row>0x2, 0x66</row>
          <row>0x2, 0x66</row>
          <row>0x2, 0x66</row>
          <row>0x2, 0x66</row>
          <row>0x2, 0x66</row>
          <row>0x2, 0x66</row>
          <row>0x2, 0x66</row>
          <row>0x2, 0x66</row>
          <row>0x2, 0x66</row>
          <row>0x2, 0x66</row>
          <row>0x3, 0x66</row>
          <row>0x3, 0x66</row>
          <row>0x3, 0x66</row>
          <row>0x3, 0x66</row>
          <row>0x3, 0x66</row>
          <row>0x3, 0x66</row>
          <row>0x3, 0x66</row>
          <row>0x3, 0x66</row>
          <row>0x3, 0x66</row>
          <row>0x3, 0x66</row>
        </rows>
      </table>
    </data>
   </content>
</calibration>
Attachments:
xmlTry.png ‏64 KB

Ray.R wrote:
Hi Darin.
How have you been? Wishing you a belated Happy New Year!
I like your expression: "step away from the mouse". Very much to the point.
Thanks for the advice. I'll check out XPath.
Cheers,
RayR
Doing well, Thanks. Wishing you an early Chinese New Year. (that's going to get bleeped). [Edit: Yay, no more bleeping Chinese]
Be a little careful with XPath. Some people have been known to wrap C++ libraries to have access to XPath 2.0 and an XSLT engine for awesome search and replace capabilities. Others have been known to find ways to program XPath graphically:

The output of a power supply in labview using a Magna Power LXI over RS232 to simulate a periodic voltage.

How can I toggle the output of a power supply in labview using a Magna Power LXI over RS232 to simulate a periodic voltage? Any help would be apreciated?

LXI is Ethernet communication.
Does the power supply have an RS232 port?
Are you looking for an RS232 to Ethernet (LXI) Converter
https://www.google.com/webhp?sourceid=chrome-instant&ion=1&espv=2&ie=UTF-8#q=rs232%20to%20ethernet%20ip
But to simulate a periodic voltage you need to send the SCPI "Source" command to the power supply in a loop.
Changing the Voltage setting in periodic value.
How fast of a periodic voltage do you need?
You may be limited to how fast LabVIEW, Windows and your power supply can respond to commands.
Use VISA writes. It is the same for LXI as it is for RS232. The LabVIEW code would be the same.
After you select the corrent VISA Ref, either a com port or an IP address, LabVIEW does not care if it is LXI or RS232.
From a Magna manual I found
Command Syntax
[SOURce]:VOLTage[:LEVel][:IMMediate][:AMPLitude] <nrf+>
[SOURce]:VOLTage[:LEVel]:TRIGgered[:AMPLitude] <nrf+>
Examples
VOLT 200
VOLTAGE:LEVEL 200
VOLTAGE:LEVEL:IMMEDIATE:AMPLITUDE 2.5

How can I find the vanishing point with Labview?

I am using a myRIO for developing a system for helping visually imapaired people in their navigation. I have already done the image processing of what is being aquired by the camera (edge detection and finding of straight lines).
How can I fin the vanishing point from the two edges of a path in an image with LabVIEW? Is there any special function that I can use?
Thank you!
Solved!
Go to Solution.

The vanishing point is the intersect of two lines, right?
https://www.google.com/webhp?sourceid=chrome-instant&ion=1&espv=2&ie=UTF-8#q=intersect%20point%20of%...
Machine Vision, Robotics, Embedded Systems, Surveillance
www.movimed.com - Custom Imaging Solutions

Como deixar a codificação padrão "iso-8859-1" ao invés de "utf-8" no navegador?

Quando faço o acesso ao banco do meu cartão de crédito, a primeira pagina deles é codificada com "UTF-8" e também existe o comando "charset=utf-8" no código HTML, após digitar o número do cartão, ele direciona para outra página, porém codificada com "iso-8859-1", mas sem nenhuma codificação no código HTML.
Identifiquei que o navegador usa por padrão o "utf-8" quando não existe codificação no código HTML, então gostaria de modificar esse padrão para "iso-8859-1".
O único lugar que encontrei para essa codificação foi ao pressionar o botão de avançado em "Fontes e cores", porém não funcionou.
A versão do meu navegado é 23.0.1, entretanto desde a versão 18 que encontro esse problema.

It is possible that the server sends the file(s) by default with UTF-8 and in such a case this encoding send by the server prevails over all other settings.
You can see the encoding here: Tools > Page Info > General
*Press the F10 key or tap the Alt key to bring up the hidden "Menu Bar" temporarily.

Open and close multisim contact with LabVIEW

Can I open and close multisim contact with labview and read the receptor estatus (p.e. lamp)?
Thanks.
Attachments:
Dibujo.JPG ‏13 KB

Hi Guddan,
I created a RFC having a query which is taking a long time to execute. So i want to close RFC connection with portals which is via java connector(JCO) before that query and open the connction again after that query.
I guess i will need to understand your requirement a little more in detail, as i understand you have an RFC which has a query within to fetch some data and is taking a long time to do so. In the meantime you don't want to keep the connection open?
My question would be, Is the role of this RFC to only execute the query and fetch the data or does it do something else?
If it does other things and these are independent of the query execution, then you can span a parallel call within the RFC to execute the query and in the meantime the RFC does the other things (or vice versa) hence reducing the overall time taken.
If the sole purpose of this RFC is to execute the query, then you will not be able(i mean to say there is no simple and direct way of doing this) to close the connection after the Query is started and re-establish the connection after its execution, for a simple reason that - how will you know if the query has completed it's execution, so that you can establish the connection back.
Alternate solutions, make this a two way asynchronous call, 1) You invoke the RFC asynchronously and close the connection, the RFC in turn will execute the query and transfer the data to JCO via another RFC call.
If this needs to be a synchronous call, then you will need to optimize the query to its best.
Regards,
Chen

LabView Exe Application file not launch Excel application for report generation

Dear All,
I created one LabVIEW application file for report generation (using Excel Template).
While I run the program in programming mode it works well and create the report file in the specified path.
After creation of the application file(exe), it gives the correct path of where the excel template is placed. The same path is given to New Report.vi, but it gives the error 'File Not Found'.
Tell me, is any other configuration required for generating Excel reports? (During exe application mode)
Give me the solution.
Thank You
Jegan.

Hello,
Most likely you are encountering a problem of stripping and/or building paths. Probably the easiest thing to do is put a couple indicators on your front panel for the path or paths you care about, build your exe, and make sure you are really using the path you'd like. If you always put the report at some deterministic place relative to the exe (that is, even it the exe is moved, it will go with the exe and remain in the same relative path location, then you can use the Current VIs Path funtion found in the ... File I/O -> File Constants palette as a start path (where you will want to strip at least the exe name off of course).
I think this will bring some clarity to the issue!
Best Regards,
JLS
Best,
JLS
Sixclear

Error involving Report Generation Toolkit and Labview Run Time Engine

Developed an application using LabVIEW 6.1 and LabVIEW Report Generation Toolkit for Microsoft Office 1.0.1. From there, tried to build a shared application for use with the LabVIEW Run Time Engine. The Run Time version functions properly until "New Report.vi" is called and then an error is generated, code 7, calling out "Open VI Reference in New Report.vi" could not be found. When building the application, I did include the "NI Reports Support" in the advanced installer options. The machine used for original development and application build is running Windows XP Pro and Office XP. Any suggestions??

I am having the exact same problem but with LV 6.1 and M/S WORD 2000. It appears that the "New Report.vi" is trying to open "C:\APP.DIR\Word_Open.vi" and "C:\APP.Dir\Word_Open_Document.vi" by reference. The "OFFICE 2000.TXT" says that "_exclsub.llb and _wordsub.llb must be added as support files when building an application or a dynamic link library with the application builder." I added them as Support Files and I copied them to the "C:\TESTER\" where the TESTER.EXE is and I still get ERROR 7 in "NEW REPORT.VI" at VI OPEN REFERENCE.
Do I need to make a "C:\TESTER\DATA\" sub-dir and put the support files there?
I am building on MY COMPUTER on F: Drive on a network and transporting files to the real Tester.
I displayed my App.Property of APP.DI
R at start up and it is C:\TESTER\ ! How would my application know that "Word_Open.vi" and "Word_Open_Document.vi" are actually inside the _wordsub.llb?
Any ideas ?
Greg Klocek

Why do I get "The exception Privileged instruction (0xc0000096) occured in the application" error message when exiting LabVIEW 6.1?

I have created a vi that uses the LV-GPIB and database connectivity vis. The program runs fine and it ends execution by running the "Close Database Connection.vi".
After closing out my front panel windows and exiting LabVIEW 6.1, I get an error dialog box that reads the message "The exception Privileged instruction (0xc0000096) occured in the application". What does this error mean and how do I resolve it?
Thanks,
Taf

Hi Taf,
Given the broad scope of your application, it may be best to try and isolate the problem down by taking out parts of your application and simplifying it down as much as possible until you can get a consistent version that throws this exception. I would first try to take out either the GPIB or database connectivity portions of the application to narrow down our problem. This error generally occurs when accessing DLLs and external applications, so I wouldn't be surprised if it's the GPIB or database. Let's try to see exactly which one it is and then we can dig deeper into that part of the code. Thanks for your cooperation!
Jeremy L.
National Instruments
Jeremy L.
National Instruments

Conversion of XML file from ANSI to UTF-8 encoding in SAP 4.6C

Hi All,
Im working on SAP 4.6C version.I have generated a XML file from my custom report.It is downloading in ANSI format.But i need to download this into UTF-8 format.So can anyone please let me know how to do this?
Is this possible in 4.6C version?
Thanks in Advance,
Aruna A N

Hello
It is possible in 4.6.
Try this code:
REPORT Z_TEST_XML_DOWN .
data:
lp_ixml type ref to if_ixml,
lp_xdoc type ref to if_ixml_document,
lp_sfac type ref to if_ixml_stream_factory,
lp_ostr type ref to if_ixml_ostream,
lp_rend type ref to if_ixml_renderer,
lp_enco type ref to if_ixml_encoding.
data:
lp_root type ref to if_ixml_element,
lp_coll type ref to if_ixml_element,
lp_elem type ref to if_ixml_element.
class cl_ixml definition load.
data:
udat like lfa1,
s type string.
select single * from lfa1 into udat where lifnr = '0000000001'. " <- set here real number
*** create xml
lp_ixml = cl_ixml=>create( ).
lp_xdoc = lp_ixml->create_document( ).
lp_root = lp_xdoc->create_simple_element( name = 'Node'
                                          parent = lp_xdoc ).
s = udat-land1.
call method lp_root->set_attribute( name = 'country_name'
                                    value = s ).
s = udat-name1.
call method lp_root->set_attribute( name = 'vendor_name'
                                    value = s ).
s = udat-ort01.
call method lp_root->set_attribute( name = 'city_name'
                                    value = s ).
*** render xml
types: begin of xml_tab_line,
         line(256) type x,
       end of xml_tab_line.
types: xtab type table of xml_tab_line.
data: t_xml type xtab,
      size type i,
      rc type i.
lp_sfac = lp_ixml->create_stream_factory( ).
lp_ostr = lp_sfac->create_ostream_itable( table = t_xml ).
lp_enco = lp_ixml->create_encoding( character_set = 'utf-8'
                               byte_order = if_ixml_encoding=>co_none ).
call method lp_ostr->set_encoding( encoding = lp_enco ).
lp_rend = lp_ixml->create_renderer( ostream = lp_ostr
                                    document = lp_xdoc ).
rc = lp_rend->render( ).
*** export to file
size = lp_ostr->get_num_written_raw( ).
call function 'WS_DOWNLOAD'
exporting
    bin_filesize = size
    filename = 'c:\sapxml_test.xml'
    filetype = 'BIN'
tables
    data_tab = t_xml
exceptions
    others = 1.
It is just simple example.

How to run downloaded drivers on Fresh Install of Labview 6.1 on a Mac G4 OS 9

I have just completed a fresh install of Labview 6.1 on an Macintosh G4 running OS9. I can run it and it seems to work just fine. I downloaded some drivers for an oscilloscope (HP 546XX) to run with an HP 54603b. When I installed, I went to open the 'Get Started.VI' I get a freeze and have to force quit out of labview. I am not sure how to resolve this. I am pretty sure that it is independent of the device, since I can open the vi's at least on another computer with no hardware attached. So I guess to boil my situation down. I have 2 questions:
-How do I get a fresh install on a mac G4 OS 9 to run downloaded drivers from the internet
-How do I ensure that I have the hardware configured on
a macintosh to run properly.
I really have little experience with macs so I am not really sure what my options are or what could be the problem so any assistance would be much appreciated.

Hmmm. I wonder if NI-VISA isn't installed correctly on this machine.
When LabVIEW loads a VI that uses a VISA name control on the front panel, it queries VISA for the installed devices. Sometimes this takes a few seconds, but maybe in your case, something has been corrupted and it's hanging.
To try to narrow this down, first run the separate program "VISAConfig". This should list your devices. If this works, this means it's pretty likely that VISA is installed correctly.
Next, run LabVIEW. On an empty front panel, select the "Controls->I/O->VISA Resource Name" and place it on the front panel. When you click on the arrow on this control, you should see a list of your devices. If this works, then that indicates that LabVIEW is successfully talking
to the VISA software.
If both of those succeeded, then we have to take a closer look at this particular instrument driver. Can you drop other VIs (say, Initialize or Close) without hanging?
If either of the first two steps fail, I'd suggest that you reinstall the VISA software. You may want to try the latest version of NI-VISA (from ni.com), but first confirm that it supports LabVIEW 6.1.
I hope this helps.
Brian

UTF-16 in labview 8.5

Similar Messages

Maybe you are looking for