Serial Communication Error -1073807253

Hello!
I'm trying to make a simple serial port reader VI and i can't get over this:
Error -1073807253 occurred at VISA Read in communication.vi
Possible reason(s):
VISA: (Hex 0xBFFF006B) A framing error occurred during transfer.
I'm pretty shure that the device sending a data works properly and the parameteres like a boud rate, parity etc. are set correctly because I've already communicate with that device via Matlab.
Although I've noticed that somebody here have the problem with this error, but I can't find any solution for me.
There is a picture of my simple VI diagram in Attachments. The parameters of the communication are set at the beginnig, after that and a litle delay the input buffer is flushed, then the loop starts. When the buffer contain nine or more bytes this bytes are readen.
Please, can anybody tell me what I'm doing wrong?
Thanks
Attachments:
VI-rs232-trouble.jpg ‏106 KB

chikvadrat wrote:
The VI works well after launch. It also read first 9 character correctly, but after that it crashs.
So what happens if by the time the loops comes back around, you have 10 bytes waiting for you at the port?
Bill
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.

Similar Messages

How to resolve the serial communication error in HP34970?

I want to use serial port to commnucation between pc and hb34970. In gpib mode, it is ok. But in serial mode, report error. just like this:
for setting com2:
16:11:47.359 2009-8-26 [Init_dq_Device]error:-1073807339--HP34970A Initialize.vi->Init_DQ_Device.vi->main_app.vi VISA read.visa name:ASRL2::INSTR
for setting com1:
16:13:25.921 2009-8-26 [Init_dq_Device]error:-1073807339--HP34970A Initialize.vi->Init_DQ_Device.vi->main_app.vi VISA read.visa name:ASRL1::INSTR
I don't know the meaning of -1073807339 and whether i should set:ASRL1::INSTR for com1. Anyone can help me about this problem.
Thanks very much.
attach my subvi.
Solved!
Go to Solution.
Attachments:
Init_DQ_Device.vi ‏48 KB

Hi, Dennis Knutson
very glad to see you.
For my vi, i only provide a UI for user to select GPIB or serial mode, and setting related port.
About "Also, the 34970 llb you are using should be replaced with the 8.x project library.", What do you
mean? There is a new driver for 34970,right?
I search the forum and find a old thread:Agilent 34970 Visa Timeout.
There is your answer:
I made a mistake. The initialize function already had a timeout function. I just didn't look at the VI closely enough. There is a case statement that sets either the serial port parameters or just sets the VISA timeout. If you are setting the timout right after the VISA Open, it's just getting set back to 10 seconds. Change it in the case statement and see if that works. Sorry, and I hope this works.
Do you think this is the same with my problem? Your mean to modify default 10 seconds to more longer timeout,right?
Thanks.

Serial communication does not work in an executable.

I have created a vi that communicates with a serial device. It works fine on the computer that it was creatd on. I then created an application and then built an installer to put it on another machine. The second machine does not have LV 2009 on it. Once installed on the machine the vi does not work. When it runs on the computer with LV 2009 the the com port control is a pull down, and it lists all comports on the computer and then you select the one you want to connect with. The computer that the vi is installed on does not list the available com ports. This leads me to believe that there is no serial comms support in the installable version. What do I do now?? I noticed that you can add "Additional Installers" when you build the installer and one of them is NI-Serial 3.4. I try to add this and a message said that it had to get, so I didn't use it thinking it was more than I needed and that standard com port driver would be included. Am I wrong here or am I missing something else?? All help is greatly appreciated.
[email protected]
Solved!
Go to Solution.

claudio.rossi wrote:
Hi at all!!
I'm new in NI forum.
I have one similar problem. My VI communicate with external device on serial port. The VI work very well, but when I create executable (.exe) file with Labview application builder (on Labview 2010) the .exe don't use serial port!!! The executable run perfectly (nothing error or warning by the application builder), but the serial data on selected COM port isn't send!!! Also on the PC where I developed the VI!!!
What do you mean by your last sentence? Are you trying to say that you can't run your executable even on the same computer on which you developed the application? If so, was LabVIEW open when you tried to run it? Try quitting LabVIEW; if you had previously run your VI and didn't close the serial port, LabVIEW might have kept it open, which would prevent the executable from accessing it. If the executable won't run on the development machine it's unlikely to be resolved by installing VISA since you need that installed for the VI to work properly in the development environment. Do you have any error handling in your code that would indicate if an error occurred after trying to write to the serial port (an indicator on the front panel, or a call to Simple Error Handler)?

Serial Communication problem in LabVIEW 7.0

I recently upgraded my test computer from a 450 Mhz machine to a
Del 2.8 Ghz Pentium 4processor with 512meg's of ram using Windows 2000 for the operating system running LabVIEW 7.0.
I use the serial port to communicate with a piece of hardware,
Rs232, 115200 baud, 8 bits, 2 stop bits. NO hardware or software handshaking
The hardware is capable of receiving data from the computer at a full 115200 baud up to 65k transfers at a time with no extra delays.
The problem that the serial data coming from the new Dell computer will send out 2 bytes then waits 2 to 3 milliseconds and sends 2 more bytes.
I generated a separate serial VI that will jest shove data out the serial port.
The VI is a VISA configure serial po
rt, into a while loop that contains 6 VISA Write VI
And on the backside of the wile loop a VISA close.
The above VI will generate the serial data stream as stated above
EXCEPT when I put a PROBE on each of the ERROR OUT of the 6 writes, then the serial port will generate a continuous serial data stream with no millisecond breaks.
I have changed the FIFO Buffer settings (all the possible combinations) of the serial port in Windows 2000, and that has hade no effect.
Any help would be greatly appreciated
James Zumstein
E-mail [email protected]
Attachments:
Serial_Test_1.vi ‏45 KB

Greetings!
Serial port commucations problems can be a real joy, can't they? Have you tried communicating with your instrument with Hyperterm? Usually Hyperterm is capable of operating with almost no overhead, so you can see if there's any strange symbols being transmitted that might be holding things up. There might be an extra CR being inserted, or something like that, which will show up as heiroglyphics in Hyperterm. See if all your symbols coming back are valid. This is where I usually start.
Hope this helps.
Eric
Eric P. Nichols
P.O. Box 56235
North Pole, AK 99705

6500a e710 a-f - Scanner Communication Error Windows 8.1

We have been experiencing issues with scanning whilst connected via USB, using the HP Scan software. The software returns an error message saying scanner communication cannot be established, half way through scanning. Then HPScan.exe fails to load again. The printer just says “scanning cancelled” on its display.
This is only effecting one model of PC and that is a HP 8300 Ultra-Slim PC.
We are running Windows 8.1 64 bit from an image install. However, I have tested this with a fresh Windows 8.1 retail installation and get the same problem.
We have tried various actions to fix this:
- Various accounts, admin accounts, domain admin accounts, local accounts etc.
- Uninstall and reinstall. Basic and Full driver packages including the latest versions
- Removed all other HP software from PC including registry keys
- Used built in Windows 8 scan software with basic driver
- All USB ports tested including 2.0, 3.0 and powered / non-powered
- Replaced cables
- Re-isntalled USB bus drivers for 8300
- Followed the print/scan doctor which shows a driver error - scandriver unable to communicate with product
- Run HPScan in compatibility mode for 7/XP
- Updated firmware on printer
- Installed latest Windows Updates
- Checked WIA service and dependencies are running
- Semi and Full factory resets on Printer
- Shell hardware detection service set to manual
- We have replaced the printer for an affected user - same issue
- Also replaced PC for an affected user - same issue.
- Updated PC BIOS
I have tested connecting the printer to the router with a network cable and then installing printer as a networked device rather than USB and then the hpscan.exe works. So this is only an issue with USB (though it wouldnt be practical to try and talk 200+ users through networking their printer).
As you can see, we have tried almost everything. Interestingly we havent been able to replicate this issue in one of our main offices - despite collecting the same PC and Printer from an estate and bringing it back to an office.
We have also sent out a working PC and Printer combo to an affected estate office and it has not worked there.
Our Estate Offices connected via an ADSL Router and "My Documents" are re-directed to a network location. Could a failure in accessing this network location cause the problems? I have tested connectivity to network store from PC and it accesses the files fine.
Any solutions would be greatly received, I have spoken to HP After Sales support but not received an working solution yet.

Greetings, @Scammell29
I have read through your post and have very ideas left for you, as you've tried quite the load of troubleshooting!
I am thinking the issue could be power related, so try a power reset and plug the printer in directly to the wall outlet. Avoid power bars, surge protectors, etc. Just a direct plug in to the wall to test the power. Afterwards, see if you still receive the communication error.
If the issue continues, next try a disk cleanup, the instructions are included in this guide: A 'No Computer Detected' or 'Connection Error' Message Displays during Scanning for HP Officejet 650...
If the error still persists, perform a Clean Boot and restart the PC and then disable the Firewall and Anti-Virus scanners.
Please let me know the results!
Good luck
R a i n b o w 7000I work on behalf of HP
Click the “Kudos Thumbs Up" at the bottom of this post to say
“Thanks” for helping!
Click “Accept as Solution” if you feel my post solved your issue, it will help others find the solution!

Problem with serial communication PLEASE HELP

Hello everybody !
I'd like to ask You for some feedback on my wierdo problem that I got with my program.
I have built a device that detects changes in magnetic field. It is used for detecting vehicles passing it on a highway. Generally the main components communicate with each other by RS-485 protocol, but I would like to connect the device to a PC. To do so I am using a RS-232 protocol (I have a RS485=RS232 hardware converter).
Now, I made the program (even two), which generally works, BUT some wierd things are going on sometimes; it happens that I have a problem to get a communication (after that, resetting the device by un-powering it helps, sometimes I have to restart the PC as well) but overall it happens quite not so often. The project itself is for passing one of my subject on the university - so I have to run the whole thing over there, here comes another problem : the program did not work on all of the bunch of PC's that are there. Same thing happens on my notebook. The effect of 'non working' is : I am recieving same data packet that is beeing sent... BTW : notebook does not have a RS232 port and I am using a USB-RS232 calbe converter (to count it out from the reason of problems I have checked it on my main PC and it works almost fine - almost because ocasionally I am getting the same sympthomps as I mentioned before ).
Other problem is, when it works, that I am loosing communication for couple of hundreds of miliseconds and then it comes back to normal (i can see it on the osciloscope).
I alredy looked for some answears here and there, and I found some suggestions about using 'buffer cleaning method', unfortunatelly I kinda do not know how to do it, and might that help anyways ?
I also thought about using VISA drivers, but I am having trouble with it as well - the damn thing just does not work.
My very bling guess is that everyting that I am expierencing is about using the communication protocol and seting it right. I am attaching both of the programs, PLEASE anyone pretty pretty help I totally ran out of ideas and knowledge and day after day I am turning it on and off on my PC and notebook hoping some miracle will occour ...
Many many thanks in advance !
Best regards
Tom
P.S. the program is very unfinished (man things are just put in), the main thing I am struggling now is getting, and setting the communication protocol right.
Attachments:
detektor_3_2.vi ‏141 KB

The biggest problem I see is in the sequence:
Write out a string.
Wait 50 mSec.
Ask how many bytes have been received.
Read that many bytes.
Can you guarantee that the data can make a round trip in 50 mSec?
You should know that the SERIAL PORT WRITE completes NOT when the data has been sent out the port, but when it has been BUFFERED for sending. In other words it returns and starts the timer BEFORE it is actually sent.
Also, given that there are 232 -> 485 --> USB conversions involved in both directions, I would bet that you are sometimes not allowing enough time for the data to get back.
If you can control the protocol of what gets sent back, I would change your receiving logic. I think you should check for a carriage return or some other delimiter, and not react until you get that character (or until a reasonable timeout expires).
In other words, try synchronizing the two ends. Something like:
N = Get # bytes at port
Read N bytes from port (flush any characters waiting).
Write out command string.
TimeLimit = NOW + 1000 mSec (or whatever)
S = ''; (Working string)
repeat
N = #Bytes at Port
If N > 0
S = S + Read N Bytes
Found = Search String for Delimiter
until Found or (Now > TimeLimit)
If Found, parse string S
You are also re-initializing the port (SERIAL PORT INIT) every time thru the outer loop - that's unnecessary.
Steve Bird
Culverson Software - Elegant software that is a pleasure to use.
Culverson.com
Blog for (mostly LabVIEW) programmers: Tips And Tricks

Problems on serial communication with an instrument

Hello everybody!
I'm having some problems interfacing with an Optical Spectrum Analyser from Anritsu via RS232. It has a GPIB interface that works well already, but i need to make communication work thru the serial port. If i use Measurement and Automation, i can write and read the commands alright. But, if i use a self made Labview vi, it doesn't work at all.
My vi consisted on:
ViOpen - ViWrite - ViRead - ViClose
Normally, i can know when the communication initialized alright with the OSA because the instrument enters a "communication state". When i use M&A, it enters on that state. When i use Labview, it doesn't.
I used NI Spy to see what differences were between the M&A and Labview. Here is a list of comm
ands issued by M&A:
viOpen(...,"ASRL1::INSTR",...)
viInstallHandler(...) *
viEnableEvent(...)
viWriteAsync(...)
viReadAsync(...)
viClose(...)
My Labview VI issues the following commands:
viOpen(...,"ASRL1::INSTR",...)
viWriteAsync(...)
viReadAsync()
viWaitonEvent()
viWaitonEvent()
viWaitonEvent()
viTerminate()
viClose()
Labview returns a "problems in serial read" error, but i know that the program doesn't even begins communication with the OSA. I suspect that the error lies on that viInstallHandle function, that is ran in the M&A routine but it isn't on Labview, but i can't find a way to make a vi that runs this function.
Anyone can help??? I am really frustrated because i know that serial communication works, but on M&A only!!!
Thanks in advance
Felipe

I consulted the document "VISA and Serial Communication" from ni.com. It
was helpful. I'm using Labview 6.
I don't know how to get Labview to tell me what it is doing at the level of
viTerminate(), etc., so I suppose I may not be able to contribute anything
to you, but I did get my serial port working in Labview recently.
I used a loopback test, by shorting pins 2 and 3, to verify that Labview was
successfully sending and receiving from the chosen serial port.
I made a .vi that let me do one thing at a time, initialize, write, and
read. This helped me realize that the instrument wasn't very fast at
getting back to me, when I was nailing down what I thought was a receiving
problem.
To get Labview to use the serial port on this system I had to uninstall a
graphics tablet driver that was taking control of the port on bootup. VISA
would report that there was a problem until I did this. Maybe if M&A runs
first your OS still thinks the port is being used and won't let Labview use
it.
Also, depending on what serial .vi I was using, I needed to verify that I
identified the port correctly. Port 0 in Labview, in my case, corresponds
to COM1, this is for the "compatibility" .vis. When using VISA serial .vis,
I discovered that COM1 was identified by VISA as ASRL1. However the default
resource name that came up when putting a VISA serial .vi into a diagram was
ASRL2 which does not exist on this system. Manually changing the "2" to a
"1" in the front panel solved my problems.
Your M&A and Labview VISA seem to agree on ASRL1, which might indicate that
isn't the problem.
I used the VISA interactive control to tell me how VISA was doing
identifying the ports and which ports it thought it could use during any
given session. This is available on my system in the VISA program group. If
there are yellow question marks on ports in this program, the port in
question has wandered away.
There are some examples and functions in the directory:
Labview 6\vi.llb\instr\serial.llb
and also in the directory
Labview 6\examples\instr\simplserl.llb,
as well as
Functions --> Instrument I/O --> Serial
and
Functions --> Instrument I/O --> I/O Compatibility --> Serial
Compatibility
"Felipe Ferri" wrote in message
news:50650000000500000004140100-1042324653000@exchange.ni.com...
> Thanks for your comment, but i tested the serial read and write
> functions that you used on your program and they didn't work...

Fieldpoint 2010 Serial Communications

I am student at Texas A&M University and we are using the FP2010 to remotely control a mobile platform. Everything is working great but we do have one question... Can we access and use the RS-232 port on the FP2010 during operation? If so, how do we do this? The documentation on the FP2010 says that it can be used to communicate to serial devices.
Thanks,
Chris Massoll (entc359.tamu.edu)
Texas A&M University

Chris,
Yes, you can access the RS-232 port during operation with an embedded VI. To do this you use the Serial VI's that are located on the Serial Compatability palatte. This is located by going to the functions palatte==>Instrument I/O==>I/O Compatability==>Serial Compatability.
Regards,
Aaron

Serial Communications with Allen Bradley PLC 2.30

Does any one know the required pin outs for the serial cable from the PC com port to the Allen Bradley 1771-KG card or directly to the Allen Bradley processor? Any samples on writing TAGs to the registers?
Roy L. Costa
Email: [email protected]
Catalyst Test Engineer
General Motors Warren Tech Center (R & D)

Hello Chad
Thanks for the pin out information. I tried that pin out configuration Monday and it did not work. I am pasting a copy of a communication with Allen Bradley in this comment box as well as a communication with another programmer that commented in here as well. Please read it and let me know what you think. Thanks again Chad.
Roy
Everything works well, from the LPD OPC Server to creating TAGS..to using the HMI wizard on the front panel,...but there is no communication with my hardware. An NI Application Engineer came by yesterday and we concluded that this was a hardware ware communication problem. I talked with an Automation Engineer in Austin yesterday and he told me to try RSLinx and see if I could get it to communicate with the hardware. I like that HMI wizard, it is pretty cool! I am pasting a copy of an email I sent to Allen Bradley so you can see a little bit more information about my hardware. thanks for your help again Khalid.
{{{I am having much difficulty in communicating to my PLC 2 communication port or through my RS-232 port on my 1771-KG card. I am using a serial (null modem) cable on com port 1 on my PC. I have Win98 operating system. I am using LabView Datalogging and Supervisory control (Lookout) software to create several HMI?s. Can you please give me the pinouts that I need to communicate with the processor port on the PLC and or the 1771-KG card? Please contact me as soon as possible for I really need to get this to communicate so I can get started on this HMI upgrade. We are using PanelMates as HMI?s, but they are 13 years old and are failing frequently as well as being obsolete. At the present time I am creating new HMI?s but we are planning to do one fuel processing line at a time and replacing the PLC 2.3 with PLC-5 and then we can use the Ethernet module. Please call me at 313-972-4635 I do not have my own email at work so you will need to email any communications to my supervisor Fred Jacobsen he then will pass it on to me. Email: [email protected] If you have something you can fax me, here is the fax number: 313-871-2835
Roy L. Costa
Email: [email protected]
Catalyst Test Engineer
General Motors Warren Tech Center (R & D)

Problem with TCP/IP communication: error ni-448 when I want to write on a TCP/IP-connection

Hi folks
I have a really annoying problem: I want a computer (Win XP, Ethernet board, Labview 7.1) to communicate with my robot controller (Win 2k, Epson SPEL+ language). The robot controller is the client, the LabViewPC the server. now reading messages sent by the robot controller are no problem to read. But when I want to send messages from the LabViewPC to the robot controller I get an error message: error ni-448, make sure that the GBIP-controller is the primary controller.
For the communication I open a TCP-listener and a TCP wait listener in a while loop. So far this works. Then I use the TCP-write function to send a string to the robot controller. Here the error described above occurs. So the communication doesn´t work.
Can anybody help me?
Please. Thank you in advance!

hi there,
are there several network adapters on your host? if so pass the IP of the network adapter to the "TCP listen.vi". i'm not sure but i think i remember that in former versions this had no effect. then you could use "TCP Listen.vi" on your slave and "TCP Open Connection" function on your host.
you can use the "Simple Data Server" and "Simple Data Client" examples for a quick test.
Best regards
chris
CL(A)Dly bending G-Force with LabVIEW
famous last words: "oh my god, it is full of stars!"

THere was an error updating your sofware. An error has ocurred while updating your devices software. Device communications error encountered. [A:0x0000000F].

I've tried the suggestion "Please try the following: Disconnect your device and restart your computer. Restart the loading process" multiple times with or without battery, but still the same.
This error propmpted while loading the system software.
Anyone encounter this issue befire and how to fix it, really appreciated
Thanks.

I found it in loader.log
[3] [8est:58:28:921] [CfpProgrammer] [0x00002f9c] [CfpProgrammer.cpp:1143] Writing to Loader Action Log "52BE2234:3.10.0.47TM connection type: PC"
[3] [8est:58:28:923] [CfpProgrammer] [0x00002f9c] [CfpProgrammer.cpp:1143] Got LAL_RESPONSE
[3] [8est:58:28:927] [CfpProgrammer] [0x00002f9c] [CfpProgrammer.cpp:1143] Retrieving persistent data struct
[3] [8est:58:28:928] [CfpProgrammer] [0x00002f9c] [CfpProgrammer.cpp:1143] Got persistent data struct
[3] [8est:58:28:928] [CfpProgrammer] [0x00002f9c] [CfpProgrammer.cpp:1143] Retrieving Blocked OS CFP
[3] [8est:58:28:929] [CfpProgrammer] [0x00002f9c] [CfpProgrammer.cpp:1143] Got Blocked OS CFP
[3] [8est:58:28:929] [CfpProgrammer] [0x00002f9c] [CfpProgrammer.cpp:1143] Getting the Device PIN
[3] [8est:58:28:929] [CfpProgrammer] [0x00002f9c] [CfpProgrammer.cpp:1143] Got Device PIN
[3] [8est:58:28:929] [CfpProgrammer] [0x00002f9c] [CfpProgrammer.cpp:1143] Getting the Device BSN
[3] [8est:58:28:930] [CfpProgrammer] [0x00002f9c] [CfpProgrammer.cpp:1143] Got Device BSN
[3] [8est:58:28:931] [CfpProgrammer] [0x00002f9c] [CfpProgrammer.cpp:1143] Corrupting opposite QNX partition 1, on archive load
[3] [8est:58:28:980] [CfpProgrammer] [0x00002f9c] [CfpProgrammer.cpp:1143] Programming Flash. Filesize: 1834156032 total bytes
[3] [8est:58:39:751] [CfpProgrammer] [0x00002f9c] [CfpProgrammer.cpp:1143] Command failed due to timeout
[1] [8est:58:39:753] [CfpProgrammer] [0x00002f9c] [CfpProgrammer.cpp:859] cfp operation failed (15): "Device communications error encountered. [A:0x0000000F]
Please try the following:
- Disconnect your device and restart your computer.
- Restart the loading process."
[1] [8est:58:39:753] [QnxProgrammerHelper] [0x00002f9c] [QnxProgrammerHelper.cpp:288] CFP::LoadQCFMFile failed. Error: F
[1] [8est:58:39:754] [QnxProgrammerHelper] [0x00002f9c] [QnxProgrammerHelper.cpp:322] WriteModule OS failed.
[20] [8est:58:39:757] [Loader] [0x00002f9c] [Loader.cpp:877] Switching connect state from 3 to 0 (timeout 15000 ms)
[20] [8est:58:39:757] [USBEnumManager] [0x00002a20] [USBEnumSerializer.h:66] Lock requested, maximum wait = 180000 ms
[20] [8est:58:39:757] [USBEnumManager] [0x00002a20] [USBEnumSerializer.h:70] Lock acquired
[3] [8est:58:39:757] [CfpProgrammer] [0x00002a20] [CfpProgrammer.cpp:1143] Requesting BootImage Exit

HP Photosmart C4380 [8A36CB] communication error with MacBook OS 10.7.5 over wireless

Hi,
I keep getting the message 'communication error' when trying to print wireless to a Photosmart C4380 from my MacBook (OS 10.7.5) through a TimeCapsule 2Gb router.
The message also says: "/usr/libexec/cups/backend/dnssd failed" but I don't know what to do with it...
I tried to de- and re-install, restart laptop, printer and router and pull all plugs in different sequences, first use the USB cable to install wireless and all other help from HP ... but nothing seems to work (HP Doctor is not available for Mac).
The strange part is that:
1.it started a couple of weeks ago, without having changed anything (by my knowledge),
2. printing from my iMac works fine (same wireless network, same software version, same settings, etcetera)!!!
2. printing over USB from my MacBook works fine
3. I can print a test-page from "HP Utility" form my MacBook (and of course from my iMac but that one works fine anyway)
4. I can access the printer through "http://hp8a36cb.local./index.htm?cat=info&page=printerInfo" and there are no issues mentioned whatsoever,
5. the 'HP Network Configuration Page' and the 'Wireless Network Test Report' congratulate me on the successful setup of my wireless printer... but it doesn't work.
I've read almost all posts about communication errors over wireless but haven't found an answer to my issue (yet).
Is there anyone with a solution? Please??
This question was solved.
View Solution.

Download and install this: http://support.apple.com/kb/DL907
Restart your Mac.
Reset the printing system:
- Go to System Preferences > Print & Scan
- Right (or control) click in the rectangle listing your printers and select Reset Printing System.
WARNING - this will delete ALL of your printers!
- Select the plus sign to re-add a printer. Select the Defualt tab on the top of the window. Look for the printer, select it and then next to the "Use" pulldown, select the printer model (not AirPrint). Wait until the "Add" button becomes available. Click it.
Say thanks by clicking "Kudos" "thumbs up" in the post that helped you.
I am employed by HP

Serial communication works in hyperterminal but not in LabView

Hello,
I am trying to control an APP Automated Pressure Controller using LabView 6.1 via a serial connection. I am able to control the system with Hyperterminal but not with LabView. I set used the same setup (9600 baud, 1 stop bit, no parity, no flow control, etc) in LabView that worked in hyperterminal.
According the the documentation from the Pressure Controller: "Every character that is sent to the controller is echoed back to your computer so you can check to see everything is working. When a valid command is given, the controller will also send a carriage return (acsii 13) followed by a line feed (ascii 10) to signify the command was executed. Before sending any commands, the program should clear any characters in the input buffer that may be there from previous responses."
In hyperterminal, when I type in a command such as "OA", the Pressure Controller responds (without pressing enter or any other keys) and I can see the "OA" on the screen. As soon as the Controller is done responding, the cursor moves down to the next line (which I assume is caused by the carriage return and line feed) and waits for the next command.
I have tried to use the Serial Communication.vi with no success. Does Hyperterminal add (or Labview omit) a special character or command that I am missing? Do I need to do something special to clear the input buffer in LabView?
Thanks for any help.
Alex

Hello,
Try to run your application in other system (computer),
frequently some PCs configurations are not recognized by LabVIEW serial
routines. I do not know exactly the problem but is not the first time I know
that kind of problem.
Sometimes the problem comes from the serial property called
Termination Character that enables receive buffered data once you have a
Carrier Return or a Line Feed symbol (Hex 0D/0A) character into the buffer. Try
to set it true and assign a 0A Hex Value.
For sending information you need to finish all command
message with an enter symbol concatenating both (Message + Hex 0D0A) using the
special character in the string palette library. This action permits system to
put out buffered data.
Good Look

Serial Communication(CAN) of Floating Point Numbers

Hi,
I have ran into a situation were I need to use floating point numbers(IEEE Floating Standard) when communicating. How can I send and recieve floating point numbers? What converstions need to be made? Is there a good resource on this?
Thanks,
Ken

Hi K.,
in automotive a lot of fractional values are exchanged via CAN communication, but still the CAN protocol is based on using integer numbers (of variable bit size)…
We are thinking we need to use single SGL floats ... that require a higher resoultion and precision
What is the needed resolution and "precision"? SGL transports 23 bits of mantissa: you can easily pack them into an I32 value!
Lets make an example:
I have a signal with a value range of 100…1000 and a resolution of 0.125. To send this over CAN I need to use 13 bits and scale the value with a gain of 0.125 and an offset of 100. Values will be send in an integer representation:
msgdata value
0 100
500 162.5
501 162.625
1000 225
5000 725
7200 1000
The formula to translate msgdata to value is easy: value := msgdata*gain+offset.
Another example: the car I test at the moment sends it's current speed as 16 bit integer value with a range of 0…65532. The gain is 0.01 so speed translates to 0.00…655.32 km/h. The values 65533-65535 have special meanings to indicate errors…
So again: What is your needed resolution and data range?
Another option: send the SGL as it is: just 4 bytes. Receive those 4 bytes on your PC as I32/U32 and typecast them to SGL…
Best regards,
GerdW
CLAD, using 2009SP1 + LV2011SP1 + LV2014SP1 on WinXP+Win7+cRIO
Kudos are welcome

Scheduled Delivery communication error

See the post at this link: If your Scheduled Delivery apps stopped printing
I work on behalf of HP.

Hi gailina,
To assist you further on the issue please give me the details of the printer and when do you get the error code.
Regards
Aneesh
Although I am an HP employee, I am speaking for myself and not for HP.
--Say "Thanks" by clicking the Kudos Star in the post that helped you.
--Please mark the post that solves your problem as "Accepted Solution"

Serial Communicat​ion Error -107380725​3

Similar Messages

Maybe you are looking for

Serial Communication Error -1073807253