How do I establish serial communication using LabView to two stepper motors using a motor controller?

I currently use an off the shelf motor controller to run my two stepper motors. It already has integrated a firmware software that sends commands to operate each motor. I would like to create an interface where I can send these commands using LabView. If someone can point me in the right direction I would appreciate it.

Look at the examples for the serial VISA vi. Something like Basic serial write and read.vi is a good starting point.
Have you searched for a LabVIEW driver at the NI LV driver network? Asked the vendor?
If you write your own driver with the serial VISA vis remember to open and configure the port only once at the beginning and close it at the end of your program.
Message Edited by Henrik Volkers on 07-13-2009 04:21 PM
Greetings from Germany
Henrik
LV since v3.1
“ground” is a convenient fantasy
'˙˙˙˙uıɐƃɐ lɐıp puɐ °06 ǝuoɥd ɹnoʎ uɹnʇ ǝsɐǝld 'ʎɹɐuıƃɐɯı sı pǝlɐıp ǝʌɐɥ noʎ ɹǝqɯnu ǝɥʇ'

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.

How do I troubleshoot installation/distribution of a LabVIEW .exe which processes data using Matlab when it works on some computers but not others?

I've been given the unenviable task of troubleshooting and installing/distributing software written by a former co-worker. I've modified the LabVIEW code and built an .exe file. I've successfully installed the Labview .exe file on several computers, but it won't work on some others. What's more baffling is that I installed it successfully on one computer, uninstalled it, and tried reinstalling it with no success. In fact, it's a new error (Dr. Watson for Windows NT application error). It doesn't help that I have different versions of LabVIEW and Matlab on the target computers. Some have LabVIEW 5.1, some
have 5.0, and some don't have it at all. Some have Matlab 5.2, some have 5.3 (R11) and some have 6.0 (R12). It's also not clear to me where the Matlab m files should be located. I'm not sure if it's a LabVIEW Runtime Engine problem, or if it's a Matlab problem. I've also wondered how LabVIEW and Matlab talk to each other. When LabVIEW calls Matlab, it seems that Matlab is running in the background. In other words, clicking on the Matlab Command Window and typing "whos" or any other command/variable doesn't work.

Jay del Rosario wrote:
>
> How do I troubleshoot installation/distribution of a LabVIEW .exe
> which processes data using Matlab when it works on some computers but
> not others?
Poke around zone.ni.com and
http://digital.natinst.com/public.nsf/$$Search/ .
Good luck, Mark

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

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...

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)

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

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

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

Interprocess Communication C++ - LabView

Hi,
I have a C++ *.exe file wich is grabbing images with a Matrox framegrabber. This program ist startet via "system exec" from LabView. I want to do a kind of time measurement with this program so i need the exact time when the grabbing of frame starts. At the moment I dont know how long the *.exe file needs to initialize the framegrabber (something about 500-1000ms).
My idea is to start a continous grabbing but start saving the images when another command via LabView will be send to the C++ application. But I don't know how to send this command! It should be a kind of a "wait until key pressed" controlled by LabView. Maybe a global bolean or something like that.
I hope somebody can help me!
(programming with LabView 7.0 and Visual C++ 2003.NET)

Hi,
What
you are looking for is called an “inter-application communication”.
There
are several options to realize it. LabVIEW supports TCP/IP, ActiveX or UDP to
communicate with another application. So
it’s not as simple as using a “global Boolean”
as you mentioned.
I advise you, to use the LabVIEW
examples which shipped with the NI example finder to get some programs as
reference. Search for keywords like TCP/IP, ActiveX and UDP.
Attached
you’ll find a link to a knowledgebase.
Hope this helps.
How Do I Use LabVIEW to Communicate with Other
Applications?
http://digital.ni.com/public.nsf/allkb/B3959ED76D55A9E586256965004D8092?OpenDocument
Regards,
Ulrich
AE NICER

How to control the size/position of LabVIEW DLL front panel in MFC application?

I would like to make a MFC application which loads a DLL generated by LabVIEW application builder. How can I control the size and position of the front panel in my MFC application? Thanks.

Did you build the DLL from Labview yourself? If so, you just add another VI to the list. This VI accepts the Title of a front panel and top,left,right,bottom value of the front panel (VI property WindowBond). I'm not familiar with building DLLs using Labview so I really could not help you on how to build the DLL, but I believe it can be done (multiple VIs as multiple functions in a single DLL).
To get the windows bonds for a vi, you need to use VI server property. Check out the examples under labview directory. There are plenty of them to demostrate how to use this feature.
Joe

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

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

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

How to force the "Bluetooth Communications Port" to be one of COM1 to COM8 ports?

Dear Lenovo Community, Happy Holidays to you all and wish you a great happy new year. Recently purchased a Bluetooth OBDII device and have difficulty making it to work with its provided software on my T61 (running original XP Home). My short story and question/problem is that I can open "My Bluetooth Places" and pair with the OBDII device as an "OBDII SPP Dev", but my T61 assigns serial port COM19 to it. The OBDII software which came with the device only can let user set to one of the COM1 to COM8 ports and in the properties of Bluetooth pairing, there is no way that I can select which COM port to use. I looked at the Device Manager and I do see these COM port assignments: COM4,5,6,7: Sierra Wireless (the HSDA modem in the laptop which I have never used BTW) COM 9,10,11,12,13,14,15,16,17: Bluetooth Serial Port COM 18, 19: Bluetooth Communications Port and I don't see anything for COM1,2,3, and 8 My question is how to force the computer/OS to assign one of the COM1 to COM8 ports to my device upon pairing? Can I disable the Sierra Wireless model from the COM ports list and hope this will happen? Thanks for your help and inputs beforehand. Regards, AL

Hi, AL_K
Have you attempted to change the port number in device manager itself? If you navigate to Device Manager and open the list of Ports, you can right-click on the device you wish to assign a different port number. After right-clicking, click Properties. There should be a tab called Port Settings. In here, you should find a setting to manually assign a port number.
Good luck, and let me know how it goes,
Adam
Did someone help you today? Press the star on the left to thank them with a Kudo!
If you find a post helpful and it answers your question, please mark it as an "Accepted Solution!" This will help the rest of the community with similar issues identify the verified solution and benefit from it.

How do I establish serial communicat​ion using LabView to two stepper motors using a motor controller​?

Similar Messages

Maybe you are looking for

How do I establish serial communication using LabView to two stepper motors using a motor controller?