• 10 dec 2017: forum version update. In case of issues use this topic.
  • 30 nov 2017: pilight moved servers. In case of issues use this topic.
Hello There, Guest! Login Register

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Basic testing pilight hardware

Recently I have bought and soldered the full PCB from the pilight store and mounted it on the GPIO pins of my Pi3B+. After that I have changed the config to reflect that I have a Pi 3 and added the gpio430 hardware settings with 0 and 1 that should correspond with pins 11 & 12 that should be the ones the PCB is wired to.

My next step would be to find put if the hardware is working but this proves to be much harder than expected. I have tried running pilight-debug and it does sporadically receive some data, but when I use my APC3 kaku remote it does not react at all.  

What would be a good way to test if the PCB has been soldered correctly and the hardware is working? Are there some sensible diagnostical steps?

Kind regards,

Just check if you see a reasonable input change in pilight-raw when pushing a button on a 433.92Mhz device.
(06-05-2018, 10:11 PM)curlymo Wrote: Just check if you see a reasonable input change in pilight-raw when pushing a button on a 433.92Mhz device.

I do not see any immediate change as a result of sending signals with the remote. Signals do appear eventually though using pilight-raw. These are 3 pulse signals same as the remote produces. Should pilight-raw show output immediately or does it periodically output what it received?
(06-06-2018, 05:28 PM)curlymo Wrote: Immediatly.

Ok, that is not what I am seeing, though I get other raw signals. How would you recommend debugging this? I have no idea how to eliminate possible issues with the PCB. 
- Power seems ok since it gets raw signals. 
- GPIO wiring also seems ok (gpio433 0,1 should work by default I read)
- Can it be the kaku remote?
- Buy a pre soldered PCB as well and compare?
- Use an external USB sender receiver and compare?
I would really appreciate a nudge in the right direction and would be more than happy to share my findings should I find out what is wrong.
I would first check with directly connection the sender/receiver to the pi.

Possibly Related Threads...
Thread Author Replies Views Last Post
  pilight 8.1.4 crashes after some hours Ulrich.Arnold 1 12 Yesterday, 06:43 PM
Last Post: curlymo
  pilight-send does not stop (terminate) va13 3 52 05-15-2019, 06:06 PM
Last Post: curlymo
  oom_reaper: reaped process pilight-daemon va13 4 77 05-15-2019, 08:03 AM
Last Post: va13
  cant configure or even start pilight on raspi 3b Xvnx23 2 88 05-06-2019, 09:47 PM
Last Post: fourty2
Sad Raspberry Pi: "NOTICE: no pilight ssdp connections found" abusch 8 115 04-30-2019, 09:10 PM
Last Post: curlymo
  Using pilight-daemon socket API def_meggi 4 78 04-29-2019, 05:58 PM
Last Post: curlymo
  pilight-flash not working danny 9 165 04-27-2019, 09:02 PM
Last Post: curlymo
  pilight and Lirc lordslash 3 82 04-24-2019, 06:32 PM
Last Post: curlymo
  hardware module issues in nightly apartmedia 17 382 04-05-2019, 06:59 PM
Last Post: curlymo
Question Pi 3+ & pilight & 433Mhz RXB6: no receiption hacklschorsch 3 434 02-05-2019, 10:37 PM
Last Post: hacklschorsch

Forum Jump:

Browsing: 1 Guest(s)