Communication failure

My printer used to print properly until 15 days ago. Now everytime i try to print something I get the error message "
Communication Failure: The computer is no longer able to communicate with your printer. Turn the printer off, check your printer connections and check for printer errors, and turn the printer back on.
Paused."
I tried everything follwing the same steps I found in the support comunity regarding the same error but no success! Please help!

Hi Renata1974,
Welcome to the HP Forums!
I understand that you are getting a communication failure with your printer, and I am happy to help you with this communication issue!
For further assistance, I will need to know:
The Product/Model Number of your printer. Follow instructions in this link. Finding Your HP Product Model Number.
If you are using a Windows or Mac Operating System. To find the exact version, visit this link. Whatsmyos.
If the printer is connected, Wireless, Ethernet, or USB.
If the printer is able to make copies by itself.
If the power cable plugged into a surge protector, or directly to the wall outlet. Issues when Connected to an Uninterruptible Power Supply/Power Strip/Surge Protector. This applies to Inkjet printers as well.
In the meantime, if you ar eusing Windows, please try our HP Print and Scan Doctor, and let me know what happens.
Hope to hear from you, and have a great day!
RnRMusicMan
I work on behalf of HP
Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
Click the “Kudos Thumbs Up" to say “Thanks” for helping!

Similar Messages

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!

TCP communication temporarily dies

Hi There
Im using TCP to communicate between my ARM processor and PC. However, the communication sporadically dies for 3 to 4 seconds and then resumes, as shown in the Task Manager Networking (attachment 1) . This happens with the simplest of test programs, as shown in the attachments, and no delays or sequences seemed to solve the issue.
After some duration the communication dies completely with error code 66.
What is causing the delays in communication and is there a fix for this?
Attachments:
simple TCP failure.jpg ‏527 KB
Simple Server - ARM.jpg ‏72 KB
Simple Client - PC.jpg ‏74 KB

Hey,
What kind of delay did you add into the VI? it sounds like a pretty classic case of reading and writing TCP too fast. You may want to take a look at this article: http://digital.ni.com/public.nsf/allkb/4CB799F36D0EA56A862576200064B2F9?OpenDocument
Regards,
Eric L.
Applications Engineer
National Instruments

It's better or necessary open and close communication with instrument every loop?

I must communicate with my instrument, but I must change its value, for example temperature, every loop. See the Figure to understand:
I think that it is better if I open communication with my instrument out of while loop so I many operation: if I put Open VISA in While loop I open VISA session every loop, instead I think it is not intelligent. Can I open VISA SESSION out of the while loop or it is an error for EXCELLENT LABVIEW VI and I must open and close VISA SESSION every times I must talk (and set) with instrument? What is the better way?
Message Edited by Michelle1892773 on 02-22-2010 02:00 PM

Something like this?
I do have to say, i don't know what is happening in the false case of yours, but if nothing happens with the 100 that is wired to the shift register, once you enter the true case, the value in the shift register will always be great than "i". You might as well do what I have done then. However, if something does happen with that number in your false case, then keep it the way you have it.
That being said, why is the condition there to see if it has looped 100 times before doing the visa write??
Message Edited by for(imstuck) on 02-22-2010 04:45 PM
Message Edited by for(imstuck) on 02-22-2010 04:46 PM
CLA, LabVIEW Versions 2010-2013
Attachments:
visa.PNG ‏13 KB

How to implement Modbus Ethernet communication in Lookout, if we want to simulate the PC as PLC ?

Problem Description :
Dear Sir,
We are doing a project where we are using Lookout with
Front end Modicon PLC. The communication is by
Ethernet, using Modbus.
Since the installation is at a distant place, we wanted
to use another PC (running Lookout) to simulate the
PLC. For this, we tried to communicate
a: the server Lookout PC running Modbus Ethernet mode of
Modbus object as Master
b: with another PC (for simulating the PLC) running
Modbus Slave
We did not get any communication. (we have given the
details of what we have done, at the end of this email)
We also tried connecting the above 2 PC's as
a: the server Lookout PC running Modbus Serial mode of
Modbus object as Master
b: with another PC (for simulating the PLC) running
Modbus Slave object
Again we did not get any communication.
If instead of PC (b) we connect the Modbus simulator to
PC (a), there is no problem in communicating
Please let us know how to go about establishing the
communication between 2 PC's using Modbus serial,
and Modbus Ethernet. A detailed step by step procedure
would help us a lot.
Thanking you
Warm Regards
Raja Mahbubani
Procedure of our trial with ethernet.
This is what we have done in detail.
On PC A:
We created an object (Pot) and connected it to
the modbus data member of the modbus object say 40001. In the
properties of the modbus object we selected modbus ethernet mode
of communication and in the IP address field we wrote the IP
address of the machine B to which we are trying to communicate
i.e. 152.63.50.2.
On PC B: we tried the following two methods
Trial 1 : We created a modbus slave object and
inserted an expression for the same data memeber to which the
object was connected hoping to get the value of the pot of machine
A on machine B.
Trial 2 : We created a modbus object on machine B and we wrote
the IP address of machine A and inserted an expression for the
same datamemeber to which the object was connected hoping to get
the value of the pot of machine A on machine B.
NI Software : Lookout
Version : 4.0.1 or 4.5
OS : Windows 98
NI Hardware : N/A
Drivers : N/A
Other Hardware/Instruments : N/A
CPU : Pentium
RAM : 64
Vendor : S-Tech
Customer Information :
Raja Mahbubani
Theta Controls
IN
[email protected]
Ph: (+91) 20 4222556/7

The ModbusSlave which comes with Lookout currently supports only Serial communication. So, you cannot use Ethernet between your two PCs. At least not with Modbus Master-Slave setup (if you must speak Ethernet between the two PCs, IPASCII object lets you do that, but then you'll need to implement your own protocol).
Since all you want to do is simulate a Modbus PLC on a PC, you can use the Serial mode of communication for now. And later on just modify the Object in your Server Lookout to use the Ethernet mode.
For setting up a Serial Modbus Slave, use a null-modem cable between the two PCs (lines 2 and 3 are swapped). On your PC 'B,' create the Modbus Slave object with the right COM port for that PC. And on your PC 'A' create the regular Modbus Object as if you w
ere connecting to the Modbus Simulator box. The only difference here is the cable. The simulator box uses a straight-through cable whereas the Slave needs a null-modem cable.
Hope this helps.
Rgds,
Khalid

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)?

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

MAX communication hangs after Standby Mode(with GPIB PCMCIA)

I have a IBM Laptop with MAX 2.2 and a GPIB PCMCIA Card installed. After booting the computer I can communicate with GPIB instruments without problems. After I get the Laptop out of a Standby Mode, MAX can not make any connection to GPIB devices; when I scan for Instruments it hangs as well.
The troubleshooting wizard tells me: one or more GPIB interfaces failed.
Does anyone have the same problems or solutions ?

On the NI-488.2 2.0 download page it is mentioned that that driver does not support standby mode. No such mention is made on the download page for NI-488.2 version 1.7 (which I need to use for my PCMCIA-GPIB interface), although the 1.7 release shows very much the same problem: After stand-by, communication with the GPIB port is no longer possible.
The Visual Basic example tool for preventing stand-by may help those users who are familiar with VB, but it does not help me.
Frankly - what I'd like to see is an improved NI-488.2 version that does support stand-by. Does NI consider providing such an upgrade/patch?

I have problem with communication bethween 2 computers

hello
i have problem with communication bethween 2 computers
On the firs computer i have installed OPC server from unitronics . In this case i communicate with my lookout process.
On the second computer i have installed only lookout.
This 2 computers are connected with a VPN whireless .
The second computer command the device from the first .
My problem is : After 10-14 hours comunications bethween computers is blocked . If i restart the first computer comunication begin to work.
How to solve this problem , i don't want to restart every 10 hours the first computer
Thanks in advice

1) Are you able to verifiy that the VPN connection is still active at the time of the loss of data? There may be a timeout in the VPN system.
2) Is there any time out n the OPC server?
3) Is there sufficiient memory on the first computer?
Robert Hill
Technology and Security Advisor

Intensity plot and MSnode-window communication

Two questions:
1) Is there an intensity plot function that can be called from the mathscript window to display 2D arrays (such as a grayscale image), similar to the matlab function "image" or "imagesc"? The only options I saw were to display a 2D array on a 3D plot. Yes, I know the intensity plot is available in the variable display window, but I would really prefer a command-line option.
2) When I wire a variable to a matlab script node and run the VI, that variable becomes available in the matlab command-line window. I find this very convenient. Is it possible to do this (or something like this) with the mathscript node and window? I know I can communicate between the node and window with globals, but I have to go through the trouble of defining globals, and this only works if I create a project for my VI, which is just far too much overhead.
thanks.

Hello,
In response to your first question, we currently do not have such a function. However, such functionality is on the roadmap for a future release. As for the second question, each MathScript node is currently sandboxed -- that is, it has its own variable space. This was done so that there is no variable collision between different MathScript nodes. We will be improving the interaction between the MathScript node and the MathScript Window in the future and your suggestion is one idea we are considering. It would most likely be an option on the node and not enabled by default to prevent any variable collisions.
You do not need to create a project in order to use globals to share data between the MathScript node and the MathScript Window. However, the MathScript node and the MathScript Window need to be in the same application instance. Thus, if you are already using projects, make sure you launch the MathScript Window from the same project in which your VI is located. If you are using the default application context (no projects open), then you should be able to share a variable "a" between a MathScript node and the MathScript Window by typing in each:
global a
Grant M.
Staff Software Engineer | LabVIEW Math & Signal Processing | National Instruments

Usb communication

Hello,
I wonder if it is possible to communicate with a microcontroller and a computer using usb. De controller had the usb function on board. I just wonder if it is posible with labview to show the data transmitted over the usb port.
Can someone tell something about it?
Tnx for helping me

VISA manual
Instrument control Tutorial
Instrument Control with the USB Hardware Bus
You could have found this info by searching the NI website.
Regards,
André
Using whatever version of LV the customer requires. (LV5.1-LV2012) (www.carya.nl)

SEVERE: com.mysql.jdbc.exceptions.jdbc4 : Communicat link failure

Hi,
I am developing web application using jsf2.0. problem is ,
when we interact with servlet by single person, It working fine. but when we interact with servlet by more then one person at same time. server throws error
SEVERE: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure
Last packet sent to the server was 0 ms ago.
How to solve the problem.
server :Glashfish v3
db :mysql 5.0
thanks in advance.

You must use a connection and then immediately close it.

Using existing c code for usb-hid communication in labview

Hello,
I want to write a simple temperatrue logger using labview and a external hardware which communicates over usb-hid. The external hardware uses an ATMEL 90USB162 µC and DS18B20 sensors.
Link to the hardware:
http://www.diamex.de/dxshop/USB-Temperatur-Sensor-Tester-fuer-DS18B20
The source of a a simple command line tool is available (see attachement), which reads out the temperature value of the connected sensors.
Is it possible to include this c-code in the labview application to simplify the communication?
Thanks a lot and best regards,
Michael
Solved!
Go to Solution.
Attachments:
CMDLINE.zip ‏17 KB

I'm not that experienced at this personally (in terms of compiling C code into DLLs), but I believe the process you need to go down to call your C code in LabVIEW is to compile the C code into a DLL which you can then call from LabVIEW using a Call Library Function node (or you can try to use the "Import Shared Library" wizard to automatically generate SubVIs).
There's more information here:
http://digital.ni.com/public.nsf/allkb/DCB90714981A1F148625731E00797C33
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

Omron (CQM1-CPU45-EV1) PLC communication and control

hi,
we have an Omron(CQM1-CPU45-EV1) PLC with RS 232C communication connected to instuments for control and monitoring of an aplication.
Unfortunately our old pc broke down and now we have to set up thisPLC with a new labview interface.
I'm not an experieinced Labview user i would need you help (tutorial) how to communicate the Omron PLC with the labview and how to acquire data and control the application.The task is somehow urgent so i would appreciate advice at your earliest convenience.

PLC Communications with Labview

How do I view and record data from my plc to labview, currently we are using autmation directs DL205 with the 260 processor

If the DL 205 communicates through the Modbus protocol, you could use the Modbus library. This library consists of a bunch of VIs which can be used for Modbus communication. Think of them as advanced Serial read/write VIs. However, if you are looking into monitoring, datalogging and controlling the registers, then I would recommend the LabVIEW Datalogging and Supervisory Control Module. Using shared variables, you can then easily bind, control and talk to the registers and most of the work is taken away from you.
If the DL 205 doesn't communicate throught the Modbus protocol, then you would need an OPC server (like the NI Industrial Automation OPC Servers) and the LabVIEW DSC Module. You can then communicate from the LabVIEW DSC Module with the OPC server.
Message Edited by Adnan Z on 03-15-2007 10:27 AM
Adnan Zafar
Certified LabVIEW Architect
Coleman Technologies

Communicat​ion failure

Similar Messages

Maybe you are looking for

Communication failure