My aim is to get my Raspberry Pi 2 connected to an adc ( which will have 8 channels and resolution should be higher than 16 bits or 16 bit )
And according to analog values from load-cells. I am going to make a weighing indicator. with 4 channels.
I have selected Texas Instruments ads1256 chip to do it.
It is 24 bit delta sigma adc.
First I have made PCB With 2 ads1256.
Simply did not work. Spidev results are random or all result is all FF in hex.
I realised , i need some kernel driver for it.
I am new to unix/linux raspbian by the way.
I thought , it 's true. It's like trying to communicate through rs232 over a converter that windows driver doesn't exist.
But there is no kernel driver for this. I asked Texas, they answered like we don't have, good day, i am closing this.
Then i found and i bought this product from china !
http://www.waveshare.com/high-precision-ad-da-board.htm
It seemed fine to me. After one week, the card came to me.
There is an example code after all. I was going to connect this on my raspberry and run the example code and get the adc values.
I did everything on thier instructions.
But turns out it doesn't work.
http://i57.tinypic.com/2efupgh.jpg
So Please show me the path :D what to do now.
It is strange but this solved as below ;
in manufacturer website , there are instructions list. 2 libraries. bcm2835 and wiringPi , i have installed bcm first. ( i did not follow top to bottom ) first i installed bcm2835 then wiringPi. Then it worked.
still don't know how.
sudo apt-get install rpi-update
sudo apt-get update
sudo apt-get upgrade
sudo raspi-config
( enable spi and device tree )
install bcm2835
install wiringPi
then it works
Related
I was trying to install scikit learn on Raspberry Pi 3 B+, with code,
python3.8 -m pip install scikit-learn==0.23.2
initially the pi was working fine showing the progress, after above 1 hour, monitor went off and the green LED on Rpi is ON all the time (before it was like blinking).
Now the Rpi seems to be ON with red and green LED full time ON, and not able to see the progress, and not detecting the input given through keyboard and mouse. its about 5 hours.
it will be very helpful for me, if someone explains me why this happens.
Thanking you in advance.
I am using the instructions of https://pimylifeup.com/raspberry-pi-rfid-rc522/ to learn how to read my rfid-rc522.
I installed all the things needed, and cloned from git all the files. I connected accordingly and double checked the wire.
The code in Write.py is
#!/usr/bin/env python
import RPi.GPIO as GPIO
import SimpleMFRC522
reader = SimpleMFRC522.SimpleMFRC522()
try:
text = raw_input('New data:')
print("Now place your tag to write")
reader.write(text)
print("Written")
finally:
GPIO.cleanup()
When I run it- The result stops after "Now place your tag to write" and nothing happens when I place my tag. Any help please? What's wrong here? The module gives red light meaning it is connected. Is it really connected? How do I know? Please help.
Edit: My title and tags were wrong in this question due to already saved data. I edited. :)
It can be multiple reasons why your reader is not retrieving any data:
The RFID cards that you are providing to the reader are not supported by the ISO 14443: Mifare Classic, 4K. (Some DesFire, etc...) are the cards you want to try. Source: https://en.wikipedia.org/wiki/ISO/IEC_14443
The MFRC522 is not receiving enough input voltage. Try to increase from 3.3V to 4V. I have tried with 5V months and the reader is still running perfectly, but be cautious. The safe range in NXP is from 2.5V to 3.6V. Source: https://www.nxp.com/docs/en/data-sheet/MFRC522.pdf
The library you are using does not support IRQ (Interruption Request). This means the process of reading UIDs is high CPU consuming and low in performance. Try to use this popular library which supports interruptions: https://github.com/ondryaso/pi-rc522 . You will need to connect another wire from the IRQ pin in the MFRC522 to one GPIO pin in the Raspberry that is free and supports reading/writing operations.
Check if SPI interfaces are enable in Raspbian. Open a terminal and run:
ls -l /dev/spi
Lastly, it could be that your reader is broken. Some chinese versions do not work as they should do. Maybe you should buy another one and try more luck.
I suppose you have connected all cables in the correct way between the MFRC522 and the Raspberry Pi. Check that again.
I have Orange Pi Plus 2e.
I want to install Fedora 24 on it.
So from
https://arm.fedoraproject.org/
I download "Fedora minimal"
https://download.fed...-1.2-sda.raw.xz
Next I unpack it:
xz -d Fedora-Minimal-armhfp-24-1.2-sda.raw.xz
and write to micro sdhc card:
dd if=Fedora-Minimal-armhfp-24-1.2-sda.raw of=/dev/my_micro_sdhc_card
(I write it to card, not to partition on card).
I have new partitions on this card like:
boot
/
swap
I put my card to Orange and turn it on, but it does not load Fedora.
Does anyone know how to do it, has any experience, can share some knowledge, links with me ?
Fedora offers a script to write the disk image as well as board specific U-Boot and dtb. You can find more information here - https://fedoraproject.org/wiki/Architectures/ARM/F24/Installation#Fedora_Arm_Installer . Be sure to use the latest version in updates-testing (fedora-arm-installer-1.99.12-1.fc24).
We would appreciate feedback or any issues you encounter, you can visit us in #fedora-arm on Freenode or send to our mailing list - https://admin.fedoraproject.org/mailman/listinfo/arm
Paul
I got some brand new banana Pi's,
these are the "Banana Pi-M2" and the "Banana Pi-M3"
I was trying to install Debian on both of them, but I couldn't get it to work.
I was exactly following this tutorial here (Windows):
http://wiki.lemaker.org/BananaPro/Pi:SD_card_installation
to save Debian on the SD Card.
The Problem is always the same. When pressing the power Button on the "M3", or plugging in the "M2", only the red LED goes on and nothing happens.
The LED for the LAN port stays off, so it comes close that the Pi is not booting up.
The power supply I am using produces 5V and 2100mA which should fit the conditions for the Banana Pi.
The distros I then tried to install were for example Bananian which I got from here:
https://www.bananian.org/download
And several distros like Debian from here:
http://www.banana-pi.org/m3-download.html
http://www.banana-pi.org/m2-download.html
I tested it using 2 different SD Cards, and also only using a USB Stick.
everything was producing the same error.
Is there something I missed?
Thanks in advance.
It sounds like an underpowering situation.
If you have a barrel jack instead of micro usb use the barrel jack.
The pre-production samples of this board had the usual 4.0/1.7mm barrel jack for DC-IN BPi M2/M2+ also use. This has been replaced by a Micro USB jack on the first production batch in Dec 2015 leading to the usual sorts of problems banana-pi.org forums are full of (see also next paragraph for some reasons). Starting in May 2016 Micro USB has been replaced by the 4.0/1.7mm barrel jack again so powering is possible more reliable now. The Micro USB receptacle on the longer board side is USB OTG, also connected to the board's PMIC and while looking like an alternative way to power the board that's not recommended unless you love underpowering situations, reboot loops and the like.
I had the same problems at one point, like #Hagen said, it could be under powered, make sure you have a 5V, 2A rated power supply. The other cause of the red led and no boot is the lack of a micro SD card. Try pushing it in a bit further though not with much force and hit reboot. if you get 3 leds, it works!
This Banana PI M3 device starts up and works normally when power supply connector (4mm/1,7mm) and a micro USB connect put to device of Banana same time from same 5V power supply. I think in the device may have something grounding problems.
I have been working for a few days trying to get the UART1 port to work on a bbb. I flashed the prebuilt kernel from the elinux wiki (http://www.elinux.org/BeagleBoardUbuntu#Flasher), and the UART1 appears in the /dev folder (as /dev/ttyO1, with a capital "o" not a zero), but when I write to it, nothing comes out of the pins. I can use UART0 (on a separate little serial header, but not the one I need) without any trouble.
I see a lot of tutorials for enabling UART1 that deal with a folder called /sys/devices/bone_capemgr.* but I don't have one. I think it is because I have a newer kernel, and nearly all of those tutorials are exclusively for older kernels (<=3.8).
I read that the current 3.13 images from Robert C Nelson don't have a cape-manager (https://groups.google.com/forum/m/#!topic/beagleboard/ND3_w7_dn8Q), and you can use the "really simple cape manager" (https://github.com/RobertCNelson/rscm), but the build.sh script doesn't work on my 3.14 kernel. I tried to change a path in the script to fix it and now that bbb won't boot.
I also tried the beaglebone-universal-io script (
https://github.com/cdsteinkuehler/beaglebone-universal-io) but when I query the relevant pin:
sudo ./config-pin -q P8_26
I get the error:
P8_26 pinmux file not found!
Please verify your device tree file
Am I missing something really simple here?