Jump to content



Photo
- - - - -

Ultimate IO and DOF?

ultimate io dof pacled64

  • Please log in to reply
45 replies to this topic

#21 rambo3

rambo3

    Enthusiast

  • Members
  • PipPipPip
  • 53 posts

  • Flag: Norway

  • Favorite Pinball: Attack from Mars!

Posted 18 February 2017 - 05:37 PM

BTW, have you tried a newer firmware, or perhaps you're already on 1.34? I just upgraded from 1.33 (WinIPAC tells you the version number at upper right corner) to 1.34. DOF still crashed, but LED stayed on and the controls weren't stuck. That's a nice upgrade, if it wasn't just random. Need to do some more testing, but it is interesting.

 

The absolute worst thing that can happen is when UIO "disconnects" and leaves all states frozen, meaning lights, contactors and keys all stay stuck. I've had contactors and lights stay stuck when PC is off due to secondary power. Not ideal.



#22 greeze

greeze

    Enthusiast

  • Members
  • PipPipPip
  • 177 posts

  • Flag: United Kingdom

  • Favorite Pinball: Cirqus Voltaire, Attack from Mars, Theatre of Magic & Medieval Madness

Posted 18 February 2017 - 05:42 PM

No, I haven't checked the firmware but will definitely do that tomorrow. Perhaps an upgrade would do it if the controls stay unstuck. Thanks again; I'll give it a try. :)

 

I'm sure I don't need to tell you to watch out for those stuck contactors, solenoids etc. They (or the wiring) will burn out if left long enough!  :shok:


Cabinet Build YouTube Channel: https://www.youtube....78ywgSq46UXFqjw

 


#23 rambo3

rambo3

    Enthusiast

  • Members
  • PipPipPip
  • 53 posts

  • Flag: Norway

  • Favorite Pinball: Attack from Mars!

Posted 18 February 2017 - 06:49 PM

Yeah, I've read about that, seen a horrifying video of it too. I put those cheap solenoids in a box and replaced them with some 10x more expensive (blew the budget) 24V Siemens contactors. Hopefully they'll be able to withstand a little bit more punishment, but it is scary.

 

I have a ButtKicker © (as in the actual Guitammer ButtKicker, not a "buttkicker") mounted underneath one of my couches. I've been wondering if that isn't a better fit. It's safe, it's extraordinary powerfull, it screws onto the wood, and I guess it could be controlled somehow in DOF by sending it low frequency "notes" if it was hooked up to its own soundcard. It's quick too. Right now I'm loving the contactors, when they all go off it's quite insane, with each and every contactor having that slightly different sound to it.

 

EDIT: All contactors and lights are disconnected while I debug this thing :)


Edited by rambo3, 18 February 2017 - 06:50 PM.


#24 rambo3

rambo3

    Enthusiast

  • Members
  • PipPipPip
  • 53 posts

  • Flag: Norway

  • Favorite Pinball: Attack from Mars!

Posted 18 February 2017 - 10:31 PM

Uploaded a new version just now on Git, killed the old one in case someone accidently clicks the wrong download. Will need some more testing tomorrow, but so far it's looking good.

https://github.com/r...ctOutput/Builds

 

Lockups / freezes from 25s-5 minutes of Attack from Mars was reproduced.  The reason so far looks to be the use of the Ultimarc SDK function Pac64SetLEDIntensities about every ms up to ~40ms. That's a 96 channel blank refresh (12 groups, 8 ports per group) when no change was needed. This was introduced into DOF around 20130809 when PacLed64 support was added in through the use of ForceFullUpdate = true. The logic (as recommended by Ultimarc SDK) is to only use Pac64SetLEDIntensities when more than half the total channels need to be refreshed due to the load, but when ForceFullUpdate is true this refresh happens continuesly regardless of change in intensity or state. Otherwise, use the quicker SetLEDIntensity (which never happened). Thing is, Pac64SetLEDIntensities seems to need about 20ms to finish before sending new commands to the UIO (according to the SDK documentation).

 

I have no idea why this was set to true. Was it a debug session, and someone forgot to turn it back to false? I have no idea. I did notice my flippers didn't get as much stuck anymore, on top of stability (for now anyway). In theory, this should be a huge performance boost / reduced load on the poor UIO.

 

Question is whether this should be applied to PacLed64 as well.


Edited by rambo3, 18 February 2017 - 10:33 PM.


#25 xantari

xantari

    Enthusiast

  • Platinum Supporter
  • 154 posts

  • Flag: United States of America

  • Favorite Pinball: Star Trek TNG

Posted 19 February 2017 - 12:34 PM

Hmm, the connectors? I hadn't thought about those TBH (and, thinking about it now, I have extended some of them. Maybe that's the problem). Thank you for the heads-up, I'll look in to them (like you said though, there're so many of the damn things!)  :D


I had problems with leaf switches on my cab. I ultimately switched them out for the cherry kind of switches because it would cause sporadic issues with keys getting stuck.

Perhaps something similar is happening here?

#26 greeze

greeze

    Enthusiast

  • Members
  • PipPipPip
  • 177 posts

  • Flag: United Kingdom

  • Favorite Pinball: Cirqus Voltaire, Attack from Mars, Theatre of Magic & Medieval Madness

Posted 19 February 2017 - 01:39 PM

 

Hmm, the connectors? I hadn't thought about those TBH (and, thinking about it now, I have extended some of them. Maybe that's the problem). Thank you for the heads-up, I'll look in to them (like you said though, there're so many of the damn things!)  :D


I had problems with leaf switches on my cab. I ultimately switched them out for the cherry kind of switches because it would cause sporadic issues with keys getting stuck.

Perhaps something similar is happening here?

 

 

Maybe. I have leaf switches too. Definitely worth checking. Thanks :)


Cabinet Build YouTube Channel: https://www.youtube....78ywgSq46UXFqjw

 


#27 mjr

mjr

    Pinball Wizard

  • Members
  • PipPipPipPipPip
  • 3,346 posts

  • Flag: United States of America

  • Favorite Pinball: Medieval Madness

Posted 19 February 2017 - 08:26 PM

 

I had problems with leaf switches on my cab. I ultimately switched them out for the cherry kind of switches because it would cause sporadic issues with keys getting stuck.

Perhaps something similar is happening here?

 

Maybe. I have leaf switches too. Definitely worth checking. Thanks :)

 

For what it's worth, the leaf switches would be the very last thing I'd suspect as the source of that kind of trouble.  Vastly more likely, in order of descending probability:

 

- electrical interference from solenoids, motors, contactors, or relays without suitable flyback diodes

- electrical interference from same devices even though they have the diodes, in which case adding small capacitors might help

- software problems

 

Leaf switches are just switches.  The physical contacts inside a microswitch are pretty much the same thing.  If you really think the leaf switch is to blame, about the only way it could be causing a stuck key problem is if it doesn't have at least a small physical gap when you're not pressing its button.  The voltages involved are so low that there's basically zero chance of an "arc" across a gap that's visible to the naked eye.

 

(The main reason I mention this is that I'd hate to see people getting unnecessarily alarmed that they should throw out their flipper button leaf switches and replace them with microswitches, since most people would find that to be a poor compromise in terms of feel.)


Edited by mjr, 19 February 2017 - 08:28 PM.


#28 greeze

greeze

    Enthusiast

  • Members
  • PipPipPip
  • 177 posts

  • Flag: United Kingdom

  • Favorite Pinball: Cirqus Voltaire, Attack from Mars, Theatre of Magic & Medieval Madness

Posted 19 February 2017 - 10:04 PM

Thanks MJR (and sorry Rambo for the thread hijacking), You may be onto something with the electrical interference, there is a solenoid pretty close to the Ultimate IO. I have since disabled that particular one and the freezing has reduced significantly. I'll keep testing/playing :)


Cabinet Build YouTube Channel: https://www.youtube....78ywgSq46UXFqjw

 


#29 rambo3

rambo3

    Enthusiast

  • Members
  • PipPipPip
  • 53 posts

  • Flag: Norway

  • Favorite Pinball: Attack from Mars!

Posted 20 February 2017 - 05:52 PM

It's all good info, the UIO "fix" solved the stuck flipper buttons for me. So, a software issue. I guess this would be because the UIO with the updated DOF is handling both inputs and outputs, as I noticed flippers / inputs would get stuck gradually until the UIO shut down completely. None of that nonsense now.

 

Still need to get better female connectors though. If a fly landed on one of the flasherbar RGB-wires I'd probably see it from outside the apartment..

 

EDIT: Well, that was stupid..ECC-mode; I wouldn't be able to see anything (no signal).


Edited by rambo3, 20 February 2017 - 08:38 PM.


#30 rambo3

rambo3

    Enthusiast

  • Members
  • PipPipPip
  • 53 posts

  • Flag: Norway

  • Favorite Pinball: Attack from Mars!

Posted 27 February 2017 - 07:25 AM

With the pincab somewhat up and running, my contactors turned out to get a little loud during the evenings. Started experimenting with "schedules" in DOF; name ("Night Mode"), clock start-end (0000-2400). Then a device ("UIO contactors"), outputs (49-58 in my case), and strength (0-100 set to 0). For instance, right now I have all the contactors on my UIO set to 0 at 2200-0400. The time setting will transition in and out during play; cab will be affected in real time. LED outputs on the UIO was confirmed to light at half strength if I set those outputs to 50.

 

Experimenting with getting this for more than the UIO (Teensy and Sainsmart USB), but it is working. Check the build links above if you're feelin' lucky and own an UIO, though still early days.



#31 rambo3

rambo3

    Enthusiast

  • Members
  • PipPipPip
  • 53 posts

  • Flag: Norway

  • Favorite Pinball: Attack from Mars!

Posted 01 March 2017 - 05:10 PM

Added auto detection of SainSmart USB devices (no need for serial numbers or Cabinet XML entries), and ScheduledSettings support for UIO, Teensy (great for reducing brightness at night), and SainSmart. Also added to PacLed64, PacDrive, LedWiz but am unable to confirm they work as I don't have those devices. As usual, highly experimental.

 

I've been asked to look into adding Philips Hue support. I have +20 bulbs including a ledstrip, motion sensor etc, so to me this is really interesting :) Right now I just need a little break to get a few tables up.

 

 

Example for ScheduledSettings (custom "night modes"). OutputList is a list of Config Tool outputs matching the webpage, and ConfigPostfixID should match the ConfigTool XML for that device. If a trigger works you'll either hear it, see it (or not), or see it listed in DirectOutput.log. Settings can be tested using DirectOutputConfigTester, and will go live / realtime as clock transitions in and out.

<ScheduledSettings>
	<ScheduledSetting>
		<Name>Night Mode</Name>
		<Enabled>true</Enabled>
		<ClockStart>2000</ClockStart>
		<ClockEnd>0400</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>

Edited by rambo3, 01 March 2017 - 05:11 PM.


#32 GInsonic

GInsonic

    Enthusiast

  • Platinum Supporter
  • 188 posts

  • Flag: Austria

  • Favorite Pinball: Addams Family

Posted 01 March 2017 - 05:34 PM

Great Rambo3, many thanks ! I am using the latest version without night mode and it works flawlessly with my setup (1 UltimateIO, 2 PacLed64). I will test the new version in the next days !

#33 xantari

xantari

    Enthusiast

  • Platinum Supporter
  • 154 posts

  • Flag: United States of America

  • Favorite Pinball: Star Trek TNG

Posted 01 March 2017 - 06:18 PM

How are you reconciling the fact that ultimate io boards don't have controller ids like pacled64 and Ledwiz devices do? On my system I have pacled64 as controller Id 1, and UIO can only be 1 as well. Contacted Andy at ultimarc and he mentioned that UIO boards do not allow controller ID assignments like pacled64 does

#34 rambo3

rambo3

    Enthusiast

  • Members
  • PipPipPip
  • 53 posts

  • Flag: Norway

  • Favorite Pinball: Attack from Mars!

Posted 01 March 2017 - 07:31 PM

Not sure I follow. Are you thinking DOF source? Then yes, the Ids used are 1-based, normally. UIO actually starts at 0 (XML postfix 27), and 1 for the second (=28). Right now there's support for two UIOs (0 and 1).


Edited by rambo3, 01 March 2017 - 07:32 PM.


#35 xantari

xantari

    Enthusiast

  • Platinum Supporter
  • 154 posts

  • Flag: United States of America

  • Favorite Pinball: Star Trek TNG

Posted 01 March 2017 - 07:53 PM

Not sure I follow. Are you thinking DOF source? Then yes, the Ids used are 1-based, normally. UIO actually starts at 0 (XML postfix 27), and 1 for the second (=28). Right now there's support for two UIOs (0 and 1).


In ledblinky it identifies devices by their controller id in case you have multiple pacled64 for example. To identify which device performs which function you need to assign controller ids.

How does DOF handle that?

So if pacled64 starts at 20 to 24, and I have two pacled64, how do I know which pacled64 is 20 and which is 21?

#36 rambo3

rambo3

    Enthusiast

  • Members
  • PipPipPip
  • 53 posts

  • Flag: Norway

  • Favorite Pinball: Attack from Mars!

Posted 01 March 2017 - 11:12 PM

It's 2348 and I'm dead tired, let's see if I can get through this befor e dozing off completely without making a complete mess.

 

I snagged the vendor Id, Product Id etc. from the "PacDrive Test" part of the Ultimarc PacDrive SDK, and debugged from there. When using GetDevicePath(int) for each detected connected device that the PacDrive SDK detects you'll eventually reach something that matches the UIO (\\?\hid#vid_d209&pid_0410&etc, important bit being the pid 041). Next number should be the device index, 0 in my case. That seperates the UIO from the PacLed64, though I don't have any other Ultimarc-devices to confirm this really happens. According to the PacLed64 support already in it has &pid_1401 for instance, pid_1402 etc. That's different from the UIO. You can see this on Github in PacDriveSingleton.

 

This device ID (which is zero-based for UIO, 1-based for PacLed64) gets added during AutoConfig to 30 for the UIO. Chronological device order shouldn't matter, as the ID for the device is added to DOF XML postfix ID and they have to be unique anyway per product family to be differentiated?

 

For the UIO this is 30+ID=30+0=30 for 1st device ID. PacLed64 ID is not zero-based, and starts at 1->4, where 20+1-1=20 for 1st PacLed64, 20+2-1=21 for 2nd, 22 for third, 23 for fourth.

 

Your first PacLed64 would be the one with device ID 1. Once you know what ID your actual physical device is, print it on a sticker, and stick it to the board physically or something, I don't know :)

 

Hopefully this makes sense? Check Github link above for source.

 

EDIT: sorry math going wrong, I'm off to bed..


Edited by rambo3, 01 March 2017 - 11:15 PM.


#37 BritXpatUSA

BritXpatUSA

    Hobbyist

  • Members
  • PipPip
  • 48 posts

  • Flag: United Kingdom

  • Favorite Pinball: wizard

  • 360 Gamer Tag: BritXpatUSA

Posted 05 June 2017 - 09:37 PM

Hey Rambo...

ive just followed your link from my help post! this sounds amazing...

Ill be building from scratch over the coming weeks and happy to be a guinea if required... As i post here is the hardware i have....

Ultimate I/O - buttons galore and two joysticks with spinner, led beacon 12v, 2 white led flashers 12v

Sainsmart 16 port relay ( i have the usb add-on also) for 10 ford 12v solenoids, shaker

teensy -programmable RGBs for sides and back ( 8 strip panel)

 

I have software installed and working:

pinballX

Dof

Doflinx

VP

FP

Steam - VR games & FX2

rocketlauncher - mame/windows 10 games

 

Once im at a point in trying your github...can i get some help guidence.....:-)

 

thanks all.



#38 rambo3

rambo3

    Enthusiast

  • Members
  • PipPipPip
  • 53 posts

  • Flag: Norway

  • Favorite Pinball: Attack from Mars!

Posted 07 June 2017 - 08:37 PM

Absolutely, sound like an almost exact copy of my own setup; got 16x SainSmart, 8x USB too, Teensy, VP, FP, Mame, Windows10, PinballX. The UIO is such a beautiful piece of well behaved hardware!

 

You'll need a DirectOutputFramework\config\Cabinet.xml, something like this if you haven't one running already (may not match, it's just an example):

<?xml version="1.0"?>
<Cabinet xmlns:xsi="http://www.w3.org/20...Schema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
	<Name>Gianna</Name>
	<!-- no need to have pacio in, will be autodetected -->
	<!-- no need to have ft245rbitbangcontroller in, will be autodetected -->
	<!-- no need to have pacled64 in, should be autodetected -->
	<!-- no need to have pacdrive in, should be autodetected -->
	<!-- no need to have ledwiz in, should be autodetected -->
	<!-- philips hue bridge will autoconfig but still needs to be manually added for ip and key, while channels / setup will rely in dof configtool -->
	<OutputControllers>
		<TeensyStripController>
			<Name>TeensyStripController</Name>
			<NumberOfLedsStrip1>576</NumberOfLedsStrip1>
			<NumberOfLedsStrip2>144</NumberOfLedsStrip2>
			<NumberOfLedsStrip3>144</NumberOfLedsStrip3>
			<NumberOfLedsStrip4>0</NumberOfLedsStrip4>
			<NumberOfLedsStrip5>0</NumberOfLedsStrip5>
			<NumberOfLedsStrip6>0</NumberOfLedsStrip6>
			<NumberOfLedsStrip7>0</NumberOfLedsStrip7>
			<NumberOfLedsStrip8>0</NumberOfLedsStrip8>
			<ComPortName>COM5</ComPortName>
		</TeensyStripController>
	</OutputControllers>
	<Toys>
		<LedStrip>
			<Name>PF Back Flashers MX</Name>
			<Width>72</Width>
			<Height>8</Height>
			<LedStripArrangement>LeftRightAlternateTopDown</LedStripArrangement>
			<ColorOrder>GRB</ColorOrder>
			<FirstLedNumber>1</FirstLedNumber>
			<FadingCurveName>SwissLizardsLedCurve</FadingCurveName>
			<OutputControllerName>TeensyStripController</OutputControllerName>
		</LedStrip>
		<LedStrip>
			<Name>PF Left Flashers MX</Name>
			<Width>1</Width>
			<Height>144</Height>
			<LedStripArrangement>TopDownLeftRight</LedStripArrangement>
			<ColorOrder>GRB</ColorOrder>
			<FirstLedNumber>577</FirstLedNumber>
			<FadingCurveName>SwissLizardsLedCurve</FadingCurveName>
			<OutputControllerName>TeensyStripController</OutputControllerName>
		</LedStrip>
		<LedStrip>
			<Name>PF Right Flashers MX</Name>
			<Width>1</Width>
			<Height>144</Height>
			<LedStripArrangement>TopDownLeftRight</LedStripArrangement>
			<ColorOrder>GRB</ColorOrder>
			<FirstLedNumber>721</FirstLedNumber>
			<FadingCurveName>SwissLizardsLedCurve</FadingCurveName>
			<OutputControllerName>TeensyStripController</OutputControllerName>
		</LedStrip>
		<LedWizEquivalent>
			<Name>LedWizEquivalent 30</Name>
			<Outputs>
				<LedWizEquivalentOutput>
					<OutputName>PF Back Flashers MX</OutputName>
					<Description>outputnumbers match configtool</Description>
					<LedWizEquivalentOutputNumber>1</LedWizEquivalentOutputNumber>
				</LedWizEquivalentOutput>    
				<LedWizEquivalentOutput>
					<OutputName>PF Left Flashers MX</OutputName>
					<LedWizEquivalentOutputNumber>4</LedWizEquivalentOutputNumber>
				</LedWizEquivalentOutput>
				<LedWizEquivalentOutput>
					<OutputName>PF Right Flashers MX</OutputName>
					<LedWizEquivalentOutputNumber>7</LedWizEquivalentOutputNumber>
				</LedWizEquivalentOutput>
			</Outputs>
			<LedWizNumber>30</LedWizNumber>
		</LedWizEquivalent>
	</Toys>
	<Colors/>
	<Curves/>
	<AutoConfigEnabled>true</AutoConfigEnabled>
</Cabinet>

You'll want to have DOF R3, the official version, installed first. Then you just overwrite that installation set of files with say the latest build on https://github.com/r...ctOutput/Builds, like the bottom _20170606 a day ago. Then, hop over to configtool on that other site, create an account, "My Account", set WS2811=1, Ultimate/IO=1, SainSmart=1 if you've got the 8-port USB version hooked up. "Save settings".

 

Next go to Port Assignments. There's a "Device" drop down list. The active device is showing a lot of ports below, 96 for the "Ultimate/IO 1" for instance. Point being 3 ports for R(1), G(2) and B(3) if you have them. Match your ports to your solder / physical UIO header output connectors. Initially I just mapped Flipper Left to port 1 and Flipper Right to port 3, which happened to be an RGB joystick. Then pressed "Save Config", then "Generate Config", and put all the INI files inside your DirectOutputFramework\config directory.

 

If that worked, I'd get red and blue flashing when using the left and right flippers in Attack from Mars VP9x-version. Very easy test. If you get that far, you're almost done. DOF is now actually running.

 

In the DOF-directory there's a "DirectOutputConfigTester". You can run this, select your DirectOutputFramework\config\GlobalConfig_B2SServer.xml, a table file (like Visual Pinball\Tables\Attack from Marsvp91x.vpt), and then a RomName (like afm). You then press OK, and can then manually toggle outputs. Quit, then check your DirectOutput.log for issues. It should show you that the UIO was detected at the top. There's also (for me anyway) a similar DirectOutput.log inside your VP\Tables directory which will be used for VP.

 

Something like this:

---------------------------------------------------------------------------------
2017.06.06 20.45.27.188	DirectOutput Logger initialized.
2017.06.06 20.45.27.188	DirectOutput Version 0.9.6366.37353 as of 2017.06.06 20.45
2017.06.06 20.45.27.188	UltimateIO edition. Original project at https://github.com/DirectOutput/DirectOutput
2017.06.06 20.45.27.188	Hail to the lizardking!
2017.06.06 20.45.27.188	Global config loaded from: D:\Tools\DirectOutput\DirectOutputFramework\config\GlobalConfig_B2SServer.xml
2017.06.06 20.45.27.188	Loading Pinball parts
2017.06.06 20.45.27.188	Loading cabinet
2017.06.06 20.45.27.188	Will load cabinet config file: D:\Tools\DirectOutput\DirectOutputFramework\config\Cabinet.xml
2017.06.06 20.45.27.766	2 output controller defnitions and 4 toy definitions loaded from cabinet config.
2017.06.06 20.45.27.766	Cabinet config file has AutoConfig feature enabled. Calling AutoConfig.
2017.06.06 20.45.27.782	Cabinet auto configuration started
2017.06.06 20.45.27.797	PacDriveSingleton.PacUIOGetIdList: i=0, numdevices=1, DeviceType=IPACIO
2017.06.06 20.45.27.797	PacUIOAutoConfigurator.AutoConfig.. Detected I-PAC Ultimate[0], name=PacUIO 0
2017.06.06 20.45.27.797	Detected and added PacUIO Id 0 with name PacUIO 0
2017.06.06 20.45.27.797 Added LedwizEquivalent Nr. 27 with name PacUIO 0 Equivalent 1 for PacUIO with Id 0

Once you get all your stuff working, there's day&night modes, custom output overrides etc you can do. Then RGB-stuff with the LED-strips is a whole different thing. Wear sunglasses, even better; cover up the stuff while testing. When everything goes to ...not well, you hit the sack and try again another time :)

 

And hey, if you've got Philips Hue; a few days ago I hooked up about 16 bulbs and LED-strips to DOF and enjoyed some Attack from Mars. It works. And it's quite insane. It's got lag, but it's cool. Then you exit a table, and you're in complete darkness C-8

 

AND: I almost forgot. If you haven't already, update your UIO-board using the Ultimarc firmware updater at https://www.ultimarc.com/download.html

Mine was a bit old, and I think it partially solved an issue I was having. Worth checking out.


Edited by rambo3, 07 June 2017 - 08:48 PM.


#39 BritXpatUSA

BritXpatUSA

    Hobbyist

  • Members
  • PipPip
  • 48 posts

  • Flag: United Kingdom

  • Favorite Pinball: wizard

  • 360 Gamer Tag: BritXpatUSA

Posted 08 June 2017 - 04:36 PM

Absolutely, sound like an almost exact copy of my own setup; got 16x SainSmart, 8x USB too, Teensy, VP, FP, Mame, Windows10, PinballX. The UIO is such a beautiful piece of well behaved hardware!

 

You'll need a DirectOutputFramework\config\Cabinet.xml, something like this if you haven't one running already (may not match, it's just an example):

<?xml version="1.0"?>
<Cabinet xmlns:xsi="http://www.w3.org/20...Schema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
	<Name>Gianna</Name>
	<!-- no need to have pacio in, will be autodetected -->
	<!-- no need to have ft245rbitbangcontroller in, will be autodetected -->
	<!-- no need to have pacled64 in, should be autodetected -->
	<!-- no need to have pacdrive in, should be autodetected -->
	<!-- no need to have ledwiz in, should be autodetected -->
	<!-- philips hue bridge will autoconfig but still needs to be manually added for ip and key, while channels / setup will rely in dof configtool -->
	<OutputControllers>
		<TeensyStripController>
			<Name>TeensyStripController</Name>
			<NumberOfLedsStrip1>576</NumberOfLedsStrip1>
			<NumberOfLedsStrip2>144</NumberOfLedsStrip2>
			<NumberOfLedsStrip3>144</NumberOfLedsStrip3>
			<NumberOfLedsStrip4>0</NumberOfLedsStrip4>
			<NumberOfLedsStrip5>0</NumberOfLedsStrip5>
			<NumberOfLedsStrip6>0</NumberOfLedsStrip6>
			<NumberOfLedsStrip7>0</NumberOfLedsStrip7>
			<NumberOfLedsStrip8>0</NumberOfLedsStrip8>
			<ComPortName>COM5</ComPortName>
		</TeensyStripController>
	</OutputControllers>
	<Toys>
		<LedStrip>
			<Name>PF Back Flashers MX</Name>
			<Width>72</Width>
			<Height>8</Height>
			<LedStripArrangement>LeftRightAlternateTopDown</LedStripArrangement>
			<ColorOrder>GRB</ColorOrder>
			<FirstLedNumber>1</FirstLedNumber>
			<FadingCurveName>SwissLizardsLedCurve</FadingCurveName>
			<OutputControllerName>TeensyStripController</OutputControllerName>
		</LedStrip>
		<LedStrip>
			<Name>PF Left Flashers MX</Name>
			<Width>1</Width>
			<Height>144</Height>
			<LedStripArrangement>TopDownLeftRight</LedStripArrangement>
			<ColorOrder>GRB</ColorOrder>
			<FirstLedNumber>577</FirstLedNumber>
			<FadingCurveName>SwissLizardsLedCurve</FadingCurveName>
			<OutputControllerName>TeensyStripController</OutputControllerName>
		</LedStrip>
		<LedStrip>
			<Name>PF Right Flashers MX</Name>
			<Width>1</Width>
			<Height>144</Height>
			<LedStripArrangement>TopDownLeftRight</LedStripArrangement>
			<ColorOrder>GRB</ColorOrder>
			<FirstLedNumber>721</FirstLedNumber>
			<FadingCurveName>SwissLizardsLedCurve</FadingCurveName>
			<OutputControllerName>TeensyStripController</OutputControllerName>
		</LedStrip>
		<LedWizEquivalent>
			<Name>LedWizEquivalent 30</Name>
			<Outputs>
				<LedWizEquivalentOutput>
					<OutputName>PF Back Flashers MX</OutputName>
					<Description>outputnumbers match configtool</Description>
					<LedWizEquivalentOutputNumber>1</LedWizEquivalentOutputNumber>
				</LedWizEquivalentOutput>    
				<LedWizEquivalentOutput>
					<OutputName>PF Left Flashers MX</OutputName>
					<LedWizEquivalentOutputNumber>4</LedWizEquivalentOutputNumber>
				</LedWizEquivalentOutput>
				<LedWizEquivalentOutput>
					<OutputName>PF Right Flashers MX</OutputName>
					<LedWizEquivalentOutputNumber>7</LedWizEquivalentOutputNumber>
				</LedWizEquivalentOutput>
			</Outputs>
			<LedWizNumber>30</LedWizNumber>
		</LedWizEquivalent>
	</Toys>
	<Colors/>
	<Curves/>
	<AutoConfigEnabled>true</AutoConfigEnabled>
</Cabinet>

You'll want to have DOF R3, the official version, installed first. Then you just overwrite that installation set of files with say the latest build on https://github.com/r...ctOutput/Builds, like the bottom _20170606 a day ago. Then, hop over to configtool on that other site, create an account, "My Account", set WS2811=1, Ultimate/IO=1, SainSmart=1 if you've got the 8-port USB version hooked up. "Save settings".

 

Next go to Port Assignments. There's a "Device" drop down list. The active device is showing a lot of ports below, 96 for the "Ultimate/IO 1" for instance. Point being 3 ports for R(1), G(2) and B(3) if you have them. Match your ports to your solder / physical UIO header output connectors. Initially I just mapped Flipper Left to port 1 and Flipper Right to port 3, which happened to be an RGB joystick. Then pressed "Save Config", then "Generate Config", and put all the INI files inside your DirectOutputFramework\config directory.

 

If that worked, I'd get red and blue flashing when using the left and right flippers in Attack from Mars VP9x-version. Very easy test. If you get that far, you're almost done. DOF is now actually running.

 

In the DOF-directory there's a "DirectOutputConfigTester". You can run this, select your DirectOutputFramework\config\GlobalConfig_B2SServer.xml, a table file (like Visual Pinball\Tables\Attack from Marsvp91x.vpt), and then a RomName (like afm). You then press OK, and can then manually toggle outputs. Quit, then check your DirectOutput.log for issues. It should show you that the UIO was detected at the top. There's also (for me anyway) a similar DirectOutput.log inside your VP\Tables directory which will be used for VP.

 

Something like this:

---------------------------------------------------------------------------------
2017.06.06 20.45.27.188	DirectOutput Logger initialized.
2017.06.06 20.45.27.188	DirectOutput Version 0.9.6366.37353 as of 2017.06.06 20.45
2017.06.06 20.45.27.188	UltimateIO edition. Original project at https://github.com/DirectOutput/DirectOutput
2017.06.06 20.45.27.188	Hail to the lizardking!
2017.06.06 20.45.27.188	Global config loaded from: D:\Tools\DirectOutput\DirectOutputFramework\config\GlobalConfig_B2SServer.xml
2017.06.06 20.45.27.188	Loading Pinball parts
2017.06.06 20.45.27.188	Loading cabinet
2017.06.06 20.45.27.188	Will load cabinet config file: D:\Tools\DirectOutput\DirectOutputFramework\config\Cabinet.xml
2017.06.06 20.45.27.766	2 output controller defnitions and 4 toy definitions loaded from cabinet config.
2017.06.06 20.45.27.766	Cabinet config file has AutoConfig feature enabled. Calling AutoConfig.
2017.06.06 20.45.27.782	Cabinet auto configuration started
2017.06.06 20.45.27.797	PacDriveSingleton.PacUIOGetIdList: i=0, numdevices=1, DeviceType=IPACIO
2017.06.06 20.45.27.797	PacUIOAutoConfigurator.AutoConfig.. Detected I-PAC Ultimate[0], name=PacUIO 0
2017.06.06 20.45.27.797	Detected and added PacUIO Id 0 with name PacUIO 0
2017.06.06 20.45.27.797 Added LedwizEquivalent Nr. 27 with name PacUIO 0 Equivalent 1 for PacUIO with Id 0

Once you get all your stuff working, there's day&night modes, custom output overrides etc you can do. Then RGB-stuff with the LED-strips is a whole different thing. Wear sunglasses, even better; cover up the stuff while testing. When everything goes to ...not well, you hit the sack and try again another time :)

 

And hey, if you've got Philips Hue; a few days ago I hooked up about 16 bulbs and LED-strips to DOF and enjoyed some Attack from Mars. It works. And it's quite insane. It's got lag, but it's cool. Then you exit a table, and you're in complete darkness C-8

 

AND: I almost forgot. If you haven't already, update your UIO-board using the Ultimarc firmware updater at https://www.ultimarc.com/download.html

Mine was a bit old, and I think it partially solved an issue I was having. Worth checking out.

you my friend are awesome! looks like ill be hitting this at the weekend....

I dont have the Hue as im using smarthub with orsam bulbs and leds...i have switch/sockets/pool etc all running through this. i have alexa (amazon) ill all rooms that can trigger also.

Something that would be really cool is ask " alexa" to turn on the pinball....I have my harmony remote turn it on at the moment....

 

Ill report back....

thnks!

J.



#40 BritXpatUSA

BritXpatUSA

    Hobbyist

  • Members
  • PipPip
  • 48 posts

  • Flag: United Kingdom

  • Favorite Pinball: wizard

  • 360 Gamer Tag: BritXpatUSA

Posted 19 June 2017 - 12:29 AM

hi all...

I have been trying all weekend and to no avail....help pls!

I stripped out the ultimate IO and just had th teensy at one stage and it would show in the directouptconfigtester. but I could not see any leds light up.

here are my files

<?xml version="1.0"?>
<Cabinet xmlns:xsi="http://www.w3.org/20...Schema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
 <Name>Pinball Arcade VR</Name>
 <!-- no need to have pacio in, will be autodetected -->
 <!-- no need to have ft245rbitbangcontroller in, will be autodetected -->
 <!-- no need to have pacled64 in, should be autodetected -->
 <!-- no need to have pacdrive in, should be autodetected -->
 <!-- no need to have ledwiz in, should be autodetected -->
 <!-- philips hue bridge will autoconfig but still needs to be manually added for ip and key, while channels / setup will rely in dof configtool -->
 <OutputControllers>
  <TeensyStripController>
   <Name>TeensyStripController</Name>
   <NumberOfLedsStrip1>280</NumberOfLedsStrip1>
   <NumberOfLedsStrip2>0</NumberOfLedsStrip2>
   <NumberOfLedsStrip3>0</NumberOfLedsStrip3>
   <NumberOfLedsStrip4>0</NumberOfLedsStrip4>
   <NumberOfLedsStrip5>0</NumberOfLedsStrip5>
   <NumberOfLedsStrip6>0</NumberOfLedsStrip6>
   <NumberOfLedsStrip7>0</NumberOfLedsStrip7>
   <NumberOfLedsStrip8>0</NumberOfLedsStrip8>
   <ComPortName>COM7</ComPortName>
  </TeensyStripController>
 </OutputControllers>
 <Toys>
  <LedStrip>
   <Name>PF Back Flashers MX</Name>
   <Width>1</Width>
   <Height>280</Height>
   <LedStripArrangement>LeftRightAlternateTopDown</LedStripArrangement>
   <ColorOrder>GRB</ColorOrder>
   <FirstLedNumber>1</FirstLedNumber>
   <FadingCurveName>SwissLizardsLedCurve</FadingCurveName>
   <OutputControllerName>TeensyStripController</OutputControllerName>
  </LedStrip>
  <LedStrip>
   <Name>PF Left Flashers MX</Name>
   <Width>1</Width>
   <Height>144</Height>
   <LedStripArrangement>TopDownLeftRight</LedStripArrangement>
   <ColorOrder>GRB</ColorOrder>
   <FirstLedNumber>577</FirstLedNumber>
   <FadingCurveName>SwissLizardsLedCurve</FadingCurveName>
   <OutputControllerName>TeensyStripController</OutputControllerName>
  </LedStrip>
  <LedStrip>
   <Name>PF Right Flashers MX</Name>
   <Width>1</Width>
   <Height>144</Height>
   <LedStripArrangement>TopDownLeftRight</LedStripArrangement>
   <ColorOrder>GRB</ColorOrder>
   <FirstLedNumber>721</FirstLedNumber>
   <FadingCurveName>SwissLizardsLedCurve</FadingCurveName>
   <OutputControllerName>TeensyStripController</OutputControllerName>
  </LedStrip>
  <LedWizEquivalent>
   <Name>LedWizEquivalent 30</Name>
   <Outputs>
    <LedWizEquivalentOutput>
     <OutputName>PF Back Flashers MX</OutputName>
     <Description>outputnumbers match configtool</Description>
     <LedWizEquivalentOutputNumber>1</LedWizEquivalentOutputNumber>
    </LedWizEquivalentOutput>   
    <LedWizEquivalentOutput>
     <OutputName>PF Left Flashers MX</OutputName>
     <LedWizEquivalentOutputNumber>4</LedWizEquivalentOutputNumber>
    </LedWizEquivalentOutput>
    <LedWizEquivalentOutput>
     <OutputName>PF Right Flashers MX</OutputName>
     <LedWizEquivalentOutputNumber>7</LedWizEquivalentOutputNumber>
    </LedWizEquivalentOutput>
   
<Outputcontroller>
      <LedWizNumber>30</LedWizNumber>
    </LedWizEquivalent>
    <LedWizEquivalent>
      <Name>PacUIO 0 Equivalent 1</Name>
      <Outputs>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.01</OutputName>
          <LedWizEquivalentOutputNumber>1</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.02</OutputName>
          <LedWizEquivalentOutputNumber>2</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.03</OutputName>
          <LedWizEquivalentOutputNumber>3</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.04</OutputName>
          <LedWizEquivalentOutputNumber>4</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.05</OutputName>
          <LedWizEquivalentOutputNumber>5</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.06</OutputName>
          <LedWizEquivalentOutputNumber>6</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.07</OutputName>
          <LedWizEquivalentOutputNumber>7</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.08</OutputName>
          <LedWizEquivalentOutputNumber>8</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.09</OutputName>
          <LedWizEquivalentOutputNumber>9</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.10</OutputName>
          <LedWizEquivalentOutputNumber>10</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.11</OutputName>
          <LedWizEquivalentOutputNumber>11</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.12</OutputName>
          <LedWizEquivalentOutputNumber>12</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.13</OutputName>
          <LedWizEquivalentOutputNumber>13</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.14</OutputName>
          <LedWizEquivalentOutputNumber>14</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.15</OutputName>
          <LedWizEquivalentOutputNumber>15</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.16</OutputName>
          <LedWizEquivalentOutputNumber>16</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.17</OutputName>
          <LedWizEquivalentOutputNumber>17</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.18</OutputName>
          <LedWizEquivalentOutputNumber>18</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.19</OutputName>
          <LedWizEquivalentOutputNumber>19</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.20</OutputName>
          <LedWizEquivalentOutputNumber>20</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.21</OutputName>
          <LedWizEquivalentOutputNumber>21</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.22</OutputName>
          <LedWizEquivalentOutputNumber>22</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.23</OutputName>
          <LedWizEquivalentOutputNumber>23</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.24</OutputName>
          <LedWizEquivalentOutputNumber>24</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.25</OutputName>
          <LedWizEquivalentOutputNumber>25</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.26</OutputName>
          <LedWizEquivalentOutputNumber>26</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.27</OutputName>
          <LedWizEquivalentOutputNumber>27</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.28</OutputName>
          <LedWizEquivalentOutputNumber>28</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.29</OutputName>
          <LedWizEquivalentOutputNumber>29</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.30</OutputName>
          <LedWizEquivalentOutputNumber>30</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.31</OutputName>
          <LedWizEquivalentOutputNumber>31</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.32</OutputName>
          <LedWizEquivalentOutputNumber>32</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.33</OutputName>
          <LedWizEquivalentOutputNumber>33</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.34</OutputName>
          <LedWizEquivalentOutputNumber>34</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.35</OutputName>
          <LedWizEquivalentOutputNumber>35</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.36</OutputName>
          <LedWizEquivalentOutputNumber>36</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.37</OutputName>
          <LedWizEquivalentOutputNumber>37</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.38</OutputName>
          <LedWizEquivalentOutputNumber>38</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.39</OutputName>
          <LedWizEquivalentOutputNumber>39</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.40</OutputName>
          <LedWizEquivalentOutputNumber>40</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.41</OutputName>
          <LedWizEquivalentOutputNumber>41</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.42</OutputName>
          <LedWizEquivalentOutputNumber>42</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.43</OutputName>
          <LedWizEquivalentOutputNumber>43</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.44</OutputName>
          <LedWizEquivalentOutputNumber>44</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.45</OutputName>
          <LedWizEquivalentOutputNumber>45</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.46</OutputName>
          <LedWizEquivalentOutputNumber>46</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.47</OutputName>
          <LedWizEquivalentOutputNumber>47</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.48</OutputName>
          <LedWizEquivalentOutputNumber>48</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.49</OutputName>
          <LedWizEquivalentOutputNumber>49</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.50</OutputName>
          <LedWizEquivalentOutputNumber>50</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.51</OutputName>
          <LedWizEquivalentOutputNumber>51</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.52</OutputName>
          <LedWizEquivalentOutputNumber>52</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.53</OutputName>
          <LedWizEquivalentOutputNumber>53</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.54</OutputName>
          <LedWizEquivalentOutputNumber>54</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.55</OutputName>
          <LedWizEquivalentOutputNumber>55</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.56</OutputName>
          <LedWizEquivalentOutputNumber>56</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.57</OutputName>
          <LedWizEquivalentOutputNumber>57</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.58</OutputName>
          <LedWizEquivalentOutputNumber>58</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.59</OutputName>
          <LedWizEquivalentOutputNumber>59</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.60</OutputName>
          <LedWizEquivalentOutputNumber>60</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.61</OutputName>
          <LedWizEquivalentOutputNumber>61</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.62</OutputName>
          <LedWizEquivalentOutputNumber>62</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.63</OutputName>
          <LedWizEquivalentOutputNumber>63</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.64</OutputName>
          <LedWizEquivalentOutputNumber>64</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.65</OutputName>
          <LedWizEquivalentOutputNumber>65</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.66</OutputName>
          <LedWizEquivalentOutputNumber>66</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.67</OutputName>
          <LedWizEquivalentOutputNumber>67</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.68</OutputName>
          <LedWizEquivalentOutputNumber>68</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.69</OutputName>
          <LedWizEquivalentOutputNumber>69</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.70</OutputName>
          <LedWizEquivalentOutputNumber>70</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.71</OutputName>
          <LedWizEquivalentOutputNumber>71</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.72</OutputName>
          <LedWizEquivalentOutputNumber>72</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.73</OutputName>
          <LedWizEquivalentOutputNumber>73</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.74</OutputName>
          <LedWizEquivalentOutputNumber>74</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.75</OutputName>
          <LedWizEquivalentOutputNumber>75</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.76</OutputName>
          <LedWizEquivalentOutputNumber>76</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.77</OutputName>
          <LedWizEquivalentOutputNumber>77</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.78</OutputName>
          <LedWizEquivalentOutputNumber>78</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.79</OutputName>
          <LedWizEquivalentOutputNumber>79</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.80</OutputName>
          <LedWizEquivalentOutputNumber>80</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.81</OutputName>
          <LedWizEquivalentOutputNumber>81</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.82</OutputName>
          <LedWizEquivalentOutputNumber>82</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.83</OutputName>
          <LedWizEquivalentOutputNumber>83</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.84</OutputName>
          <LedWizEquivalentOutputNumber>84</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.85</OutputName>
          <LedWizEquivalentOutputNumber>85</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.86</OutputName>
          <LedWizEquivalentOutputNumber>86</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.87</OutputName>
          <LedWizEquivalentOutputNumber>87</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.88</OutputName>
          <LedWizEquivalentOutputNumber>88</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.89</OutputName>
          <LedWizEquivalentOutputNumber>89</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.90</OutputName>
          <LedWizEquivalentOutputNumber>90</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.91</OutputName>
          <LedWizEquivalentOutputNumber>91</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.92</OutputName>
          <LedWizEquivalentOutputNumber>92</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.93</OutputName>
          <LedWizEquivalentOutputNumber>93</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.94</OutputName>
          <LedWizEquivalentOutputNumber>94</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.95</OutputName>
          <LedWizEquivalentOutputNumber>95</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
        <LedWizEquivalentOutput>
          <OutputName>PacUIO 0\PacUIO 0.96</OutputName>
          <LedWizEquivalentOutputNumber>96</LedWizEquivalentOutputNumber>
        </LedWizEquivalentOutput>
 <PacUIO>
      <Name>PacUIO 0</Name>
      <Id>0</Id>
    </PacUIO>
  </OutputControllers>
  <ScheduledSettings />
  <SequentialOutputSettings />
  <TableOverrideSettings />
 </Toys>
 <Colors/>
 <Curves/>
 <AutoConfigEnabled>true</AutoConfigEnabled>
</Cabinet>

 

Global config

<?xml version="1.0" encoding="utf-8"?>
<!--Global configuration for the DirectOutput framework.-->
<!--Saved by DirectOutput Version 0.9.6366.37353: 2017-06-17 20-35-44-->
<GlobalConfig>
  <LedWizDefaultMinCommandIntervalMs>1</LedWizDefaultMinCommandIntervalMs>
  <LedControlMinimumEffectDurationMs>60</LedControlMinimumEffectDurationMs>
  <LedControlMinimumRGBEffectDurationMs>120</LedControlMinimumRGBEffectDurationMs>
  <IniFilesPath>D:\Files\DirectOutput\config</IniFilesPath>
  <CabinetConfigFilePattern>D:\Files\DirectOutput\config\cabinet.xml</CabinetConfigFilePattern>
  <TableConfigFilePatterns />
  <EnableLogging>true</EnableLogging>
  <ClearLogOnSessionStart>true</ClearLogOnSessionStart>
  <LogFilePattern>D:\Files\DirectOutput\DirectOutput.log</LogFilePattern>
</GlobalConfig>

 

 

LOG FILE

---------------------------------------------------------------------------------
2017.06.18 20:10:17.986 DirectOutput Logger initialized
2017.06.18 20:10:17.986 DirectOutput Version 0.9.5812.27024 as of 2015.11.30 15:00
2017.06.18 20:10:17.987 Global config loaded from: D:\Files\DirectOutput\config\GlobalConfig_B2SServer.xml
2017.06.18 20:10:17.987 Loading Pinball parts
2017.06.18 20:10:17.987 Loading cabinet
2017.06.18 20:10:17.987 Will load cabinet config file: D:\Files\DirectOutput\config\cabinet.xml
2017.06.18 20:10:18.073 EXCEPTION: Could not load cabinet config from XML data.
2017.06.18 20:10:18.073 EXCEPTION: Thread:
2017.06.18 20:10:18.073 EXCEPTION: Message: Exception --> Could not deserialize the cabinet config from XML data.
2017.06.18 20:10:18.073 EXCEPTION: A exception occured when loading cabinet config file: D:\Files\DirectOutput\config\cabinet.xml
2017.06.18 20:10:18.073 EXCEPTION: Thread:
2017.06.18 20:10:18.073 EXCEPTION: Message: NullReferenceException --> Object reference not set to an instance of an object.
2017.06.18 20:10:18.074 EXCEPTION: Stacktrace:    at DirectOutput.Log.Exception(String Message, Exception E)
2017.06.18 20:10:18.074 EXCEPTION: Stacktrace:    at DirectOutput.Cab.Cabinet.GetCabinetFromConfigXml(String ConfigXml)
2017.06.18 20:10:18.074 EXCEPTION: Stacktrace:    at DirectOutput.Cab.Cabinet.GetCabinetFromConfigXmlFile(String FileName)
2017.06.18 20:10:18.074 EXCEPTION: Stacktrace:    at DirectOutput.Cab.Cabinet.GetCabinetFromConfigXmlFile(FileInfo CabinetConfigFile)
2017.06.18 20:10:18.074 EXCEPTION: Stacktrace:    at DirectOutput.Pinball.Setup(String GlobalConfigFilename, String TableFilename, String RomName)
2017.06.18 20:10:18.074 EXCEPTION: Targetsite: Void Exception(System.String, System.Exception)
2017.06.18 20:10:18.074 No cabinet config file loaded. Will use AutoConfig.
2017.06.18 20:10:18.075 Cabinet auto configuration started
2017.06.18 20:10:18.102 Debug: Ledwiz devicelist content. Handles: 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, Num devices: 0
2017.06.18 20:10:18.102 Debug: Disposing LedWiz instance -01.
2017.06.18 20:10:18.102 Cabinet auto configuration finished
2017.06.18 20:10:18.102 Cabinet loaded
2017.06.18 20:10:18.102 Loading table config
2017.06.18 20:10:18.102 Warning: No table config file found. Will try to load config from LedControl file(s).
2017.06.18 20:10:18.102 Will try to load configs from DirectOutput.ini or LedControl.ini file(s) for RomName afm
2017.06.18 20:10:18.104 Loading LedControl file D:\Files\DirectOutput\config\directoutputconfig27.ini
2017.06.18 20:10:18.149 Loading LedControl file D:\Files\DirectOutput\config\directoutputconfig30.ini
2017.06.18 20:10:18.476 2 directoutputconfig.ini or ledcontrol.ini files loaded.
2017.06.18 20:10:18.476 Config for RomName afm exists in LedControl data. Updating cabinet and config.
2017.06.18 20:10:18.484 Table config loading finished
2017.06.18 20:10:18.484 Pinball parts loaded
2017.06.18 20:10:18.484 Starting processes
2017.06.18 20:10:18.484 Initializing cabinet
2017.06.18 20:10:18.484 Debug: Initializing output controllers
2017.06.18 20:10:18.484 Debug: Output controllers initialized
2017.06.18 20:10:18.484 Cabinet initialized
2017.06.18 20:10:18.487 Loading shape definition file: D:\Files\DirectOutput\config\DirectOutputShapes.xml
2017.06.18 20:10:18.519 Framework initialized.
2017.06.18 20:10:18.519 Have fun! :)
2017.06.18 20:10:30.903 Finishing framework
2017.06.18 20:10:30.904 Finishing cabinet
2017.06.18 20:10:30.904 Debug: Finishing output controllers
2017.06.18 20:10:30.904 Debug: Output controllers finished
2017.06.18 20:10:30.904 Cabinet finished
2017.06.18 20:10:30.904 DirectOutput framework finished.
2017.06.18 20:10:30.904 Bye and thanks for using!
 

 

carried out the dof config tool put the files in config folder

directoutputconfig30

directoutputconfig27

 

 

I have the iPAQ port 1(+RGB) to the port1 (relay) on the sainssmart

I have the teensy wired like this

power to lep strip on red

Green data led strip to CAT6 to teensy solid orange

Black led strip to CAT6 orange/white & power black -

 

teensy is flasing orange led with a flash flash every 1.5 sec when nothing is running

 

hoping someone can point me in the right direction......:-)

 

Brit







Also tagged with one or more of these keywords: ultimate io, dof, pacled64