Cobrapin RGBW issue

[Anthony Bates]

I am retheming a 1978 Stern pin and using a combination of LISY35 as the MPU to control the backbox, switches, and coils, and then just added the Cobrapin in order to swap all the playfield lights to RGBW LEDs. I'm having an issue with the coding/syntax side of things though. I initially had my lights config set up as just type: rgb and while the lights would work, obviously the channels were all wrong so the combination of lights and colours were all over the place. 
I since changed the format to reference the "previous" named LED and changed it to RGBW. Now when I run mpf, none of my coils or switches load for some reason and I get this response when I close MPF:
(mpf) PS C:\Users\antho\nightpin> mpf both -x
Godot Engine v4.3.stable.official.77dcf97d8 - https://godotengine.org
Vulkan 1.4.312 - Forward Mobile - Using Device #0: NVIDIA - NVIDIA GeForce RTX 2060

12:23:29.913 : LOG : GMC : Initializing GMC version 0.1.3
12:23:29.913 : LOG : GMC : Found GMC configuration file C:/Users/antho/nightpin/gmc.cfg.
12:23:30.095 : INFO : GMCMedia : Traversing directory tree for media.
12:23:30.112 : INFO : Registered display MPFDisplay<DefaultDisplay>
12:23:30.123 : INFO : GMCServer : GMC listening on port 5050
ERROR: BUG: Unreferenced static string to 0: Physics2DConstraintSolveIslands
   at: unref (core/string/string_name.cpp:127)
ERROR: BUG: Unreferenced static string to 0: Physics2DConstraintSetup
   at: unref (core/string/string_name.cpp:127)
ERROR: BUG: Unreferenced static string to 0: @export_range
   at: unref (core/string/string_name.cpp:129)
ERROR: BUG: Unreferenced static string to 0: @export_multiline
   at: unref (core/string/string_name.cpp:129)
ERROR: BUG: Unreferenced static string to 0: @icon
   at: unref (core/string/string_name.cpp:129)
ERROR: Pages in use exist at exit in PagedAllocator: N7Variant5Pools11BucketLargeE
   at: ~PagedAllocator (./core/templates/paged_allocator.h:170)
Shutdown reason: SIGINT or keyboard interrupt

I have attached my main config and lights config files and am using MPF version 0.80. Any help would be appreciated because I have tried multiple variations and cannot control the RGBW LEDs how I would like. 

Additionally, if anyone is well versed in MPF and would be interested in helping write code, I would be very happy to pay someone for their time. This is a big project that a started back in August and unfortunately my work and life schedule has since taken a huge turn so my progress has slowed to a crawl and some additional help working through the coding side of things would be incredibly appreciated. 

Anyway, if anyone can point me in the right direction or is willing to help code for paid compensation, please let me know. 

Thanks in advance,

Anthony 

[cobra18t]

I am not familiar with GMC as I have not used 0.80 yet. That does not look like a lighting related error, though. Someone else will have to chime in on that.

On your lights, however, I would change the type to "type: grbw" as that is the channel order of the LEDs you got from me. I know, we refer to them as RGBW but internally they are GRBW.

[Anthony Bates]

Thanks for the response. I'm not sure if there is an issue with using RGBW LEDs with OPP in MPF 0.80+ or if I am just using incorrect syntax. It's weird that it will work if I have them labelled as just RGB but crashes when I change it to RGBW. 

Good to know about the GRBW order though. I thought that was the case and figured the colours would just be off if so, but currently can't actually progress to even running my pin at present when everything was working before this change. 

Hopefully someone else has the fix. I'm hoping I don't have to roll back to an earlier version of mpf now that I am finally getting my head around Godot. 

Cheers,

Anthony 

--
You received this message because you are subscribed to a topic in the Google Groups "MPF Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/mpf-users/91qXQ8eIJsM/unsubscribe.
To unsubscribe from this group and all its topics, send an email to mpf-users+...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/mpf-users/8739f057-2897-4517-abe3-575b3d885211n%40googlegroups.com.

[cobra18t]

Could you also post the mpf and gmc logs when the error occurs?

I noticed you have a list defined for the "platform" section of your config. Typically, you would only define one as the default and assign the other individually as you have already done in the lights section. I would probably make the platform section just "platform: lisy"

More details here:  Mixing-and-Matching hardware platforms - The Mission Pinball Framework

[cobra18t]

Oh, and I do know that RGBW with OPP/CobraPin works on MPF 0.80 because multiple people have it working. I have just never done it myself. The RGBW/OPP elements were not really changed from 0.57 to 0.80 as that is handled on the MPF core side, not the GMC side.

[Anthony Bates]

Okay, good to know. I figured there would be no reason that RGBWs would work in 0.57 and not 0.80, but was wondering if something with my config files is not formatted correctly. 

I was under the impression that I had to list all used hardware under the platform section but I did just try removing opp under my hardware section and the same issue remains. 

I have attached a complete log when I try to run the machine and it seems to have an issue with my attract mode. I'm not sure why though as I have not actually changed anything in my attract mode apart from the names of the shows. 

I have attached a copy of the log as well as my attract mode and two shows associated with the mode. For the shows I used the show creator software to design these. They're relatively simple because I just wanted to get things up and running first. Perhaps there is a formatting issue with my attract mode or one of the 2 shows but I can't work out what the issue would be.  

To view this discussion visit https://groups.google.com/d/msgid/mpf-users/92021fdf-26a7-4475-bdad-bd0ff519c594n%40googlegroups.com.

[cobra18t]

Sorry, I only see 3 yaml files and no log files.

[Anthony Bates]

Oh sorry, not sure why that didn't attach. Here it is. 

To view this discussion visit https://groups.google.com/d/msgid/mpf-users/89899661-9f7c-4063-8dfb-b60908360a2fn%40googlegroups.com.

[cobra18t]

Is there a gmc log as well?

[Anthony van Winkle]

What an interesting challenge!

The Godot crash at the top has nothing to do with GMC, and I suspect it's just Godot crashing at some point because the connection is being dropped and the program is exiting.

I would recommend running mpf with the -b option to disregard BCP connections, and don't run GMC/Godot. This will help to isolate whatever issue MPF is having that's causing it to not boot correctly.

That said, something is definitely off about that MPF log because it skips right from init_phase_1 at 10:26:50 to starting the main loop at 10:26:55, so that's five seconds missing where all of the initialization and startup procedures occur. Not sure what's going on there, but adding -v -V to the command will output and log a lot more, and hopefully that can shed some more light on the situation.

[Anthony Bates]

There doesn't appear to be. I added a logging section in my main config for GMC but I don't see any comment of GMC in the log. I think MPF is crashing before it even gets to the point of loading GMC. 

To view this discussion visit https://groups.google.com/d/msgid/mpf-users/cefb6a55-6dda-4fab-b5b7-b8bf9a85bde9n%40googlegroups.com.

[cobra18t]

What CobraPin board(s) is hooked up? The main board or something else?

[cobra18t]

Please run "mpf hardware scan" from your machine folder and post the full output.

[Anthony Bates]

Yeah I'm really confused as to what's happening. My config files and pin used to work just fine and the only things I have updated are the main config to include OPP as well as the lights config and my attract mode with associated light shows. 
I tried running again with -v as well as -b. I have attached the 2 logs from those attempts. 

It still seems to be having an issue with the lights config and then attract mode, presumably because the attract mode cannot work properly due to the lights config. I'm just not sure how to get around this issue. 

I only have the main cobrapin board hooked up in addition to LISY35 but nothing else. 

To view this discussion visit https://groups.google.com/d/msgid/mpf-users/f9800c36-874a-4150-b339-75fb9a331baen%40googlegroups.com.

[cobra18t]

Ah, there is at least one problem. "number" is not a valid setting for RGBW because it assumes 3 channels. You need "start_channel: 0-0-0" in your config of l_top_right_corner instead.

[Anthony van Winkle]

In case it helps, here are two of my configs. One of them uses a combination of Cobra RGBW and regular RGB lights, note that I have to manually code some of the addresses to account for some lights having four channels and the others having three, but it does the job. The other config includes two lighting platforms: fadecandy (the default) and fast, with some lights specifying platform:fast as appropriate. Also a mix of RGB and GRB lights, some explicit channels and other using the "previous" syntax.

Hopefully something in there is helpful?

[Anthony van Winkle]

That being said, at least the logs are saying something that may guide you in the right direction:

Config File Error in ConfigValidator: Your config contains a value for the setting "lights:l_top_right_corner:led_order", but this is not a valid setting name.