I'm looking for a list of receivers that are compatible with the Raspberry Pi. I am trying to get an idea of all the different methods of communication that the Raspberry Pi is currently able to pick up. So far, I know that there is at least one Pi-compatible instance of each of the following receivers on the market:
RF (Radio Frequency) receiver
IR (Infrared) receiver
Bluetooth receiver
Internet searches have yielded nothing so far. Can anyone add to this list? I'd like to know if there's a receiver that can pick up a magnetic field change (like the iPhone's Hall sensor) or a receiver that can pick up a frequency change, but I'm looking for anything to add to this list.
Thanks
http://elinux.org/RPi_VerifiedPeripherals
This is a list of all verified devices for the pi I found.
Related
Good evening.
I have a short question regarding the use of CODESYS Development System V3 and the associated CODESYS Control for Raspberry Pi SL. How do I manage to acquire the values of the connected sensors (e.g. si705x, vcnl) or to write certain bits via the I2C bus? Unfortunately, I cannot find any decisive results or useful documentation for use. With the datasheets of the respective sensors I don't get on either.
Greez
A good worked example, but for another i2c sensor, with code for RPi can be found on this page. Read/learn from this one and you can build your own.
I have a Raspberry PI with two NFC readers attached. Problem is that the readers get different device numbers each time the system reboots or a reader is detached and attached again.
I therefore created udev rules that create a fixed device name depending on the physical port a device is attached to. E.g. plug in NFC reader in the upper left port leads always to /dev/nfc_a and plugged into the upper right port leads always to /dev/nfc_b.
How can I now configure libnfc to use these devices and report the device names such as /dev/nfc_a as a part of the reading? I am using Node-RED with node-red-contrib-nfc (https://github.com/hardillb/node-red-contrib-nfc) on top of libnfc. My ultimate goal is to safely distinguish the two readers within my Node-RED flow to act differently upon the readings.
I already found the "connstring" configuration but I don't know how to correctly set it for using /dev/nfc_a.
It's been a LONG time since I wrote this node, but looking back at the nodejs library it's based on (nfc) the output message should contain a field called deviceID which should indicate which NFC reader triggered the input.
When I run on my machine I get:
deviceID: 'pn53x_usb:001:005'
Where 001 is the USB bus id and 005 is the device ID, which matches up with the output from lsusb. These should stay static as long as the readers are always plugged into the same USB sockets.
I'm a bit confused. I explain to you my project, I would like to make a "reader" by using beacon technology (ibeacon for apple, eddystone for android) using a raspberry pi 3. The smatphone application sends an acknowledgment code when passing the person. The raspberry marks and updates an online database. I wanted to ask, first of all can this be done? My problem is to realize the beacon transmission, then for the app and the database I have no problems. I tried using bluez but I can not detect the phone. Is there any online tutorial that could help me? Thanks
If you are looking to use the phone to emit a beacon transmission and then use the Raspberry Pi 3 to detect the beacon, then yes, this is possible. I put together a tutorial on how to use the Android Things to detect beacons on the Raspberry Pi 3.
The problem with using BlueZ for beacon detection is that it is simply not stable on the Raspberry Pi, and will freeze up and stop detecting requiring a reboot.
I plan to extend the range of my Wifi with my Notebook. - My question to this, is it possible to build a wireless repeater with only one NIC? or do I really need at least two NICs, one for being logged in and receiving the packets and the other for extending the WiFi/Signal. - Actually, what I wanna do is, using my laptop as a WiFi-Repeater, but only with the built-in NIC, no second one.
I've searched the net already but found nothing about the functionality of a WiFi-Repeater and if they have two NICs integrated.
Hope you guys can enlight me ;)
EDIT(added schemes):
Possibility A
Possibility B
What can be achieved with an AP capable Chip/Firmware, for instance, the Ath9k.
You can't turn laptop's WiFi into range extender, since I believe it requires a special WiFi chip firmware and a special configuration of antenna(s).
However, you might try to look on the internet if WiFi chip you have supports AP mode in firmware (not all manufacturers provides that), and if yes, you can set up the access point with the same SSID. In this case your WiFi clients will roam from one AP to another. Of course, this kind of setup requires Ethernet cable attached to your laptop.
I want to send/receive out some data from a raspberry pi using the WLAN protocol IEEE-802.11n. I tried searching a lot but could not find any library in any language which can send/receive data sent through the ieee 802.11n protocol. My receiver is also a raspberry pi.
Basically, the sender is connected to some devices and is supposed to send out some data which is to be sent through the wifi (ieee.802.11n) to another raspberry pi. And to add to my problems how is the data sent from the sender is not known. All I know is that it is sent through the ieee.802.11n protocol.(There is a wifi dongle attached to the senders raspberry pi.)
So if someone could point me to a library or any solution as to how to read that data sent through this protocol.
You need to research this more so that you can ask more specific questions. I doubt any answer is worth an upvote except for the effort put in.
I'll give it a try, and hope this "puts you" in the right direction.
If you manage to setup the RPi-sender as an access point and manage to connect the RPi-receiver to that network, you are well on your way. Since beacons and probe request will start being sent automagically from the sender to the receiver. From there you can start injecting, injecting or in some other way sending packets from sender to receiver. Easiest first step is of course pinging (this can go either way. sender->receiver and vice versa)
If you manage to setup an ad-hoc network, then there is no real "sender" and/or "receiver", but injecting/sending packets work the same way.
Here is a similar question on SO.
Also mentioning libraries