Main Restorations Software Audio/Jukebox/MP3 Everything Else Buy/Sell/Trade
Project Announcements Monitor/Video GroovyMAME Merit/JVL Touchscreen Meet Up Retail Vendors
Driving & Racing Woodworking Software Support Forums Consoles Project Arcade Reviews
Automated Projects Artwork Frontend Support Forums Pinball Forum Discussion Old Boards
Raspberry Pi & Dev Board controls.dat Linux Miscellaneous Arcade Wiki Discussion Old Archives
Site News

Unread posts | New Replies | Recent posts | Rules | Chatroom | Wiki | File Repository | RSS | Submit news


  

Author Topic: Having trouble with RGBCommander and Led-WizGP  (Read 396 times)

0 Members and 1 Guest are viewing this topic.

MacGyver

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 288
Having trouble with RGBCommander and Led-WizGP
« on: March 24, 2018, 04:28:22 pm »
My issue is that I have single LED buttons, in fact I have no RGB LEDs in use at all, and this hasn't been an issue with LEDBlinky for years.
However I'm trying really hard to break free from using Windows in our cabinet so I found RGBCommander and thought I might be able to finally switch to Linux.

I have 21 LEDs connected to various ports on my LED-Wiz (2-18 and 29-32), and I have tried various ways of making RGBCommander just turn the single lights off and on.
Here is what I have right now. (using 2 unused ports for Green and Blue)
Code: [Select]
<ledboards>
<ledboard name="LEDWIZ_1" hwthrottle="12000">
                        <control name="P1_TRACKBALL" pin="2,20,21"/>
                        <control name="P2_START" pin="3,20,21"/>
                        <control name="P1_START" pin="4,20,21"/>
                        <control name="P1_BUTTON6" pin="5,20,21"/>
                        <control name="P1_BUTTON5" pin="6,20,21"/>
                        <control name="P1_BUTTON4" pin="7,20,21"/>
                        <control name="P1_BUTTON3" pin="8,20,21"/>
                        <control name="P1_BUTTON2" pin="9,20,21"/>
                        <control name="P1_BUTTON1" pin="10,20,21"/>
                        <control name="P2_BUTTON1" pin="11,20,21"/>
                        <control name="P2_BUTTON2" pin="12,20,21"/>
                        <control name="P2_BUTTON3" pin="13,20,21"/>
                        <control name="P2_BUTTON4" pin="14,20,21"/>
                        <control name="P2_BUTTON5" pin="15,20,21"/>
                        <control name="P2_BUTTON6" pin="16,20,21"/>
                        <control name="P2_JOYSTICK" pin="17,20,21"/>
                        <control name="P1_JOYSTICK" pin="18,20,21"/>
                        <control name="P1_COIN" pin="29,20,21"/>
                        <control name="P2_COIN" pin="30,20,21"/>
                        <control name="P1_BUTTON8" pin="31,20,21"/>
                        <control name="P2_BUTTON8" pin="32,20,21"/>
  </ledboard>
</ledboards>
This method has mixed results, lighting up buttons 1-6 on Player 1 with Red will turn off each one before, and using White doesn't, but turns on Player 2 buttons here and there.
I have tried using various methods of configuring RGBC to only use one LED, like this: (where I use the same bogus port for the unused ones)
Code: [Select]
<control name="P2_BUTTON8" pin="32,0,0"/>
and tried using second and 3rd port that were out of range and different one for all the assignments
Code: [Select]
<control name="P2_BUTTON8" pin="32,49,50"/>

But I get random results.
The only thing that works is if I stay in the confines of the way the program works and do something like this:
Code: [Select]
                        <control name="P1_BUTTON1" pin="2,3,4"/>
                        <control name="P1_BUTTON2" pin="5,6,7"/>
                        <control name="P1_BUTTON3" pin="8,9,10"/>
                        <control name="P1_BUTTON4" pin="11,12,13"/>
                        <control name="P1_BUTTON5" pin="14,15,16"/>
                        <control name="P1_BUTTON6" pin="17,18,29"/>
                        <control name="P2_BUTTON1" pin="30,31,32"/>
And then make crazy color mixes to turn whole buttons off and on, so white turns on all 3 but red only the first, green only the 2nd, and orange the first 2.

That method is too nuts to deal with.

I tried this:
Code: [Select]
                        <control name="P1_TRACKBALL" pin="2,2,2"/>
                        <control name="P2_START" pin="3,3,3"/>
                        <control name="P1_START" pin="4,4,4"/>
                        <control name="P1_BUTTON6" pin="5,5,5"/>
                        <control name="P1_BUTTON5" pin="6,6,6"/>
                        <control name="P1_BUTTON4" pin="7,7,7"/>
                        <control name="P1_BUTTON3" pin="8,8,8"/>
                        <control name="P1_BUTTON2" pin="9,9,9"/>
                        <control name="P1_BUTTON1" pin="10,10,10"/>
                        <control name="P2_BUTTON1" pin="11,11,11"/>
                        <control name="P2_BUTTON2" pin="12,12,12"/>
                        <control name="P2_BUTTON3" pin="13,13,13"/>
                        <control name="P2_BUTTON4" pin="14,14,14"/>
                        <control name="P2_BUTTON5" pin="15,15,15"/>
                        <control name="P2_BUTTON6" pin="16,16,16"/>
                        <control name="P2_JOYSTICK" pin="17,17,17"/>
                        <control name="P1_JOYSTICK" pin="18,18,18"/>
                        <control name="P1_COIN" pin="29,29,29"/>
                        <control name="P2_COIN" pin="30,30,30"/>
                        <control name="P1_BUTTON8" pin="31,31,31"/>
                        <control name="P2_BUTTON8" pin="32,32,32"/>
But to give you an idea of how bizare it acts, if I send "set,button,P1_BUTTON1,Blue" it only turns on P2_BUTTON2, and if I send "set,button,P1_BUTTON1,Green" it only turns on P2_BUTTON1, and if I send "set,button,P1_BUTTON1,Red" it actually turns on P1_BUTTON1, sending White tuns on all 3 buttons. Remember every port is set to just one number, in this case 10,10,10. How is it turning on 11 and 12?

The only way this makes any sense is if it doesn't care what you set the 2nd and 3rd number to, it just seems to be assigning the last two numbers to what ever the first number was +1 and then +2.


How can I configure RGBCommander to go against its RGB nature and let me assign a single port for all 3 color profiles? (I know there will be issues when the default button assignments and I'm willing to deal with it)

Is my only way of using Linux to buy a second LedWiz and hook up all 21 LEDs to every 3rd port?
I really just need a way assigning any color to activate only one port, or making RGBCommander treat assignments as off/on like the monitor rotate feature must. I'd settle for it just letting me assign the same number to all three.

I'm more than willing to try to solve it myself if anyone has access to the sourcecode.  Is there another program better suited for my setup that runs under Linux?

Thanks for any help anyone can give me.

MacGyver

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 288
Re: Having trouble with RGBCommander and Led-WizGP
« Reply #1 on: March 24, 2018, 05:14:34 pm »
I also tried assigning them the following values:

Code: [Select]
                        <control name="P1_TRACKBALL" pin="2"/>
                        <control name="P2_START" pin="3"/>
                        <control name="P1_START" pin="4"/>
                        <control name="P1_BUTTON6" pin="5"/>
                        <control name="P1_BUTTON5" pin="6"/>
                        <control name="P1_BUTTON4" pin="7"/>
                        <control name="P1_BUTTON3" pin="8"/>
                        <control name="P1_BUTTON2" pin="9"/>
                        <control name="P1_BUTTON1" pin="10"/>
                        <control name="P2_BUTTON1" pin="11"/>
                        <control name="P2_BUTTON2" pin="12"/>
                        <control name="P2_BUTTON3" pin="13"/>
                        <control name="P2_BUTTON4" pin="14"/>
                        <control name="P2_BUTTON5" pin="15"/>
                        <control name="P2_BUTTON6" pin="16"/>
                        <control name="P2_JOYSTICK" pin="17"/>
                        <control name="P1_JOYSTICK" pin="18"/>
                        <control name="P1_COIN" pin="29"/>
                        <control name="P2_COIN" pin="30"/>
                        <control name="P1_BUTTON8" pin="31"/>
                        <control name="P2_BUTTON8" pin="32"/>
But it also acts weird. I can turn almost all the LEDs on at once with "set,leds,on,White", (almost in that it doesn't turn on the ones attached to port 31 and 32 for some reason).
The log looks like this afterwards:
Code: [Select]
24/03/18 20:49:51 [INFO] [startListening] processing command  set,leds,on,White
24/03/18 20:49:51 [INFO] [processCmd] #args is 4
24/03/18 20:49:51 [INFO] [processCmd] set
24/03/18 20:49:51 [INFO] [processCmd] leds
24/03/18 20:49:51 [INFO] [processCmd] on
24/03/18 20:49:51 [INFO] [processCmd] White
24/03/18 20:49:51 [INFO] [fadeSpeed] unsupported/unimplemented command
24/03/18 20:49:51 [WARNING] [allOn] setting LEDWIZ_1 -> fadeSpeed(0) -> failed

but then "set,button,P2_BUTTON2,White" stops working entirely for any button. and the log looks like this:
Code: [Select]
24/03/18 20:52:38 [INFO] [startListening] processing command  set,button,P2_BUTTON2,White
24/03/18 20:52:38 [INFO] [processCmd] #args is 4
24/03/18 20:52:38 [INFO] [processCmd] set
24/03/18 20:52:38 [INFO] [processCmd] button
24/03/18 20:52:38 [INFO] [processCmd] P2_BUTTON2
24/03/18 20:52:38 [INFO] [processCmd] White
24/03/18 20:52:38 [ERROR] [setButton] got inexistent button -> P2_BUTTON2 -> skipping

The only thing that seems to work is using the "set,button,LEDWIZ_1,5,White" style commands, but they do the same weird "applies to what would be the 2nd and 3rd pins" and lights up the next 2 LEDs as well.
Its log output looks like this:
Code: [Select]
24/03/18 21:08:31 [INFO] [startListening] processing command  set,button,LEDWIZ_1,5,White
24/03/18 21:08:31 [INFO] [processCmd] #args is 5
24/03/18 21:08:31 [INFO] [processCmd] set
24/03/18 21:08:31 [INFO] [processCmd] button
24/03/18 21:08:31 [INFO] [processCmd] LEDWIZ_1
24/03/18 21:08:31 [INFO] [processCmd] 5
24/03/18 21:08:31 [INFO] [processCmd] White


Any ideas?

ZoOl007

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 125
    • RGBcommander
Re: Having trouble with RGBCommander and Led-WizGP
« Reply #2 on: March 27, 2018, 03:12:05 am »
Hi, I must say I  haven't read your complete post in detail. You're actually trying to use it for something it wasn't designed to do.
RGBcommander is all about RGB leds - hence the name :)
I know of two people that actually use it like you want it to work (to some degree or completely - I'm not really sure).
There is a section in the rgbcmdd.xml UIO example that mentions single color leds - search for the word 'hacky'.
The key will be that you need to use color values 255,0,0   0,255,0    0,0,255 255,255,0 etc - check the colors section. Basically you're going to tell the daemon you've got x/3 buttons.
So BUTTON1 wil be on pin 1,2 and 3 for example but in reality you have 3 buttons not one...
So, if you want your real 1 and 2 lit you write 255,255,0 to the BUTTON1 and that'll yield what you want.
You'll need to fiddle around with the correct 'colors' to obtain the result you want.
If 0.5 ever sees the light of day I'll likely open source it and consider implementing single color leds. It won't happen any time soon though. No time...

EDIT: I just completely read your post...
as you state : That method is too nuts to deal with. well yes that's the above he... so no can do I'm afraid.
As for the bold section e.g. the +1 +2 that is correct - it doesn't really care in that area iirc . I wrote that part a long time ago...

I'll think about an elegant way to implement it... it does interest me but it's just that there are only 24 hours in a day you know.
« Last Edit: March 27, 2018, 12:42:57 pm by ZoOl007 »

ZoOl007

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 125
    • RGBcommander
Re: Having trouble with RGBCommander and Led-WizGP
« Reply #3 on: March 27, 2018, 12:51:41 pm »
Tell me: how do you want to see it function?
How should I translate for example 128,26,175 to a single color button? Or shouldn't I?
What do you expect to happen when you launch a rom that has rgb preconfiguration data in the rgbcmdd.xml
Describe your needs please.

MacGyver

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 288
Re: Having trouble with RGBCommander and Led-WizGP
« Reply #4 on: March 27, 2018, 09:29:54 pm »
Thanks for looking into it, I've been wanting to get rid of Windows from our cabinet for a long time and your program only brings me closer to that goal.

I would be happy with one of your crude early test binaries that I could throw 2 variables at representing the port and intensity. I could then create some scripts to do the rest.

As far as how to implement it into RGBCommander, simply having the ability to set the second and third variables to specific non-sequential ports including setting them to a bogus or NULL assignment would work too, I could easily change every color reference to White or Red and it would simply act as an off or on (setting it to above 0 but less than 255 would be on but dimmer), I am more than happy to put in the work needed to accommodate any implementation that lets me use Linux in my cabinet. Believe me, I tried everything to work within the confines of the existing RGBCommander.

Thanks again for even the possibility and the work you've put in so far. :cheers:  (also the builtin SevoStik support works great and I love the way RGBCommander it blinks the player 1 buttons when I play Dig Dug)
« Last Edit: March 27, 2018, 10:29:23 pm by MacGyver »

ZoOl007

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 125
    • RGBcommander
Re: Having trouble with RGBCommander and Led-WizGP
« Reply #5 on: March 29, 2018, 01:19:07 pm »
Hi,
I adapted the daemon to work with single color leds for the LEDWiz board only. By no means conclusive and I can't test it but logically it has to work.
When all three pins are the same it considers it to be a non RGBled and it'll calculate the average of the RGB values yielding 'an' intensity that'll be consistent with the config.
That way it'll map its whole RGB cfg to an 'intensity map' for the regular leds
So, to have a full intensity you write 'White' and to have it fully off you write 'Off'(yes, that's a color too).
If the pins differ, the original method is called. So, it'll only really kick in if you specify for example <control name="P1_BUTTON1" pin="6,6,6"/>.
One should be able to mix RGB and normal leds too.
If you like to invest some time and thoroughly test it contact me by email please.
If it works out I'll try to find time to properly integrate it for all supported hardware.
Cheers.

MacGyver

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 288
Re: Having trouble with RGBCommander and Led-WizGP
« Reply #6 on: March 30, 2018, 04:55:14 pm »
That rocks! And is a clever way to keep the color system happy!

I'm more than happy to test it out. I sent you an email.

Thanks again.
« Last Edit: March 30, 2018, 04:58:59 pm by MacGyver »

MacGyver

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 288
Re: Having trouble with RGBCommander and Led-WizGP
« Reply #7 on: April 01, 2018, 01:12:01 am »
Sorry it took so long to check back in, I had to completely rebuild the whole OS following some unrelated Linux live/persistence failure.

So I tried it, and after designating all colors to 255,255,255, it worked perfectly.

The only thing is that it crashed after a bit of running the random light sequence once, may have been a fluke.

It does exactly what I hoped it would do.  Thank you.

My only wish would be to have Attract Mode be able to light the buttons based upon the game currently in the selector, but that is Attract Mode and not RGBCommander.

Thanks for looking into it and coming up with a perfect solution, here is a sample of the log after running a few games though Mame from Attract Mode so you can know what it outputs.

Code: [Select]
user@arcade:~$ tail -f /usr/sbin/rgbcommander/rgbcmdd.log
31/03/18 21:48:47 [INFO] [processMonitor] mame is no longer running
31/03/18 21:48:47 [INFO] [setStick] committing state to joystick hardware -> SERVOSTIK
31/03/18 21:48:47 [INFO] [setWay]SERVOSTIK already in position 8
31/03/18 21:48:47 [INFO] [execOutputHook] exec hook -> "/usr/sbin/rgbcommander/scripts/OnEmuStop.sh"  'mame'
31/03/18 21:48:47 [INFO] [RGBAstart]random animation chosen -> Pattern58_32
31/03/18 21:48:47 [INFO] [fadeSpeed] unsupported/unimplemented command
31/03/18 21:48:47 [WARNING] [fadeSpeed] LEDWIZ_1 fadespeed set to  0 -> FAILURE
31/03/18 21:48:47 [WARNING] [setOff] setting LEDWIZ_1 -> fadeSpeed(0) -> failed
31/03/18 21:48:47 [INFO] [setRGBAspeed] RGBA Pattern58_32 speed set to 100
31/03/18 21:48:47 [INFO] [RGBAthread] rgba Pattern58_32 play back start at speed 100
31/03/18 22:02:47 [INFO] [RGBAstop] awaiting animation stop...
31/03/18 22:02:47 [INFO] [fadeSpeed] unsupported/unimplemented command
31/03/18 22:02:47 [WARNING] [fadeSpeed] LEDWIZ_1 fadespeed set to  0 -> FAILURE
31/03/18 22:02:47 [WARNING] [setOff] setting LEDWIZ_1 -> fadeSpeed(0) -> failed
31/03/18 22:02:47 [INFO] [RGBAthread] rgba Pattern58_32 playback stop -> anim runtime ->  839.361s
31/03/18 22:02:47 [INFO] [RGBAstop] animation stop -> success ...
31/03/18 22:02:47 [INFO] [processMonitor] mame is running
31/03/18 22:02:47 [INFO] [setState] setting state for mame yiear
31/03/18 22:02:47 [INFO] [setState] emu friendly name mame
31/03/18 22:02:47 [INFO] [setState] emu default active colour Red r 255 g 255 b 255
31/03/18 22:02:47 [INFO] [setState] emu default inactive colour Off r 0 g 0 b 0
31/03/18 22:02:47 [INFO] [setState] emu default joyway 8
31/03/18 22:02:47 [INFO] [setState] emu default rgba RANDOM at speed 100
31/03/18 22:02:47 [INFO] [setState] emu default monitor rotation -> horizontal
31/03/18 22:02:47 [INFO] [setState] mame  references emu arcade
31/03/18 22:02:47 [INFO] [fadeSpeed] unsupported/unimplemented command
31/03/18 22:02:47 [WARNING] [fadeSpeed] LEDWIZ_1 fadespeed set to  0 -> FAILURE
31/03/18 22:02:47 [WARNING] [setOff] setting LEDWIZ_1 -> fadeSpeed(0) -> failed
31/03/18 22:02:47 [INFO] [setState] yiear known in minimame
31/03/18 22:02:47 [INFO] [setState] joyway set according to rom data -> 8
31/03/18 22:02:47 [INFO] [setState] rom monitor rotation is horizontal
31/03/18 22:02:47 [INFO] [setState] yiear -> preconfiguration data available -> appending to state
31/03/18 22:02:47 [INFO] [setState] appending LEDWIZ_1 button name P1_BUTTON1 button colour Red r 255 g 255 b 255
31/03/18 22:02:47 [INFO] [setState] appending LEDWIZ_1 button name P1_BUTTON2 button colour Blue r 255 g 255 b 255
31/03/18 22:02:47 [INFO] [setState] appending LEDWIZ_1 button name P1_COIN button colour White r 255 g 255 b 255
31/03/18 22:02:47 [INFO] [setState] appending LEDWIZ_1 button name P1_JOYSTICK button colour Red r 255 g 255 b 255
31/03/18 22:02:47 [INFO] [setState] appending LEDWIZ_1 button name P1_START button colour White r 255 g 255 b 255
31/03/18 22:02:47 [INFO] [setState] appending LEDWIZ_1 button name P2_BUTTON1 button colour Red r 255 g 255 b 255
31/03/18 22:02:47 [INFO] [setState] appending LEDWIZ_1 button name P2_BUTTON2 button colour Blue r 255 g 255 b 255
31/03/18 22:02:47 [INFO] [setState] appending LEDWIZ_1 button name P2_COIN button colour White r 255 g 255 b 255
31/03/18 22:02:47 [INFO] [setState] appending LEDWIZ_1 button name P2_JOYSTICK button colour Red r 255 g 255 b 255
31/03/18 22:02:47 [INFO] [setState] appending LEDWIZ_1 button name P2_START button colour White r 255 g 255 b 255
31/03/18 22:02:47 [INFO] [setState] preparing blinking led2 active colour Red r 255 g 255 b 255
31/03/18 22:02:47 [INFO] [setState] preparing blinking led2 inactive colour Off r 0 g 0 b 0
31/03/18 22:02:47 [INFO] [setState] preparing blinking led0 active colour White r 255 g 255 b 255
31/03/18 22:02:47 [INFO] [setState] preparing blinking led0 inactive colour Off r 0 g 0 b 0
31/03/18 22:02:47 [INFO] [setState] preparing blinking led1 active colour White r 255 g 255 b 255
31/03/18 22:02:47 [INFO] [setState] preparing blinking led1 inactive colour Off r 0 g 0 b 0
31/03/18 22:02:47 [INFO] [setState] committing state to led hardware -> LEDWIZ_1
31/03/18 22:02:47 [INFO] [setStick] committing state to joystick hardware -> SERVOSTIK
31/03/18 22:02:47 [INFO] [setWay]SERVOSTIK already in position 8
31/03/18 22:02:47 [INFO] [setState] total setState processing time -> 0.101001s
31/03/18 22:02:47 [INFO] [execOutputHook] exec hook -> "/usr/sbin/rgbcommander/scripts/OnEmuStart.sh"  'arcade' 'yiear'
31/03/18 22:02:47 [INFO] [mameNetworkCommunicator] mame yiear started -> setState -> success
31/03/18 22:03:15 [INFO] [processMonitor] mame is no longer running
31/03/18 22:03:15 [INFO] [setStick] committing state to joystick hardware -> SERVOSTIK
31/03/18 22:03:15 [INFO] [setWay]SERVOSTIK already in position 8
31/03/18 22:03:15 [INFO] [execOutputHook] exec hook -> "/usr/sbin/rgbcommander/scripts/OnEmuStop.sh"  'mame'
31/03/18 22:03:15 [INFO] [RGBAstart]random animation chosen -> Pattern23_32
31/03/18 22:03:15 [INFO] [fadeSpeed] unsupported/unimplemented command
31/03/18 22:03:15 [WARNING] [fadeSpeed] LEDWIZ_1 fadespeed set to  0 -> FAILURE
31/03/18 22:03:15 [WARNING] [setOff] setting LEDWIZ_1 -> fadeSpeed(0) -> failed
31/03/18 22:03:15 [INFO] [setRGBAspeed] RGBA Pattern23_32 speed set to 100
31/03/18 22:03:15 [INFO] [RGBAthread] rgba Pattern23_32 play back start at speed 100
31/03/18 22:03:19 [INFO] [RGBAstop] awaiting animation stop...
31/03/18 22:03:19 [INFO] [fadeSpeed] unsupported/unimplemented command
31/03/18 22:03:19 [WARNING] [fadeSpeed] LEDWIZ_1 fadespeed set to  0 -> FAILURE
31/03/18 22:03:19 [WARNING] [setOff] setting LEDWIZ_1 -> fadeSpeed(0) -> failed
31/03/18 22:03:19 [INFO] [RGBAthread] rgba Pattern23_32 playback stop -> anim runtime ->  4.09066s
31/03/18 22:03:19 [INFO] [RGBAstop] animation stop -> success ...
31/03/18 22:03:19 [INFO] [processMonitor] mame is running
31/03/18 22:03:19 [INFO] [setState] setting state for mame 1942
31/03/18 22:03:19 [INFO] [setState] emu friendly name mame
31/03/18 22:03:19 [INFO] [setState] emu default active colour Red r 255 g 255 b 255
31/03/18 22:03:19 [INFO] [setState] emu default inactive colour Off r 0 g 0 b 0
31/03/18 22:03:19 [INFO] [setState] emu default joyway 8
31/03/18 22:03:19 [INFO] [setState] emu default rgba RANDOM at speed 100
31/03/18 22:03:19 [INFO] [setState] emu default monitor rotation -> horizontal
31/03/18 22:03:19 [INFO] [setState] mame  references emu arcade
31/03/18 22:03:19 [INFO] [fadeSpeed] unsupported/unimplemented command
31/03/18 22:03:19 [WARNING] [fadeSpeed] LEDWIZ_1 fadespeed set to  0 -> FAILURE
31/03/18 22:03:19 [WARNING] [setOff] setting LEDWIZ_1 -> fadeSpeed(0) -> failed
31/03/18 22:03:19 [INFO] [setState] 1942 known in minimame
31/03/18 22:03:19 [INFO] [setState] joyway set according to rom data -> 8
31/03/18 22:03:19 [INFO] [setState] rom monitor rotation is vertical
31/03/18 22:03:19 [INFO] [setState] 1942 -> preconfiguration data available -> appending to state
31/03/18 22:03:19 [INFO] [setState] appending LEDWIZ_1 button name P1_BUTTON1 button colour Red r 255 g 255 b 255
31/03/18 22:03:19 [INFO] [setState] appending LEDWIZ_1 button name P1_BUTTON2 button colour White r 255 g 255 b 255
31/03/18 22:03:19 [INFO] [setState] appending LEDWIZ_1 button name P1_COIN button colour White r 255 g 255 b 255
31/03/18 22:03:19 [INFO] [setState] appending LEDWIZ_1 button name P1_JOYSTICK button colour Red r 255 g 255 b 255
31/03/18 22:03:19 [INFO] [setState] appending LEDWIZ_1 button name P1_START button colour White r 255 g 255 b 255
31/03/18 22:03:19 [INFO] [setState] appending LEDWIZ_1 button name P2_BUTTON1 button colour Red r 255 g 255 b 255
31/03/18 22:03:19 [INFO] [setState] appending LEDWIZ_1 button name P2_BUTTON2 button colour White r 255 g 255 b 255
31/03/18 22:03:19 [INFO] [setState] appending LEDWIZ_1 button name P2_COIN button colour White r 255 g 255 b 255
31/03/18 22:03:19 [INFO] [setState] appending LEDWIZ_1 button name P2_JOYSTICK button colour Red r 255 g 255 b 255
31/03/18 22:03:19 [INFO] [setState] appending LEDWIZ_1 button name P2_START button colour White r 255 g 255 b 255
31/03/18 22:03:19 [INFO] [setState] preparing blinking led2 active colour Red r 255 g 255 b 255
31/03/18 22:03:19 [INFO] [setState] preparing blinking led2 inactive colour Off r 0 g 0 b 0
31/03/18 22:03:19 [INFO] [setState] preparing blinking led0 active colour White r 255 g 255 b 255
31/03/18 22:03:19 [INFO] [setState] preparing blinking led0 inactive colour Off r 0 g 0 b 0
31/03/18 22:03:19 [INFO] [setState] preparing blinking led1 active colour White r 255 g 255 b 255
31/03/18 22:03:19 [INFO] [setState] preparing blinking led1 inactive colour Off r 0 g 0 b 0
31/03/18 22:03:19 [INFO] [setState] committing state to led hardware -> LEDWIZ_1
31/03/18 22:03:19 [INFO] [setStick] committing state to joystick hardware -> SERVOSTIK
31/03/18 22:03:19 [INFO] [setWay]SERVOSTIK already in position 8
31/03/18 22:03:19 [INFO] [setState] total setState processing time -> 0.100836s
31/03/18 22:03:19 [INFO] [execOutputHook] exec hook -> "/usr/sbin/rgbcommander/scripts/OnEmuStart.sh"  'arcade' '1942'
31/03/18 22:03:19 [INFO] [mameNetworkCommunicator] mame 1942 started -> setState -> success
31/03/18 22:03:23 [INFO] [processMonitor] mame is no longer running
31/03/18 22:03:23 [INFO] [setStick] committing state to joystick hardware -> SERVOSTIK
31/03/18 22:03:23 [INFO] [setWay]SERVOSTIK already in position 8
31/03/18 22:03:23 [INFO] [execOutputHook] exec hook -> "/usr/sbin/rgbcommander/scripts/OnEmuStop.sh"  'mame'
31/03/18 22:03:23 [INFO] [RGBAstart]random animation chosen -> Pattern58_32
31/03/18 22:03:23 [INFO] [fadeSpeed] unsupported/unimplemented command
31/03/18 22:03:23 [WARNING] [fadeSpeed] LEDWIZ_1 fadespeed set to  0 -> FAILURE
31/03/18 22:03:23 [WARNING] [setOff] setting LEDWIZ_1 -> fadeSpeed(0) -> failed
31/03/18 22:03:23 [INFO] [setRGBAspeed] RGBA Pattern58_32 speed set to 100
31/03/18 22:03:23 [INFO] [RGBAthread] rgba Pattern58_32 play back start at speed 100
31/03/18 22:03:31 [INFO] [RGBAstop] awaiting animation stop...
31/03/18 22:03:31 [INFO] [fadeSpeed] unsupported/unimplemented command
31/03/18 22:03:31 [WARNING] [fadeSpeed] LEDWIZ_1 fadespeed set to  0 -> FAILURE
31/03/18 22:03:31 [WARNING] [setOff] setting LEDWIZ_1 -> fadeSpeed(0) -> failed
31/03/18 22:03:31 [INFO] [RGBAthread] rgba Pattern58_32 playback stop -> anim runtime ->  8.05838s
31/03/18 22:03:31 [INFO] [RGBAstop] animation stop -> success ...
31/03/18 22:03:31 [INFO] [processMonitor] mame is running
31/03/18 22:03:31 [INFO] [setState] setting state for mame arkanoidu
31/03/18 22:03:31 [INFO] [setState] emu friendly name mame
31/03/18 22:03:31 [INFO] [setState] emu default active colour Red r 255 g 255 b 255
31/03/18 22:03:31 [INFO] [setState] emu default inactive colour Off r 0 g 0 b 0
31/03/18 22:03:31 [INFO] [setState] emu default joyway 8
31/03/18 22:03:31 [INFO] [setState] emu default rgba RANDOM at speed 100
31/03/18 22:03:31 [INFO] [setState] emu default monitor rotation -> horizontal
31/03/18 22:03:31 [INFO] [setState] mame  references emu arcade
31/03/18 22:03:31 [INFO] [fadeSpeed] unsupported/unimplemented command
31/03/18 22:03:31 [WARNING] [fadeSpeed] LEDWIZ_1 fadespeed set to  0 -> FAILURE
31/03/18 22:03:31 [WARNING] [setOff] setting LEDWIZ_1 -> fadeSpeed(0) -> failed
31/03/18 22:03:31 [INFO] [setState] arkanoidu known in minimame
31/03/18 22:03:31 [INFO] [setState] joyway set according to rom data -> 8
31/03/18 22:03:31 [INFO] [setState] rom monitor rotation is vertical
31/03/18 22:03:31 [INFO] [setState] arkanoidu -> no preconfiguration data available -> deducting buttons
31/03/18 22:03:31 [DEBUG] [setState] auto generated button names :
31/03/18 22:03:31 [DEBUG] [setState]P1_BUTTON1
31/03/18 22:03:31 [DEBUG] [setState]P2_BUTTON1
31/03/18 22:03:31 [DEBUG] [setState]P1_COIN
31/03/18 22:03:31 [DEBUG] [setState]P1_START
31/03/18 22:03:31 [DEBUG] [setState]P2_COIN
31/03/18 22:03:31 [DEBUG] [setState]P2_START
31/03/18 22:03:31 [INFO] [setState] appending LEDWIZ_1 -> P1_BUTTON1 -> Off r 0 g 0 b 0
31/03/18 22:03:31 [INFO] [setState] appending LEDWIZ_1 -> P1_COIN -> White r 255 g 255 b 255
31/03/18 22:03:31 [INFO] [setState] appending LEDWIZ_1 -> P1_START -> White r 255 g 255 b 255
31/03/18 22:03:31 [INFO] [setState] appending LEDWIZ_1 -> P2_BUTTON1 -> Off r 0 g 0 b 0
31/03/18 22:03:31 [INFO] [setState] appending LEDWIZ_1 -> P2_COIN -> White r 255 g 255 b 255
31/03/18 22:03:31 [INFO] [setState] appending LEDWIZ_1 -> P2_START -> White r 255 g 255 b 255
31/03/18 22:03:31 [INFO] [setState] preparing blinking led2 active colour Off r 0 g 0 b 0
31/03/18 22:03:31 [INFO] [setState] preparing blinking led2 inactive colour Off r 0 g 0 b 0
31/03/18 22:03:31 [INFO] [setState] preparing blinking led0 active colour White r 255 g 255 b 255
31/03/18 22:03:31 [INFO] [setState] preparing blinking led0 inactive colour Off r 0 g 0 b 0
31/03/18 22:03:31 [INFO] [setState] preparing blinking led1 active colour White r 255 g 255 b 255
31/03/18 22:03:31 [INFO] [setState] preparing blinking led1 inactive colour Off r 0 g 0 b 0
31/03/18 22:03:31 [INFO] [setState] committing state to led hardware -> LEDWIZ_1
31/03/18 22:03:31 [INFO] [setStick] committing state to joystick hardware -> SERVOSTIK
31/03/18 22:03:31 [INFO] [setWay]SERVOSTIK already in position 8
31/03/18 22:03:31 [INFO] [setState] total setState processing time -> 0.100813s
31/03/18 22:03:31 [INFO] [execOutputHook] exec hook -> "/usr/sbin/rgbcommander/scripts/OnEmuStart.sh"  'arcade' 'default'
31/03/18 22:03:31 [INFO] [mameNetworkCommunicator] mame arkanoidu started -> setState -> success
31/03/18 22:03:34 [INFO] [processMonitor] mame is no longer running
31/03/18 22:03:34 [INFO] [setStick] committing state to joystick hardware -> SERVOSTIK
31/03/18 22:03:34 [INFO] [setWay]SERVOSTIK already in position 8
31/03/18 22:03:34 [INFO] [execOutputHook] exec hook -> "/usr/sbin/rgbcommander/scripts/OnEmuStop.sh"  'mame'
31/03/18 22:03:34 [INFO] [RGBAstart]random animation chosen -> Pattern60_32
31/03/18 22:03:34 [INFO] [fadeSpeed] unsupported/unimplemented command
31/03/18 22:03:34 [WARNING] [fadeSpeed] LEDWIZ_1 fadespeed set to  0 -> FAILURE
31/03/18 22:03:34 [WARNING] [setOff] setting LEDWIZ_1 -> fadeSpeed(0) -> failed
31/03/18 22:03:34 [INFO] [setRGBAspeed] RGBA Pattern60_32 speed set to 100
31/03/18 22:03:34 [INFO] [RGBAthread] rgba Pattern60_32 play back start at speed 100
31/03/18 22:03:54 [INFO] [RGBAstop] awaiting animation stop...
31/03/18 22:03:54 [INFO] [fadeSpeed] unsupported/unimplemented command
31/03/18 22:03:54 [WARNING] [fadeSpeed] LEDWIZ_1 fadespeed set to  0 -> FAILURE
31/03/18 22:03:54 [WARNING] [setOff] setting LEDWIZ_1 -> fadeSpeed(0) -> failed
31/03/18 22:03:54 [INFO] [RGBAthread] rgba Pattern60_32 playback stop -> anim runtime ->  20.3082s
31/03/18 22:03:54 [INFO] [RGBAstop] animation stop -> success ...
31/03/18 22:03:54 [INFO] [processMonitor] mame is running
31/03/18 22:03:54 [INFO] [setState] setting state for mame kinst
31/03/18 22:03:54 [INFO] [setState] emu friendly name mame
31/03/18 22:03:54 [INFO] [setState] emu default active colour Red r 255 g 255 b 255
31/03/18 22:03:54 [INFO] [setState] emu default inactive colour Off r 0 g 0 b 0
31/03/18 22:03:54 [INFO] [setState] emu default joyway 8
31/03/18 22:03:54 [INFO] [setState] emu default rgba RANDOM at speed 100
31/03/18 22:03:54 [INFO] [setState] emu default monitor rotation -> horizontal
31/03/18 22:03:54 [INFO] [setState] mame  references emu arcade
31/03/18 22:03:54 [INFO] [fadeSpeed] unsupported/unimplemented command
31/03/18 22:03:54 [WARNING] [fadeSpeed] LEDWIZ_1 fadespeed set to  0 -> FAILURE
31/03/18 22:03:54 [WARNING] [setOff] setting LEDWIZ_1 -> fadeSpeed(0) -> failed
31/03/18 22:03:54 [INFO] [setState] kinst known in minimame
31/03/18 22:03:54 [INFO] [setState] joyway set according to rom data -> 8
31/03/18 22:03:54 [INFO] [setState] rom monitor rotation is horizontal
31/03/18 22:03:54 [INFO] [setState] kinst -> preconfiguration data available -> appending to state
31/03/18 22:03:54 [INFO] [setState] appending LEDWIZ_1 button name P1_BUTTON1 button colour Cyan r 255 g 255 b 255
31/03/18 22:03:54 [INFO] [setState] appending LEDWIZ_1 button name P1_BUTTON2 button colour Cyan r 255 g 255 b 255
31/03/18 22:03:54 [INFO] [setState] appending LEDWIZ_1 button name P1_BUTTON3 button colour Cyan r 255 g 255 b 255
31/03/18 22:03:54 [INFO] [setState] appending LEDWIZ_1 button name P1_BUTTON4 button colour Cyan r 255 g 255 b 255
31/03/18 22:03:54 [INFO] [setState] appending LEDWIZ_1 button name P1_BUTTON5 button colour Cyan r 255 g 255 b 255
31/03/18 22:03:54 [INFO] [setState] appending LEDWIZ_1 button name P1_BUTTON6 button colour Cyan r 255 g 255 b 255
31/03/18 22:03:54 [INFO] [setState] appending LEDWIZ_1 button name P1_COIN button colour White r 255 g 255 b 255
31/03/18 22:03:54 [INFO] [setState] appending LEDWIZ_1 button name P1_JOYSTICK button colour Black r 255 g 255 b 255
31/03/18 22:03:54 [INFO] [setState] appending LEDWIZ_1 button name P1_START button colour White r 255 g 255 b 255
31/03/18 22:03:54 [INFO] [setState] appending LEDWIZ_1 button name P2_BUTTON1 button colour Cyan r 255 g 255 b 255
31/03/18 22:03:54 [INFO] [setState] appending LEDWIZ_1 button name P2_BUTTON2 button colour Cyan r 255 g 255 b 255
31/03/18 22:03:54 [INFO] [setState] appending LEDWIZ_1 button name P2_BUTTON3 button colour Cyan r 255 g 255 b 255
31/03/18 22:03:54 [INFO] [setState] appending LEDWIZ_1 button name P2_BUTTON4 button colour Cyan r 255 g 255 b 255
31/03/18 22:03:54 [INFO] [setState] appending LEDWIZ_1 button name P2_BUTTON5 button colour Cyan r 255 g 255 b 255
31/03/18 22:03:54 [INFO] [setState] appending LEDWIZ_1 button name P2_BUTTON6 button colour Cyan r 255 g 255 b 255
31/03/18 22:03:54 [INFO] [setState] appending LEDWIZ_1 button name P2_COIN button colour White r 255 g 255 b 255
31/03/18 22:03:54 [INFO] [setState] appending LEDWIZ_1 button name P2_JOYSTICK button colour Black r 255 g 255 b 255
31/03/18 22:03:54 [INFO] [setState] appending LEDWIZ_1 button name P2_START button colour White r 255 g 255 b 255
31/03/18 22:03:54 [INFO] [setState] preparing blinking led2 active colour Cyan r 255 g 255 b 255
31/03/18 22:03:54 [INFO] [setState] preparing blinking led2 inactive colour Off r 0 g 0 b 0
31/03/18 22:03:54 [INFO] [setState] preparing blinking led0 active colour White r 255 g 255 b 255
31/03/18 22:03:54 [INFO] [setState] preparing blinking led0 inactive colour Off r 0 g 0 b 0
31/03/18 22:03:54 [INFO] [setState] preparing blinking led1 active colour White r 255 g 255 b 255
31/03/18 22:03:54 [INFO] [setState] preparing blinking led1 inactive colour Off r 0 g 0 b 0
31/03/18 22:03:54 [INFO] [setState] committing state to led hardware -> LEDWIZ_1
31/03/18 22:03:54 [INFO] [setStick] committing state to joystick hardware -> SERVOSTIK
31/03/18 22:03:54 [INFO] [setWay]SERVOSTIK already in position 8
31/03/18 22:03:54 [INFO] [setState] total setState processing time -> 0.105408s
31/03/18 22:03:54 [INFO] [execOutputHook] exec hook -> "/usr/sbin/rgbcommander/scripts/OnEmuStart.sh"  'arcade' 'kinst'
31/03/18 22:03:54 [INFO] [mameNetworkCommunicator] mame kinst started -> setState -> success
31/03/18 22:03:59 [INFO] [processMonitor] mame is no longer running
31/03/18 22:03:59 [INFO] [setStick] committing state to joystick hardware -> SERVOSTIK
31/03/18 22:03:59 [INFO] [setWay]SERVOSTIK already in position 8
31/03/18 22:03:59 [INFO] [execOutputHook] exec hook -> "/usr/sbin/rgbcommander/scripts/OnEmuStop.sh"  'mame'
31/03/18 22:03:59 [INFO] [RGBAstart]random animation chosen -> Pattern44_32
31/03/18 22:03:59 [INFO] [fadeSpeed] unsupported/unimplemented command
31/03/18 22:03:59 [WARNING] [fadeSpeed] LEDWIZ_1 fadespeed set to  0 -> FAILURE
31/03/18 22:03:59 [WARNING] [setOff] setting LEDWIZ_1 -> fadeSpeed(0) -> failed
31/03/18 22:03:59 [INFO] [setRGBAspeed] RGBA Pattern44_32 speed set to 100
31/03/18 22:03:59 [INFO] [RGBAthread] rgba Pattern44_32 play back start at speed 100

Let me know if you need any thing else. I also made a donation to your page so have some beers on me.  :cheers:
« Last Edit: April 01, 2018, 01:18:05 am by MacGyver »

ZoOl007

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 125
    • RGBcommander
Re: Having trouble with RGBCommander and Led-WizGP
« Reply #8 on: April 01, 2018, 02:54:30 am »
It is kind of you to donate. Thank you for the beers :)

as for the crash - I gave you an alpha version - it really shouldn't do that. I've had alternating sequences running for days during dev.
It is likely, though not certain, that it has something to do with the modifications. I only modified the most heavily used method and only for the LEDWiz as a poc. Can you reproduce?
There's also a second recalculation as the ledwiz doesn't support all the intensity values as the Ultimarc boards do.

as for pin - 30 and 31 that don't light up during the lightall method that is because one can only add 10 rgb leds on the board you have so I don't care about the 2 last ones as they were useless to me.

as for all changing all the color to 255,255,255: In my mind you shouldn't need to do that as 1 RGB results in one intensity if a single color led is used. But, the resulting intensity is maybe too low to be noticeable so yes maybe all 255,255,255 yields 255 so... as do Red Blue etc...

as for showing the game in the selector: that should be possible using rgbcmdcon if AttractMode lets you obtain the game in the selector. rgbcmdcon actually supports most of the commands the daemon supports but this specific one is not allowed to be called externally. I need to update rgbcdmcon for that. It is a small change.

Now that I know it sort off works I'll try to find the time to implement it properly. I'll send you an updated binary to test.

kind regards.


  
 

Sitemap 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31