46 replies to this topic

[Swisslizard]

Ok, please try a SS table, e.g Medival Madness. If that doesnt work either let me have the log again.

Are you sure your setup works hardware wise? Try to control the output of the Packed using the application which belongs to the Pacled.

[Steve G]

Sorry I have just edited my previous post before I saw yours.

I can get the hardware (PACLED64) to work with your DirectOutputConfigTester as well using the software which belongs to the controller.

[Steve G]

Ok, I am getting somewhere, I did a little reading on another forum and saw that I had the problem of the "Plugin settings" icon in the "B2S Backglass Server" greyed out.

 

I got that solved and now I have lights when I launch a table, but as soon as I enter the credits and hit the start button, the RGB flipper lights go out.

 

When I click on the "Plugin settings" icon and then show the DirectOutput frontend window, it says in Global configuration File: <no config file found>.

 

Lastly, the "DirectOutput.log" only updates when I use the "DirectOutputConfigTester".

[lizard]

I had this problem with the rgb flippers going out to after switching to a pacled64. I think only one other person said they had the same thing so no one was able to provide a solution. I pulled the pacled and put the ledwiz back in and all was good again. I then put the pacled64 in a poker machine cabinet i am building and it did the same thing with some outputs dropping others out when turned on. They would all work individually fine but when activated together strange things would happen. The more i played with it the worse it got. The pacled now sits in the cupboard where i have no problems with it. Maybe there is a fault with some of these boards. I will be interested to see if you get that sorted.

 

Cheers

[Swisslizard]

@Steve:

This sounds a bit familiar. Other users had similar problems earlier. The fact that there is no DOF log when using VP, most likely indicates that DOF is no called by the B2S.Server.

 

Please double check that you only have 1 installation of the B2S.Server on your cab and that the registraction of the B2S.Server points to that installation.

B2S.Server is a COM-object. References to those objects are resolved by a object name and not by the path where the B2S.Server is installed. This means that even if you have the B2S.Server in the table directory it is possible that another instance of the B2S.Server is called by VP when the B2S.Server object is instanciated.

[blashyrk]

Hope I don't encounter this problem with my pacled64

[Swisslizard]

I'm almost 100% certain that this is not a pacled problem.Otherwise the pacled wouldnt work with the testing application either.

[blashyrk]

Let's hope so

[Steve G]

Well yes I did have multiple installation of the B2S.Server as I had separate table folders for the different versions of VP.

I have now got everything in one "Tables" folder, but still have the same problem. 

[Swisslizard]

Can you see DOF in the list of plugins if you open the settings of the B2S.Server?
Can open the DOF frontend from there?
Are the logs enabled in the global config? Are logs generated when you launch a table?
Try all this again please. Just to make sure your B2S.Server does really call DOF.

[Steve G]

The DOF is listed in the settings of B2S.Server - see attached.

But in the DOF frontend "<no global config found>" - see attached.

The logs are enabled in the Global Config, but it does not update when a table is launched - it only updates when I use the testing application.

Attached Files

•  mmbg.jpg   148.56KB   4 downloads
•  mmpf.jpg   235.32KB   4 downloads

[Swisslizard]

Well if the global config is not loaded the log doesnt get activated either.

Most likely the global config is in the wrong directory. Check the following page for possible locations of that file: http://pinball.weile...balconfig2.html

In my setup the global config is in the config subdir within the directory where DOF is installed (that works for sure), but as you can see in the docu you have other options as well.

 

When you look at the DOF frontend you can also see, that no table config gets loaded. I guess the config ini files are also in a wrong directory. For the ini files there are also several places where they can be stored: http://pinball.weile...les_directories

I personally recommend to put the ini files either into the dir you have specified in the global config (use the global config editor for this) or into the directory where the global config is stored. In my setup the are in the config subdir of the install dir and the global config which resides in the same dir does also have a pointer to the ini files.

[Steve G]

I am pretty sure I have everything as it should be, I have attached pictures showing the main DOF folder, the Config subfolder and the shortcut within the tables-plugins folder.

 

Attached Files

•  DOF main.jpg   97.37KB   6 downloads
•  DOF shortcut.jpg   21.66KB   4 downloads
•  DOF sub.jpg   35.64KB   3 downloads

[Swisslizard]

Rename the global config file to GlobalConfig_B2SServer.xml (as specified in the docu). The is the name DOF is looking for.

 

If that doesnt solve your problem, put the ini file into the dof config folder (IMHO the best place for it anyway) and adjust the path in the gloabal config accordingly.

[Steve G]

Ok I did what you suggested and now the frontend is seeing the "GlobalConfig_B2SServer.xml" and the "DirectOutput.log" is getting updated - but I still have problems.

 

If I launch "Attack From Mars".

 

Flippers light as they should also Coin and Exit.

I enter the coins and then the Start light starts flashing as it should - then I start and the Start light goes out and the Launch Ball light starts flashing.

But then as soon as I launch the ball all the lights go out :-(

 

[Swisslizard]

Well and whats in the log now?

 

I also dont understand the thing about lights which go off. When are they turned on before they are turned off?

DOF does alsoway turn off all output during the initialization phase when it starts. Only after that has been done, the lights which are always on (typically buttons, coin slots and the like) are turned on again.

[Steve G]

I will email you the log.

 

To explain exactly what happens:

 

When the table is launched (in this case Medieval Madness) the RGB flipper buttons light up Red.

The Coin button and Exit button also light up.

I enter the credits and then the Start button begins to flash, once I hit the Start button that light goes out and so does the Exit button.

When the ball enters the table, the Launch Ball button begins to flash - as soon as the Launch Ball button is pressed, it's light goes out and also both RGB flipper buttons go out to.

This leaves just the Coin Button lit.

The Launch Ball button does flash, as it should each time a new ball enters the table.

Edited by Steve G, 16 November 2015 - 08:47 AM.

[lizard]

That is exactly what was happening to me on attack from mars and medieval madness as well. All my outputs turned off and on one at a time perfectly with the pacled software or ledblinky but didn't like some combinations. Have you tried swapping your ports to see if it makes a difference. I spent about 3 full days testing and trying things before i gave in and swapped back to the ledwiz. What OS are you running, both machines i tried the pacled in were w7x64. 

[Steve G]

Hi lizard,

 

I have not tried swapping any ports yet, but I will do so tonight.

My PC is running Windows 10.

[Steve G]

Ok, so I decided to try the r3 beta and it works - well I think it is anyway?

No lights are going out when they are not supposed to although the Start and Launch Ball lights don't really flash any longer - they pulse very quickly so it almost looks like they are just continuously on.

When I hit the Start button it now slowly dims until it's off and the same happens with the Launch Ball - is this how it is supposed to be?