COMMAPI freeing serial port

I have a question about Java commapi and serial ports. In my application I call close on a SerialPort object and associated input/outputstreams. Later on I try to open the port again by calling open on a CommPortIdentifier object and I get a RuntimeException with message "Device busy". If I close the application and start it again, the serial port is opened without problems. My question is should I do something more when closing the port to free it?
Code that tries to close the port:
inStream.close(); //inputstream
outStream.close(); //outputstream
inStream=null;
outStream=null;
port.close(); //SerialPort
port.removeEventListener();
port=null;My platform is Sparc Solaris 10.
Thanking you in advance,
Anguinus

I know this is a very old post, but google came up with it after searching for ttyUSB0 and java, so I thought I'd chip in the solution so that other people arriving here might benefit :)
The trick is to go into javax.comm.properties and add the ttyUSB0 to the list of serial ports:
# Implementation specific driver
driver=com.sun.comm.LinuxDriver
# Paths to server-side serial port devices
serpath0 = /dev/ttyS0
serpath1 = /dev/ttyS1
serpath2 = /dev/ttyUSB0               # <--- added ttyUSB0
# Paths to server-side parallel port devices
parpath0 = /dev/parport0
parpath1 = /dev/parport1Works fine for me

Similar Messages

  • Question of commapi - BlackBox could not find serial port.

    Hi,
    I have installed jdk1.5.0_04 and commapi2.0_win32 at following directory
    c:\Java\netbeans-4.1
    c:\Java\jdk1.5.0_04
    c:\Java\commapi
    C:\Program Files\Java\jre1.5.0_04
    Then I do exactly what installation instruction ask me to do
    Copy win32com.dll to c:\Java\jdk1.5.0_04\bin
    Copy comm.jar to c:\Java\jdk1.5.0_04\lib
    Copy javax.comm.properties to c:\Java\jdk1.5.0_04\lib
    However, when I run BlackBox,BlackBox still gives me a message that
    says "No serial ports found!"
    Can any one help me out, thanks in advance ?
    Daniel

    Many forum posts about installation to java 1.4. Also see:
    http://forum.java.sun.com/thread.jspa?forumID=31&threadID=453195
    and
    http://forum.java.sun.com/thread.jspa?forumID=31&threadID=444673
    I had success on winXP when I installed to the JRE below Program Files/java, no success when installed to c:\j2sdk etc etc.
    The directions for setting the classpath seem bogus; I did not need to specify a class path. Simply went to the commapi/samples/BlackBox folder, then typed java BlackBox. It found a couple of ports. I think this means that (despite the post in the forum to the contrary) that the comm API can deal with the NT hardware abstraction layer (HAL) just fine.
    I'm very new to this, hope this helps.
    chris...

  • CommAPI within servlet returns no known serial ports

    I've seen a number of postings for the use of COMMAPI within a servlet but have not yet seen a solution. Working within JBuilder 6, I'm using JDK 1.3.1_04-b02, Tomcat 3.2 and COMMAPI 2.0 on Windows 2000 Pro. Everything compiles fine and I don't get any exceptions.
    However, CommPortIdentifier.getPortIdentifiers() returns null. I've used the same code standalone with no problems.
    Is the security model getting in the way and do I need to disable or configure the security to allow access from a servlet to the serial ports? Perhaps a parameter within web.xml is required? Maybe an act of God?
    Please help as I'm sure a number of people, in addition to myself, would like to know once and for all how to solve this problem.
    PS. I've already tried unjarring the commapi jar file into the jre/lib directory without success.

    DrClap,
    Thanks for the advice. After some trial and error, I got it working. I came to the following conclusions via some experimentation.
    1. comm.jar is required in the Tomcat lib directory (c:\JBuilder6\jakarta-tomcat-3.2.3\lib) but not the JDK lib directory (c:\jdk1.3.1_04\lib).
    2. Similarly, javax.comm.properties is required in the Tomcat lib directory (c:\JBuilder6\jakarta-tomcat-3.2.3\lib) but not the JDK lib directory (c:\jdk1.3.1_04\lib).
    3. win32com.dll is required in both the JDK bin directory (c:\jdk1.3.1_04\bin) and the Tomcat bin directory (c:\JBuilder6\jakarta-tomcat-3.2.3\bin).
    4. Within JBuilder, library comm.jar must be included in the Tomcat 3.2 configuration. Go to Project->Project Properties...->Webserver tab->Setup...->Paths tab->Classes tab and then add the comm.jar library at the end of the list. Adding it to the global definition of Tomcat 3.2 (Tools->Configure Libraries..., etc) did not seem to achieve the desired result. Perhaps doing so would help with new projects though.
    Perhaps you could shed some light on why this arrangement works and how the JVM resolves the various dependencies?
    Thanks.
    Karl.

  • Buffersize, Outputstream to serial port

    Hello,
    I working with some infosigns and got the following problem.
    The java commapi use a OutputStream to send information to the serial port. The OutputStream seems to have a upper buffersize of 512 bytes, which means that I am sending my message ( of 7702 bytes ) in 'small packets'.
    My infosign make a timeout, because of the time it takes to send the message... I only reache about 2 Kb when it answer.
    this is my code which send the data ....
    private OutputStream os;
    public int[] Transmit(ByteArrayOutputStream b) {
    BufferedOutputStream bos = new BufferedOutputStream(os,8192);
    writeable = true;
    Consumer c = new Consumer(this);
    c.start();
    try {
    bos.write(b.toByteArray());
    bos.flush();
         } catch (IOException e) {
         System.err.println("OutputStream write error: " + e);
    while (c.isAlive()) {
    try{
    this.wait(10);
    }catch(Exception e){}
    return respondTavle;
    I use a thread class to make timeout if the infosign is not responding.
    I�ve got no problem with data of small size, lets say below 2 kb.
    My cuestion is ... Is it possible to raise the buffersize ?
    In another application (windows ) the portmonitor see this :
    send 7702: 55 AA 02 1E 0E 40 93 66 0C 31 2E 53 45 4B ......
    response : 55 AA 02 00 00 A1 00 00 5E !!! Yes data recieved....
    when I launch the java application it seems like this :
    send 512: 55 AA 03 1E 0E....
    send 512: 00 00 00 00 00 00....
    send 512: 00 00 00 00 00 00 ....
    response : 55 AA 02 00 00 A1 00 00 5E !!! AARRRGGG I�m not finished.
    send 512: 00 00 00 00 00 00...
    send 512: 00 00 00 00 00 00....
    as you see it is divided in packets of 512 bytes....

    And why are you using a Buffered stream?

  • Connect a PIC/MCU micro controller to serial port of phone

    Hello,
    I am relatively new to j2me programming and i would lke to ask if it's possible to connect a MCU to the serial port of the phone and receive streamng data while the MIDlet is on?
    If so how can this be done> Does it work the same way a serial connection? I connect the MCU to the USB pins then to the mobile phone.
    Does anyone who have worked with this care to share their valuable experience? Thanks in advance.

    Hi, i checked with the helpdesk from motorola and they replied that i require a license to access the proprietary interface (please refer to the reply below). I'm thinking ofusing Sony Ericsson k610i since it's JP-7. However, I wonder if they have similar issues with it.
    It seems that since we are to interfacing with a PC, the allocation of a virtual port might be a problem, that'smy main concern.
    FAQ found in motorola website:
    We'd like to connect a RS232 device to a RAZR V3 phone. From a Java API perspective this is possible via the CommAPI.
    We have succesfully tested to connect the RAZR V3 Mini-USB with a PC via a USB-cable - and we were able to transmit data from the RAZR V3 to the PC (Hyper Terminal) and vice versa.
    Which technology is needed in the RS232 device (no PC - just a stand alone RS232 device) to communicate to the RAZR V3 via the Mini-USB?
    Answer
    We do not normally support the use of non-PC RS232 connections to current Motorola handsets. The only serial connection supported is serial-over-USB, where the handset is connected to a USB port on a PC, and the PC operating system assigns a virtual COM port to the USB connection for this purpose. Microsoft Windows is normally needed to meet this requirement.
    Although RS232 functionality exists within the handsets, it is a Motorola proprietary interface only available to firms who licence the technology from us. Motorola currently licenses the CE Bus technology to selected 3rd party companies interested in building accessories for our PCS devices. Please contact Gene Eggleston ([email protected]) or telephone 847-523-4976 (USA) for information on the license and business arrangement. As a licensee you will receive a specification that details the access and use of Motorola's CE Bus.

  • Accessing serial port on Arm platform

    I need to read and write on the serial ports of an ARM platform with a Java application, running a cross-compiled JVM.
    I considered both solutions java COMMAPI and JNI, but the problem is the same: I haven't library to support them: libLinuxSerialParallel.so, to support COMMAPI, or libnativelib.so, to implement native methods for JNI.
    How can I have this library for my ARM architecture? Is it possible to cross-compile sources for it?
    Thanks in advance.
    regards.

    Hello,
    I have a igep boar with arm core.
    I am trying to access to serial port through java.
    I am using rxtx (gnu.io) http://rxtx.qbang.org.
    I dowloaded the api for arm architecture (http://rxtx.qbang.org/ToyBox/2.1-7-build1/Linux/glibc-2.3.5/), but there is a problem with dependencies with glib.
    This is the error when i try to call from java:
    java.lang.UnsatisfiedLinkError: /home/jdoe/equinox-SDK-3.5.2/plugins/configuration/org.eclipse.osgi/bundles/2/1/.cp/librxtxSerial.so: /lib/vfp/libpthread.so.0: version `GLIBC_2.0' not found (required by /home/jdoe/equinox-SDK-3.5.2/plugins/configuration/org.eclipse.osgi/bundles/2/1/.cp/librxtxSerial.so) thrown while loading gnu.io.RXTXCommDriver
    I tested the librxtxSerial.so:
    jdoe@ubuntu:~$ ldd librxtxSerial.so
    ./librxtxSerial.so: /lib/vfp/libpthread.so.0: version `GLIBC_2.0' not found (required by ./librxtxSerial.so)
    ./librxtxSerial.so: /lib/vfp/libc.so.6: version `GLIBC_2.1.3' not found (required by ./librxtxSerial.so)
    ./librxtxSerial.so: /lib/vfp/libc.so.6: version `GLIBC_2.1' not found (required by ./librxtxSerial.so)
    ./librxtxSerial.so: /lib/vfp/libc.so.6: version `GLIBC_2.0' not found (required by ./librxtxSerial.so)
    libpthread.so.0 => /lib/vfp/libpthread.so.0 (0x40022000)
    libc.so.6 => /lib/vfp/libc.so.6 (0x40041000)
    /lib/ld-linux.so.3 (0x2a000000)
    And this is my glic version:
    jdoe@ubuntu:~$ ls -al /lib/libc*
    -rwxr-xr-x 1 root root 1201672 2009-04-09 18:02 /lib/libc-2.9.so
    lrwxrwxrwx 1 root root 14 2010-07-01 16:52 /lib/libcap.so.1 -> libcap.so.1.10
    -rw-r--r-- 1 root root 13984 2008-11-14 02:47 /lib/libcap.so.1.10
    lrwxrwxrwx 1 root root 14 2010-06-16 17:21 /lib/libcap.so.2 -> libcap.so.2.11
    -rw-r--r-- 1 root root 13800 2008-11-17 06:14 /lib/libcap.so.2.11
    -rw-r--r-- 1 root root 181816 2009-04-09 18:02 /lib/libcidn-2.9.so
    lrwxrwxrwx 1 root root 14 2010-06-16 17:21 /lib/libcidn.so.1 -> libcidn-2.9.so
    lrwxrwxrwx 1 root root 17 2010-06-16 17:21 /lib/libcom_err.so.2 -> libcom_err.so.2.1
    -rw-r--r-- 1 root root 9648 2009-02-12 16:55 /lib/libcom_err.so.2.1
    -rw-r--r-- 1 root root 38400 2009-04-09 18:02 /lib/libcrypt-2.9.so
    -rw-r--r-- 1 root root 1210776 2009-04-04 03:06 /lib/libcrypto.so.0.9.8
    lrwxrwxrwx 1 root root 15 2010-06-16 17:21 /lib/libcrypt.so.1 -> libcrypt-2.9.so
    lrwxrwxrwx 1 root root 11 2010-06-16 17:21 /lib/libc.so.6 -> libc-2.9.so
    What should I do?

  • Serial Port - Linux OK, Windows No Way

    I have been trying to write to my serial port with hardware flowcontrol under windows XP all weekend. With no flow control all is well. I was about to give up on my serial port program when I decided to try my sample app under Linux Redaht 8 using the RXTX commapi. To my surprise, the code that would not work under windows worked just fine under Linux! I'm happy and confused at the same time. Here's the code snippet that processes the serial events. Does anyone have any insight into why this simple write with flow control would not work under windows XP? I have LED's connected to the serial lines and can see the CTS line doing what it's supposed to. I have administrative rights on XP. A few observations that probably mean nothing. Windows XP repors outputbuffersize=0, yet Linux returns a value. The API notes say it is advisory and may not report a value so I don't think it means anything.
    ANY help you have would be greatly appreciated.
    Thank You!
    public void serialEvent(SerialPortEvent event) {
            long timein,timeout;
              switch(event.getEventType()) {
                   case SerialPortEvent.BI:
                   case SerialPortEvent.OE:
                   case SerialPortEvent.FE:
                   case SerialPortEvent.PE:
                   case SerialPortEvent.CD:
                   case SerialPortEvent.CTS:
                        if(boolDataforWriting & event.getNewValue()){
                                  //Write data
                             timein=System.currentTimeMillis();
                             try {
    // ########## LINE THAT PRODUCES ERROR IN WINDOWS BUT NOT LINUX ###########
                                                    streamSerialOut.write(strDataForWriting.getBytes());
                             } catch (IOException e) {
                                  e.printStackTrace(); 
                             }//end catch
                             System.out.println("-->Done writing " +strDataForWriting.length()+" Bytes. Resetting str");
                                   timeout=System.currentTimeMillis();
                                   System.out.println("--->Time to write="+ (timeout-timein) + " ms");
                             //reset flags for next write operation
                             strDataForWriting="";
                             boolDataforWriting=false;
                        }//end if
                   case SerialPortEvent.DSR:
                   case SerialPortEvent.RI:
                   case SerialPortEvent.OUTPUT_BUFFER_EMPTY:
                        break;
                   case SerialPortEvent.DATA_AVAILABLE:
                        try {
                                       byte[] readBuffer = new byte[100]; //create byte array
                                      char c;
                                      int numBytes=0;
                            while (streamSerialIn.available() > 0) {
                                     numBytes = streamSerialIn.read(readBuffer);
                                   } catch (IOException e) {}
                             break;
                                    String strtemp=(new String(readBuffer)).trim();
    }//end serialevent

    I've had this very same problem and there is a solution.
    Interestiingly I found that the same code worked on Win98 but not WinXP.
    The problem seems to lie in the JavaComm implementation. I'm guessing but your probably running with the javacomm20-win32.zip that you downloaded from Sun. I've also tried using the implementation javacom that IBM provide with there download of java1.3 and it has the same problem. So you should have a look at http://www.rxtx.org I've had success running this implementation on WinXP and Linux. To save you some time compiling there is a reasonably recent binary version at this location http://www.jcontrol.org/html/en/download.html (scroll to the bottom of the page)

  • Big Problems with the Serial Port

    I'm Spanish and my English is not very good, I'm sorry but I need your help.
    I want to connect two computers (my desktop and my handbook) with the serial port (COM2 in both sides).
    I have the cable.
    I have installed JBuilder 7 in both computers.
    I have installed "commapi"
    I'm running SimpleWrite.java (the example from Sun) in one of them and SimpleRead.java in the other.
    I don't get in any moment receive any data.
    I execute first SimpleRead and I can see what this process is waiting something. After, I execute SimpleWrite (many times), this process star and stop correctly but never the first aplication receives nothing.
    I am trying for four days, I am desespereted.
    I need your help is very important to me. I don't understand what is happening!!!!. This is my e-mail: [email protected]
    Thank you very much.
    NOTE: my handbook has just one serial port, before had a winmodem but it was eliminated.

    hi,
    when your notebook has only one port, how do u know that this port is COM2? I think u gave a wrong parameter for the SimpleReader or SimpleWriter so one send data to a port (say COM1) but the other receives data from another port (say COM2).
    regards,
    eedych

  • Unable to capture data from Serial port using LVRT2010 in single core pentium 4 machine

    I am using application written in Labview using windows Labview
    Runtime environment 2010. Application creates a tunnel to intercept data from
    Serial port.
    My problem is, Currently, I am using single core Pentium
    processor. When I am trying to intercept the data between COM1 and COM7 (COM 7
    is a virtual port) it is not able to capture data.
    When I am running Labview RT environment using dual core
    processor machine it is running normally. I wonder whether it could be the compatibility issues with
    single core Pentium processor.

    Hi Magnetica
    Are both of the machines running the same runtime engine,
    drivers ect?
    Have you had RT applications running on this
    machine before?
    Is the development computer a 64bit machine?
    The processor is a supported model (See link below).
    http://zone.ni.com/devzone/cda/tut/p/id/8239
    Regards
    Robert
    National Instruments UK & Ireland

  • Problem on WinXP / Labview 6.1 with VISA (serial port)

    There is a problem on WinXP / Labview 6.1 with VISA which i use to poll the state lines of the serial port. The only functions that i use are "VISA Open", "Find Resource", line state properties and "VISA close".
    On my own machine (WinME) it works fine as a standalone application (with runtime engine in the same direction), even if i rename the Labview directory so that Labview is not found.
    From my VXIpnp directory i deleted all but these files:
    directory "Win95",
    subdirectory "Bin" containing "NiViAsrl.dll",
    subdirectory "NIvisa" containing "visaconf.dll".
    When shipping this to WinXP (and copying "VXIpnp" to the root directory), the serial port was not found, so i renamed the direction "Win95" to "
    WinNT", but this did not work also.
    I installed the VISA server, although it seems not to be required -- no result.
    Final question:
    What must i do for distributing the program as a standalone application for all windows platforms?

    Hey Joachim,
    In order to create an installer that includes the VISA Run-time engine for serial IO you will have to purchase LabVIEW 7.x. See screen shot. This packages a small compact version of the run-time that can only be used for serial, but it takes up much less space. The installer that I created has my application, the LV Run-time, and the VISA run-time and it is about 26 MB.
    That is much smaller than if I had to include the 32 MB LV 7.1 run-time and the 14 MB VISA run-time separately. It would have been even smaller if I would have uncheck some of the items that I wasn't using.
    -Josh
    Attachments:
    advanced.JPG ‏31 KB

  • Using a PS/2 keyboard on a Sparc workstation through the serial port

    We have recently migrated an application that used to run on a PC, to now run on a Sparc Workstation. This is a SunBlade 1500, running Solaris 8. The application is running in a dedicated console which has a fitted keyboard and trackerball that have PS/2 connectors and cannot be changed.
    We need a way of connecting the PS/2 keyboards to the serial ports of the Sparc workstation. We already have a piece of software that will read ascii values from the serial port so we definately want to go through the serial ports.
    Can someone please suggest what converters will be required to get the output of the keyboard and trackerball as ascii input to the serial port.

    Actually, that's not a bit perverse, at all.
    Jonathan's suggestion is a standard method of connecting to a server.
    (null cable between the computer serial ports)
    ... see the Solaris man pages.
    man tip
    TeraTerm and Hyperterminal are customarily used on a PC running some dialect of Windows.
    The 'tip' command is all that's necessary between Solaris systems.
    PS/2 is not a serial connection, but is a keyboard/mouse interface 'invented' by IBM when they offered their XT-class PS/2 line of desktop systems, back in the 1980's.
    I found this next link by using Google:
    http://members.chello.at/theodor.lauppert/computer/ps2/
    The smaller DIN ports were more compact than the AT-class keyboard ports and the mouse moved from a serial port to a dedicated mouse port.
    Serial communication devices are not keyboards, per se,
    and keyboards are not serial communication devices.
    You need other hardware in between to translate what the human being sends, and another computer is a common method to accomplish that translation.
    Having said all that ...
    Since you cannot change the dedicated console hardware,
    I suggest you go to the manufacturer of that console equipment
    and have them suggest some sort of serial-to-serial interface lash-up.

  • Using a serial port under j9.. How?

    I am trying out j9 on an ipaq. I am trying to get javax.comm to work.
    When I call CommPortIdentifier.getIdentifiers ();
    I get java.lang.string.NoSuchMethodError: java/lang/String.<init>([BIII)V
    It would appear that the javax.comm package was implemented using a now deprecated String method, and that IBM has chosen not to implement deprecated methods in it's j9 vm (I get the same issue trying to run swing.)
    One would think that what is needed is an updated javax.comm package. However, there doesn't appear to be a javax.comm package on Sun's site, let alone an updated one. Whats going on here? Can someone give me an idea of how Sun and/or the JCP thinks about developers who want to use serial ports?
    Is there a workaround? A different way of talking to a serial port? Or should I abandon j9? I should add that I got my software running just fine on nsi.com's creme vm (javax.comm and swing too) and it worked without any hassles. It even understands jar files (is there a reason why IBM insists on having a link file?). However, the reason I persevered was that a) j9 is cheaper and more importantly b) nsi.com don't seem terribly keen on actually selling their product. I have lots of references to them selling their vm in bundles of 40 ($1000) which is a bit ouchy but hey I'm not paying for it. But, you'd think the nsi.com people would actually confirm this on their site?
    So.. can it be done? And why, in the world of embedded systems (my field) and now lots of phones and pdas, is so little attention given to the humble serial port? It doesn't matter how fancy the protocol is, underneath it all is a UART. grumble
    -Russel

    Hi Russel,
    I will probably soon be in the position you are in trying to get this to work. I found the following page which offers some promise.
    http://www.intrinsyc.com/support/I-Linux/405-cube/misc/smf_serial_port_access_example.htm
    Mike

  • I have problem with delay in serial port

    I have problem with serial port. I have connected two computers by serial port and I need to create program in Labview for transfer strings using start bits and stop bits. My problem is that my program is working quite well ...when I press start bit it starts to concatenate strings and if i press stop bits it stops...this is the purpose of this program...but problem is that it working only with delay...and need that this program dont need delay, because it can only concatenating data depends on delay from start bit....I wana solved problem with delay...I dont want using delay process in my program, but allways when I try to delete this delay it stop works correct
    here is my program

    Ok this should be simple - if I understand you correctly.
    You have the VISA session initialized with read termination character enabled.  So reading the number of bytes at port is NOT the correct way to read from the port.  Set the read number of bytes to something large (say 4096) and the read will return as soon as a termination character is received (or timeout).
    You'll need to make sure the sending device is configured to send termination character on writes (you can set that with a VISA property node)  and that you are sending the correct termination character.  The default is 0x0A (newline).
    Jeff

  • Open and configure serial port

    Hi,
    when i use the function configured serial port, i can work with it.
    for which case i need the function open port. do i need both an in which order?
    thanks florian 

    Hi florian
    check the help examples
    Attached png file shows  the example.
    chow
    xseadog
    Attachments:
    serial.PNG ‏39 KB

  • How do I process serial port strings as bits

    In response to my commands, my instrument is sending bytes to my serial
    port. In one instance, 2 bytes are received. I want to treat these 2 bytes
    as a group of 16 bits.
    The VISA and Compatibility Serial functions return these bytes from the
    serial port to Labview clearly labelled a "string".
    Everything I can find in the way of Labview functions and .vis don't want to
    do bit twiddling, bit swapping, and bit dropping, with "string" data.
    I thought "hex string to number" could be used here, but I can't find a way.
    The 2 Bytes in question can be represented as hex, but the data are not the
    ASCII codes for the hex representation of a binary number, they are the
    binary number. This "hex string to number" seems to want ASCII c
    odes.
    You can feed a hex number typed into a "control" box wired into "hex string
    to number" and you get a meaningful number. You can feed the 2 bytes from
    the serial port into an "indicator" set to read in hex and you get a hex
    number that is a correct representation. But that is Labview handing them
    around to itself. I need to get my "hands" on them.
    I can't feed those same bytes that show up as a correct hex representation
    in an indicator into the "hex string to number" or anything else, so far,
    and get a number that is useful for further processing.
    I thought "variant to data", but I can't find enough reference material to
    understand how to use it. A boolean array seems like a bit of a weird
    approach, so I thought I'd ask before I looked into that.
    I'm used to dealing directly with binary numbers on the processor stack, I
    call them whatever I want, and turn them into anything I feel like.
    I'm sure I'm staring the solution in the face, but I can't find any way to
    persuade
    Labview to treat this "string" data as 16 bits.
    I've got the 16 bits, which is better than not having them, but I don't have
    much hair left.

    duh, well I finally discovered the "Unflatten from String" function. A guy
    just feeds in the bytes he's collected from his serial port that Labview
    thinks are a "string", and out come lovely little unsigned 16 bit numbers,
    or whatever other type of number he wants to turn the bytes into. And there
    are great little bit twiddlers available after that, like "swap bytes", and
    you can mask out bits with the logic operators, why this is fun. There's
    nothing like being a moron...... fly me to the moon...................
    "David Lewis" wrote in message
    news:[email protected]..
    > The two bytes would come from a serial port read.vi in Labview, classed as
    a
    > string. For instance, D3 and 02. The output wou
    ld swap the two bytes,
    i.e.
    > to 02 and D3, consider the two swapped bytes as 16 bits, drop the six most
    > significant bits, and output the ten bits that are left as an integer
    > classed by Labview as some kind of number, not a string.
    >
    > Your example StringToBits_Converter.vi I found on the ni.com site
    > unfortunately gives an error message and refuses to open on my system
    saying
    > it comes from a newer version of Labview 6 than I am running. Mine says
    > 6.0.1b3. Thank you very much anyway.
    >
    > "FightOnSCTrojan" wrote in message
    > news:[email protected]..
    > > In another words, you want to create a VI in which the input is 2
    > > strings (i.e. AB) and the output is the converted array bits (e.g.
    > > 1010101010101010)?
    >
    >

Maybe you are looking for

  • How do you open Garageband for iPad files with Garageband?

    I was led to believe that Garageband could open up Garageband For iPad files, but not vice versa. However when a friend sent me his Garageband For iPad file, and I tried to open it, a "compatibility updater" started running then stopped halfway throu

  • Simplified Chinese format problem in File-File Scenario.

    Hi, I have configured File(FTP) - > File(FTP) Scenario. I am expecting a Chinese File from Source system which is AS400. I am using the file encoding format UTF-8 while the chinese characters are in GB2312 format. My sender file adapter picks up the

  • Restart successful Message in PI

    Hi All, I have a scenario where we created a BPM which calles three RFC's in sequence on ECC side one by one. The response of first RFC is the request for Second RFC. Now we have a situtaion where our FA says if the Third RFC call is failed, she shou

  • Transporter name in partner determination in vl01n

    Hello, I am facing one problem so required help in SD -abap side in t-code VL01n . if the freight is beared by company and payment is made by A/c, in that case users need to capture the Transporter name while making the Delivery in goto option ->part

  • OSB Async Reponse

    Hi , We have a requirement where BPEL is Async Process .OSB calls async BPEL process which works fine for request line.Where as for response from the Async BPEL is not able to catch in OSB Proxy service. we went for Async BPEL since at first instant