20 replies to this topic

[chrisseear]

Can someone please point me to some more detailed information on how to make a cabinet.xml. I have read the wiki a million times and anything else i can google but cant find all the info.

Currently I have DOFR2 running with config files from dof config tool (Pacled64 auto configure), it seems to work well enough with visual pinball. I am hoping to install DOFR3 and get it to work but when I do, all the wrong toys go off. I am guessing I need a cabinet.xml and am trying to make one, but I have no idea how to define my toys (I got what I could from the example but I need more I think). Can someone please have a look at my attached cabinet.xml and point me in the right direction.

 

The long term goal is to get DOFR3 working well, then DOFLinks to bring future pinball and PinballFX to life, (1 step at a time though).

Thanks in advance

Attached Files

•  cabconfig.xml   29.01KB   208 downloads
•  dofconfig.png   305.25KB   20 downloads

[arngrim]

you don't need more a cabinet.xml for dof r2 than r3, but you need to configure dof with GlobalConfigEditor.exe in order to make it working for dof r3

[chrisseear]

Thanks for replying, I tried what you said a million times but it never worked right.

I had my existing DOFR2 working properly with all VP9 and VP10.

I backed up my R2 Folder, copied the latest R3 into the Directoutput folder.

Then I used the globalconfigeditor to create GlobalConfig.xml and saved it in the /DirectOutput/Config Folder

 

<?xml version="1.0" encoding="utf-8"?>
<!--Global configuration for the DirectOutput framework.-->
<!--Saved by DirectOutput Version 0.9.5818.37242: 2017-01-29 10-51-43-->
<GlobalConfig>
  <LedWizDefaultMinCommandIntervalMs>1</LedWizDefaultMinCommandIntervalMs>
  <LedControlMinimumEffectDurationMs>60</LedControlMinimumEffectDurationMs>
  <LedControlMinimumRGBEffectDurationMs>120</LedControlMinimumRGBEffectDurationMs>
  <IniFilesPath />
  <CabinetConfigFilePattern></CabinetConfigFilePattern>
  <TableConfigFilePatterns />
  <EnableLogging>true</EnableLogging>
  <ClearLogOnSessionStart>true</ClearLogOnSessionStart>
  <LogFilePattern>.\DirectOutput.log</LogFilePattern>
</GlobalConfig>

 

Then I used DirectOutputConfig Tester which gave me this log, I had to select a table, I choose "attack from mars" and afm.rom

 

---------------------------------------------------------------------------------
2017.01.29 12:10:20.428 DirectOutput Logger initialized
2017.01.29 12:10:20.428 DirectOutput Version 0.9.5818.37242 as of 2015.12.06 20:41
2017.01.29 12:10:20.428 Global config loaded from: C:\Pinball\DirectOutput\Config\GlobalConfig.xml
2017.01.29 12:10:20.428 Loading Pinball parts
2017.01.29 12:10:20.428 Loading cabinet
2017.01.29 12:10:20.428 No cabinet config file loaded. Will use AutoConfig.
2017.01.29 12:10:20.428 Cabinet auto configuration started
2017.01.29 12:10:20.535 Detected and added PacLed64 Id 1 with name PacLed64 1
2017.01.29 12:10:20.535 Added LedwizEquivalent Nr. 20 with name PacLed64 1 Equivalent 1 for PacLed64 with Id 1
2017.01.29 12:10:20.551 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.01.29 12:10:20.551 Debug: Disposing LedWiz instance -01.
2017.01.29 12:10:20.551 Cabinet auto configuration finished
2017.01.29 12:10:20.551 Cabinet loaded
2017.01.29 12:10:20.551 Loading table config
2017.01.29 12:10:20.551 Warning: No table config file found. Will try to load config from LedControl file(s).
2017.01.29 12:10:20.551 Will try to load configs from DirectOutput.ini or LedControl.ini file(s) for RomName afm
2017.01.29 12:10:20.551 Loading LedControl file C:\Pinball\DirectOutput\Config\directoutputconfig20.ini
2017.01.29 12:10:20.942 1 directoutputconfig.ini or ledcontrol.ini files loaded.
2017.01.29 12:10:20.942 Config for RomName afm exists in LedControl data. Updating cabinet and config.
2017.01.29 12:10:20.957 Table config loading finished
2017.01.29 12:10:20.957 Pinball parts loaded
2017.01.29 12:10:20.957 Starting processes
2017.01.29 12:10:20.957 Initializing cabinet
2017.01.29 12:10:20.957 Debug: Initializing output controllers
2017.01.29 12:10:20.957 PacLed64 Id:1 initialized and updater thread started.
2017.01.29 12:10:20.957 Debug: Output controllers initialized
2017.01.29 12:10:20.957 Cabinet initialized
2017.01.29 12:10:20.957 Loading shape definition file: C:\Pinball\DirectOutput\DirectOutputShapes.xml
2017.01.29 12:10:20.989 Framework initialized.
2017.01.29 12:10:20.989 Have fun!
2017.01.29 12:12:45.319 Finishing framework
2017.01.29 12:12:45.319 Finishing cabinet
2017.01.29 12:12:45.319 Debug: Finishing output controllers
2017.01.29 12:12:46.351 PacLed64 Id:1 finished and updater thread stopped.
2017.01.29 12:12:46.351 Debug: Output controllers finished
2017.01.29 12:12:46.351 Cabinet finished
2017.01.29 12:12:46.351 DirectOutput framework finished.
2017.01.29 12:12:46.351 Bye and thanks for using!

 

I click and pulse outputs, I have no idea if they are right or wrong. When I play table they are clearly wrong, wrong stuff going off all the time, I am scared I am going to damage it soon testing this.

 

I must be missing something simple but after a week or 2 of trying to get this going I am losing hope. This is the reason I thought making a cabinet.xml might help, but I don't know how to define the toys for my cab and cant find the info anywhere to it properly without guessing. I filled in the fields in the cabinet.xml I asked you to look at, but since I guessed there's no possible way it can be correct.

 

Anyone have any idea's ?
 

[chrisseear]

Out of curiosity I did the same test with my R2 folder, with the same table and rom and the log produced a lot of strange stuff. (to long to copy paste)

But when I Play the table everything works perfectly, not sure if this means anything ??

Attached Files

•  DirectOutput.zip   18.29KB   76 downloads

Edited by chrisseear, 29 January 2017 - 01:55 AM.

[arngrim]

yes you absolutely need dof r3 with the actual configs from the configtool, hence all the error messages, try to override the dof r3 files on the dof r2 files after a backup of the r2, unblock all the files, i think you need to execute this as well RegisterDirectOutputComObject.exe

[chrisseear]

Thankyou for replying again. The log from the third post if after I did exactly what you said, With DOFR3 overwriting my R2 files, new configs from the config tool, after I unblock all files and register the com thing. I get no errors from DOF, but when I play the table all the wrong toys go off which sounds super terrible (example would be a flashing effect on a solenoid or a motor).

Again comparing

in post 3 you can see DirectOutput Version 0.9.5818.37242: 2017-01-29 10-51-43   R3 no errors - wrong toys go off

in post 4 you can see DirectOutput Version 0.8.5307.1702 as of 2014.07.13 00:56   R2 with new configs from the config tool gives a lot of errors (config tool version 2308), table plays perfectly.

 

I must be missing something

 

I might go back and completely reinstall DOF

Thankyou again for replying, I am spending a lot of time trying to fix this.

 

==========================================================

So I went back and did a complete reinstall of dof R1, then R2, then R3, overwriting each time. Pulled fresh config files from the Config Tool, made a new globalconfig_b2sserver.xml, put all the config files in ./directoutput/config. All files unblocked and set to run as administrator, RegisteretDirectOutputComObject successful.

 

Started a table (Mars attacks) and its still up the shit. The light effects activate solenoids and contactors and replay knocker, it sounds terrible, I cant run it for more than 3 seconds because it sounds like it will do damage.

 

When I bring up the B2SServr interface and check plugins I can see its running R3 and using the globalconfig_b2sserver.xml that I made. Here is the logging from my last attempt, logging looks perfect and error free.

Please for the love of god help, I have been trying to fix this for 2 weeks.

 

 

2017.01.29 19:15:37.480 DirectOutput Logger initialized
2017.01.29 19:15:37.480 DirectOutput Version 0.9.5818.37242 as of 2015.12.06 20:41
2017.01.29 19:15:37.480 Global config loaded from: \\CHRIS-PINBALL\PINBALL\DIRECTOUTPUT\config\GlobalConfig_B2SServer.xml
2017.01.29 19:15:37.480 Loading Pinball parts
2017.01.29 19:15:37.480 Loading cabinet
2017.01.29 19:15:37.481 No cabinet config file loaded. Will use AutoConfig.
2017.01.29 19:15:37.481 Cabinet auto configuration started
2017.01.29 19:15:37.534 Detected and added PacLed64 Id 1 with name PacLed64 1
2017.01.29 19:15:37.535 Added LedwizEquivalent Nr. 20 with name PacLed64 1 Equivalent 1 for PacLed64 with Id 1
2017.01.29 19:15:37.549 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.01.29 19:15:37.550 Debug: Disposing LedWiz instance -01.
2017.01.29 19:15:37.550 Cabinet auto configuration finished
2017.01.29 19:15:37.550 Cabinet loaded
2017.01.29 19:15:37.550 Loading table config
2017.01.29 19:15:37.551 Warning: No table config file found. Will try to load config from LedControl file(s).
2017.01.29 19:15:37.551 Will try to load configs from DirectOutput.ini or LedControl.ini file(s) for RomName afm_113b
2017.01.29 19:15:37.557 Loading LedControl file \\CHRIS-PINBALL\PINBALL\DIRECTOUTPUT\config\directoutputconfig20.ini
2017.01.29 19:15:37.946 1 directoutputconfig.ini or ledcontrol.ini files loaded.
2017.01.29 19:15:37.947 Config for RomName afm_113b exists in LedControl data. Updating cabinet and config.
2017.01.29 19:15:37.969 Table config loading finished
2017.01.29 19:15:37.970 Pinball parts loaded
2017.01.29 19:15:37.970 Starting processes
2017.01.29 19:15:37.970 Initializing cabinet
2017.01.29 19:15:37.970 Debug: Initializing output controllers
2017.01.29 19:15:37.972 PacLed64 Id:1 initialized and updater thread started.
2017.01.29 19:15:37.972 Debug: Output controllers initialized
2017.01.29 19:15:37.975 Cabinet initialized
2017.01.29 19:15:37.980 Loading shape definition file: \\CHRIS-PINBALL\PINBALL\DIRECTOUTPUT\DirectOutputShapes.xml
2017.01.29 19:15:38.033 Framework initialized.
2017.01.29 19:15:38.033 Have fun!
2017.01.29 19:15:42.460 Finishing framework
2017.01.29 19:15:42.462 Finishing cabinet
2017.01.29 19:15:42.463 Debug: Finishing output controllers
2017.01.29 19:15:42.475 PacLed64 Id:1 finished and updater thread stopped.
2017.01.29 19:15:42.475 Debug: Output controllers finished
2017.01.29 19:15:42.475 Cabinet finished
2017.01.29 19:15:42.475 DirectOutput framework finished.
2017.01.29 19:15:42.475 Bye and thanks for using!

Edited by chrisseear, 29 January 2017 - 09:53 AM.

[arngrim]

not sure it will help but at least you don't have the latest dof r3, grab it from here

 

http://vpuniverse.co...-board-support/

[chrisseear]

Thanks for the effort, you are a champ for trying

 

I gave it a try, but no difference.

Mabey I will wipe the hard disk and reinstall everything.

I tried the pinballX plugin and that seems to work, but after a bit my outputs start to flash when they shouldn't, I am worried I have done damage to my hardware trying to get this going.

 

I really have tried everything and read everything, maybe I should just give up , the oonly thing I haven't tried is using a cabinet XML but I don't know how to make it hence this thread

[arngrim]

it's ok that's my job to support users and i don't like that someone is blocked to not be able to enjoy my work

 

that is strange
2017.01.29 19:15:37.549 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.01.29 19:15:37.550 Debug: Disposing LedWiz instance -01.

 

i have to check on my system what it says

 

so your ini is located there?

Loading LedControl file \\CHRIS-PINBALL\PINBALL\DIRECTOUTPUT\config\directoutputconfig20.ini

 

can you try a relative path?

[chrisseear]

My ini file are located at C:\Pinball\DirectOutput\Config , I don't know why the log uses the network name\\CHRIS-PINBALL

Its also the same place that I put the GlobalConfig_B2SServer.xml

Which I am sure is one of 3 default places to put them where they are located automatically.

 

When I look at the R2 log output it says

2017.01.29 12:31:50.814 Global config loaded from: C:\Pinball\DirectOutput\Config\GlobalConfig.xml

2017.01.29 12:31:50.911 Loading LedControl file C:\Pinball\DirectOutput\Config\directoutputconfig20.ini

 

I am still interested in trying a cabinet.xml if someone could take a look at the first post and help me define the toys properly, I did what I could with the information I could find, and guessed for the rest which I am sure is wrong and needs to be fixed.

 

Thankyou for still trying

 

I will try what you said ASAP, I am currently at work Nightshift (12Hrs), will test and post log when I get home

Edited by chrisseear, 30 January 2017 - 01:02 PM.

[arngrim]

with the globalconfigeditor you can define the location of your ini files etc

Sent from tapatalk

[arngrim]

try to put only one toy in the configtool like a flipper contactor to see if it changes something

Sent from tapatalk

[chrisseear]

Just got home from work and tested, log file looks normal and error free

 

2017.01.31 07:56:09.385 DirectOutput Logger initialized
2017.01.31 07:56:09.385 DirectOutput Version 0.9.6184.23828 as of 2016.12.06 13:14
2017.01.31 07:56:09.385 Global config loaded from: \\CHRIS-PINBALL\PINBALL\DIRECTOUTPUT\config\GlobalConfig_B2SServer.xml
2017.01.31 07:56:09.385 Loading Pinball parts
2017.01.31 07:56:09.385 Loading cabinet
2017.01.31 07:56:09.385 No cabinet config file loaded. Will use AutoConfig.
2017.01.31 07:56:09.386 Cabinet auto configuration started
2017.01.31 07:56:09.521 Detected and added PacLed64 Id 1 with name PacLed64 1
2017.01.31 07:56:09.522 Added LedwizEquivalent Nr. 20 with name PacLed64 1 Equivalent 1 for PacLed64 with Id 1
2017.01.31 07:56:09.531 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.01.31 07:56:09.532 Debug: Disposing LedWiz instance -01.
2017.01.31 07:56:09.532 Cabinet auto configuration finished
2017.01.31 07:56:09.532 Cabinet loaded
2017.01.31 07:56:09.532 Loading table config
2017.01.31 07:56:09.533 Warning: No table config file found. Will try to load config from LedControl file(s).
2017.01.31 07:56:09.533 Will try to load configs from DirectOutput.ini or LedControl.ini file(s) for RomName afm_113b
2017.01.31 07:56:09.536 Loading LedControl file C:\Pinball\DirectOutput\Config\directoutputconfig20.ini
2017.01.31 07:56:09.539 Min DOF Version is 0.8 for file directoutputconfig20.ini
2017.01.31 07:56:09.603 1 directoutputconfig.ini or ledcontrol.ini files loaded.
2017.01.31 07:56:09.604 Config for RomName afm_113b exists in LedControl data. Updating cabinet and config.
2017.01.31 07:56:09.622 Table config loading finished
2017.01.31 07:56:09.622 Pinball parts loaded
2017.01.31 07:56:09.622 Starting processes
2017.01.31 07:56:09.622 Initializing cabinet
2017.01.31 07:56:09.622 Debug: Initializing output controllers
2017.01.31 07:56:09.624 PacLed64 Id:1 initialized and updater thread started.
2017.01.31 07:56:09.624 Debug: Output controllers initialized
2017.01.31 07:56:09.628 Cabinet initialized
2017.01.31 07:56:09.633 Loading shape definition file: \\CHRIS-PINBALL\PINBALL\DIRECTOUTPUT\DirectOutputShapes.xml
2017.01.31 07:56:09.681 Framework initialized.
2017.01.31 07:56:09.681 Have fun!
2017.01.31 08:01:38.971 Finishing framework
2017.01.31 08:01:38.972 Finishing cabinet
2017.01.31 08:01:38.973 Debug: Finishing output controllers
2017.01.31 08:01:39.985 PacLed64 Id:1 finished and updater thread stopped.
2017.01.31 08:01:39.985 Debug: Output controllers finished
2017.01.31 08:01:39.985 Cabinet finished
2017.01.31 08:01:39.985 DirectOutput framework finished.
2017.01.31 08:01:39.985 Bye and thanks for using!

 

There was no change, random stuff firing off for no reason.

​I then did another test with new configs with flippers only configured, and still I heard replay knocker go off and some solendoids.
​I added 5 flasherRGB and strobe and it same thing happened, random stuff firing off that isn't even configured.

 

None of these problems happen when using DOFR2, it always worked perfectly since the first day I built it. Just to make sure I used the same configs on R2 and none of these problems happened.

​Is DOFR3 using a different Pacled64 driver ?

 

I tried replacing the Pacdrive.dll with the R2 version but it didn't help.

 

Thanks again Arngrim
 

Edited by chrisseear, 30 January 2017 - 09:32 PM.

[chrisseear]

Been reading the internet about this and it looks like i am not the only person having this problem

http://vpuniverse.co...certain-tables/

Sorry for linking to the other forum not sure if its allowed.

At the end of the  thread they suggest that the USB interface is to fast exposing a problem in R3 (which runs faster than R2 apparently) and using a shitty USB2.0 hub might slow it down enough to mask the underlying problem (what ever that is).

 

I cant test atm though because I had a brain fart and tried to upgrade the Pacled64 firmware. I downloaded the application from Ultimarc clicked the upgrade firmware option which appears to have blanked it. It now detects in device manager as a “U-Hid Upgrade Firmware detected” for which there was a driver supplied with the application. I put the driver in and can now load a firmware, Problem is I haven't got a firmware. I have emailed Andy from Ultimarc and hoping to hear back from him, once that happens/if it happens I will do more testing.

 

Mabey this thread should have been called "DOFR3 and Pacled64 problems"

[chrisseear]

Andy from Ultimarc responded

 

Chris, 

"It should revert to normal operation if you unplug and reconnect the USB cable. 

I have attached the firmware. Its very likely the same as you already had, as there have not been any changes for 4-5 years. 

Andy"

​And sure enough Pacled64 back up and running, (I powered the cab down and the power point but the didn't fix it, strange)

 

​After it was running again I did some testing, I had the Pacled64 plugged into a USB 3 port, I moved it to a USB 2 port but it didn't help, still random outputs firing off that are not even configured. Even using the PinballX plugin with only the 5RGB flasher and flippers configured still fire random shit off.

​Don't know if its relevant but the PC I am using is pretty modern and fast. Gigabyte Z170MX/i5./16gig ram/SSD/Win 10

 

​On the plus side, I went and tested DOFlinx out with future pinball and it looks fantastic (This was the whole reason I started trying to upgrade to R3), but unfortunately I couldn't play for long because same thing happened, random outputs firing and I am concerned it might do damage.

 

​I don't know what to do now ? except maybe wait for R3 to get improved. I would really love to get everything working, I get very envious when I watch YouTube of other peoples cabs with no problems. If I ever solve this problem I will add ledstrips in also.

[Thalamus]

I'm curious, reading your dof struggles as I'm a dof user that don't actually know what I'm doing but seems to be lucky not having any issues either. What about creating c:\directoutput and get the latest beta 3 version and not overwrite from anything old. So, a new folder location and new software. Delete the old shortcut from "tables\plugins" folder and create a new one pointing to the new location.

 

Only add the two xml files from configtool - preferably by one toy configured as Arngrim said. Sorry - you might have tried this already, but, if not ...

 

I see that you tried changing usb ports - good, do you by any chance have a usb hub laying around, then I would try that as well.

 

Since I'm not 100% sure I'm doing everything correctly myself, I'm just grabbing around for things I might have done being in your situation.

[chrisseear]

Thanks for the suggestion, but I am gald to tell you that its going great now. I had to buy a shitty USB 2.0 HUB, plug that into the USB 3.0 port on the PC, and then plug the pacled64 into the hub. Other people have had this issue it turns out and luckily they made a thread like this one that I eventually stumbled across. My pinball PC is pretty modern and fast Z170/i5/16gigram/Win10

 

R2 works perfectly, R3 does not unless I use a Hub, only software gurus can tell you why.

 

I am happily playing with Doflinx now, and its working perfectly. The new (Doflinx) Future Pinball tables are fantastic

I am also using the PinballX plugin which makes the frontend even better.

 

Now that everything is working perfect, I will order some led strips and Kill my-self trying to get them going also, I am sure you will see me begging for help again soon.

 

Thanks again to Arngrim for taking the time to try and help.

[arngrim]

glad it works and to know what is the solution, it will help for the others too

Sent from tapatalk

[MajorFrenchy]

Hey guys, i have only 4 solenoids in my cab , 

everything works well in future pinball on dof tables.

in visual pinball my 4 solenoids work but only on assigned ports, fipper left right and slingshot left right.

how do i assign the same solenoids for different actions,  i.e rear , middle and middle left bumpers.

 

thanks

 

 

**************************

I found my answer and here is what i did. 

 

Even if i only have 4 solenoids using port 1-2-3-4 on a sainsmart board that has 8 ports  in Dofconfigtool i assign all 8 ports 

 

 Port 1 slingshot left

Port 2 Slingshot right

Port 3 flipper left

Port 4 flipperright

port 5 8 bumper left

port 6 8 bumper center

port 7 8 bumper back

port 8 8 Bumper Right

 

the only assigned ports are port 1 to 4 but i want to have the bumper left use the same solenoid as the left slingshot

 

So i my Cabinet.xml i will change the following :

 

-<LedWizEquivalentOutput>

 

<OutputName>Sainsmart 2.05</OutputName>

 

<LedWizEquivalentOutputNumber>5</LedWizEquivalentOutputNumber>

 

</LedWizEquivalentOutput>\

 

For this: 

-<LedWizEquivalentOutput>

 

<OutputName>Sainsmart 2.01</OutputName>

 

<LedWizEquivalentOutputNumber>5</LedWizEquivalentOutputNumber>

 

</LedWizEquivalentOutput>

 

 

Which means that My Real port 2.01 on my Sainsmart is using port 5 assignment ( port 5 8 bumper left in the DOF config) . 

 

Thank you for helping myself ( lol, ) hope it helps someone

Edited by MajorFrenchy, 13 December 2018 - 11:30 PM.

[gtxjoe]

The DOF configtool supports combining toys

Log in and go to Combine Toys
Select Slingshot Left and 8 Bumper Left
Click Add to create Combo1
Repeat for other toys

Use Combo1-4 in you configuration