975 replies to this topic

[Santos76]

Ok,

thank´s for watching.

And a great thanks´s for the amazing Project.

 

 

Sascha

 

[hauntfreaks]

MJR, I'm about to buy a LEDwiz.... (this would be the first one in my rig)

it says to Please Choose: Device Number:

what # would i choose while using the pinscape setup as well?

[mjr]

MJR, I'm about to buy a LEDwiz.... (this would be the first one in my rig)

it says to Please Choose: Device Number:

what # would i choose while using the pinscape setup as well?

 

Since you can change the Pinscape LedWiz assignment on the fly, you can choose any unit# for the real LedWiz and just move the Pinscape unit so that it doesn't collide.

 

That said, I'd go with the defaults for all real LedWiz'es - #1 for the first unit in your system, #2 for your second, etc.  That's the numbering that DOF expects, so it'll make that setup easiest.

 

And then just leave the Pinscape unit on LedWiz #8 (the Pinscape default), since that won't collide with the real LedWiz'es on the lower numbers.

[hauntfreaks]

thank you Sir for the fast response as always!!..... I have all my contactors.... LEDwiz soon.... i'm only like 5 years behind on DOF...lol

[mjr]

there it´s a problem with the configuratoin.

When i select the  CCD Sensor TSL 1410R, all is good.

But i select the TSL 1412R, blink the led red/pink.

Can you test it, or i do somthing wrong.

 

I just tried it, and it reproduces for me too.  The red/pink diagnostic display means that the controller is out of memory.  The TSL1412R has more pixels, so it needs more memory for its pixel buffers.  The software has been pushing the memory limits of the device for a while now, but I guess I hadn't tested the TSL1412R configuration in a while.

 

I'll have to find some more unnecessary bytes to squeeze out to get it to fit.  I'll let you know when I have an update for you.

 

Okay, it should be fixed now.  I just posted a new version (build timestamp 2016-05-12-0524) that makes more memory available.  I've tested it with the most memory-hungry configuration I can come up with, and it actually works now - TSL1412R, all expansion board options enabled, and all 128 output ports populated.  That configuration leaves about 1.5K of memory free now, so there's still room to squeeze in a few more features.

 

If your KL25Z is stuck in "out of memory" mode with the fast red/purple flashing, you can reset it by doing a new firmware install, as though it's a new unit.  Run the config tool and click the "Set up new KL25Z" button on the front page.  On the next page, click "skip this step" to skip the boot loader update, as you've already done this.  Then just follow the usual procedure to install the firmware and configure settings.  If you have Auto Download enabled, the new firmware update should appear in the list shortly after you run the tool.

 

Let me know how it goes when you try the update.

[Santos76]

Wow, what a fast Support.

Great THANK'S

Sascha

[Santos76]

Mjr ,
I have a question for the wiring of the plunger sensor .
which is correct.

 

1st.

In the Config-Tool is A01 and A02 briged and five cables are wired.     http://www.directupl...9fptlxt_jpg.htm

 

2nd.

In the schematic of the Mainboard is A01 and A02 separately and seven cables are wired.     http://www.directupl...cynvdhd_jpg.htm

 

3rd.

Do the bridges as in version one elsewhere be prepared ?       http://www.directupl...lbo2467_jpg.htm

 

 

Greeting Sascha

 

[mjr]

I have a question for the wiring of the plunger sensor .
which is correct.

 

1st.

In the Config-Tool is A01 and A02 briged and five cables are wired.     http://www.directupl...9fptlxt_jpg.htm

 

2nd.

In the schematic of the Mainboard is A01 and A02 separately and seven cables are wired.     http://www.directupl...cynvdhd_jpg.htm

 

3rd.

Do the bridges as in version one elsewhere be prepared ?       http://www.directupl...lbo2467_jpg.htm

 

Version 1 - AO1 and AO2 connected together - is the one to use.

 

The expansion boards provide the *option* for separate wiring for AO1 and AO2 into the microcontroller, but the software doesn't currently support that configuration.  And it probably never will, because it turns out there's no advantage to it.  I added the extra connection on the expansion boards because I wanted to leave the option open for a slightly different way of reading the sensor that I thought might be faster using the separate connections.  However, I've now investigated that option, and it turns out that the old single-input method is the best one after all with the KL25Z.

 

In case you want the technical details, here's what's going on.  The TSL1410R/1412R devices are internally arranged into two physical sensors, arranged end-to-end inside the case.  AO1 is the Analog Output from the first sensor, AO2 is the Analog Output from the second sensor.  This design allows applications to read the two sensor halves in parallel - i.e., at the same time.  Applications can also read the two halves serially - that is, you read all of the pixels from the first half-sensor, then you read all of the pixels from the second half-sensor.  The Pinscape software has always used the serial mode.  Parallel mode has the advantage *in principle* that you can read the sensor twice as fast.  Most of the time it takes to read the sensor is spent waiting for the ADC (Analog-to-Digital Converter) on the microcontroller to sample the voltage level and turn it into a digital reading.  If you can read two pixels at the same time, you can speed things up by doing two separate ADC samples at the same time - you get two pixels for each ADC delay rather than just one.  That's why I wanted to investigate this to see if I could get that promised speed-up.  Upon closer examination, though, it turns out that you can't use this mode effectively with the KL25Z.  The KL25Z's on-board ADC hardware is limited to one sample at a time.  Even if you provide the two separate physical wire connections (to AO1 and AO2), the KL25Z ADC will still have to wait for each pixel individually.  But wait, it gets even more interesting.  In addition to the conversion time, there's "setup time" required to program the ADC to read each pixel.  If you want the ADC to switch back and forth between two inputs, you get hit with that extra setup time for each pixel.  So much to my surprise, the fastest way to read the sensor with the KL25Z is one pixel at a time, on one input wire - that way you get the fastest ADC time by paying the setup time once up front and having the ADC crank through all of the pixels on the same wire.  I came up with some fiendish tricks with the DMA controller that get the pixel read time down to a little under 2us (microseconds) per sample, which is close to the theoretical maximum speed for the ADC quoted in the KL25Z data sheet.  Parallel mode can't take advantage of those tricks, either, so the effective pixel read time goes to about 6us.  It's hugely counterintuitive on the surface that it should be faster to run a loop with 1280 steps rather than 640 steps, but the 640-step loop takes 6 times as long per step, so it ends up being 3 times faster to run the loop that's twice as long!

 

The one remaining possibility is that we could conceivably add an *external* ADC chip that's capable of taking two samples at the same time.  That would have to be connected between the sensor and the KL25Z; the KL25Z wouldn't take the samples itself, but would program the external ADC chip to do that work and read the data back via an I2C connection or the like.  Such chips exist, so I'm pretty sure this approach could be made to work, and with the right chip it could get right up to the theoretical maximum read speed for the sensor, which is (in parallel mode) about 4x faster than what we're getting in the latest software.  I'm slightly tempted to look into it because it triggers my OCD to know that a better way exists that I'm not using... but for the plunger application, there's really no reason to try to make it faster.  The new software's serial read speed is already so fast that it can see the plunger release motion in detail without motion blur.  Speeding it up further would be cool from an engineering perspective, but I don't think it would do anything to make the plunger operation better.

 

So anyway, you can just stick with the combined AO1/AO2 wiring as in the Build Guide.

Edited by mjr, 12 May 2016 - 05:23 PM.

[sliderpoint]

Can someone please verify that the ZB Launch ball is functioning in the latest version. 

 

I have had to re-install some things in the last week, so it's very possible it's me, but I just want to verify before I go digging through my DOF and b2s setup to see why mine does not seem to be functioning any longer.

 

Thanks

-Mike

Edited by sliderpoint, 13 May 2016 - 12:06 AM.

[Santos76]

Hi Mjr,

thank you for the detailed description.

 

I have wired the Sensor.

Here is the Picture.  http://www.directupl...87v9kyy_jpg.htm

 

 

 1.   Vpp  

 2.   SI1

 3.   HOLD1

 4.   CLK1

 5.   GND

 6.   AO1

 7.   SO1

 8.   SI2

 9.   HOLD2

10.  CLK2

11.  SO2

12.  AO2

13.  VDD

 

My wiring:

1+5     to pin 6

2+3+9 to pin 8

4+10   to pin 3

6+12   to pin 1

7+8     bridged

13       to pin 5

 

But i can´t calibrate the Sensor.

What am I doing wrong.

 

Sascha

Edited by Santos76, 13 May 2016 - 01:54 AM.

[Santos76]

Oh, I have seen taht i have twisted the sides of the Sensor.

 

I sign up again later.

 

Sascha

[Santos76]

So, everything changed, and it works.

I got lucky, that the Sensor is not broken.

 

 

 

Sascha

[mjr]

So, everything changed, and it works.

I got lucky, that the Sensor is not broken.

 

Congrats!  Glad to hear it's working (and very glad that you don't have a dead sensor!).

 

 

Can someone please verify that the ZB Launch ball is functioning in the latest version. 

 

I have had to re-install some things in the last week, so it's very possible it's me, but I just want to verify before I go digging through my DOF and b2s setup to see why mine does not seem to be functioning any longer.

 

I just tried it on the latest posted rev, and it looks like it's working fine for me.

 

Before going to the DOF config, you might want to double-check on the Settings page that everything in the ZB Launch section is set the way you used to have it, because the defaults are all different now.  ZB Launch isn't even enabled by default, and it'll send an Enter key by default.  The old setup always used a joystick button, so you probably have your VP key settings configured that way.  You can just set it back to the same joystick button in the Settings page rather than changing VP.

[shadowshd]

Hi MJR,

 

Thanks for this great update

 

I have the same problem as Sliderpoint with the ZB Launch Ball function.

 

In v1 Pinscape firmware, I used to use ZBLaunchBallPort=32 and LaunchBallButton=9.

My physical Launch Ball button is wired as joystick button #9.

 

My contactors are wired to ports #11 to #20 via a relay board on my KL, and didn't work anymore with v2.

I added a Pinscape device and deleted my KL25Z device in my DOF account, and my contactors are working again.

 

But I can't find what to do to re-enable ZB Launch Ball.

 

I've set Button 9 in v2 settings, with port 32, I've set in my DOF's Pinscape port 32 as ZB Launch Button, but still doesn't work.

 

Thank you for any tip or step I've missed in the run

 

++

[mjr]

Hi MJR,

 

Thanks for this great update

 

I have the same problem as Sliderpoint with the ZB Launch Ball function.

 

In v1 Pinscape firmware, I used to use ZBLaunchBallPort=32 and LaunchBallButton=9.

My physical Launch Ball button is wired as joystick button #9.

 

My contactors are wired to ports #11 to #20 via a relay board on my KL, and didn't work anymore with v2.

I added a Pinscape device and deleted my KL25Z device in my DOF account, and my contactors are working again.

 

But I can't find what to do to re-enable ZB Launch Ball.

 

I've set Button 9 in v2 settings, with port 32, I've set in my DOF's Pinscape port 32 as ZB Launch Button, but still doesn't work.

 

Thank you for any tip or step I've missed in the run

 

Did you enable it in the Config Tool?  On the Settings page, scroll down to the "ZB Launch Ball Setup" section (there's a red "Launch Ball" button picture in the right margin).  Tick the Enabled box.  That'll show the three settings you have to configure for it - the port number, key, and push distance.

 

It occurs to me that there's one other thing you might need to double-check.  The old setup had the automatic 32 ports of the LedWiz.  The new setup has the exact number of ports you configure, which by default is only 22.  That's really the same as the old setup in terms of how many are actually wired, but the new software tells DOF the number of allocated ports rather than just reporting the fixed 32 of the LedWiz.  

 

So what you might need to do is add a "virtual" port for the ZB control port.  Go down to the Output Port section at the bottom of the settings page and click the "+" button at the very bottom of the table.  That'll add a blank row labeled "Virtual".  That's not connected to anything physical, but it makes it a valid output number in DOF.  If you click on the row, it'll bring up a port selector page, and you can click "ZB Launch Port" to make it the ZB port.

 

If you're using the default set of 22 physically wired outputs, that'll make your ZB port #23.  You should update your DOF config to make that match.  Or, if it's a hassle to change the DOF config, you can just add more virtual ports until you have a port #32, and keep that as your ZB port.

 

Let me know if this helps!

[Santos76]

Hi Mjr,

do you have a DirectOutput Version for the Pinscape-Controller ?

When i install the DirectOutput_R3Beta2_Build_5818.37242, PinballX don´t start.

 

 

I've already opened a thread. http://www.vpforums....756#entry343715

 

Can anyone help me.

 

 

Sascha

[shadowshd]

I appreciate your precious help and advices MJR, I will try to add a virtual port in my settings tomorrow and will feedback here.

ZB Launch Ball is enabled in the settings, and it will be no hassle to change my DOF config

By the way, is it relevant to remove the KL25Z in DOF and "replace" it with Pinscape device, or can we let them "live" together ?

And another question, I dunno if you can answer it, but with v2, LEDBlinky's SimpleLedTest.exe doesn't work anymore.
I mean with v1, we can test the toys wired to the KL (or to a Ledwiz, as SimpleLedTest sees the KL as Ledwiz-8) by an on/off and intensity function, i.e. if I activate port #11, then my first contactor will switch on. No more with v2.

It's not as annoying as it seems, but when you build a cab and need to test your toys, SimpleLedTest is very useful

Have a good night

++

[mjr]

Hi Mjr,

do you have a DirectOutput Version for the Pinscape-Controller ?

When i install the DirectOutput_R3Beta2_Build_5818.37242, PinballX don´t start.

 

I think that one should be working.

 

One test you might want to try: go into the Pinscape setup tool and set all of your buttons (including the ZB Launch Ball setup if you use that) to use JOYSTICK buttons, not keyboard keys.  There was one version of the Pinscape code for DOF that didn't work properly if the KL25Z presented a keyboard interface to Windows.  I sent swisslizard the fixes for that, but I'm not absolutely certain he released a new version with the fixes.  You should be able to test that by turning off all of the keyboard keys - if it works, that must be what's going on.

 

 

By the way, is it relevant to remove the KL25Z in DOF and "replace" it with Pinscape device, or can we let them "live" together ?

 

Probably best to have one or the other, not both.  They're basically different ways of accessing the same interface, so it could create some confusion in DOF if it's trying to access both at the same time.  And there's no advantage to having both.  The "Pinscape" interface is a pure superset of the "KL25Z" interface, so there's nothing you're losing by turning off the KL25Z interface.

 

And another question, I dunno if you can answer it, but with v2, LEDBlinky's SimpleLedTest.exe doesn't work anymore.
I mean with v1, we can test the toys wired to the KL (or to a Ledwiz, as SimpleLedTest sees the KL as Ledwiz-8) by an on/off and intensity function, i.e. if I activate port #11, then my first contactor will switch on. No more with v2.

 

I'm not sure why it shouldn't work - the LedWiz interface is still fully supported.  (More completely than it was in V1, in fact - it supports all of the LedWiz blinking modes now, which it didn't in V1.)  What did you select for the "USB Identification" in the Pinscape config tool settings page?  If you selected "LedWiz Unit 8", it should work exactly like before.  That's assuming that you didn't change the port numbering in the Output Port section, of course, but the defaults are the same as they used to be, so if you didn't change anything, the contactor on port #11 should still be on port #11.

 

I'm going to add an output port tester directly in the config tool, by the way, but that's a future feature.

Edited by mjr, 18 May 2016 - 10:37 PM.

[shadowshd]

Hi MJR,

 

OK, adding a virtual #23 port in settings and configuring DOF to match did the trick 

 

And SimpleLedTest is working again now, but yesterday it won't   (I surely had a wrong setting somewhere - or I should have reboot my cab after changing them) .

 

For information, I first updated manually my KL to v2 by the old way of doing it (MBed compile) - you know, old habits die hard -

Then -in the hurry of testing, I didn't took the time to check my settings  - all my Visual Pinball exe's (VP9, PM5 and VPX) were crashing (VP has stopped working blablabla) when I launched a table.

And I had strange behaviors such as the old famous "unknown device" we discussed in february with red LED blinking on my KL.

 

But after putting back my v1 binary, updating the bin via Config Tool and double checking settings (and forgetting how they worked with v1 and how they now work with v2), all is working good 

 

And my KL now works on my motherboard's USB ports, I've just checked with a reboot and a power cycle, no more red blinking LED 

 

Thanks again for your valuable work on this magic board

 

++

Edited by shadowshd, 15 May 2016 - 08:56 AM.

[Santos76]

 Hi Mjr ,

you were right with the keyboard input .

I just all off.

PinballX starts now.

 

DirectOutput_R3Beta2_Build_5818.37242 was the latest version that I've found.

DirectOutput still does not work with me.

DirectOutput seems to start well , but I get no output from the Pinscape controller.

 

Is there a tool where you can directly control the output to the test.

 

 

Greeting Sascha

 

PinballX DirectOutput Plugin.log

16.05.15 12:46:45.173 Initializing plugin
16.05.15 12:46:45.173 Loading PBX config data
16.05.15 12:46:45.188 PBX config data loaded
16.05.15 12:46:45.188 Initializing DOF
16.05.15 12:46:45.516 DOF initialized
16.05.15 12:46:45.516 Loading Table/Romname mappings
16.05.15 12:46:45.516 Table mapping filename: C:\PinballX\Plugins\DirectOutput\config\tablemappings.xml
16.05.15 12:46:45.578 PinballX.Table2RomMapping.TableNameMappings TableMappings loaded
16.05.15 12:46:45.578 No romnames are configured in DOF.
16.05.15 12:46:45.578 Table/RomName mapping loaded
16.05.15 12:46:45.578 Sending initial PBX state to DOF
16.05.15 12:46:45.594 Init complete
16.05.15 12:46:47.373 Action: PBXGameSelect
16.05.15 12:46:47.376 Best match for DOFTEST is DOF TEST TABLE (dof_test). Match Value: 0,521739130434783
16.05.15 12:46:47.376 Game selected dof_test (No update sent)
16.05.15 12:46:51.406 Event_Input
16.05.15 12:46:53.639 Event_Input
16.05.15 12:46:53.639 Action: PBXMenuSelect
16.05.15 12:46:54.185 Running dof_test
16.05.15 12:59:35.302 Exiting game dof_test
16.05.15 12:59:41.297 Event_Input
16.05.15 12:59:41.297 Action: PBXMenuOpen
16.05.15 12:59:42.230 Event_Input
16.05.15 12:59:42.231 Action: PBXMenuSelect
16.05.15 12:59:42.734 Running dof_test
16.05.15 01:10:41.177 Exiting game dof_test
16.05.15 01:10:46.937 Event_Input
16.05.15 01:10:46.937 Action: PBXMenuOpen
16.05.15 01:10:47.820 Event_Input
16.05.15 01:10:47.821 Action: PBXMenuSelect
16.05.15 01:10:48.324 Running dof_test
16.05.15 01:21:50.477 Exiting game dof_test
16.05.15 01:21:57.377 Event_Input
16.05.15 01:21:57.377 Action: PBXQuit
16.05.15 01:21:57.810 Event_Input
16.05.15 01:21:57.811 Action: PBXMenuDown
16.05.15 01:21:58.760 Event_Input
16.05.15 01:21:58.761 Action: PBXMenuSelect
16.05.15 01:21:58.921 Exiting PBX