41 replies to this topic

[arngrim]

swisslizard is the best person to answer

[eldiego]

What can i do? because the dof r2 not recognize my clone ledwiz automaticly

[Swisslizard]

Hi

 

To be able to help some more information about your setup is needed. So please post more details.

 

Did you follow the installation instructions (http://pinball.weile...allation.html)?

 

Does the B2S.Server recognize DOF?

 

Create a global config file with logging enabled (http://pinball.weile...balconfig2.html). Like that you can see if DOF is getting activated, if it finds the config files and what hardware has been recognized resp. configured.

[eldiego]

Thanks swisslizard

tomorrow I will review that you ask me and I'll answer as soon as possible. thank you very much for your help.

[Outhere]

Doesn't work with  LED Blinky

[javier1515]

I have the same ledwiz clone buy eldiego and the problem is that it works with ledblinky but not with DOF.

Possibly it is a configuration problem, I am not clear as to create the file cabinet and file directoutputconfig with  buttons Led  and Knocker.

 

My directory is C: \ Visual Pinball \ Tables \ plugin \ directOutput \ config that way right.

 

The B2S backglass Server has marked the plugins option.

 

Here at the end of the world we are slow to understand 

[Swisslizard]

If the ledwiz clone does not work with DOF, then the clone is not fully compatible with a org ledwiz.

 

There are two drivers for the org ledwiz. The old legacy vbs solution used a driver which is a COM object. This drivers has quite a few downsides (most important it is slower). The other driver which is included in the LEDWIZ SDK allows for somewhat higher speed and is easier to support from DOFs architecture. Therefore ledwiz closes which should operate with DOF. have to be compatible with the drivers in the SDK. COmpatibilty with the COM object is irrelevant.

 

If you only have a ledwiz, you dont need a cabinet config file. All you have to do is to install DOF (be sure the follow the install instrcutions closely) and to download config files for your setup from the config tool.

[javier1515]

ok, I will try to do what you say.

 

Thanks. 

[eldiego]

Hi

 

To be able to help some more information about your setup is needed. So please post more details.

 

Did you follow the installation instructions (http://pinball.weile...allation.html)?

 

Yes, i do again recently

 

Does the B2S.Server recognize DOF?

 

Yes, active

 

Create a global config file with logging enabled (http://pinball.weile...balconfig2.html). Like that you can see if DOF is getting activated, if it finds the config files and what hardware has been recognized resp. configured.

 

i do and nothing, my cabinet config is empty, y try to add:

 

<OutputControllers>

<LedWiz>

<Name>LedWiz 01</Name>

<Number>1</Number>

</LedWiz>

</OutputControllers>

 

but in directoutputconfigtester continue empty (the output controller)

when you say "and to download config files for your setup from the config tool." 

you reffer to directoutputconfig.ini?

[ROFElectronics]

Hi,

 

for the ones using the LEDWiz clone made by us:

 

we create a new DLL, but compatible with the LEDWiz SDK. Still, we made our own implementation of each dll function call, because we created a better product. For example, in the original LEDWiz hardware / dll, setting the outputs values takes 4 control report writings ( 4 chunks of 8 bytes each one). Our dll made it in only one report (32 bytes long). Also, our product haves a higher refresh rate ( aprox 244 Hz = no flickering during video recording) and we also allow LEDWiz ID changing at any time with a simple App. we made.

 

So, replacing the original dlls with the one's provided by us should be enough for any sofware (LEDBlinky, DOF, etc) to see our product and control it as an original LEDWiz device.

 

Cheers.

Edited by ROFElectronics, 28 December 2014 - 06:40 PM.

[nos2k]

Hey

 

First of all, thanks for the hard work - its very appreciated.

 

I had a VP machine i built myself from ground up - unfortunately too many errors, not enough planning made me get rid of it, as it ended up being functional....but not very pretty.

 

I then forgot all about it, until i bought a mini vp cabinet from a friend; this time im hooked again. All that was wrong with mine, is right with this, so i want to expand it.

 

However, when i did this the last time, i was using ledcontrol (i think?) and i had 7 contactors. 3 bumpers, 2 slings, and 2 flippers. This cabinet however works great, and has 5 contactors - theyre setup for 3 bumpers, and 2 slingshots. 

 

Now, after studying the homepage of directoutput, and reading around, im exactly no where nearer figuring out if theres an easy way for me to map the two slingshot contactors, so they will double as flipper contactors as well, across all tables.

 

Can you please guide me a bit here if this can be done?

 

Thank you!

[arngrim]

i'm not aware that something like that can be achieved by configuring the cabinet.xml of dof, but that is something i plan to add in the configtool, combining multiple DOF toy to one controller output.

once i have cleaned up the list of tables to do, i want to attack this, which won't be that easy to develop, that's why i can't focus on it now

[Slydog43]

when did tablemappings.xml get added to the config tool?

[nos2k]

i'm not aware that something like that can be achieved by configuring the cabinet.xml of dof, but that is something i plan to add in the configtool, combining multiple DOF toy to one controller output.

once i have cleaned up the list of tables to do, i want to attack this, which won't be that easy to develop, that's why i can't focus on it now

 

Hey

 

Thanks for the swift reply. Unfortunate that this cant be solved easily, but hey - atleast now i know that its not something i should mess with. However, if i understand correctly, and not having played with this myself before (direct output), if i buy two more contactors, and hook them up correctly, they will autodetect, and be used correctly - right?

[gtxjoe]

Doesn't the LEDwiz just provide a ground path for the contactor?

 

 In DOF, for example, if you had assigned LEDwiz port 1 as the Left Flipper and LEDwiz port 10 as the Left Sling.  Couldn't you just connect both ports 1 and 10 to the - side of the single contactor?  So if either the DOF left flipper port or DOF left sling gets triggered the contactor would fire...

 

I certainly haven't tried this so do at your own risk but maybe someone else can comment on it

 

 

DOF does not autodetect what you have connected to the LEDwiz.  You have to login to the DOF Config website and tell DOF what you have connected to the LEDwiz but it's an easy to setup pull down menu

[arngrim]

the tablemappings is something i prepared for swisslizard and DOF for Pinballx, it contains all the tables in the configtool with their rom suffixes.

 

it is personnalized with your rom choice, for certain tables, you can choose your rom, the tablemappings displays the rom that you have choosen in that case

 

It was only in dev env, and i sent it by mistake to the prod configtool, it doesn't harm, and can even be useful if you want to have an idea of the list of your roms

[alandee]

Firstly, thanks for all the hard work you guys do, I don't know how you do most of it, but it's awesome !

Now I've got the crawling out the way .. like an idiot I've now got 2 x ultimarc pacdrives .. the dof config tool only lets me config one of them .. is there a hack by hand way around getting the rest of my solenoids on a second pacdrive configured and working ?

At the very worst I can steal the ultimarc pacled64 from my mame and use that for the rgb's and then just one pacdrive for the bumpy things, but I'd prefer not to .. as everything is wired, configured and working for the first one !

Any thoughts ?

 

Cheers,

al.

Edited by alandee, 31 October 2016 - 02:30 AM.

[arngrim]

i see you have only one pacled defined in your 'my account' tab in the configtool, choose 2, save and you can fill 2 pacleds

[alandee]

Yeah, ta, but .. Pac Drive I have 2 of that I wanted to use, the Pac LED I didn't want to .. but under account Pacdrive it's 0 or 1 .. ?

Cheers,

al.

[arngrim]

ah ok, i misread

 

pacdrive is really not recommended as DOF Controller, it is supported because it was easy to add, but if i recall, pacdrive doesn't allow PWM, means the toys won't work well for RGB toys, you will get red, green, blue, and an ON OFF combination of these, so 2*2*2 -1 colors, while a ledwiz, you can have 48*48*48 -1 colors, and a pacled, you have 255*255*255 -1 colors (-1 at least to omit the black color)

 

and DOF only supports one pacdrive natively:

 

http://directoutput....timarc_pacdrive