Beiträge von videxx

IT WOOOOORKS

Finally done with the wiring. Would be very nice if anyone could proof that its correct.

Hi
My LED and PSU arrived today. I am wiring everything up right now. I will send a picture when I´m done just to be sure it is correct

Zitat von jeroen warmerdam

no problem man,

I have the same setup almost but i am running Rasbian Buster full with Hyperion.NG 2.1 as .deb package
did all the updates and upgrades
APA102 and WS2801 works out of the box on RPI3b, no resistors or Arduino or levelshifters needed.
I see it like this always; the less equipment you need the less can go broke or offline

see you then

Alles anzeigen

True, but in this case the most important pice of equipment seems to be broke. Now it is just Ambi without light

Zitat von jeroen warmerdam

SPI mode is the kind of signal you just tested on the GPIO's, 0 is spi device0 > thats the first device output for SPI devices
you have also SPI 0.1 but that's almost never in use because default is 0

why did i have spi mode 4 and you had spi mode 0 ?

Zitat von jeroen warmerdam

Troubleshooting
Loopback test
This can be used to test SPI send and receive. Put a wire between MOSI and MISO. It does not test CE0 and CE1.

wget https://raw.githubusercontent.…ntation/spi/spidev_test.c
gcc -o spidev_test spidev_test.c
./spidev_test -D /dev/spidev0.0
spi mode: 0
bits per word: 8
max speed: 500000 Hz (500 KHz)

FF FF FF FF FF FF
40 00 00 00 00 95
FF FF FF FF FF FF
FF FF FF FF FF FF
FF FF FF FF FF FF
DE AD BE EF BA AD
F0 0D

example of output after command, source https://www.raspberrypi.org/do…raspberrypi/spi/README.md

Alles anzeigen

do you know what spi mode is

sounds very nice
thank you so much for troubleshooting with me
I will get back here sometime next week, when the new LED stripe arrived

Now I am pretty shure the LED stripe is broke.
All pins are connected right and die SPI output is working
And also the software is up to date

just bc I´m interrested: what do you do for a living? you know so lot about all this stuff xD

so
GND to GND
DI to GPIO10
CI to GPIO11
right?

updates made (for the last command it said 0 installed)
just reconnected the pins, I think I didn´t connect the right ones, now gpio9 and gpio10 are connected. New output:

The updates are running right now, shouldn´t take to long

Zitat von jeroen warmerdam

did you connect the pins together? GPIO 9 and 10

yes

ok, I´ll do it.
thats the output for the test:

Zitat von jeroen warmerdam

btw;

did you run a few commands before installation in the terminal like

sudo apt-get update
sudo apt-get upgrade

sudo apt-get install git cmake build-essential qtbase5-dev libqt5serialport5-dev libqt5sql5-sqlite libqt5svg5-dev libqt5x11extras5-dev libusb-1.0-0-dev python3-dev libcec-dev libxcb-image0-dev libxcb-util0-dev libxcb-shm0-dev libxcb-render0-dev libxcb-randr0-dev libxrandr-dev libxrender-dev libavahi-core-dev libavahi-compat-libdnssd-dev libjpeg-dev libturbojpeg0-dev libssl-dev zlib1g-dev
sudo apt-get install libraspberrypi-dev

Alles anzeigen

do you mean with the other raspberry? I didn´t do it for the Hyperbian one, I thought that all this stuff should be preinstalled

Oh its 19 and 21

I will try it. So MOSI and MISO should be pin 19 and 23 on raspberry Pi3 right?

smothing is off
I think Hyperbian should work as its only job is to run Hyperion
I just installed Raspbian on another Raspberry and used python with code from a tuturial to try it out and it also didn´t work

Where is this setting? What is tab remote?
Is there a program you can recommend?
Ik, that was the reason why i choose it. I will get a new on from the seller next week.

So, baudrate is correct now and for some reason some random LEDs are white now, I mean immediately after I plugged into power. Controlling still doesn´t work. As I saw the line "dtparam=spi=on" spi seems to be on so it should be the stripe which isn´t working. Just wrote an mail to the amazon vendor

do you know where i can check this in the conifig.txt?

mine looks like this:

# For more options and information see
# http://rpf.io/configtxt
# Some settings may impact device functionality. See link above for details

# uncomment if you get no picture on HDMI for a default "safe" mode
#hdmi_safe=1

# uncomment this if your display has a black border of unused pixels visible
# and your display can output without overscan
disable_overscan=0

# uncomment the following to adjust overscan. Use positive numbers if console
# goes off screen, and negative if there is too much border
#overscan_left=16
#overscan_right=16
#overscan_top=16
#overscan_bottom=16

# uncomment to force a console size. By default it will be display's size minus
# overscan.
#framebuffer_width=1280
#framebuffer_height=720

# uncomment if hdmi display is not detected and composite is being output
hdmi_force_hotplug=1

# uncomment to force a specific HDMI mode (this will force VGA)
#hdmi_group=1
#hdmi_mode=1

# uncomment to force a HDMI mode rather than DVI. This can make audio work in
# DMT (computer monitor) modes
#hdmi_drive=2

# uncomment to increase signal to HDMI, if you have interference, blanking, or
# no display
#config_hdmi_boost=4

# uncomment for composite PAL
#sdtv_mode=2

#uncomment to overclock the arm. 700 MHz is the default.
#arm_freq=800

# Uncomment some or all of these to enable the optional hardware interfaces
#dtparam=i2c_arm=on
#dtparam=i2s=on
dtparam=spi=on

# Uncomment this to enable infrared communication.
#dtoverlay=gpio-ir,gpio_pin=17
#dtoverlay=gpio-ir-tx,gpio_pin=18

# Additional overlays and parameters are documented /boot/overlays/README

# Enable audio (loads snd_bcm2835)
dtparam=audio=on

[pi4]
# Enable DRM VC4 V3D driver on top of the dispmanx display stack
dtoverlay=vc4-fkms-v3d
max_framebuffers=2

[all]
#dtoverlay=vc4-fkms-v3d

#self edit
core_freq=250