This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

DLP2000: DLP2000EVM-ENG

Part Number: DLP2000

Hello together,

For my project I have to use the DLP2000EVM for 3D-scanning and it should work on a Raspberry Pi 3. I found this code on GitHub:https://github.com/RobertCNelson/boot-scripts/tree/master/device/bone/capes/DLPDLCR2000/structured_light.

This code is designed for the Beagle Bone Black board, so my question is it possible to run the same code on my Raspberry Pi?

I attached the DLP on the Raspberry Pi like in the instructions on this page: http://frederickvandenbosch.be/?p=2948 

Thank you.

  • Hello User,

    The programs in this hub will likely work on the Raspberry Pi. However, modifications are will likely be needed to be made to the scripts to port them over to the RPi. For example, the I2C commands will need to be sent via the following format:

    sudo i2cset -y 3 0x1b 0x0b 0x00 0x00 0x00 0x00 i


    This will have to be reflected in the programs. This can similarly be seen in Vandenbosch's page.

    Additionally, this E2E post may be of use to you regarding integrating the Raspberry Pi video capabilities.

    Regards,

    Austin

  • Hello Austin,

    I changed the I2C commands in the programs. After that I tried to run the ./pattern_disp -t code which should display a few test patterns on the DLP but there is one error showing in the terminal:

    I also tried some of the I2C commands, but nothing happend on the DLP. 

    Regards

    Maximilian

  • Hello User,

    Thank you for the feedback. We will look into the error that you are getting. Thank you for your patience.

    Regards,

    John

  • Hello Maximilian,

    Are you writing to multiple devices in the above screenshot? It appears that you are issuing commands to two I2C buses and two device addresses.

    Our first steps should be confirming that we have a consistent I2C connection. Please refer to Section 2.1 of the DLP2000EVM User's Guide and this E2E thread to ensure that communications are established. Please report back on if this has corrected the issue.

    Regards,

    Austin

  • Hello Austin,

    My apology for the late response. I was checking the code from Kyle Rakos again and I found out that in the code the gpio pins are configured for the Beagle Bone Black.

    This code is from display_app.h from the structured light code from Kyle Rakos.

    I changed the gpio_out and gpio_in to different numbers and after running the ./pattern_disp -t again it didn´t show any error. But it also didn´t show any pictures.

    Do you have an idea what could be the problem?

    Thanks

    Maximilian

  • Hello Maximilian,

    Were you able to establish i2c communication with the above pin chnages? Please refer to the thread shared by austin above for the procdure to validate the i2c communication. 

    If you are able to establish communication please share the detected device address you see listed

    Regards,

    Akhil

  • Hello Akhil,

    When I use the i2cdetect command in the terminal I found the device on the bus 11:

    I also tried some i2c commands to display a test pattern and this worked aswell.

    I think that I need different GPIO pins to get some picture displayed out of the DLP.

    I also tried to set up the /boot/config.txt like in the instructions from Frederick Vandenbosch: http://frederickvandenbosch.be/?p=2948.

    But when I restart the raspberry I can´t see the Desktop screen displayed from the beamer neither on my monitor screen.

    Regards,

    Maximilian

  • Hello Maximilian,

    Thank you for confirming the I2C bus. Does the performance change at all when using only the 11 I2C bus and 0x1b device address?

    Regards,

    Austin

  • Hello Austin,

    I am not sure what you mean exactly. How should I test the DLP to see if the performance is changing?

    Regards,

    Maximilian

  • Hi Maximilian,

    Apologies if my request was unclear. I was hoping to see if the errors were cleared from the terminal and the behavior was changed on the DLP system if the I2C bus and device address were included in the below commands in place of those used previously.

    Regards,

    Austin