Hi i dont know if this is right to post here but i dont know where to go. i have an RFID Reader this one http://www.stronglink-rfid.com/en/rfid-readers/sl500.html and already installed the driver from that website. the problem is the port is on com23 which is i think is not valid.
can somebody help me out?
Im using win7 64bit
If your software program supports configurable COM port number, I think it is nothing wrong with high-numbered COM port. If your software program accepts only certain COM port numbers (I have seen some S/W that provide list of predefined COM port number), you can just right click the record and change it to any un-used COM port you want.
Seem ok. Your RFID device uses this port to communicate.
Related
So I've built an Arduino module with a Bluetooth chip (HM-10) and it pairs succesfully with my Windows laptop. They both use Bluetooth BLE.
The problem is that the pairing doesn't seem to open a COM port, so I have no way to actually communicate across the connection.
There are no COM port connections when I go into Bluetooth settings->COM Ports, even though Windows is definitely telling me that the pairing was successfull.
Does anyone know why this could be?
Thanks for reading
Lukas
I had the same problem on a Mac. Turns out it's not a problem. BLE doesn't quite work like regular ol' Bluetooth and you won't have a COM port. You need to write your own middleware to take care of the communication between the Arduino and your computer.
There are different projects working on that in Python or Node.js. A simple google search should provide with a proficiency of solutions.
I'm trying to reverse the protocol used by an early nineties logic analyzer an its PC software.
The device is connected via RS-232 (propietary wiring) and communicates with a DOS program, successfully running on DOSBOX.
I'm able to control the device with the original software but it would be useful to autimathe the downloading of data from the analyzer using a custom program but to do so I need to know what is going on the serial port.
Ineed to know what mode is the serial port set, while I know for sure the datarate is either 1200 or 9600 bps (configurable on the device) I don't know the flow control (I guess it is RTS/CTS).
I also need to tap into the conversation between the prgram and the device without disturbing their communication.
Reading the serial port with another program (cutecom/minicom) prevents the emulator from receiving the data from the hardware.
So, summing up, what I need to know is:
What configuration is set on /dev/ttyS0 (via IOCTL calls, i think)
What goes on between program and device.
I was thinking in programming a library which acts as a proxy for the standard c library (via LD_PRELOAD) but there must be an easier way to do this.
You can use slsnif (Serial Line SNIFfer).
http://linux.die.net/man/1/slsnif
Here's a link to the sourceforge project so you can download it. I don't believe it comes with any modern distributions but I could be wrong so check your distro's software repository first.
http://sourceforge.net/projects/slsnif/
I use ttyrpld for tty sniffing. I ported it to PPC and run it on 2.6.32. It logs all of the tty traffic on the board to files, one per tty. Works well.
I'm trying to use a Bluetooth OBDII (on-board diagnosis) to connect with a Bluetooth dongle connected to my computer (My OS is windows 7). The dongle connects to the device and assigns it 2 virtual com ports (COM4 for incoming and COM5 for outgoing), But unfortunately I couldn't communicate with this device over the virtual com port. I also attempted to work with winsock library but I didn't find any example for working with Bluetooth OBD and send and receive the instruments. I just found one Bluetooth API for android but it's not useful for me because I want to implement it inside the visual C++ and for PC. and right now I have 2 questions about that :
1. which method is better, Virtual com port or winsock and how ?
2. Do you have any sample code for working with Bluetooth OBD ?
1: Has your device a ELM327 chip? If so, you can setup a serial port over bluetooth, and communicate with that port. I don't know winsock very much, but I think a serial port is better suited for this job.
To set it up, have a look here: http://windows.microsoft.com/en-us/windows7/choose-a-com-port-for-a-bluetooth-enabled-device
Maybe if you can pair with the device, windows 7 will automagically set it up?
2:
You might want to have a look at: http://icculus.org/obdgpslogger/
It's open-source, so you can have a peek how it works. There's also a simulator in the package, which could help you developing/testing. Mostly is Linux based, but it should give you hints where to go. There are also windows installers available for the simulator.
So I have my computer linked up via bluetooth to two different devices, and I'd like to relay the input from one device to the other device automatically.
I figure I can do this with a script, but I'm pretty green with scripting languages, and I'm not even sure if this is possible.
I know that like Linux, OSX treats serial ports as if they were file directories, so I figure this can't be too hard. I just have no idea where to start.
Can someone point me in the right direction?
I would use a simple python script. Manipulating serial ports is simple with the pyserial module. Then create thread for each port that reads from one port and writes to the other.
I am trying to use scilab for a project and I need to pass on some values to a robot via a serial port.
I had done this successfully on Matlab. I have ported almost everything to Scilab now but I don't know how to pass those parameter through serial port.
On the Sclilab site there are some modules, but they only work under Windows
http://atoms.scilab.org/
I am the maintainer for the Serial Communication toolbox in Scilab. This works on Linux as well. You can find it here: http://atoms.scilab.org/toolboxes/serial. This is fairly easy to use- it has functions to establish communication with the serial port, to read from and write to the serial port, and to terminate communication with the serial port. Please let me know about any feedback or questions you may have. Thanks.