• 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 for Raspbian Buster (raspberry pi 4) ? starob 31 7,139 2 hours ago
Last Post: PPacman
  No hardware module configured steffeneilers 3 236 06-25-2020, 08:22 AM
Last Post: steffeneilers
  pilight switch node in node-red framp 0 228 06-24-2020, 10:01 PM
Last Post: framp
  pilight-control TML 13 890 05-27-2020, 07:51 AM
Last Post: curlymo
  API Requests by HTTP from other devices fore use in pilight scootermacro 2 397 05-10-2020, 08:19 AM
Last Post: scootermacro
  pilight-send seems successful but doesn't actually send RF signal ayeyebrazov 37 3,073 03-31-2020, 01:02 PM
Last Post: curlymo
  pilight 8.1.5 not working on Raspberry pi after reboot beejayf 4 839 03-08-2020, 12:14 AM
Last Post: beejayf
  pilight cpu usage possibly associated with noticeable sluggishness? hepcat72 4 893 01-28-2020, 08:02 PM
Last Post: hepcat72
  apt.pilight.org stable Release' is not signed. thomasol 2 939 01-23-2020, 11:34 PM
Last Post: thomasol
  pilight and SIGNALduino cc1101 Caleus 0 686 01-19-2020, 09:13 AM
Last Post: Caleus

Forum Jump:

Browsing: 1 Guest(s)