Jump to content
Search In
  • More options...
Find results that contain...
Find results in...

rambo3

Members
  • Content Count

    34
  • Joined

  • Last visited

  • Days Won

    1

rambo3 last won the day on November 3 2018

rambo3 had the most liked content!

Community Reputation

8 Neutral

About rambo3

  • Rank
    Advanced Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Partially back from the dead, pincab is doing Netflixduty lately but I did try Attack from Mars (VPX). The Hue lightstrip undercab did light up, though on an older Philips hub. I haven't tried the ginormous apartment-wide 2-hub test again. Thing is, I'm still using the same software. If I get some time this weekend I'll try and go 6000lumenstyle test again and see if it still works with 3 years of pending Hue Hub updates...
  2. Hopefully I'll have that sorted out next week as I'm merging his changes into it to get it synced with DOFLinx.
  3. Have you tried the TableOverrideSettings in my DOF-branch? You should be able to, per-table, either reduce or kill completely, specific outputs if you know your shaker controller and output trigger. Though it will affect that/those output(s) for the entire table run.
  4. mjr; if you are reading this (or anyone else), I'd like to merge your changes (https://github.com/mjrgh/DirectOutput/tree/Release20151130) into my own branch (https://github.com/rambo3/DirectOutput/tree/ultimateio). I don't have a LedWiz myself, so I can't test for stability issues, but is this a stable branch for people with and without Pinscape? It's just 4 commits, but there's a significant set of changes regarding LedWiz.cs and OutputControllerCompleteBase.cs that seem to remove the need for ledwiz.dll?
  5. Ain't happenin' to nobody I had some issues with my flippers getting stuck actually on the Ultimate I/O where support was based on the PacLed64. Turns out it was an issue in the code hammering the poor UIO so much it started missing / skipping commands, in effect causing stuck flippers.
  6. Nice work! One can never, ever, EVER have too many LEDs, PC hardware manufacturers finally figured that one out with actual fully digital RGB output headers and RGB RAM modules C-:
  7. DOF loves one word ROM-names Cool thing with prefixes is that we'd be able to use wildcards (fp_*) for manual table overrides in Cabinet.xml now too.
  8. DOF just got support for custom table output overrides through the <TableOverrideSettings>. Individual outputs can be globally adjusted (contactors disabled for instance), per-rom, per-table, or using wildcards (afm* for all versions of Attack from Mars). Lights or contactors can be reduced or shut off completely, overriding your configtool export settings. As always; backup your entire DirectOutputFramework - directory before toying with this ! I take no responsibility for issues, fire, damages, psychosis, insomnia etc. https://github.com/rambo3/DirectOutput/tree/ultimateio/DirectOutput/Builds Swisslizard: huge thanks for putting the project on GitHub. My cab would be dead without it. Introduction Kiwi wondered if it would be possible to turn off certain toys based on tables. No, but that's actually a great idea. So here we go! Setup Add the following to your Cabinet.xml, say just before </Cabinet> at the end of your XML, and start adjusting / removing. The example below globally turns off left and right flipper contactors. For Bad Cats turns off my overcab light, and reduces the undercab light to 50%. <TableOverrideSettings> <TableOverrideSetting> <Name>Globally disable left and right contactors</Name> <Enabled>true</Enabled> <Roms>*</Roms> <Tables>*</Tables> <TableOverrideSettingDeviceList> <TableOverrideSettingDevice> <Name>Ultimate I/O contactors</Name> <ConfigPostfixID>27</ConfigPostfixID> <Outputs>49,52</Outputs> <OutputPercent>0</OutputPercent> </TableOverrideSettingDevice> </TableOverrideSettingDeviceList> </TableOverrideSetting> <TableOverrideSetting> <Name>Bad Cats, disable or reduce undercab light</Name> <Description>Disables or reduces output percent on specific outputs for specific tables</Description> <Enabled>true</Enabled> <Roms>bcats*</Roms> <TableOverrideSettingDeviceList> <TableOverrideSettingDevice> <Name>Philips Hue projector overcab</Name> <ConfigPostfixID>70</ConfigPostfixID> <Outputs>7,8,9</Outputs> <OutputPercent>0</OutputPercent> </TableOverrideSettingDevice> <TableOverrideSettingDevice> <Name>Philips Hue undercab</Name> <ConfigPostfixID>70</ConfigPostfixID> <Outputs>10,11,12</Outputs> <OutputPercent>50</OutputPercent> </TableOverrideSettingDevice> </TableOverrideSettingDeviceList> </TableOverrideSetting> </TableOverrideSettings> Settings <TableOverrideSetting> is a mode containing a descriptive name, enabled state, comma seperated ROMs, and / or comma seperated Tables. Wildcards are supported. A single * specifies global. <Roms> specify list of ROMs without spacing, for instance: <Roms>afm*,bcats*</Roms> <Tables> specify table filenames without extension and spacing before commas, for instance: <Tables>AttackFromMars_FS_B2S,Bad Cats.VPX.v1.0</Tables> No commas in filenames, and no spacing before seperator. If there are commas in filename, use first part and add a wildcard / * at the end (AttackFromMars*). Filename are case-insensitive. <TableOverrideSettingDeviceList> contains all the devices you want to affect. <TableOverrideSettingDevice> is a single device, its outputs (according to configtool) to affect, and the output strength in percent 0-100. 0 is off. To let DOF know which device you want to control, match the ConfigPostfixID with your configtool ini file, for instance directoutputconfig27.ini with 27 being the postfixid. Debugging Check your DirectOutput.log file for details if nothing works. You should see something like: ... 2017.06.06 20.45.30.157 Debug: Setting up shape effect for area. L: 91, T: 0, W: 9, H: 30 2017.06.06 20.45.30.157 Table config loading finished: romname=afm, tablename=Attack from Marsvp91x 2017.06.06 20.45.30.157 TableOverrideSettings.activateOverrides... activeSetting[Globally disable left and right contactors]=True 2017.06.06 20.45.30.157 TableOverrideSettings.activateOverrides... activeSetting[Attack from Mars, disable flippers]=True 2017.06.06 20.45.30.157 TableOverrideSettings.activateOverrides... activeSetting[Bad Cats, disable or reduce undercab light]=False 2017.06.06 20.45.30.157 Pinball parts loaded ... Device support Currently Ultimate I/O, Teensy, and Philips Hue are fully supported. PacLed64, PacDrive have the support added in, but since I don't have those devices I can't confirm that they actually work. SainSmart USB have the support added in, but not fully testet yet. LedWiz is planned, but not sure how to add it in yet and will need to be confirmed by someone else since I don't have the thing. Fun thing Outputs can be individually affected, for instance I accidentally applied 0 OutputPercent in Bad Cats to one or two (can't remember) of the three undercab channel outputs causing a yellowish bright green instead of orange.
  9. Just added support for overriding outputs per table, globally, or using wildcards for ROMs and table filenames (either, or both). Outputs can be anything from 0-100 with 0 being turn off, and 100...not making much sense but it's there for consistency. Right now I've got left and right flipper contactors globally shut off, and undercab light at full strength + overcab light completely off for Bad Cats (ROM name "bcats*" with wildcard at the end). Also experimented with undercab at 20-50% strength, and individual R, G, B strength offsets which gave me a nice green color instead of orange in Bad Cats to prove that individual channels were indeed affected That should pretty much cover it. Need to do some more testing before putting up a new thread for <TableOverrideSettings>, hopefully tomorrow. EDIT: EM tables don't have ROMs, right? They're basically analog? In this case, I think we got that covered too as a <Roms> being blank instead of something like "afm" (Attack from Mars) could in effect be triggered to say disable LED strips.
  10. Allright then, I think I have something to work on. I'm kind of in the "DOF"-mode these days. Experimented yesterday with capturing and testing the latency of my UIO -> Sainsmart --> contactor signal delay by basically capturing the devices inside the pincab at 60FPS. You can see when an output gets triggered (LED on Sainsmart), and when a contactor pushes and releases. A full cycle was about 180ms, with the Sainsmart at ~100ms, contactor ON ~34ms, contactor OFF ~46ms rougly. It hit me that if the left flipper was triggered twice within say 100ms and the primary contactor was still busy processing, why not offload retrigger to the slingshot contactor sitting right beside it? Basically have another output assist a running output while the first one was still running as a way of compensating for slow hardware. It worked quite well practically, sounded a bit funny due to different contactor assisting on quick retriggers, but then realised that the real problem of course was the Sainsmart itself; 100ms before reaching the contactor is alot. I'll do some experimenting in a few hours with the disable-toy-feature and report back!
  11. One recommendation; take care of your eyes. Use sunglasses, look through the camera of your phone if you have to stare or something. I'm not kidding, don't even dare staring at those. I just put a cover on top and watched the indirect light from the wall in the end, and did recordings using the phone to watch how the LEDs were lighting up.
  12. Wait a minute; can't you disable toys manually in configtool on a table-basis, specific to your configtool account?
  13. No, but that's actually a great idea. Any suggestions on how you'd want something like this implemented, or what you'd need? The <ScheduledSetting> is a background thing running continuesly, but something like <TableSettings> could work? Right now I'm thinking something with Name, Enabled, Table name (not sure; filename? rom?), and the devicelist similar to above. It'd be nice to have day/night-modes run simultaneously. That should make it possible to not only turn off stuff on a per-table basis, but set a strength property to some toys like lights. Eh...suggestions?
  14. Just did a software-approach to this in DOF. Currently using it for shutting off contactors, and adjusting Teensy brightness output to 30%. Been testing it for a few months now, check if out if you're feelin' lucky
  15. DOF now has support for custom day and night modes through three classes: ScheduledSettings, ScheduledSettingDevice, and ScheduledSetting. This is a software approach to having lights or outputs adjusted on-the-fly during different times of the day. As always; backup your entire DirectOutputFramework - directory before toying with this ! I take no responsibility for issues, fire, damages, earthquakes etc. https://github.com/rambo3/DirectOutput/tree/ultimateio/DirectOutput/Builds Swisslizard: huge thanks for putting the project on GitHub. This project, like Philips Hue support, is not official but a side project off the original R3. Introduction As I got home from the job tired I wanted to play pincabs with less noise or brightness. I was changing the Cabinet.xml, renaming files to shut off the contactors, powering off the RGB or using alternative fade curves. At one point I started experimenting with overriding DOF output strength through Cabinet.xml and just brute force code, and eventually the XML settings got to a point that I could have full brightness on everything during the day, gradually shut off contactors, and adjust the Teensy brightness at midnight. Changes would kick in during a game and over midnight, which initially seemed like a bug where contactors would suddenly no longer "work". This is a software approach to specific devices in DOF for dynamically adjusting custom outputs, including Teensy brightness for individually adjustable RGB strips which by default are very powerful. Setup Add the following to your Cabinet.xml, say just before </Cabinet> at the end of your XML, and start adjusting / removing. The example below goes into effect 2200-0500, sets my contactor specific outputs to off, adjusts the Teensy back LED-matrix to 30%, and shuts off the SainSmart USB outputs. And it's enabled. <ScheduledSettings> <ScheduledSetting> <Name>Night Mode</Name> <Enabled>true</Enabled> <ClockStart>2200</ClockStart> <ClockEnd>0500</ClockEnd> <ScheduledSettingDeviceList> <ScheduledSettingDevice> <Name>Ultimate I/O contactors</Name> <ConfigPostfixID>27</ConfigPostfixID> <Outputs>49,50,51,52,53,54,55,56,57,58</Outputs> <OutputPercent>0</OutputPercent> </ScheduledSettingDevice> <ScheduledSettingDevice> <Name>Teensy LEDs back matrix</Name> <ConfigPostfixID>30</ConfigPostfixID> <Outputs>1</Outputs> <OutputPercent>30</OutputPercent> </ScheduledSettingDevice> <ScheduledSettingDevice> <Name>Sainsmart USB</Name> <Description>Note that the Sainsmart is a 0/1 relay array and that 0=off while 1-100 is considered on. There is no inbetween, a relay is either open or closed ("bitbang").</Description> <ConfigPostfixID>40</ConfigPostfixID> <Outputs>1,2,3,4,5,6,7,8</Outputs> <OutputPercent>0</OutputPercent> </ScheduledSettingDevice> </ScheduledSettingDeviceList> </ScheduledSetting> </ScheduledSettings> Settings <ScheduledSetting> is a mode containing start-end time of effect, enabled state, device list. You can have multiple <ScheduledSetting> objects to specify morning, daylight, evening, midnight. Times are forward-looking; typing 2050-0800 would literally mean from 2050 and until 0800 in the coming morning. <ScheduledSettingDeviceList> contains all the devices you want to affect. <ScheduledSettingDevice> is a single device, its outputs (according to configtool) to affect, and the output strength in percent 0-100. To let DOF know which device you want to control, match the ConfigPostfixID with your configtool ini file, for instance directoutputconfig27.ini with 27 being the postfixid. Passing midnight The settings have been confirmed to work passing midnight, which initially was a real problem practically and technically. There's an interesting issue here when a range passes to the next day (2300-0300 for instance), idea being schedules should be able to run all day long in real time without reboots. It's important checks are done in real time, not at DOF boot, as it probably wouldn't become active again if a pincab was online more than a day. Debugging Check your DirectOutput.log file for details if nothing works. Device support Currently Ultimate IO, SainSmart, Teensy and Philips Hue are fully supported. PacLed64, PacDrive and LedWiz have the support added in, but since I don't have those devices I can't confirm that they actually work. Note that the switches / relays like Sainsmart USB device is a 0/1 relay array and that 0=off, while 1-100 is considered on. There is no inbetween, either open or closed ("bitbang"). Gotta run real quick for work; hopefully this post doesn't have too many errors, I'll recheck after work.
×
×
  • Create New...