Re: Problem using RFID reader (ucom0 at uslcom0 portno 0)
On 08/29/16 18:00, Remco wrote: Op 08/29/16 om 14:28 schreef Martijn Rijkeboer: Hi, I'm having trouble using the Stronglink SL500 RFID reader with OpenBSD. The SL500 is a USB based RFID reader that attaches to ucom. When I write data to it and try to read the response, I'm often getting wrong results. Sometimes the program even lock and unplugging the device is the only option. I'm using the test program attached below. This program should produce the following output (as it always does on Linux): $ ./test received: 0xaa 0xbb 0x06 0x00 0x11 0x12 0x07 0x01 0x00 0x05 received: 0xaa 0xbb 0x06 0x00 0x11 0x12 0x07 0x01 0x00 0x05 When I run the program on OpenBSD-current (AMD64) I get the following: $ ./test received: 0xaa 0xbb 0x06 0x00 0x11 0x12 0x07 0x01 0x00 0x05 received: 0xaa 0xbb 0x06 0x00 0x11 0x12 0x07 0x01 0x00 0x05 $ ./test received: 0x0a 0xbb 0x06 0x00 0x00 0x00 0x07 0x01 0x02 0x04 received: 0xaa 0xbb 0x06 0x00 0x11 0x12 0x07 0x01 0x00 0x05 $ ./test received: 0xaa 0xbb 0x06 0x00 0x11 0x12 0x07 0x01 0x00 0x05 received: 0x0a 0xaa 0xbb 0x06 0x00 0x11 0x12 0x07 0x01 0x00 $ ./test received: 0xaa 0xbb 0x06 0x00 0x11 0x12 0x07 0x01 0x00 0x05 received: 0x0a 0xaa 0xbb 0x06 0x00 0x11 0x12 0x07 0x01 0x00 In the output above the first run is correct. In the second run the first response is incorrect. In the third and fourth run the second response is incorrect. Any suggestions what is wrong? To me it looks like a bug in ucom or uslcom, but I could also be doing something wrong... I've included the test program, lsusb output and dmesg output below. Kind regards, Martijn Rijkeboer Test program O_NONBLOCK: not sure this is necessary. The O_NONBLOCK is indeed not necessary. Check return values, at least of read and write (EAGAIN, partial read/write ?), they will probably tell you what's wrong. None of the calls returned -1, but issuing a `tcflush(fd, TCIOFLUSH)' before sending the first data fixed the problem. Thanks for your time. Kind regards, Martijn Rijkeboer
Re: Problem using RFID reader (ucom0 at uslcom0 portno 0)
Op 08/29/16 om 14:28 schreef Martijn Rijkeboer: Hi, I'm having trouble using the Stronglink SL500 RFID reader with OpenBSD. The SL500 is a USB based RFID reader that attaches to ucom. When I write data to it and try to read the response, I'm often getting wrong results. Sometimes the program even lock and unplugging the device is the only option. I'm using the test program attached below. This program should produce the following output (as it always does on Linux): $ ./test received: 0xaa 0xbb 0x06 0x00 0x11 0x12 0x07 0x01 0x00 0x05 received: 0xaa 0xbb 0x06 0x00 0x11 0x12 0x07 0x01 0x00 0x05 When I run the program on OpenBSD-current (AMD64) I get the following: $ ./test received: 0xaa 0xbb 0x06 0x00 0x11 0x12 0x07 0x01 0x00 0x05 received: 0xaa 0xbb 0x06 0x00 0x11 0x12 0x07 0x01 0x00 0x05 $ ./test received: 0x0a 0xbb 0x06 0x00 0x00 0x00 0x07 0x01 0x02 0x04 received: 0xaa 0xbb 0x06 0x00 0x11 0x12 0x07 0x01 0x00 0x05 $ ./test received: 0xaa 0xbb 0x06 0x00 0x11 0x12 0x07 0x01 0x00 0x05 received: 0x0a 0xaa 0xbb 0x06 0x00 0x11 0x12 0x07 0x01 0x00 $ ./test received: 0xaa 0xbb 0x06 0x00 0x11 0x12 0x07 0x01 0x00 0x05 received: 0x0a 0xaa 0xbb 0x06 0x00 0x11 0x12 0x07 0x01 0x00 In the output above the first run is correct. In the second run the first response is incorrect. In the third and fourth run the second response is incorrect. Any suggestions what is wrong? To me it looks like a bug in ucom or uslcom, but I could also be doing something wrong... I've included the test program, lsusb output and dmesg output below. Kind regards, Martijn Rijkeboer Test program O_NONBLOCK: not sure this is necessary. Check return values, at least of read and write (EAGAIN, partial read/write ?), they will probably tell you what's wrong.
Problem using RFID reader (ucom0 at uslcom0 portno 0)
Hi,
I'm having trouble using the Stronglink SL500 RFID reader with OpenBSD.
The SL500 is a USB based RFID reader that attaches to ucom. When I
write data to it and try to read the response, I'm often getting
wrong results. Sometimes the program even lock and unplugging the
device is the only option. I'm using the test program attached below.
This program should produce the following output (as it always does on
Linux):
$ ./test
received: 0xaa 0xbb 0x06 0x00 0x11 0x12 0x07 0x01 0x00 0x05
received: 0xaa 0xbb 0x06 0x00 0x11 0x12 0x07 0x01 0x00 0x05
When I run the program on OpenBSD-current (AMD64) I get the following:
$ ./test
received: 0xaa 0xbb 0x06 0x00 0x11 0x12 0x07 0x01 0x00 0x05
received: 0xaa 0xbb 0x06 0x00 0x11 0x12 0x07 0x01 0x00 0x05
$ ./test
received: 0x0a 0xbb 0x06 0x00 0x00 0x00 0x07 0x01 0x02 0x04
received: 0xaa 0xbb 0x06 0x00 0x11 0x12 0x07 0x01 0x00 0x05
$ ./test
received: 0xaa 0xbb 0x06 0x00 0x11 0x12 0x07 0x01 0x00 0x05
received: 0x0a 0xaa 0xbb 0x06 0x00 0x11 0x12 0x07 0x01 0x00
$ ./test
received: 0xaa 0xbb 0x06 0x00 0x11 0x12 0x07 0x01 0x00 0x05
received: 0x0a 0xaa 0xbb 0x06 0x00 0x11 0x12 0x07 0x01 0x00
In the output above the first run is correct. In the second run the
first response is incorrect. In the third and fourth run the second
response is incorrect. Any suggestions what is wrong? To me it looks
like a bug in ucom or uslcom, but I could also be doing something
wrong...
I've included the test program, lsusb output and dmesg output below.
Kind regards,
Martijn Rijkeboer
Test program
#include
#include
#include
#include
int open_port(void) {
int fd = open("/dev/cuaU0", O_RDWR | O_NONBLOCK); // OpenBSD
//int fd = open("/dev/ttyUSB0", O_RDWR | O_NONBLOCK); // Linux
if (fd == -1) {
perror("can't open port");
} else {
fcntl(fd, F_SETFL, 0);
}
struct termios options;
tcgetattr(fd, );
cfsetispeed(, B19200);
cfsetospeed(, B19200);
options.c_cflag |= (CLOCAL | CREAD);
options.c_cflag &= ~CSTOPB;
cfmakeraw();
tcsetattr(fd, TCSANOW, );
return fd;
}
void send_led_green(int fd) {
unsigned char data[] =
{0xaa,0xbb,0x06,0x00,0x00,0x00,0x07,0x01,0x02,0x04};
write(fd, data, sizeof(data));
}
void send_led_red(int fd) {
unsigned char data[] =
{0xaa,0xbb,0x06,0x00,0x00,0x00,0x07,0x01,0x01,0x07};
write(fd, data, sizeof(data));
}
void recv_led(int fd) {
unsigned char actual[10];
read(fd, , sizeof(actual));
printf("received: ");
printf("0x%02x ", actual[0]);
printf("0x%02x ", actual[1]);
printf("0x%02x ", actual[2]);
printf("0x%02x ", actual[3]);
printf("0x%02x ", actual[4]);
printf("0x%02x ", actual[5]);
printf("0x%02x ", actual[6]);
printf("0x%02x ", actual[7]);
printf("0x%02x ", actual[8]);
printf("0x%02x ", actual[9]);
printf("\n");
}
int main() {
int fd = open_port();
send_led_green(fd);
recv_led(fd);
send_led_red(fd);
recv_led(fd);
close(fd);
}
$ lsusb
===
Bus 000 Device 001: ID 1b6f:
Bus 001 Device 001: ID 1b6f:
Bus 002 Device 001: ID 1002:
Bus 003 Device 001: ID 1002:
Bus 004 Device 001: ID 1002:
Bus 004 Device 002: ID 05ac:1006 Apple, Inc. Hub in Aluminum Keyboard
Bus 004 Device 003: ID 046d:c069 Logitech, Inc. M500 Laser Mouse
Bus 004 Device 004: ID 05ac:0221 Apple, Inc. Aluminum Keyboard (ISO)
Bus 005 Device 001: ID 1002:
Bus 006 Device 001: ID 1002:
Bus 006 Device 002: ID 10c4:ea60 Cygnal Integrated Products, Inc. CP210x
UART Bridge / myAVR mySmartUSB light
Bus 007 Device 001: ID 1002:
$ lsusb -v -s 6:2
=
Bus 006 Device 002: ID 10c4:ea60 Cygnal Integrated Products, Inc. CP210x
UART Bridge / myAVR mySmartUSB light
Device Descriptor:
bLength18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize064
idVendor 0x10c4 Cygnal Integrated Products, Inc.
idProduct 0xea60 CP210x UART Bridge / myAVR mySmartUSB light
bcdDevice1.00
iManufacturer 1 Silicon Labs
iProduct2 CP2102 USB to UART Bridge Controller
iSerial 3 0001
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 32
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass
Re: USB RFID Reader misreads
As a minimum, you should post a dmesg and look for any suspicious message in it (overrun or usb error). Also, does the problem happen if connected to an USB 1 controller or an USB 2 controller? This might matter. Miod
Re: USB RFID Reader misreads
Here is a dmesg from the macmini, if it helps much. I dont deny that the devices could have a badly implemented HID spec, but then why do they work flawlessly on other systems? and why does it work perfectly if i first plug in a normal USB keyboard, and then the reader? Anyhow, i think if i could figure out what exactly happens when a Normal USB keyboard is plugged in, and then load the same things as soon as i plug in my Reader, i think i will be fine. I assume i can somehow control this behavior via hotplugd, but can anyone tell me how exactly i would pretend to the system that i plugged in a certain usb keyboard? Thanks, David Travers Buda wrote: * David Schulz [EMAIL PROTECTED] [2008-11-21 17:17:57]: Hi all, i have a RFID Proximity Card Reader connected to a Computer via USB. Basically how they work is that as soon a RFID Card comes near it, the Reader reads the Number on the Card, and sends it to STDIN followed by a newline Character. It really works the same as a Magnetic Card Reader, Barcode Scanner, standard USB keyboard. The problem i am having is that the Reader misreads the Number on the Card more than often. For example a swipe should look like: 0011920435 0011920435 but often it does look like: 001cr20435 001192\s30435 920435 I have tried under : i386 OpenBSD 4.3 PC i386 OpenBSD 4.4 ThinkPad X61 Laptop macppc OpenBSD 4.4 Macmini macppc OpenBSD 4.4 iMac All of this with 2 different USB Readers. Mostly the same results, too many misreads. no matter how slow or fast i swipe the Card. Now, one thing that i have noticed is that when i first plugin a normal USB Keyboard, AND THEN plug in the USB Reader next to it, everything works great. I have tested and repeated this behavior on the macppc MacMini. Trying with a PS/2 Version of the Reader, it works all great, no Problems (but there is no ps/2 on the macppc's nor on my Laptop anymore. grr.) I have tried the USB Reader on a Windows XP Machine, and it works like it should. First detects it as a USB Keyboard, and then nicely reads any card i swipe at it. I also tried it on a Ubuntu Linux Asus Laptop, and it works as well. Now what i want to ask is obviously, does anyone have any idea what i could try to do to make my USB Reader work nicely and don't misread all the time? Will anyone work with me to make it work, or at least figure out why it doesn't? Maybe there is some way i can tune the behaviour of attached USB Keyboards, so that they (?) somehow give the Reader more time before attempting to read the Card. Thanks and best regards, David A dmesg would help. In all likelyhood, your hardware is not following the HID spec. [ using 408000 bytes of bsd ELF symbol table ] console out [ATY,RockHopper2_A]console in [keyboard] , using USB using parent ATY,RockHopper2Paren:: memaddr 9800 size 800, : consaddr 9c008000, : ioaddr 9002, size 2: memtag 8000, iotag 8000: width 640 linebytes 768 height 480 depth 8 Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. Copyright (c) 1995-2008 OpenBSD. All rights reserved. http://www.OpenBSD.org OpenBSD 4.4 (GENERIC) #1854: Mon Aug 11 13:32:35 MDT 2008 [EMAIL PROTECTED]:/usr/src/sys/arch/macppc/compile/GENERIC real mem = 536870912 (512MB) avail mem = 509779968 (486MB) mainbus0 at root: model PowerMac10,1 cpu0 at mainbus0: 7447A (Revision 0x102): 1249 MHz: 512KB L2 cache mem0 at mainbus0 spdmem0 at mem0: 512MB DDR SDRAM non-parity PC3200CL3.0 memc0 at mainbus0: uni-n hw-clock at memc0 not configured kiic0 at memc0 offset 0xf8001000 iic0 at kiic0 mpcpcibr0 at mainbus0 pci: uni-north, Revision 0xff pci0 at mpcpcibr0 bus 0 pchb0 at pci0 dev 11 function 0 Apple UniNorth AGP rev 0x00 vgafb0 at pci0 dev 16 function 0 ATI Radeon 9200 rev 0x01, mmio wsdisplay0 at vgafb0 mux 1: console (std, vt100 emulation) mpcpcibr1 at mainbus0 pci: uni-north, Revision 0x5 pci1 at mpcpcibr1 bus 0 pchb1 at pci1 dev 11 function 0 Apple UniNorth PCI rev 0x00 macobio0 at pci1 dev 23 function 0 Apple Intrepid rev 0x00 openpic0 at macobio0 offset 0x4: version 0x4614 little endian macgpio0 at macobio0 offset 0x50 modem-reset at macgpio0 offset 0x1d not configured modem-power at macgpio0 offset 0x1c not configured macgpio1 at macgpio0 offset 0x9 irq 47 programmer-switch at macgpio0 offset 0x11 not configured gpio5 at macgpio0 offset 0x6f not configured gpio6 at macgpio0 offset 0x70 not configured extint-gpio15 at macgpio0 offset 0x67 not configured escc-legacy at macobio0 offset 0x12000 not configured zsc0 at macobio0 offset 0x13000: irq 22,23 zstty0 at zsc0 channel 0 zstty1 at zsc0 channel 1 aoa0 at macobio0 offset 0x1: irq 30,1,2 audio0 at aoa0 timer at macobio0 offset 0x15000 not configured adb0 at macobio0 offset 0x16000 irq 25: via-pmu, 0 targets apm0 at adb0: battery flags 0x0, 0% charged piic0 at adb0 iic1 at piic0 maxtmp0 at iic1
USB RFID Reader misreads
Hi all, i have a RFID Proximity Card Reader connected to a Computer via USB. Basically how they work is that as soon a RFID Card comes near it, the Reader reads the Number on the Card, and sends it to STDIN followed by a newline Character. It really works the same as a Magnetic Card Reader, Barcode Scanner, standard USB keyboard. The problem i am having is that the Reader misreads the Number on the Card more than often. For example a swipe should look like: 0011920435 0011920435 but often it does look like: 001cr20435 001192\s30435 920435 I have tried under : i386 OpenBSD 4.3 PC i386 OpenBSD 4.4 ThinkPad X61 Laptop macppc OpenBSD 4.4 Macmini macppc OpenBSD 4.4 iMac All of this with 2 different USB Readers. Mostly the same results, too many misreads. no matter how slow or fast i swipe the Card. Now, one thing that i have noticed is that when i first plugin a normal USB Keyboard, AND THEN plug in the USB Reader next to it, everything works great. I have tested and repeated this behavior on the macppc MacMini. Trying with a PS/2 Version of the Reader, it works all great, no Problems (but there is no ps/2 on the macppc's nor on my Laptop anymore. grr.) I have tried the USB Reader on a Windows XP Machine, and it works like it should. First detects it as a USB Keyboard, and then nicely reads any card i swipe at it. I also tried it on a Ubuntu Linux Asus Laptop, and it works as well. Now what i want to ask is obviously, does anyone have any idea what i could try to do to make my USB Reader work nicely and don't misread all the time? Will anyone work with me to make it work, or at least figure out why it doesn't? Maybe there is some way i can tune the behaviour of attached USB Keyboards, so that they (?) somehow give the Reader more time before attempting to read the Card. Thanks and best regards, David
Re: USB RFID Reader misreads
* David Schulz [EMAIL PROTECTED] [2008-11-21 17:17:57]: Hi all, i have a RFID Proximity Card Reader connected to a Computer via USB. Basically how they work is that as soon a RFID Card comes near it, the Reader reads the Number on the Card, and sends it to STDIN followed by a newline Character. It really works the same as a Magnetic Card Reader, Barcode Scanner, standard USB keyboard. The problem i am having is that the Reader misreads the Number on the Card more than often. For example a swipe should look like: 0011920435 0011920435 but often it does look like: 001cr20435 001192\s30435 920435 I have tried under : i386 OpenBSD 4.3 PC i386 OpenBSD 4.4 ThinkPad X61 Laptop macppc OpenBSD 4.4 Macmini macppc OpenBSD 4.4 iMac All of this with 2 different USB Readers. Mostly the same results, too many misreads. no matter how slow or fast i swipe the Card. Now, one thing that i have noticed is that when i first plugin a normal USB Keyboard, AND THEN plug in the USB Reader next to it, everything works great. I have tested and repeated this behavior on the macppc MacMini. Trying with a PS/2 Version of the Reader, it works all great, no Problems (but there is no ps/2 on the macppc's nor on my Laptop anymore. grr.) I have tried the USB Reader on a Windows XP Machine, and it works like it should. First detects it as a USB Keyboard, and then nicely reads any card i swipe at it. I also tried it on a Ubuntu Linux Asus Laptop, and it works as well. Now what i want to ask is obviously, does anyone have any idea what i could try to do to make my USB Reader work nicely and don't misread all the time? Will anyone work with me to make it work, or at least figure out why it doesn't? Maybe there is some way i can tune the behaviour of attached USB Keyboards, so that they (?) somehow give the Reader more time before attempting to read the Card. Thanks and best regards, David A dmesg would help. In all likelyhood, your hardware is not following the HID spec. -- Travers Buda
Re: RFID Reader
On Thu, 7 Aug 2008 15:14:24 +0100 Conor [EMAIL PROTECTED] wrote: On Thu, Aug 7, 2008 at 1:05 PM, Duncan Patton a Campbell [EMAIL PROTECTED] wrote: On Thu, 7 Aug 2008 10:46:40 +0100 Conor [EMAIL PROTECTED] wrote: Are there any RFID readers supported by OpenBSD? Regards, Conor. This: http://www.openpcd.org/ claims to be an open design with GPL'd drivers, but this http://www.motorola.com/business/v/index.jsp?vgnextoid=1722e90e3ae95110VgnVCM108406b00aRCRD should be fairly trivial to make work with OBSD, despite being a Windoze CE box as it has numerous open interfaces and claims to talk to SAP and IBM stuff ... The question of being supported is misleading as most of these devices will be designed to operate using standard industrial interfaces. Dhu Thanks Duncan, The OpenPCD is what I was hoping would work with OBSD, I just don't have access to the hardware yet to try it. On a FreeBSD host most of these just appear with ugen0 and thats about as far as it will go. I'll look into the Motorola but I'm not willing to committ to buying something that isn't going to work, however the same could be said for the OpenPCD. Although at least I know that OpenPCD will unfortunately work with something like Debian or Slackware as a last resort. If I can get the hardware to work with OpenBSD it'll just be a case then afterwards of getting librfid to work. At the moment I'm trying to get the Omnikey 5121 to work while I await the OpenPCD reader. It is not going well as one might imagine. I've been thinking about this, and what is needed is an economic model. Proprietary supply chains don't have a need to be able to cross-reference and check their weight and measures so they can tolerate a closed architecture. Notably, closed architectures can be first to market but cannot stay that way because they can't be currently (in RT) validated by more than one party, so they amount to private money. However any commercial organization or association with more than one member should be interested in this because it will allow for multiparty validation of transactions. Also, quite frankly, I can't see a viable taxation system without such mechanisms, either. Dhu ATB, Conor.
RFID Reader
Are there any RFID readers supported by OpenBSD? Regards, Conor.
Re: RFID Reader
On Thu, 7 Aug 2008 10:46:40 +0100 Conor [EMAIL PROTECTED] wrote: Are there any RFID readers supported by OpenBSD? Regards, Conor. This: http://www.openpcd.org/ claims to be an open design with GPL'd drivers, but this http://www.motorola.com/business/v/index.jsp?vgnextoid=1722e90e3ae95110VgnVCM108406b00aRCRD should be fairly trivial to make work with OBSD, despite being a Windoze CE box as it has numerous open interfaces and claims to talk to SAP and IBM stuff ... The question of being supported is misleading as most of these devices will be designed to operate using standard industrial interfaces. Dhu
Re: RFID Reader
On Thu, Aug 7, 2008 at 1:05 PM, Duncan Patton a Campbell [EMAIL PROTECTED] wrote: On Thu, 7 Aug 2008 10:46:40 +0100 Conor [EMAIL PROTECTED] wrote: Are there any RFID readers supported by OpenBSD? Regards, Conor. This: http://www.openpcd.org/ claims to be an open design with GPL'd drivers, but this http://www.motorola.com/business/v/index.jsp?vgnextoid=1722e90e3ae95110VgnVCM108406b00aRCRD should be fairly trivial to make work with OBSD, despite being a Windoze CE box as it has numerous open interfaces and claims to talk to SAP and IBM stuff ... The question of being supported is misleading as most of these devices will be designed to operate using standard industrial interfaces. Dhu Thanks Duncan, The OpenPCD is what I was hoping would work with OBSD, I just don't have access to the hardware yet to try it. On a FreeBSD host most of these just appear with ugen0 and thats about as far as it will go. I'll look into the Motorola but I'm not willing to committ to buying something that isn't going to work, however the same could be said for the OpenPCD. Although at least I know that OpenPCD will unfortunately work with something like Debian or Slackware as a last resort. If I can get the hardware to work with OpenBSD it'll just be a case then afterwards of getting librfid to work. At the moment I'm trying to get the Omnikey 5121 to work while I await the OpenPCD reader. It is not going well as one might imagine. ATB, Conor.
Re: RFID Reader
On Thu, Aug 7, 2008 at 1:12 PM, Joachim Schipper [EMAIL PROTECTED] wrote: On Thu, Aug 07, 2008 at 10:46:40AM +0100, Conor wrote: Are there any RFID readers supported by OpenBSD? Don't most readers communicate with the host PC over some common protocol, say RS232 (serial), or maybe USB? OpenBSD will allow you to access those, so if you find or write a program that can communicate with the reader via RS232/USB/whatever, it should work as well on OpenBSD as on any other system. Joachim Not all, some only pop as like this ugen0 at uhub1 port 1 OMNIKEY AG Smart Card Reader USB rev 2.00/1.00 addr 2 *This was the only output seen until I plugged it out then I got the generic device detached message. ugen0 detached In theory they should all emulate/act as a serial interface in some form or another. ACG USB readers use an FTDI serial converter although I won't have one of those to test for quite sometime as they are a bit too expensive when compared to OpenPCD. I don't think the Omnikey readers play as nice as the OpenPCD or ACG readers. I'll have a chance to test the OpenPCD reader with OpenBSD 4.3 in about a week or so. Conor.
Re: RFID Reader
On Thu, 7 Aug 2008 17:05:19 +0100 Conor [EMAIL PROTECTED] wrote: On Thu, Aug 7, 2008 at 1:12 PM, Joachim Schipper [EMAIL PROTECTED] wrote: On Thu, Aug 07, 2008 at 10:46:40AM +0100, Conor wrote: Are there any RFID readers supported by OpenBSD? Don't most readers communicate with the host PC over some common protocol, say RS232 (serial), or maybe USB? OpenBSD will allow you to access those, so if you find or write a program that can communicate with the reader via RS232/USB/whatever, it should work as well on OpenBSD as on any other system. Joachim Not all, some only pop as like this ugen0 at uhub1 port 1 OMNIKEY AG Smart Card Reader USB rev 2.00/1.00 addr 2 *This was the only output seen until I plugged it out then I got the generic device detached message. ugen0 detached In theory they should all emulate/act as a serial interface in some form or another. ACG USB readers use an FTDI serial converter although I won't have one of those to test for quite sometime as they are a bit too expensive when compared to OpenPCD. I don't think the Omnikey readers play as nice as the OpenPCD or ACG readers. I'll have a chance to test the OpenPCD reader with OpenBSD 4.3 in about a week or so. Conor. There some trick I don't exactly recall where you need to suppress the ugen device to allow ucom to grab the device. I think it involved disableing ugen. Dhu
Re: RFID Reader
On Thu, 7 Aug 2008 15:14:24 +0100 Conor [EMAIL PROTECTED] wrote: On Thu, Aug 7, 2008 at 1:05 PM, Duncan Patton a Campbell [EMAIL PROTECTED] wrote: On Thu, 7 Aug 2008 10:46:40 +0100 Conor [EMAIL PROTECTED] wrote: Are there any RFID readers supported by OpenBSD? Regards, Conor. This: http://www.openpcd.org/ claims to be an open design with GPL'd drivers, but this http://www.motorola.com/business/v/index.jsp?vgnextoid=1722e90e3ae95110VgnVCM108406b00aRCRD should be fairly trivial to make work with OBSD, despite being a Windoze CE box as it has numerous open interfaces and claims to talk to SAP and IBM stuff ... The question of being supported is misleading as most of these devices will be designed to operate using standard industrial interfaces. Dhu Thanks Duncan, The OpenPCD is what I was hoping would work with OBSD, I just don't have access to the hardware yet to try it. On a FreeBSD host most of these just appear with ugen0 and thats about as far as it will go. I'll look into the Motorola but I'm not willing to committ to buying something that isn't going to work, however the same could be said for the OpenPCD. Although at least I know that OpenPCD will unfortunately work with something like Debian or Slackware as a last resort. If I can get the hardware to work with OpenBSD it'll just be a case then afterwards of getting librfid to work. At the moment I'm trying to get the Omnikey 5121 to work while I await the OpenPCD reader. It is not going well as one might imagine. You need to get the OpenPCD to talk on ucom/uplcom OR use the Moto which has RS232 and Ethernet interfaces (as well as USB) which can be used in a more conventional manner. Dhu ATB, Conor.
