PLEASE HELP! No LED responses

[Greg Sealby]

I am having some difficulties with LEDs and was hoping I could get a sanity check on my config.  When we turn the machine on, all LEDs come up...which is good.  We have configured two PD-LEDs.

The config on mu config.yaml for PROC is as follows:

hardware:
   platform: p3_roc
   driverboards: pdb

Do I need to add anything to this for the LED boards?

My LED configs look like this:

#config_version=5
lights:
#------------------------------------------------------------
# LIGHTS::GAME::PD_LED Board 1 (0-x-x-x)
#------------------------------------------------------------
    l_top_lane_1:
      number: 0-0-1-2
      subtype: led
    l_top_lane_2:
      number: 0-3-4-5
      subtype: led
    l_top_lane_3:
      number: 0-6-7-8
      subtype: led
    l_popbumper_top_left_1:
      number: 0-9-10-11
      subtype: led
    l_popbumper_top_left_2:
      number: 0-12-13-14
      subtype: led

I have set up a show that responds to an event when you hit switches on the playfield:

#config_version=5
show_player:
    test_l_top_lane_1:
        show_lights_test:
            loops: 0
            show_tokens:
                led: l_top_lane_1
                colour1: green
                colour2: blue
                colour3: red
                colour4: yellow
                colour5: purple

I can see the test_l_top_lane_1 event firing when I press the top lane switch, but no change in the LED colours as per the show.

Is there something incorrect/missing from my config?

[jabdoa]

Hi Greg,

Config looks good. A few things to verify:

1. Is the ID of your PD-LED 0? Is the ID of your second one 1?
2. Does the watchdog LED turn off when you send the first color? If not you probably have some kind of bus issue (usually twisted wires or missing ground).
3. Are you running MPF without -X?

Things I'm not sure about:
1. For switches and coils it is not a good idea to use the first four IDs (because they can be shadowed by the P3-Roc for local switches/coil). Not sure if this also happens with PD-LEDs.
2. I'm also not sure if PD-LED IDs might conflict with PD-16 IDs. But it would be worth a try to give them separate ones.

Jan

[jabdoa]

You can also use the service cli to turn LEDs on/off in case you want to rule out problems with your show: http://docs.missionpinball.org/en/dev/tools/service_cli/index.html. Alternatively you can verify the color of your lights using MPF monitor.

Jan

[Greg Sealby]

Thanks Jan, that was really helpful.  Yes, I know all about the watchdog LED now on these boards!

I ended up finding the issue.  It seems that all of the PD-LED boards we got came from the factory with the address 4 dipswitch set on.  I didn't check that, I was only checking the first two address dipswitch settings, assuming that all others were off by default.  Dumb assumption.

Appreciate your help!

[Greg Sealby]

Still having an issue with LEDs ... The colours are not what I am sending.  In fact they seem to be the opposite - when they should be blue they are white, white when they should be blue.  Has anybody had issue with their LEDs coming out unexpected colours and what did you do?

[mike wiz]

Are you using serial LEDs? 

In my config for lights I need to put:

type: grb

http://docs.missionpinball.org/en/dev/mechs/lights/leds.html?highlight=type%3A%20grb#serial-leds

If not try setting the channels?

[jabdoa]

On PD-LED this might either be the channel order or your LEDs might be common anode/cathode. Try setting invert to true in that case. It sounds like that to me.

What color do you get with red? What with green? What with blue?

Jan

[Greg Sealby]

Appreciate the advice Mike, thanks.

Jan, you put me on the right track, and this is a case of I should have read the doco properly - it was in there.  Just needed to set the polarity for each LED... This did the trick.

      platform_settings:
         polarity: True