Open sanggod opened 3 years ago
It was supposed to be serial communication. I am not sure about the final GPIOs used. Indeed we had similar problems with lights control (seems like not sending message to Dali Bus). Perhaps use an oscilloscope to measure the output control signals frequency. I have tried to find out a few things, but it is not feasible anymore, since as I said, the hardware setup is withdrawn. Neither of my collegaues in the team is at position to provide solutions. We are all heavily engaged in other projects. So, I can't see how I can help you any further.
I think the entire problem is below
RPI’s GPIO14 pin out, connected to RST pin in Pi click shield, is used to transmit commands (DALI_TX) to the DALI LED driver. On the other hand, RPI’s GPIO15 pin in, connected to INT pin in Pi click shield, is used to receive feedback (DALI_RX) from the DALI LED driver
Understand that you may busy on other projects, but this research is awesome and less people is doing such things via RaspberryPi. Hope I can contribute more and expand the research works.
GPIO 14 is not connect to RST pin in Pi click shield. I purchased all the hardware equipment that mentioned in the research paper. Hope you could give me some hints on how to get GPIO 14 to connect RST pin in Pi Click Shield via Serial connection
using the multimeter, I can verified that, the TX of DALI Board is sending out signal, that means, the GPIO mapping is cleared. However, the DALI Bus is not sending signal out some how V_V
In RPi_DALI_drv.c , it use GPIO_14 & GPIO_15 and it refer to Pi Click RST & Pi Click INT however, according to the specifcation from Click, https://download.mikroe.com/documents/add-on-boards/click-shields/pi-shield/pi-click-shield-schematic-v100.pdf Connecting to DALI click (TX/RX) is using RST & INT but it is not GPIO_14 & 15 Is there any trick to use GPIO 14 & 15?
Now I can run the app and use the kernel module, but cannot control the Lights. It feels like not sending message to Dali Bus