Several Serial Comms

Similar Questions

• Hardware handshaking, originally a serial comm problem?

  Hello...  I posted a little different but related question a few days ago, when I had no success at all communicates with a vapor deposition rate controller Cygnus of Inficon.  What I discovered, was that I couldn't communicate at all at 19 200 same baud if that was shown in the manual Cygnus as an acceptable rate.  I got sporadic readings at 9600 baud, and found that I had to go all the way up to 2400 baud to get a READING/WRITING/waiting Seraglio whenever I asked a (once every 10 seconds)...  I also found that I had to increase the time between WRITING and READING of an original of 100 msec to 500 msec to be able to capture the entire message (rather than just a part of it) every time that... So now we run labview code that captures the data of this instrument once every 10 seconds for hours and hours...  And the news is not yet as good as I had hoped...  What I see now, is, perhaps, one in every 20 readings is completely wrong...  The message that I will be back to the serial port is a long string of digits HEX that I then analyze in a way known to extract four relevant parts of digital data...  I have then that plot the data and send it also to an Excel spreadsheet...  The numbers that all directions until one of these erroneous readings happen to be a number which is always between-100 and + 100, it will be rather something like 5.7E + 38...  And when one of the four readings is bad, they are ALL wrong, which means that the reading series (or perhaps writing series?) was corrupt...

  I used a very similar code to extract information very similar to an another Inficon Vapor Deposition rate controller (model SQC310) running at 19 200 baud and had zero problems...  I contacted Inficon yesterday and all that they have said so far is that the "the 310 does not use handshaking HW for communication" (the implication being that the Cygnus should use those handshakes) and he went on to say that...

  "It is possible that his LabView application cannot be configured to use HW handshaking.  Have him check his application for the HW handshake settings.  It can cause the Cygnus to become confused if it is not activated or properly initialized.  He may also want to try the simplified 2, 3 and 7 (possibly to pin 1) cable for the Cygnus.  It would eliminate his lines of communication of handshaking HW and solve its problem of communication. »

  Of course, I am not knowledgeable on how to correctly configure this handshake...  I have communicated with several instruments using VISA series WRITING and READING the thread of years and for the most part, you set baud rate, number of bits of data, stop bits, what kind of parity and control flow, if any and GO...  It's just worked...  It's my first experience with an instrument that will not work with the LabVIEW code...

  First of all, I guess I have set up or at least would check handshaking through a property node (yes/no?)...  Anyone can present my views on how I could verify this?  Second, observations on their tips above I am building a cable series that just TX, RX son and mass to ensure that the hardware handshake lines are not yet hooked?

  INFICON told me they use some executable owner in the House to talk with the instrument of Cygnus series and they are not well informed and are suspicious therefor, LabVIEW is causing communication problems I saw of my...  I, however, worry that instrument, although currently made and rather expensive (4 times the cost of a SQC310) is based on ancient technology (he has a floppy drive on the front and "monitor" is a screen of CRT type that takes a number of seconds to 'warm up' and 'activate' when you turn on the unit first...

  Any ideas or advice on material transfer protocol or if you think that it would be a reasonable step to "cut the wires of the handshake" on a special serial cable would be very appreciated...

  The unit of Cygnus is available on the link below (you can also download its manual on this page)

  http://www.inficonthinfilmdeposition.com/en/cygnusthinfilm.html

  Thank you very much... bob...

  Some USB-adapters series do funny things with the handshake lines.  I had one several years ago which said only the lines of the handshake then that he was transmitting a character and released between the characters.  The device with which I tried to communicate has got very confused because it expected of these lines be invoked unless an interruption of transmission was actually necessary.  This behavior was not documented in the manual or on the website of the manufacturer of the adapter.  So, if you decide to try to use the handshake, check what actually makes your card.

  Lynn

• Several serial numbers

  Hello community,

  TestStand 2014 32-bit

  I currently have a file of sequence of work that scans a unique barcode and records the serial number on the report using "Locals.Barcode is RunState.Root.Locals.UUT.SerialNumber". It then records the serial number to a database using schema for the treatment of the results.

  Whereas before I was testing only a single control, now in my file sequence I need to test 10 control both. Each control has a different pass/fail result and the serial number. I want to be able to scan all 10 bar at the beginning of my sequence codes. Then, run by the test of success/failure of my 10 witnesses. In the reports have all the codes bars as well as their control. In addition, for each barcode with the result of the control connected to my database.

  How can I go to what I already have for a control, but with 10 controls in a single sequence file?

  Is 'control' a synonym for the unit under Test?

  If so, you want to model parallel or batch to create 10 Testsockets. Each medium presents a single DUT (unit under test, synonym of unit under test, use). Please note that your sequence should be prepared for the parallel execution, which means that shared resources must be protected and synchronization between struggling might be necessary.

  Norbert

• Modbus Library for serial comm.

  I downloaded version 8.2 of labview libray and tried to use the serial port to test the provided example of master/slave...

  For some reason any null-modem solution does not work for me (I tested with success of communication RS-232 example)

  P.S. I get timeout on reading...

  Any comments will be appreciated

  Greetings,

  Jack

  
  

• CS5 student creation: how to find and reinstall several serial

  HI, I have a new coumputer and stll have the disc and the box for this CS5 version. I am a student in my master.  I would use it on her.
  Where can I get the nuber series.

  I have not registered the product when I bought it!

  If you have not kept track of your serial number when you installed before, as well as your number does not show on your page ID (go to https://accounts.adobe.com/ then click on Plans & products at the top) I know no other way to help

  You have a redemption http://helpx.adobe.com/x-productkb/global/redemption-code-help.html Code

  - and https://forums.adobe.com/thread/1572504

• interruptions and serial Comms

  I collect data from a number of devices using RS485.

  Data collection is initiated by a request message sent from the PC to the device and a message is displayed.

  I need "divorce" the transformation data collection, and to this end, I tried using multithreading.

  It works to a certain extent, but the change of context seems to take too long.

  Data throughput is 115kBaud, messages are ~ 8 bytes for the request and ~ 30 bytes for the answer.

  There are up to 32 devices, and I need to acquire every 5 times per second.

  (This is equivalent to 5 * 32 * (8 + 30) = 6080 bytes 60800 bits every second.)

  This is feasible at a baud rate of 115 k baud rate, with about 53% of the use of the communication channels).

  To make this work correctly, I need to be able to "hang" for interrupts generated by the device drivers for transmit them and receive so that the passage of shipment to receive can be achieved with minimum latency.

  Maintenance of data for to transmit them and receive would not take too long, even if done on each of the characters.

  Is this possible without the need to write a device driver?

  If Yes, how would you please.

  I didn't program anything in RS485, but have you tried the function for InstallComCallback?  There you can set different reminders for the different characters received.

• Tecra M11 - 17V - identify the serial port on the docking station

  I have a laptop Toshiba Tecra M11 - 17V, which I often use with the docking station that accompanies it.
  There is a DB9 serial port at the back of the docking station, but I don't know what COM Port.

  I use Windows 7.

  In the device, COM9 Manager - COM22 are identified as Port BT (bluetooth). Com7 - COM8 are RIM Virtual Serial Port v2, COM17 is Prolific USB-to-Serial Comm Port and COM18 is USB-Serial CH340.

  I thought that COM17 or COM18 were the most likely candidates, but have not been able to get to answer using one of them.

  I connect a Psion 5 (Comms app) to him and have developed ports and the Psion 8bits, 19200 baud, no parity, 1 stop bit.

  Hello

  > There is a serial port DB9 on the back of the docking station, but I don't know what COM Port, it is

  I think you have misunderstood something wrong
  COM ports in Device Manager are virtual com ports
  There is no link between a serial port and a virtual com port.

  I have a question: what docking station you have exactly?

  I had an express port replicator and this device required an additional serial port driver installation.

• Problems with the simple serial communication.

  I followed a tutorial online to start learning basic communication series. The involved tutorial shorting pins 1 and 3 on port 1 Comm and write a simple program (attached). I've edited it a bit, the program to see varied results I get when trying to write and read a simple sentence via a serial port.

  Could someone explain what causes the kind of result shown in "Serial Comm example.png"? I think it has to do with timing. Why would be transmitted only the parts of the sentence?

  Thank you

  Sarah

  sarahzig wrote:

  The involved tutorial shorting pins 1 and 3 on the Comm 1 port

  What should be pins 2 and 3?  On a standard serial port DB-9, pin 2 is the receive and pin 3 is the transmission.

  Now for your code...

  1. move the Serial Port to be before the loop to set it up.  Simply configure the port once.

  2. close the port after the loop.

  3. managing your error after closing.

  4 stop your loop on an error or the stop button has been pressed.  You will need a RC in there.

  5. no need to Flush Buffer function.  Remove it.

  6. using the bytes to the Port is a dangerous thing.  It introduced all kinds of race conditions that are interesting.  Instead, say VISA reading to read the number of bytes that you expect to read.

  6a. Moreover, don't forget to send a character to end of line at the end of your data and all the number of bytes to read something a lot more than you ever expect read.  The VISA read will stop reading when he a) sees the number of bytes, it was said to read, b) sees the stop character (currently enabled and set to a line break, which is part of the end of line), or c) the time-out occurs.  Whichever comes first.

  7. with 6, the wait is no longer necessary.

• too many comm usb ports

  Hello

  I ran into what may be soon, where we test units that have built in USB ports that appear as serial comm ports. The problem is that whenever we connect to an object that has not been run on this computer until Windows assigns it a new com port number to measure. My concern is that fast enough, as the production line is in full swing, we will hit the 'magic number' of 255, the highest number of com port and I have not any idea that Windows will do at this point. Before you begin to write the code to analyze the new com port number returned by VISA and adjust"registry entries accordingly, I want to know if it's necessary. I think there are a couple of possible scenarios, Windows complains and it won't deliver a com port #, that Windows starts from the beginning, or that Windows strikes only 255, then keeps the front it. I'd rather it be at least two, won't my program messing around in the registry and really have no time at the moment, nor access to the machine (s) to experiment to see.

  Thank you

  
  

• initialization problem multiple serial

  Hello all

  I have attached a vi that gives me a problem I cannot solve and would appreciate any help.

  The vi is supposed to intialise up to 7 ports series (only using 5 at the moment), and I guess that's a plausible way to do initialization (maybe wrong). The serial ports are connected to a pc via a usb hub. The windows XP operating system recognizes the Device Manager ports.

  The problem is that when the vi is executed, the following error is reported as shown in the word document attached.

  I compared the port settings in the properties in Device Manager for each port to the vi settings, and they match. What can we do?

  If anyone has a configuration with several serial ports could try the vi and see if it works for them?

  Thank you and best regards

  Ray

  It has nothing to do with several serial ports.  This has to do with an invalid parameter, you are trying to use it to configure one of the serial ports.

  Look at the information in the error message.  Point 4 of the property node to configure Serial Port VI is the setting of Stop Bits.  I see a point of stress goes in this VI, then that tells me the type of data in performing connections does not quite.

  You have an array of values of I32 and your values are made up of 1.  Disconnect this table and right-click on the terminal to configure Serial Port VI and choose Create Constant.  You'll see you get a data type of ring.  It's a U16.  But if you look at the items in there, you will see that the stop bits 1.0 has a value of 10.  1.5 has a value of 15, 2.0 has a value of 20.  If the value of 1 has no meaning to this property node and you get an error.  You should be wiring in a value of 10.

  Delete this table.  Create a table of constants in the ring.  Turn it into a control, and then choose the value of the correct ring for each item in your table.

  You have several other points of constraint.  They may not cause problems, but I consider disconnect them, create a constant of the correct data type and that using the table that you wire to configure Subvi.

  I have modified your VI and attached to it.  See if it works for you.

• The port adapter driver prolific PL2303 USB-to-Serial fails to install

  I am installing a cable adapter USB - to - Serial-PL2303 prolific port 1 '. This is done by cutting. It seems that many people have not all the problems, and they have XP, Vista and Win7 drivers available for it. I downloaded the latest installer for the Vista driver from the prolific website (http://www.prolific.com.tw/eng/downloads.asp?ID=31, 02/12/2009). The driver said that he installed. I then perform a restart. After the system is installed, I plugged the cable. Windows detects I inserted the USB key and displays the dialog box drivers you are looking for. Weird, I thought. I click to observe the Statute and it ends with the message:

  "USB prolific to serial comm port (COM4) - failed".

  In Device Manager, it shows an exclamation mark next to it. If it's a Vista driver, why it fails? What can I do to get this install?

  I also have another Vista machine I tried on, just to see if it was this machine or what. She doesn't have too!

  Thank you

  Thanks for the quick response. I was not the installation as the link "Run as Admin" as a first step, even if my account has administrator rights. But yes, so I started to do this, no change.

  However, I am happy to say that I found the problem! After the announcement, I did a search in these forums and came across another post that had a lot of comments... someone in whom we posted a link to the drivers that I had not tried. The thread is here: http://social.answers.microsoft.com/Forums/en-US/vistahardware/thread/a366f74b-9853-4cae-95c3-4249172951da .

  Drivers Vista cooldrives (http://www.cooldrives.com/wividrforprc.html) did the trick! I have no idea of the lineage of this package, but they worked. And they worked when those on the supplied CD didn't; When those on the site Web of the card does not, and when those prolific site does not.

  Thank you

  Tom

• drivers for USB to serial port cable

  I am trying to install drivers for a USB cable to serial port on a HP Pavilion dv7 laptop (Windows 7) - I go through the download and when I plug the cable of the toolbar displays a sequence of installation but then an error of installation failed. I tried all sorts of updates and Windows says that it cannot verify the signature of the device.

  Would have been nice to know exactly what you had already tried :-)

  I do not know what adapter you are using, but I have a Trendnet TU-S9 that I use to connect my OBDII code reader to my PC, so I can save the CEL errors that I receive on different vehicles. I thought I had the drivers for it installed, but I have not (could not even find on a HARD drive). But I plugged it in just to see what happened. The message was that no local driver could be found, I wanted to try Windows Update? I said yes, and installed a "Prolific USB - to - Serial Comm Port (COM3)". Plugged the code reader, started the PC-Link software and here!, everything was good.

  You could try to uninstall anything that you have already installed, restart, then connect the adapter and see if you have the same success. I use Win7 HP x 86, but Vista should at least try to do the same thing, and who knows, it might work :-)

  SC Tom

• Said device USB to serial port Manager works, but it is not

  Original title: PL2303 USB to Serial No. GB
  My laptop is running Windows 7. I loaded the drivers PL2303. The Manager of said devices usb-serial comm port works. Set at 9600 baud, 8 No 1 order no flow.
  The GPS is a Garmin etrex Euro software version 2.06. GPS version model 156 206.
  I communicate successfully with the GPS unit via an DB9pin port at the back of my office. 9600 8 No 1 Garmin format.
  When I added the USB cable series to communicate via a usb port the "EasyGPS'program cannot read the GPS.

  I down loaded the PL2303 drivers for my desktop (XP) and the same problem occurs.

  I get the message ' device working properly "for both laptop and desktop."
  There is however no communication to the GPS.
  I tried again via the DB9pin port and communication are OK.

  Any Suggestions
  Thanks, Jim

  Hello

  I suggest you to join easygps helpdesk on this issue.
  www.EasyGPS.com/support.asp

• Serial communications port unusable - that makes Vmware Player useless for me.

  I have installed XP Professional DVD original (inside Windows 7 Home premium), but although XP seems to 'see' the Serial Comm port, the application is not.

  This request is Picstart16C old 16-bit software (1994) running in DOS mode (console) that attempts to communicate with a device so Assembly code to program in the internal EEPROM to a microcontroller.

  In fact, I tried two different devices and software and none could communicate via the serial port.

  The motherboard is the Gigabyte G41M-Combo.

  Any ideas?

  You try to use COM1 for Serial Port?  If so, the question may be a conflict with ThinPrint (printer under hardware in the settings of the virtual computer) like it by default uses COM1.  If stop you the virtual machine, remove the Serial Port and printer and then add the Serial Port back and set it to COM1 if you need printer host then crosses the prompt add printer after a Serial Port must set the printer to the COM2 port.

• Satellite Pro L100: USB2 drivers do not have compatibility with Win XP

  SAT Pro L100 - I loaded the USB 2 drivers received using a prolific USB to Serial Comm Port (Sunix - UTS1009B) a single port USB to serial port cable.

  In each instance of loading the drivers message appears "did not the Windows Logo test for compatibility with Win XP. If continue or stop, drivers do not work.

  Seems as if there is a problem loading the USB 2 drivers. need assistance?

  Expensive branded

  That s nothing unusual.
  Many 3rd party drivers have not been tested by Microsoft and the message appears so that the pilot didn't make the Windows logo test for compatibility with Win XP!

  But if you use a driver that was designed for Win XP, you just continue and finish the installation.

  So, don t worry not and follow these steps!

  Best regards