Adding Serial Ports
Solaris is new to me and I am mostly familar with SCO. I had quite an experience trying to add a serial (Siig) port to Solaris. I could kind of see what was going on and was able to define the serial port via the boot procedure (port=3e8-3ef, IRQ=5) but never saw any new devices (nodes) being added for the port. I looked in /dev and saw ttya and ttyb and saw how they were setup so I went into /devices/isa and added my own nodes (mknod) and now everything seems to be okay...is there a standard way to do this?
Thanks,
Tom Carter ([email protected])
I just ran into this problem (but with 8.5 not 9). It should be on one of the CDs. I don't know how the 2009 CDs are set up, but with 8.5 I put the main CD in that included everything on it (drivers etc). Then when this error came up, I browsed for the location. I went into drive(whatever drive letter is your cd drive) and looked in the signal express folder. In there you will find the file nidist.id. This is the file you need
CLA, LabVIEW Versions 2010-2013
Similar Messages
-
How do I connect two components (A LCD Display and a Battery Charger) to a single serial port on a SBRIO 9642?
Depending on the nature of your two serial devices, you may be able to use a serial port combiner or switch like these devices from B&B electronics:
Serial Port Combiners: Good for intermittent data sources, but Tx data from the host is broadcast to both devices, which may cause undesired behavior in your device if the devices share any common or similar commands.
Serial Port Switches: More flexible for communicating with multiple devices because the Tx data is sent only to the desired device. The downside is any LabVIEW instrument driver you may be using will have to be modified to account for the extra "addressing" commands the switch uses to determine which device you want to talk to.
This is the only way I know to communicate with two devices using only one serial port. One downside of both approaches is they limit the bandwidth available because only one device can communicate with the Single-Board RIO at any time. If one device communicates often or continuously and the other is an intermittent device, you may have trouble getting the intermittent data through the switch or combiner because the first device to communicate gains access and blocks the other port until the communication is complete.
If you need a dedicated serial port for each device, you have a few of options for adding ports to Single-Board RIO, depending on your needs for ease of integration, size, and cost.
Easiest option, use an Ethernet based RS-232 device. Downside, extra cost of an ethernet hub and ENET-232 device, but it does offer native VISA support from Single-Board RIO.
RS-232 C series module: The NI 9870E module adds 4 RS232 ports to Single-Board RIO. Downside, added cost and size of Single-Board RIO system, and the serial ports are not supported through VISA, so an RT interface layer and driver must be written in LabVIEW FPGA.
Most difficult work, but lowest cost option, Emulate RS232 port in LabVIEW FPGA: Depending on your devices, you may need to add an RS232 transceiver to the front end of your FPGA DIO lines to make this option work, but many devices can work with an "RS232 TTL" level signals. This would be very low cost, but again this option does not provide VISA API support, so any instrument drivers you may have would need to be ported to your custom FPGA-232 driver API.
Hopefully this clearly lays out your options and tradeoffs for adding serial ports to Single-Board RIO.
Cheers,
Spex
National Instruments
To the pessimist, the glass is half empty; to the optimist, the glass is half full; to the engineer, the glass is twice as big as it needs to be... -
Inconsistent prob when adding listeners to serial ports for sending AT cmds
I have an app that sends and receives SMSs from two different cell phone carriers (lets say verizon and sprint by example).
For that matter i have two cell phones, exactly the same model, one from each carrier, connected to the PC serial ports, COM, COM6 and COM7 being aware that they are available.
-The application communicats with the phones through the a serial communication API and sending AT commands.
-The application can send messages correctly from both phones within the same transaction, this is, i click in send message and the message is sent from both phones.
The problem is when receiving, getting the SMS received by the phones:
-When i have ONE phone connected to the PC it work properly for both phones.
-When i have BOTH phones connected, only Carrier1 phone receives properly.
When checking, i just find out that the problem rises when i try to add the listeners (see code comments below).
When both phones connected there seems to be a problem that i cant figure out, and may be its a conceptual misunderstanding from me.
I attach the code if you can help me,
thank you,
fernando
// class fields
private static String PORT_CARRIER1;
private static String PORT_CARRIER2;
private static CommPortIdentifier portId;
private static Enumeration portsList;
private static SerialPort carrier1SP;
private static SerialPort carrier2SP;
private static InputStream carrier1_input;
private static InputStream carrier2_input;
private static OutputStream carrier1_output;
private static OutputStream carrier2_output;
// ... all the code below is from the app method where everything is initializated
portsList = CommPortIdentifier.getPortIdentifiers();
while(portsList.hasMoreElements()){
portId = (CommPortIdentifier) portsList.nextElement();
if(portId.getPortType() == CommPortIdentifier.PORT_SERIAL){
// try to open ports
try{
if(portId.getName().equals(PORT_CARRIER1))
carrier1SP = (SerialPort) portId.open("SMS", 5000);
else if(portId.getName().equals(PORT_CARRIER2))
carrier2SP = (SerialPort) portId.open("SMS", 5000);
else System.out.println("Error " + portId.getName());
}catch(PortInUseException piue){
System.out.println("Exception while opening serial ports: "+piue.getMessage());
continue;
// try to open input streams
try{
if(portId.getName().equals(PORT_CARRIER1))
carrier1_input = carrier1SP.getInputStream();
else if(portId.getName().equals(PORT_CARRIER2))
carrier2_input = carrier2SP.getInputStream();
}catch(IOException ioe){
System.out.println("Exception while opening input streams: "+ioe.getMessage());
continue;
// try to open output streams
try{
if(portId.getName().equals(PORT_CARRIER1))
carrier1_output = carrier1SP.getOutputStream();
else if(portId.getName().equals(PORT_CARRIER2))
carrier2_output = carrier2SP.getOutputStream();
}catch(IOException ioe){
System.out.println("Exception while opening output streams: "+ioe.getMessage());
continue;
// adding listeners
try{
if(portId.getName().equals(PORT_CARRIER1))
carrier1SP.addEventListener(new ListenerPuerto(this, carrier1_input, "CARRIER1"));
else if(portId.getName().equals(PORT_CARRIER2))
carrier2SP.addEventListener(new ListenerPuerto(this, carrier2_input, "CARRIER2"));
}catch(TooManyListenersException tmle){
System.out.println("Error while adding listeners: " + tmle.getMessage());
continue;
// Adding specific event to listeners
if(portId.getName().equals(PORT_CARRIER1))
carrier1SP.notifyOnDataAvailable(true);
else if(portId.getName().equals(PORT_CARRIER2))
carrier2SP.notifyOnDataAvailable(true);
// Setting params to serial communication
try{
if(portId.getName().equals(PORT_CARRIER1)){
carrier1SP.setSerialPortParams(9600, SerialPort.DATABITS_8, SerialPort.STOPBITS_1, SerialPort.PARITY_NONE);
carrier1 = true;
}else if(portId.getName().equals(PORT_CARRIER2)){
carrier2SP.setSerialPortParams(9600, SerialPort.DATABITS_8, SerialPort.STOPBITS_1, SerialPort.PARITY_NONE);
carrier2 = true;
}catch(UnsupportedCommOperationException uscoe){
System.out.println("Error while setting params for serial communication: " + uscoe.getMessage());
continue;
// ... nothing else important ...thanks in advanceThinking of a java application as its what I am most
comfortable with, but also thinking of having an
apache server, and using jsp pages or servlets...
because I hate formatting things in a java frame..
have never quite mastered that! Any thoughts on what
I should use?I'd prefer a Swing GUI for a maximum of controls. If you have any problems regarding layout, you can post concrete questions here (or even better: the Swing forum).
And my main stumbling block would be how do I send
signals to the green light from the computer? How do
I get signals from the light beams to the computer?
How do I use a serial port (for eg) from a java app.There's an additional library for serial I/O, it's named javax.comm ... should be downloadable somewhere on the java.sun.com site. -
I need to add a single 9-pin serial (COM) port to hook up a device that has a serial connector. The MB has an 16550A electrical connection but no serial port. What should I be looking for? Most of what I see online are PCI serial cards or ISA-slotted ones. I assume that if there's an electrical connection there's no need for a PCI board. Thanks.
Quote from: Built2Last on 14-May-06, 10:16:06
genegold, I just picked up the same board for my HTPC and it came with the com bracket in the box along with a audio out bracket & tv out bracket. Maybe you should check with your supplier to see if you got short changed.
Wow, this is getting better. Mine came from ZipZoomFly and doesn't have one, but does have the others you mention. The serial header is listed as optional in the manual, but with other parts that means if the board has the connection then there should be a bracket. I'll have to call MSI Monday and ask (and look all around just to see if it dropped somewhere). Thanks! -
Java ME 8 Permission check failed when opening a serial port
I have a larger Jave ME8.1 application that was going well until I tried to add one last piece, reading and writing data from a serial port. This was left to last because it is trivial, at least in most programming languages. The is IDE NetBeans 8.0.2 running on a Windows 7 PC. The platform is a Raspberry Pi B or B+ (I have tried both) with the most current Raspbian (12/24/2014 I believe). To simplify the process I created a new app with just the open and close code and this generates the same error I am experiencing in the larger application. The program is as follows:
package javamecomapp;
import java.io.IOException;
import java.io.InputStream;
import java.io.OutputStream;
import java.util.logging.Level;
import java.util.logging.Logger;
import javax.microedition.io.CommConnection;
import javax.microedition.io.Connector;
import javax.microedition.midlet.MIDlet;
* @author ****
public class JavaMEcomApp extends MIDlet {
static int BAUD_RATE = 38400;
static String SERIAL_DEVICE = "ttyAMA0";
static CommConnection commConnection = null;
static OutputStream os = null;
static InputStream is = null;
static String connectorString;
private int rtnValue = -1;
@Override
public void startApp() {
java.lang.System.out.println("Opening comm port.");
try {
rtnValue = JavaMEcomApp.openComm();
} catch (IOException ex) {
Logger.getLogger(JavaMEcomApp.class.getName()).log(Level.SEVERE, null, ex);
@Override
public void destroyApp(boolean unconditional) {
java.lang.System.out.println("Closing comm port.");
try {
rtnValue = JavaMEcomApp.closeComm();
} catch (IOException ex) {
Logger.getLogger(JavaMEcomApp.class.getName()).log(Level.SEVERE, null, ex);
private static int openComm()throws IOException {
java.lang.System.out.println("Opening comm port.");
connectorString = "comm:" + SERIAL_DEVICE + ";baudrate=" + BAUD_RATE;
commConnection = (CommConnection)Connector.open(connectorString);
is = commConnection.openInputStream();
os = commConnection.openOutputStream();
return 0;
private static int closeComm()throws IOException {
java.lang.System.out.println("Closing comm port.");
is.close();
os.close();
commConnection.close();
return 0;
If I comment out the JavaMEcomApp.openComm and closeComm lines it runs fine. When they are included, the following error is dumped to the Raspberry Pi terminal:
Opening comm port.
Opening comm port.
[CRITICAL] [SECURITY] iso=2:Permission check failed: javax.microedition.io.CommProtocolPermission "comm:ttyAMA0;baudrate=38400" ""
TRACE: <at java.security.AccessControlException: >, startApp threw an Exception
java.security.AccessControlException:
- com/oracle/meep/security/AccessControllerInternal.checkPermission(), bci=118
- java/security/AccessController.checkPermission(), bci=1
- com/sun/midp/io/j2me/comm/Protocol.checkForPermission(), bci=16
- com/sun/midp/io/j2me/comm/Protocol.openPrim(), bci=31
- javax/microedition/io/Connector.open(), bci=77
- javax/microedition/io/Connector.open(), bci=6
- javax/microedition/io/Connector.open(), bci=3
- javamecomapp/JavaMEcomApp.openComm(), bci=46
- javamecomapp/JavaMEcomApp.startApp(), bci=9
- javax/microedition/midlet/MIDletTunnelImpl.callStartApp(), bci=1
- com/sun/midp/midlet/MIDletPeer.startApp(), bci=5
- com/sun/midp/midlet/MIDletStateHandler.startSuite(), bci=246
- com/sun/midp/main/AbstractMIDletSuiteLoader.startSuite(), bci=38
- com/sun/midp/main/CldcMIDletSuiteLoader.startSuite(), bci=5
- com/sun/midp/main/AbstractMIDletSuiteLoader.runMIDletSuite(), bci=130
- com/sun/midp/main/AppIsolateMIDletSuiteLoader.main(), bci=26
java.security.AccessControlException:
- com/oracle/meep/security/AccessControllerInternal.checkPermission(), bci=118
- java/security/AccessController.checkPermission(), bci=1
- com/sun/midp/io/j2me/comm/Protocol.checkForPermission(), bci=16
- com/sun/midp/io/j2me/comm/Protocol.openPrim(), bci=31
- javax/microedition/io/Connector.open(), bci=77
- javax/microedition/io/Connector.open(), bci=6
- javax/microedition/io/Connector.open(), bci=3
- javamecomapp/JavaMEcomApp.openComm(), bci=46
- javamecomapp/JavaMEcomApp.startApp(), bci=9
- javax/microedition/midlet/MIDletTunnelImpl.callStartApp(), bci=1
- com/sun/midp/midlet/MIDletPeer.startApp(), bci=5
- com/sun/midp/midlet/MIDletStateHandler.startSuite(), bci=246
- com/sun/midp/main/AbstractMIDletSuiteLoader.startSuite(), bci=38
- com/sun/midp/main/CldcMIDletSuiteLoader.startSuite(), bci=5
- com/sun/midp/main/AbstractMIDletSuiteLoader.runMIDletSuite(), bci=130
- com/sun/midp/main/AppIsolateMIDletSuiteLoader.main(), bci=26
Closing comm port.
Closing comm port.
TRACE: <at java.lang.NullPointerException>, destroyApp threw an Exception
java.lang.NullPointerException
- javamecomapp/JavaMEcomApp.closeComm(), bci=11
- javamecomapp/JavaMEcomApp.destroyApp(), bci=9
- javax/microedition/midlet/MIDletTunnelImpl.callDestroyApp(), bci=2
- com/sun/midp/midlet/MIDletPeer.destroyApp(), bci=6
- com/sun/midp/midlet/MIDletStateHandler.startSuite(), bci=376
- com/sun/midp/main/AbstractMIDletSuiteLoader.startSuite(), bci=38
- com/sun/midp/main/CldcMIDletSuiteLoader.startSuite(), bci=5
- com/sun/midp/main/AbstractMIDletSuiteLoader.runMIDletSuite(), bci=130
- com/sun/midp/main/AppIsolateMIDletSuiteLoader.main(), bci=26
java.lang.NullPointerException
- javamecomapp/JavaMEcomApp.closeComm(), bci=11
- javamecomapp/JavaMEcomApp.destroyApp(), bci=9
- javax/microedition/midlet/MIDletTunnelImpl.callDestroyApp(), bci=2
- com/sun/midp/midlet/MIDletPeer.destroyApp(), bci=6
- com/sun/midp/midlet/MIDletStateHandler.startSuite(), bci=376
- com/sun/midp/main/AbstractMIDletSuiteLoader.startSuite(), bci=38
- com/sun/midp/main/CldcMIDletSuiteLoader.startSuite(), bci=5
- com/sun/midp/main/AbstractMIDletSuiteLoader.runMIDletSuite(), bci=130
com/sun/midp/main/AppIsolateMIDletSuiteLoader.main(), bci=26
I have tried this with three different serial ports, /dev/ttyAMA0 (yes I did disable the OS from using it), an arduino board /dev/ttyACM0, and a USB to RS485 adaptor /dev/ttyUSB0. All of these ports could be connected and use normally with both a C program and terminal program in the Pi. The API Permissions were set in the project properties / Application Descriptor / API Permissions to jdk.dio.DeviceMgmtPermission "/dev/ttyAMA0". This of course was changed as I tested different devices.
I found a reference suggesting adding the line "authentication.provider = com.oracle.meep.security.NullAuthenticationProvider" to the end of the jwc_properties.ini file. This had no effect. I found references that during development in eclipse and NetBeans, the app is already elevated to the top level so this should not be an issue until deployment. This does not appear to be the case.
I am out of time and need a solution quickly. Any suggestions are welcome.Terrence,
Thank you for responding and confirming the issues I'm having with static addressing. As far as the example above, I do have the standard LEDs working correctly, however, the example I'm referring to above is from the JavaME samples using the GPIO Port for the LEDS, according to the Device I/O Preconfigured List you referenced:
GPIO Ports
The following GPIO ports are preconfigured.
Devicel ID
Device Name
Mapped
Configuration
8
LEDS
PTB22
PTE26
PTB21
direction = 1 (Output only)
initValue = 0
GPIOPins:
controllerNumber = 1
pinNumber = 22
mode = 4 (Push-pull mode)
controllerNumber = 4
pinNumber = 26
mode = 4 (Push-pull mode)
controllerNumber = 1
pinNumber = 21
mode = 4 (Push-pull mode)
So is the assumption that using GPIOPort for accessing the GPIO port for Device ID 8 as listed in the Device I/O Preconfigured list not supported? -
How to access the serial port on sdk 3.1.3 ?
Hi all,
I know that accessing serial port is not possible on firmware 2.x for non jailbroken iPhones.
But what about firmware 3.0?
Apple has focused firmware 3.0 on accessories, through bluetooth or through serial port. So, accessing serial port should be possible.
But I can't find any documentation / sample code for that.
Would you please help me?
Regards,
Alx
PS: I tried to read the port /dev/cu.iap and get this message:
Error opening serial port /dev/cu.iap - Permission denied(13).
Looks bad.Yes I am enregistred in the Mad For iPod program?
And I try to communique with my accessorie
So the Code
+*// SerialPortsModuleAppDelegate.m*+
+*// SerialPortsModule*+
+*// Created by BPO iMac on 08/02/10.*+
+*// Copyright _MyCompanyName_ 2010. All rights reserved.*+
+*#import "SerialPortsModuleAppDelegate.h"*+
+*#import <fcntl.h>*+
+*@implementation SerialPortsModuleAppDelegate*+
+*@synthesize window;*+
+*- (void)applicationDidFinishLaunching:(UIApplication *)application {*+
+*// Override point for customization after application launch*+
+*[window makeKeyAndVisible];*+
+* portSerie = [SerialManager alloc];*+
+* [portSerie init];*+
+* int nb_port;*+
+* nb_port = [portSerie findRS232Ports];*+
+* NSString path_port;+
+* path_port = [NSString alloc];*+
+* int num_port;*+
+* if(nb_port!=0)*+
+* {*+
+* num_port=0;*+
+* path_port=[portSerie pathAtIndex:num_port];*+
+* int resultat= [portSerie openInput:path_port baudrate:9600 bits:8 parity:0 stopbits:1 flags:O_RDONLY];*+
+* if(resultat==-1)*+
+* {*+
+* NSLog(@"Communication Error");*+
+* }*+
+* resultat= [portSerie openOutput:path_port baudrate:9600 bits:8 parity:0 stopbits:1];*+
+* if(resultat==-1)*+
+* {*+
+* NSLog(@"Communication Error");*+
+* }*+
+* }*+
+* [path_port release];*+
+* *+
+*- (void)dealloc {*+
+*[window release];*+
+*[super dealloc];*+
@end
+*// SerialPortsModuleAppDelegate.h*+
+*// SerialPortsModule*+
+*// Created by BPO iMac on 08/02/10.*+
+*// Copyright _MyCompanyName_ 2010. All rights reserved.*+
+*#import <UIKit/UIKit.h>*+
+*#import "SerialManager.h"*+
+*@interface SerialPortsModuleAppDelegate : NSObject <UIApplicationDelegate> {*+
+*UIWindow window;+
+* SerialManager portSerie;+
+*@property (nonatomic, retain) IBOutlet UIWindow window;+
@end
+*// SerialManager.m*+
+*// K3 Tools*+
+*// Created by Kok Chen on 4/28/09.*+
+*// Copyright 2009 Kok Chen, W7AY. All rights reserved.*+
+*#import "SerialManager.h"*+
+*#include <unistd.h>*+
+*#include <termios.h>*+
+*#include <sys/ioctl.h>*+
+*#include <IOKit/IOKitLib.h>*+
+*#include <IOKit/serial/IOSerialKeys.h>*+
+*#import <fcntl.h>*+
+*#import <UIKit/UIKit.h>*+
+*@implementation SerialManager*+
+*- (id)init*+
+* self = [ super init ] ;*+
+* if ( self ) {*+
+* termiosBits = -1 ;*+
+* inputfd = outputfd = -1 ;*+
+* useTermiosThread = NO ;*+
+* needsNotification = NO ;*+
+* termioLock = [ [ NSLock alloc ] init ] ;*+
+* }*+
+* return self ;*+
+*static int findPorts( CFStringRef *stream, CFStringRef *path, int maxDevice, CFStringRef type )*+
+*kernreturnt kernResult ;*+
+*machportt masterPort ;*+
+* ioiteratort serialPortIterator ;*+
+* ioobjectt modemService ;*+
+*CFMutableDictionaryRef classesToMatch ;*+
+* CFStringRef cfString ;*+
+* int count ;*+
+*kernResult = IOMasterPort( MACHPORTNULL, &masterPort ) ;*+
+*if ( kernResult != KERN_SUCCESS ) return 0 ;*+
+* *+
+*classesToMatch = IOServiceMatching( kIOSerialBSDServiceValue ) ;*+
+*if ( classesToMatch == NULL ) return 0 ;*+
+* *+
+* // get iterator for serial ports (including modems)*+
+* CFDictionarySetValue( classesToMatch, CFSTR(kIOSerialBSDTypeKey), type ) ;*+
+*kernResult = IOServiceGetMatchingServices( masterPort, classesToMatch, &serialPortIterator ) ;*+
+* // walk through the iterator*+
+* count = 0 ;*+
+* while ( ( modemService = IOIteratorNext( serialPortIterator ) ) ) {*+
+* if ( count >= maxDevice ) break ;*+
+*cfString = IORegistryEntryCreateCFProperty( modemService, CFSTR(kIOTTYDeviceKey), kCFAllocatorDefault, 0 ) ;*+
+*if ( cfString ) {*+
+* stream[count] = cfString ;*+
+* cfString = IORegistryEntryCreateCFProperty( modemService, CFSTR(kIOCalloutDeviceKey), kCFAllocatorDefault, 0 ) ;*+
+* if ( cfString ) {*+
+* path[count] = cfString ;*+
+* count++ ;*+
+* }*+
+* }*+
+*IOObjectRelease( modemService ) ;*+
+* IOObjectRelease( serialPortIterator ) ;*+
+* return count ;*+
+*// return number of ports*+
+*- (int)findPorts:(CFStringRef)type*+
+* CFStringRef cstream[64], cpath[64] ;*+
+* int i ;*+
+* *+
+* numberOfPorts = findPorts( cstream, cpath, 64, type ) ;*+
+* for ( i = 0; i < numberOfPorts; i++ ) {*+
+* stream = [ [ NSString stringWithString:(NSString*)cstream ] retain ] ;*+
+* CFRelease( cstream ) ;*+
+* path = [ [ NSString stringWithString:(NSString*)cpath ] retain ] ;*+
+* CFRelease( cpath ) ;*+
+* }*+
+* return numberOfPorts ;*+
+*- (int)findPorts*+
+* return [ self findPorts:CFSTR( kIOSerialBSDAllTypes ) ] ;*+
+*- (int)findModems*+
+* return [ self findPorts:CFSTR( kIOSerialBSDModemType ) ] ;*+
+*- (int)findRS232Ports*+
+* return [ self findPorts:CFSTR( kIOSerialBSDRS232Type ) ] ;*+
+*- (NSString)streamAtIndex:(int)n+
+* if ( n < 0 || n >= numberOfPorts ) return nil ;*+
+* return stream[n] ;*+
+*- (NSString)pathAtIndex:(int)n+
+* if ( n < 0 || n >= numberOfPorts ) return nil ;*+
+* return path[n] ;*+
+*// common function to open port and set up serial port parameters*+
+*static int openPort( NSString *path, int speed, int bits, int parity, int stops, int openFlags, Boolean input )*+
+* int fd, cflag ;*+
+* struct termios termattr ;*+
+* *+
+* fd = open( [ path cStringUsingEncoding:NSASCIIStringEncoding], openFlags ) ;*+
+* if ( fd < 0 ) return -1 ;*+
+* *+
+* // build other flags*+
+* cflag = 0 ;*+
+* cflag |= ( bits == 7 ) ? CS7 : CS8 ; // bits*+
+* if ( parity != 0 ) {*+
+* cflag |= PARENB ; // parity*+
+* if ( parity == 1 ) cflag |= PARODD ;*+
+* }*+
+* if ( stops > 1 ) cflag |= CSTOPB ;*+
+* *+
+* // merge flags into termios attributes*+
+* tcgetattr( fd, &termattr ) ;*+
+* termattr.c_cflag &= ~( CSIZE | PARENB | PARODD | CSTOPB ) ; // clear all bits and merge in our selection*+
+* termattr.c_cflag |= cflag ;*+
+* *+
+* // set speed, split speed not support on Mac OS X?*+
+* cfsetispeed( &termattr, speed ) ;*+
+* cfsetospeed( &termattr, speed ) ;*+
+* // set termios*+
+* tcsetattr( fd, TCSANOW, &termattr ) ;*+
+* return fd ;*+
+*- (int)openInput:(NSString*)pathname baudrate:(int)speed bits:(int)bits parity:(int)parity stopbits:(int)stops flags:(int)openFlags*+
+* return ( inputfd = openPort( pathname, speed, bits, parity, stops, openFlags, YES ) ) ;*+
+*- (int)openInput:(NSString*)pathname baudrate:(int)speed bits:(int)bits parity:(int)parity stopbits:(int)stops*+
+* return ( inputfd = openPort( pathname, speed, bits, parity, stops, ( O_RDONLY | O_NOCTTY | O_NDELAY ), YES ) ) ;*+
+*- (int)openOutput:(NSString*)pathname baudrate:(int)speed bits:(int)bits parity:(int)parity stopbits:(int)stops flags:(int)openFlags*+
+* return ( outputfd = openPort( pathname, speed, bits, parity, stops, openFlags, NO ) ) ;*+
+*- (int)openOutput:(NSString*)pathname baudrate:(int)speed bits:(int)bits parity:(int)parity stopbits:(int)stops*+
+* return ( outputfd = openPort( pathname, speed, bits, parity, stops, ( O_WRONLY | O_NOCTTY | O_NDELAY ), NO ) ) ;*+
+*- (void)closeInput*+
+* if ( inputfd > 0 ) close( inputfd ) ;*+
+*- (void)closeOutput*+
+* if ( outputfd > 0 ) close( outputfd ) ;*+
+*- (int)inputFileDescriptor*+
+* return inputfd ;*+
+*- (int)outputFileDescriptor*+
+* return outputfd ;*+
+*- (int)getTermios*+
+* int bits ;*+
+* *+
+* if ( inputfd > 0 ) {*+
+* [ termioLock lock ] ;*+
+* ioctl( inputfd, TIOCMGET, &bits ) ;*+
+* [ termioLock unlock ] ;*+
+* return bits ;*+
+* }*+
+* return 0 ;*+
+*- (void)setRTS:(Boolean)state*+
+* int bits ;*+
+* if ( inputfd > 0 ) {*+
+* [ termioLock lock ] ;*+
+* ioctl( inputfd, TIOCMGET, &bits ) ;*+
+* if ( state ) bits |= TIOCM_RTS ; else bits &= ~( TIOCM_RTS ) ;*+
+* ioctl( inputfd, TIOCMSET, &bits ) ;*+
+* [ termioLock unlock ] ;*+
+* }*+
+*- (void)setDTR:(Boolean)state*+
+* int bits ;*+
+* if ( inputfd > 0 ) {*+
+* [ termioLock lock ] ;*+
+* ioctl( inputfd, TIOCMGET, &bits ) ;*+
+* if ( state ) bits |= TIOCM_DTR ; else bits &= ~( TIOCM_DTR ) ;*+
+* ioctl( inputfd, TIOCMSET, &bits ) ;*+
+* [ termioLock unlock ] ;*+
+* }*+
+*// IO Notifications*+
+*// prototype for delegate*+
+*- (void)port:(NSString*)name added:(Boolean)added*+
+* if ( delegate && [ delegate respondsToSelector:@selector(port:added:) ] ) [ delegate port:name added:added ] ;*+
+*// this is called from deviceAdded() and deviceRemoved() callbacks*+
+*- (void)portsChanged:(Boolean)added iterator:(ioiteratort)iterator*+
+* ioobjectt modemService ;*+
+* CFStringRef cfString ;*+
+* while ( ( modemService = IOIteratorNext( iterator ) ) > 0 ) {*+
+* cfString = IORegistryEntryCreateCFProperty( modemService, CFSTR( kIOTTYDeviceKey ), kCFAllocatorDefault, 0 ) ;*+
+* if ( cfString ) {*+
+* [ self port:(NSString*)cfString added:added ] ;*+
+* CFRelease( cfString ) ;*+
+* }*+
+* IOObjectRelease( modemService ) ;*+
+* }*+
+*// callback notification when device added*+
+*static void deviceAdded(void *refcon, ioiteratort iterator )*+
+* ioobjectt modemService ;*+
+* *+
+* if ( refcon ) [ (SerialManager*)refcon portsChanged:YES iterator:iterator ] ;*+
+* else {*+
+* while ( modemService = IOIteratorNext( iterator ) ) IOObjectRelease( modemService ) ;*+
+* }*+
+*static void deviceRemoved(void *refcon, ioiteratort iterator )*+
+* ioobjectt modemService ;*+
+* *+
+* if ( refcon ) [ (SerialManager*)refcon portsChanged:NO iterator:iterator ] ;*+
+* else {*+
+* while ( modemService = IOIteratorNext( iterator ) ) IOObjectRelease( modemService ) ;*+
+* }*+
+*- (void)startNotification*+
+* CFMutableDictionaryRef matchingDict ;*+
+* *+
+* notifyPort = IONotificationPortCreate( kIOMasterPortDefault ) ;*+
+* CFRunLoopAddSource( CFRunLoopGetCurrent(), IONotificationPortGetRunLoopSource( notifyPort ), kCFRunLoopDefaultMode ) ;*+
+* matchingDict = IOServiceMatching( kIOSerialBSDServiceValue ) ;*+
+* CFRetain( matchingDict ) ;*+
+* CFDictionarySetValue( matchingDict, CFSTR(kIOSerialBSDTypeKey), CFSTR( kIOSerialBSDAllTypes ) ) ;*+
+* *+
+* IOServiceAddMatchingNotification( notifyPort, kIOFirstMatchNotification, matchingDict, deviceAdded, self, &addIterator ) ;*+
+* deviceAdded( nil, addIterator ) ; // set up addIterator*+
+* IOServiceAddMatchingNotification( notifyPort, kIOTerminatedNotification, matchingDict, deviceRemoved, self, &removeIterator ) ;*+
+* deviceRemoved( nil, removeIterator ) ; // set up removeIterator*+
+*- (void)stopNotification*+
+* if ( addIterator ) {*+
+* IOObjectRelease( addIterator ) ;*+
+* addIterator = 0 ;*+
+* }*+
+* if ( removeIterator ) {*+
+* IOObjectRelease( removeIterator ) ;*+
+* removeIterator = 0 ;*+
+* }*+
+* if ( notifyPort ) {*+
+* CFRunLoopRemoveSource( CFRunLoopGetCurrent(), IONotificationPortGetRunLoopSource( notifyPort ), kCFRunLoopDefaultMode ) ;*+
+* IONotificationPortDestroy( notifyPort ) ;*+
+* notifyPort = nil ;*+
+* }*+
+*// prototype for delegate or subclass*+
+*- (void)controlFlagsChanged:(int)termbits*+
+* if ( delegate && [ delegate respondsToSelector:@selector(controlFlagsChanged:) ] ) [ delegate controlFlagsChanged:termbits ] ;*+
+*- (void)termiosThread*+
+* NSAutoreleasePool *pool = [ [ NSAutoreleasePool alloc ] init ] ;*+
+* int termbits ;*+
+* while ( 1 ) {*+
+* if ( useTermiosThread == NO ) break ;*+
+* if ( inputfd > 0 ) {*+
+* if ( [ termioLock tryLock ] ) {*+
+* ioctl( inputfd, TIOCMGET, &termbits ) ;*+
+* if ( termiosBits != termbits ) [ self controlFlagsChanged:termbits ] ;*+
+* termiosBits = termbits ;*+
+* [ termioLock unlock ] ;*+
+* }*+
+* [ NSThread sleepUntilDate:[ NSDate dateWithTimeIntervalSinceNow:0.25 ] ] ;*+
+* }*+
+* else {*+
+* [ NSThread sleepUntilDate:[ NSDate dateWithTimeIntervalSinceNow:1.0 ] ] ;*+
+* }*+
+* }*+
+* [ pool release ] ;*+
+*// If delegate is set, setDelegate also starts a termiosThread if delegate responds to -controlFlagsChanged:*+
+*- (void)setDelegate:(id)object*+
+* delegate = object ;*+
+* if ( delegate == nil ) {*+
+* useTermiosThread = NO ;*+
+* if ( needsNotification ) {*+
+* needsNotification = NO ;*+
+* [ self stopNotification ] ;*+
+* }*+
+* }*+
+* else {*+
+* if ( [ delegate respondsToSelector:@selector(controlFlagsChanged:) ] ) {*+
+* useTermiosThread = YES ;*+
+* [ NSThread detachNewThreadSelector:@selector(termiosThread) toTarget:self withObject:nil ] ;*+
+* } *+
+* if ( [ delegate respondsToSelector:@selector(port:added:) ] ) {*+
+* needsNotification = YES ;*+
+* [ self startNotification ] ;*+
+* }*+
+* }*+
+*- (id)delegate*+
+* return delegate ;*+
@end
+*// SerialManager.h*+
+*// K3 Tools*+
+*// Created by Kok Chen on 4/28/09.*+
+*// Copyright 2009 Kok Chen, W7AY. All rights reserved.*+
+*//#import <Cocoa/Cocoa.h>*+
+*#import <Foundation/Foundation.h>*+
+*#import <UIKit/UIKit.h>*+
+*#import <CoreData/CoreData.h>*+
+*//#import <IOKit/IOKitLib.h>*+
+*//#import <IOKitLib.h>*+
+*#include <IOKit/IOKitLib.h>*+
+*typedef int FileDescriptor ;*+
+*@interface SerialManager : NSObject {*+
+* NSLock *termioLock ;*+
+* FileDescriptor outputfd ;*+
+* FileDescriptor inputfd ;*+
+* id delegate ;*+
+* // serial ports in system*+
+* NSString *stream[64] ;*+
+* NSString *path[64] ;*+
+* int numberOfPorts ;*+
+* *+
+* // termios*+
+* int termiosBits ;*+
+* Boolean useTermiosThread ;*+
+* *+
+* // IO notifications*+
+* IONotificationPortRef notifyPort ;*+
+* ioiteratort addIterator, removeIterator ;*+
+* Boolean needsNotification ;*+
+*- (void)setDelegate:(id)sender ;*+
+*- (int)findPorts ;*+
+*- (int)findModems ;*+
+*- (int)findRS232Ports ;*+
+*- (NSString*)streamAtIndex:(int)n ;*+
+*- (NSString*)pathAtIndex:(int)n ;*+
+*- (FileDescriptor)openInput:(NSString*)path baudrate:(int)speed bits:(int)bits parity:(int)parity stopbits:(int)stops ;*+
+*- (FileDescriptor)openInput:(NSString*)path baudrate:(int)speed bits:(int)bits parity:(int)parity stopbits:(int)stops flags:(int)openFlags ;*+
+*- (FileDescriptor)openOutput:(NSString*)path baudrate:(int)speed bits:(int)bits parity:(int)parity stopbits:(int)stops ;*+
+*- (FileDescriptor)openOutput:(NSString*)path baudrate:(int)speed bits:(int)bits parity:(int)parity stopbits:(int)stops flags:(int)openFlags ;*+
+*- (void)closeInput ;*+
+*- (void)closeOutput ;*+
+*- (FileDescriptor)inputFileDescriptor ;*+
+*- (FileDescriptor)outputFileDescriptor ;*+
+*- (int)getTermios ;*+
+*- (void)setRTS:(Boolean)state ;*+
+*- (void)setDTR:(Boolean)state ;*+
+*- (void)setDelegate:(id)object ;*+
+*- (id)delegate ;*+
+*// delegates*+
+*- (void)port:(NSString*)name added:(Boolean)added ;*+
+*- (void)controlFlagsChanged:(int)termbits ;*+
@end
Could you help me ? -
0 bytes at serial port after Visa Write
Hi,
I'm having problems communicating with a Pollux box controlling a stepper motor (both from Micos). The Pollux box has an RS232/485 connection to the computer.
I have tried adaptations of LV's Basic Serial Read and Write example. Even for the basic example there has never been any bytes at the serial port after the write.
I have attached some sample code for LV 10.0.1(64bit) and the OS is Windows Server Enterprise 2008.
The Visa drivers have just been installed.
After some research I have added a 'Set I/O buffer size' as advised by http://digital.ni.com/public.nsf/allkb/60DDFED7EFEFE7188625705700750821?OpenDocument
The time-out is set to 10s, I have a wait of 1s before read and 0.5s between each write (the characters are written individually incase that was the problem).
The write command getaxisno_ should reply with the default axis no which is 1. However, there is never any reply.
The termination character for Venus2 is a space for transmitting commands and ASCII CR LF at the end of received data.
I'm not sure what else could be wrong. According to MAX the device is working properly. Although, when I try to open a Visa test panel in MAX the program crashes. I'm not sure if this is a related problem.
I'd be really grateful for any advice, have been trying to fix this for a few days now.
Thanks in advance!
Ciara
Attachments:
Getaxisno test.vi 18 KBThanks, I'll search those now.
When I click the test panel button, the Max window disappears and the program is closed. Next time I open it an Unexpected Error box opens with a message saying there was an unexpected error and I should search Info Code MAXKnownException.
'The exception occurred in the NIMax process in the function (Unknown).'
I have searched this and the info advised me to send a report with log files etc to NI which I have done. Just waiting on the reply.
I copied the Visa resource name from MAX and the termination character is the same as what a previous owner of the equipment used in Visual Basic. -
Serial ports not appearing in MAX - VISA installed.
Hi All,
Had a rather strange issue today that I couldn't resolve with serial ports not appearing in MAX (and hence being inaccessible to LabVIEW). Under the windows device manager it shows 4 COM ports and I have verified with an external program that they are functioning correctly.
I had the LabVIEW 2011 SP1 f2 runtime installed, DAQmx 9.6.1 and NI-VISA 5.3 (5.2 also didn't work).
Things I have tried:
- Updating VISA from 5.2 to 5.3
- Reinstalling the COM port devices under device manager
- Changing the COM port numbers
- Verifying that the COM ports are functioning correctly
- Tried adding a USB to Serial converter as a new COM port
- Reinstalling MAX
- Reinstalling NI-VISA
- Reinstalling everything (reboot each time when prompted)
- Resetting the hardware configuration from within MAX
- Run installers / MAX as administrator (this is running from the local admin account)
- Checked that NI-VISA appears under software in MAX
- Repaired MAX/NI-VISA
Is there anything else that could cause the COM ports not to appear in MAX when they appear (and work correctly) in device manager when a reinstall of NI VISA / MAX won't solve?
Certified LabVIEW Architect, Certified TestStand Developer
NI Days (and A&DF): 2010, 2011, 2013, 2014
NI Week: 2012, 2014
Knowledgeable in all things Giant Tetris and WebSockets
Solved!
Go to Solution.I found the solution - it turns out that the serial ports were available to LabVIEW, they just didn't show up in MAX because installing just the runtime does not show the devices in MAX.
Despite doing a lot of googling earlier, it didn't throw up this knowledgebase article until I searched for it under a different phrase - http://digital.ni.com/public.nsf/allkb/766FD80DAE42E52886256A0200619CFE?OpenDocument
Certified LabVIEW Architect, Certified TestStand Developer
NI Days (and A&DF): 2010, 2011, 2013, 2014
NI Week: 2012, 2014
Knowledgeable in all things Giant Tetris and WebSockets -
Serial port: Input/output signal errantly combined
I am currently in the process of using LabView to replace another user interface for a scientific instrument.
LabView is connected to this instrument through a serial port. The instrument streams 25 bytes of binary data every second to the computer. I can read the binary string (VISA Read) and save contiuously to disk using a while loop. In addition, there are a few instructions I can send to the instrument that will do various functions (start logging, turn LEDs on/off, etc). I can successfully send these instructions to the instrument using the previous interface, and in a stand-alone vi using VISA Write, but when I place the VISA Write function into the larger interface vi, signals go haywire. Specifically, there are two separate LEDs that I can toggle with two different commands, but when in the larger interface vi, both commands toggle the same LED. Also, it appears that the singal I send to the instrument (a single ASCII character) immediately bounces back to the computer into the 25 bytes of streaming binary data. In other words, after I press the LED "on" key, one column of my streaming data changes when it is not supposed to (ex: after Binary to ASCII conversion, it changes from a single digit to a twenty digit value).
Initially, I thought the problem was the sequence of VISA Read/Write. In the current configuration, I read all data, then allow for Write commands. Both the VISA functions are within the same While loop to continuously monitor the data. Is it possible the Write signal output is not leaving the while loop and being read as input? What would make the instrument read two different commands as the same one? My goal is to run an interface that displays the streaming data as ASCII, and allows for a few different toggle options while the interface is running - is there are more efficient/elegant way than a while loop?
~Going Bananas
Solved!
Go to Solution.New replies now in gray.
CodeMunkee wrote:
1. If you keep giving me good advice like this, I'll be tempted to change the background to Baltimore prison purple.
I'll ignore this statement.
2. The buffer now lives outside the loop. I understand clearly. Part of the problem might be my instrument - when I cycle power the 19 digit number that was 'echoed' disappears. Forget about that display stuff, it works properly - I accidentally removed the time delay when editing the vi. But you do bring up an interesting point...
Without the delay, the loop ran much faster. If the bytes weren't at the port, the read statement would have returned nothing when it read zero bytes, thus blanking out the indicator rather quickly.
Yes, Hexadecimal display shows 04 to indicate the end of the 25-byte data sample.
Doing a bytes at port read is not always a good idea. If not all the bytes had arrived yet when you ask for the read, you won't get all the data. The remaining data being sent in that stream from the instrument will show up at the front of the buffer on the next read command.
While this isn't a common occurence, it does happen. How can I prevent this from ever happening?
Since you know each commands ends with a hex 04 (ASCII character for EOT), you could enable the termination character when you configure the serial port. Set the termination character to be 4. Then when you execute the VISA read, read a large number of bytes such as 25 or more. The read will terminate at either the timeout, the requested number of bytes, or when the termination character is read. With this setup, you could eliminate the wait statement and also not request the number of bytes as the port. The VISA read will control the pacing of the loop. Any extra bytes after the termination character are part of the next frame of data and will wait around until the next time you read the VISA port.
3. Implementing your ideas for the latch button works better. I am still encountering issues with these commands however. Attached is the new vi. There are two commands I want to send, 't' turns on the LED light (they blink for 30 sec then time out), and the latch works perfectly for that, 'p' turns on the magnetometer light (an additional 'p' is required to turn it off), but I cannot get the command sent to the mag while the loop is running. It turns on either at the beginning of the vi, or at the end of the vi (after Finish button is pressed). This leads me to think the command 'p' is stuck inside the loop. I tried adding another film strip (see attached vi) for the toggles to force the issue, but it didn't work. Additionally, the 'p' command effectively works as a 't' command, and the LED lights begin to blink when I press the 'p' button. This isn't supposed to happen, and leads me to believe the 'p' command does in fact exit the loop but in the wrong manner.
The "film strip" is another frame of a flat sequence structure. It enforces the order of execution. The next frame can't execute until everything in the prior frame has completed. It isn't necessary in your case because the Error and VISA wires determine the order of execution with respect to the other VISA statements. But it shouldn't hurt.
There is no reason the "p" case structure should behave any differently than the "t" case structure. Although you should wire the error wire through in the False case of the "p" structure like you did for the "t" structure. There is no "exiting of the loop" in either case. The loop runs until the stop button is pressed. I would check the manual to see that t and p commands do what you think they should do. Do they need a termination character of their own when they are sent? Should they be upper case letters rather than lower case? You can run NI Spy on your serial port and see the operations occurring with it and see the data coming in and what data is going out. I would be suspicious that the device is not handling the command properly.
Any ideas? I think I've tried to put the toggle buttons outside the loop before, but then could only toggle once before the loop took over. Ideally, these toggles would be available at any time while the data is streaming, so therefore inside the loop?
The toggle buttons need to be within the loop so that they can be read on every iteration of the loop. Outside the loop, as you discovered, they are only read once at the very beginning before the loop is started.
4. Thank you for the suggestion about the Selection Mode for the Open/Create File option. It is annoying to create a file first. I made the change, but I still get error messages when I use a file that does not yet exist. LabView takes me to the first Open/Create/Replace vi when the error occurs. Is there something else I must do?
On the open file VI, there is an input that is Open as default when unwired. Create a constant there and change to Replace or Create.
Remember, if you have any questions about the way LabVIEW is handling something with serial ports, close the port within LabVIEW. Open Hyperterminal and try the commands from there.
Message Edited by Ravens Fan on 01-13-2009 03:55 PM -
How can i browse FP 2000 via serial port same use Ethernet port(RJ 45)?
I am a new user for labview.I develope my program with FP 2000 but I have some problem
1 How can i browse FP 2000 via serial port same use Ethernet port(RJ 45)? if it can Tell me please.
2 If I use GSM/GPRS modem via FP 2000 rs 232 port (I under stand how to send AT command) and leave it stand alone
Can I dial modem and browse file in FP 2000 same as use Ethernetport?
Someone please help me.Thank you very much.Hi!
First, I can say that your project involves many things, I cannot describe all features in the forum, and I'm not used with GPRS modems (my modems are base band serial modems...).
Anyway, I would say that in your project you should proceed like this:
1) Configure your FP 2000 module via MAX and ethernet connection;
2) Download an embedded application to your module (build in LabView Real-Time)
3) In your application, you should build a kind of serial port manager, and by the means of serial port you send/receive commands from PC.
The commands from PC can include "Tell me the about the FP 2000 file system ", or "switch on line X", or anything you need.
I think it would be difficult to use Internet exp, because you use IE with TCP/IP, and TCP/IP is over ethernet.
I know that for Windows you can find some wrappers that make you "see" the serial port as an ethernet, but these wrapper do not exist under filed Point, and you shoul build one yourself!!!(and that's not easy).
For example, to browse your files, you should build a VI that searches through your file system, and reports, via serial, the files present in a directory (it's an example....).
About communication between GPRS modems and FP2000, I know nothing. I suppose that these modems accept serial inputs, so you'll have to configure your serial port on FP 2000 with the correct baud rate, parity, and so on..... and you send your data to the modem. The modem will transfer data in its way, no matter on how it does.
To send data to your modem you shoud take a look to some Serial communication examples. What I suggest you, first, is to connect the serial port of FP2000 to a PC, and test communication between PC and FP2000, without modems. Just direct cable connection! If you're able to do this, insertion of modems is the next step, and should be quite easy. If you're not able to make the PC receive strings of data from FP2000, over RS232, adding modems is a further complication, and you won't come out of this mess!
So, what I say, is just build, for now, a simple embedded application for FP2000, that, using RS232, sends data to a PC (you should see data sent with use of Hyper terminal).
To build this application, use Instrument I/O --> VISA commands (VISA open, VISA write, and Property node should be enough, for now).
Please, let me know if this helps......
Have a nice (programming) day!
graziano -
Error 37 with serial port / no with hyperterminal
I have added to my Pc a card with two serial port, I can access to them by hyperteminal or by labview but only at port 0 and 1 at the same time or 2 and 3, if not I have an error 37. What can I do?
Error 37 means that LabVIEW cannot find the appropriate serial device. This indicates that one of the following conditions exists:
LabVIEW cannot open the specified serial port;
LabVIEW cannot find the file serpdrv.
Make sure that the serial driver was installed before the board, and that the com ports appear normally in the control panel. If you cannot get it working, contact NI through either phone or email support. Since there are several potential causes, this is difficult to diagnose without more information. You can contact NI using the following webpage.
http://sine.ni.com/apps/we/niae_asc.main
Kim L.
Applications Engineer
National Instruments -
MEASURING FORCE ON BALANCE USING AN ELECTRONIC BALANCE FROM THE SERIAL PORT
Hi,
I am trying to measure FORCE using an electronic BALANCE from the serial port. My measurements are strange! The BALANCE sometimes give ZERO reading! Is it because of the sample rate, baud rate etc? I have attached the readings concerned.
Attachments:
databalance.doc 144 KBI think your problem is due to the way you read the weight :
1/ask the balance to send the data
2/oversee the byte number on the serial port until it is constant
3/read the bytes received
4/convert to number
During step 2, you compare the bytes at serial port with the previous value. So far, you have been very lucky to be able to read something : the answer here is always ZERO since the readings occur BEFORE the balance has been able to send anything! means that your loop stops immediately (if you are not convinced, jujst add an indicator to display the loop index. However, since you added a wait (0.8 s), when going to step 3, the balance has had some time to send something. Here, you should not have read again the number of bytes at serial port, but that unwillingly corrects the previous error and you can read most of the received data...
You should modify completely your algorithm. Usually, a balance send the weight as a string with some terminator (RC or LF). Accordingly, the algorithm should be :
1/ask the balance to send the data
2/read the serial port, concatenating the received chars until a terminator char is received or a timeout has occured
3/convert to number
CC
Chilly Charly (aka CC)
E-List Master - Kudos glutton - Press the yellow button on the left... -
Strange init serial port issue
Hello:
My Labview application is reading data from the COM1..COM6 ports (I have
added a MOXA serial board to get 4 more ports). I am using RS232 reading
on each port (old legacy Vis, 9m long communication cables). The devices to which I am connected are weigh scale that continuously send weight readings to the Labview app through 3-wires RS232 (RD, TX and GND). Everything goes well for hours and hours. Then after a while (maybe after power is cut and restarted on the PC side?) I restart the PC and launch Labview. If I try to init the serial port that I use to connect to the weigh scale I get an error 37. I also tried to init thru HyperTerminal right after restarting the PC and could not. The only thing that works to unlock the port is
this:
- unplug the weigh scale communication cable from the Moxa connector
- restart the PC
- relaunch LV or HyperTerminal
Unplug then restart Labview or HyperTerminal is not sufficient.
To the same Moxa board I connect other devices such as PLC or PC through serial ports but never see any problems even after restarting the Host PC. So there is something strange with weigh scales (I tried two different brands) but what? I cannot use the built-in serial port as it is already in use by another application.
Does someone out there have an explanation and ways to avoid this very annoying problem?
Thank you very much, I am completely lost,
ChristopheChris:
Thank you for your help. I investigated the problem further and this is what I found. I am still clueless so if you think of other tracks that I might explore I would be glad to hear them.
- Hard boot (power off, remove power cord, restart) does not release the port
- I change the port ie. I used the built-in COM1 PC port, got the communication, could read char, then restarted the PC and fell into the same trap: could not init the port (Labview). I did the same after restarting and could not open the port with HyperT. Hence it is not a Moxa issue.
- The question is: how can I resolve that, is it an HW or SW issue, a combination of the two, has it got something to deal with WIndows 2K, are there some tools that allow to diagnose whi
ch service or application grasps the serial port during the boot sequence? Or is it a problem during the shutdown sequence that the port is not released properly?
TIA,
Christophe -
My problem is that I have written a comand through the serial port, and I doesn´t receive the answer. If I execute the programm step by step, I don´t have any problem but if the program runs i don´t get the answer!!!It is not a problem of the bytes that I write and receive, i have used the function "Visa Bytes at Serial Port"!!I have used th function "wait" but it doesn´t work!!!!i have used a Flat sequence but it hasn´t solved the problem!!so, i don´t know what i can do!!!
I attach the "different versions" that i did, maybe someone find a solution!!
Dennis, I have the problem, when
I read the last time in the program, I don´t receive the answer!thank you!!!
Gracinda
Attachments:
salida_analogica.vi 67 KB
config_rango.vi 41 KB
salida_ana_v1.vi 69 KBDear Mads;
Thank you for your answer.
I don´t have a termination character but I know the number of bytes that I have to receive. I tried checking the number of bytes that I received, using "Bytes at Port", but it gets a value and it isn´t refreshed, it has a value so my program stop in the while structure that I have added. I attach the vi. I don´t know how to do that. I am starting with Labview, and it is a little difficult for me!!
In the first change that I did, I added the function "Bytes at Port" inside the While loops, but it doesn´t work either !!!
Thank you!
Attachments:
entrada_analogica.vi 94 KB -
VISA get resource name doesn't return USB serial ports
We built an application on a computer that had an onboard serial port - COM1. We put the option to change the COM port in the application. We installed the built application on a computer with no serial ports, but installed a USB to serial converter that registers as COM3. LabView does not see this port, even with a test application to return only the VISA resource names.
We have verified that the port is good with another program (a Modbus simulator) and installed the latest VISA runtime v4.41 separately to no avail.
Any suggestions at further troubleshooting would be extremely helpful.
Joe T.
Solved!
Go to Solution.My main application still isn't working, but now the small test ones are.
Here's what I did:
1. Update my LabView 8.5 with the latest VISA runtime - 4.4. This updated the Installer as well.
2. Added the MAX Installer to the build.
3. Added the NI-VISA Configuration Support to the build
4. Uninstalled the application and reinstalled it with the new install volume.
When I run MAX, COM3 shows up. It also shows up in the Get Resources test application. The simple test Modbus write program works, too. I have a sneaky feeling that COM1 may be hard-coded somewhere in the main application; our next task is to find where the communications breaks down in our code. The bottom line seems to be a lack of experience with the Application Builder on our part.
Thanks to all who contributed!
Joe T.
Maybe you are looking for
-
can you help?
-
Is it possbile to have multiple clients on our Production instance
We have our Production system with client 101 Our abapers want me to create another client 500 (config only - not easy to accomplish) to be used for our Mexican users. I told them to create another company code for Mexico, but they do not know how t
-
Trouble downloading photos from camera to iPod to PowerBook
Four "rolls" of photos I downloaded from my camera to the iPod appear in the iPod "Photos" menu separately from the other eleven rolls, which are found in "Photo Import". Those eleven can be transferred to my PowerBook desktop easily from "DCIM", but
-
Finder window not appearing when selected from the Dock
Hi My Finder exhibits the following behavior: Right Click Finder in Dock Finder displays list of currently open windows, etc. I select one of the windows Nothing happens Note: If a select "New Finder Window" a new window is opened. This has become m
-
STOCK OF FINISHED PRODUCT BY PIR NOT CONSIDERING WHILE TAKING MRP RUN
DEAR SAPGURUS, I have finished product stock of 50 nos through planned independent requairement. now i am creating sales order for finished product but mrp run generate the planned order for finished product. I dont have planned order for fini