975 replies to this topic

[CainArg]

I'm in the way of building a VR pinball controller with your Pinscape (many thanks and hat off to you for that!!!)

 

I saw a Youtube video that a controller has a bluetooth connection and I was looking since then in your Pinscape docs if that was possible.

 

 

Just another way to connect to the PC, an USB cable alternative... I'm already know that there's only one USB available, I read your documentation (thanks for that too!!!)

 

I will look for a I2C bluetooth.

 

Thanks!!!!

[mjr]

[Bluetooth to KL25Z]

I'm in the way of building a VR pinball controller with your Pinscape (many thanks and hat off to you for that!!!)

 

So I guess you're looking to connect the KL25Z to the PC via Bluetooth, as a substitute for connecting the KL25Z via Bluetooth?

 

If that's what you have in mind, then it seems possible in theory - someone would just have to make an adapter that emulates a USB connection over Bluetooth.  I don't know if any such thing exists, but if it does, you'd presumably be able to plug one adapter into the KL25Z USB port and plug a matching adapter into the PC's USB port.  Or maybe use a Bluetooth driver on the PC to emulate a USB connection on that end.  In any case, this all seems plausible, but I have no idea if anyone makes anything like that, or if such a thing would be compatible with the Pinscape software.  If the USB-over-Bluetooth emulation were perfect, the Pinscape software shouldn't be able to tell the difference and everything should just work, but my experience with everything USB and everything Bluetooth is that most device implementations are far from perfect and nothing ever just works.

 

When I web-search for "USB over Bluetooth" I get a few hits, so you might try that.  Doesn't look entirely encouraging from a brief glance.

[fhjui]

Pinscape: Night-Mode doesn't work as described, when using a dedicated Button

 

I had build up a vPinball Cab using the original PCB-layouts from mjr, with recent firmware. (FW 2021-12-22-2148, PinscapeConfigtool also from 2021-12-22)

Soldering and Build-up was a fun, with this great work from mjr, thanks for that.

All works fine from the beginning but not the switching to night-mode using a button.

 

Problem: Pinscape does not switch on or off when pushing this special button.

 

Configuration in PinscapeConfigtool:

• configured Button #25(PTC16) as input button for switching night-mode


• configured Port# 59 (LED3R) as LED-Output for night-mode indicator


• appropriate configuration of Button# and Output# in  the Pinscape After-Dark section

I have installed DOF ad DOFLinx, the night-mode port is NOT used/configured in DOF-configuration

 

What I have tested and what works well:

• pushing the night mode button is correctly displayed in the test-button section of Pinscapeconfigtool


• switching the night-mode on/off in pinscapeconfigtool lights up the button-LED correctly and switches pinsacpe to night-mode on/off


• Sending "nightmode=off" or "on" using pinscapeCmd.exe works also correct, LED is switched on/off

The problem is, when pushing the night-mode button nothing happens, no switching of the night-mode

 

For my understanding the pinscape must switch the night-mode directly with the appropriate button, completely indipendend of the used pinball-software (in my case VPX and FP)

 

here some pics of my configuration:

 

 

 

Perhaps someone as a hint or an explanation whats wrong here.

[Suikazz]

Pinscape: Night-Mode doesn't work as described, when using a dedicated Button

 

I had build up a vPinball Cab using the original PCB-layouts from mjr, with recent firmware. (FW 2021-12-22-2148, PinscapeConfigtool also from 2021-12-22)

Soldering and Build-up was a fun, with this great work from mjr, thanks for that.

All works fine from the beginning but not the switching to night-mode using a button.

 

Problem: Pinscape does not switch on or off when pushing this special button.

 

Configuration in PinscapeConfigtool:

• 
  
• configured Button #25(PTC16) as input button for switching night-mode
• 
  
• configured Port# 59 (LED3R) as LED-Output for night-mode indicator
• 
  
• appropriate configuration of Button# and Output# in  the Pinscape After-Dark section
• 
  

I have installed DOF ad DOFLinx, the night-mode port is NOT used/configured in DOF-configuration

 

What I have tested and what works well:

• 
  
• pushing the night mode button is correctly displayed in the test-button section of Pinscapeconfigtool
• 
  
• switching the night-mode on/off in pinscapeconfigtool lights up the button-LED correctly and switches pinsacpe to night-mode on/off
• 
  
• Sending "nightmode=off" or "on" using pinscapeCmd.exe works also correct, LED is switched on/off
• 
  

The problem is, when pushing the night-mode button nothing happens, no switching of the night-mode

 

For my understanding the pinscape must switch the night-mode directly with the appropriate button, completely indipendend of the used pinball-software (in my case VPX and FP)

 

here some pics of my configuration:

 

 

 

Perhaps someone as a hint or an explanation whats wrong here.

did youn define noisy toys?
Pinscape can only turn things off that are known to be noisy. for that you have to assign the bell right next to your loud toys!

 

have a look here:

http://mjrnet.org/pi...p?sid=nightmode

[fhjui]

 

Pinscape: Night-Mode doesn't work as described, when using a dedicated Button

 

I had build up a vPinball Cab using the original PCB-layouts from mjr, with recent firmware. (FW 2021-12-22-2148, PinscapeConfigtool also from 2021-12-22)

Soldering and Build-up was a fun, with this great work from mjr, thanks for that.

All works fine from the beginning but not the switching to night-mode using a button.

 

Problem: Pinscape does not switch on or off when pushing this special button.

 

Configuration in PinscapeConfigtool:

•  
• configured Button #25(PTC16) as input button for switching night-mode
•  
• configured Port# 59 (LED3R) as LED-Output for night-mode indicator
•  
• appropriate configuration of Button# and Output# in  the Pinscape After-Dark section
•  

I have installed DOF ad DOFLinx, the night-mode port is NOT used/configured in DOF-configuration

 

What I have tested and what works well:

•  
• pushing the night mode button is correctly displayed in the test-button section of Pinscapeconfigtool
•  
• switching the night-mode on/off in pinscapeconfigtool lights up the button-LED correctly and switches pinsacpe to night-mode on/off
•  
• Sending "nightmode=off" or "on" using pinscapeCmd.exe works also correct, LED is switched on/off
•  

The problem is, when pushing the night-mode button nothing happens, no switching of the night-mode

 

For my understanding the pinscape must switch the night-mode directly with the appropriate button, completely indipendend of the used pinball-software (in my case VPX and FP)

 

here some pics of my configuration:

 

 

 

Perhaps someone as a hint or an explanation whats wrong here.

did youn define noisy toys?
Pinscape can only turn things off that are known to be noisy. for that you have to assign the bell right next to your loud toys!

 

have a look here:

http://mjrnet.org/pi...p?sid=nightmode

 

@Suikazz, yes , haven't mentioned it, I have defined noisy devices, added pic.

 

As I described, night-mode works well, but NOT when bushing the night-mode button.

 

[fhjui]

Because there is no solution in sight, Please, can anyone who uses a night-mode button with Pinscape, confirm that this works ? and how its configured?

 

I have checked and looked up the whole parts (including my test environment) and cannot find any mistake.

 

I fear it may be a bug in the firmware? (sorry mjr for that suspicion) and hasn't been noticed so far because nobody uses it.

[svorak]

I am no expert, but something doesn't look right here. (I am in the process of building my cab - have most of the hardware ready to install, have built a set of Pinscape boards (just waiting on 5940s and one more 2064).  So nothing yet working, but I've been doing a lot of reading of mjr's doc.

The screenshot of you Pinscape config does not look right. I'm assuming based on your words ("using the original PCB-layouts from mjr") that you've built a Pinscape expansion, chime and power board?

But the screenshot that you've posted shows the config for a KL25Z with external TLC5940/74HC595 chips.  If you've built the Pinscape expansion set, you should be using the Pinscape expansion config, and include how many output and chime boards you have added.

 

Shouldn't your knockers be configured as timed digital output of the chime board, not as a PWM output of the TLC5940.

[fhjui]

@svorak, thanks for your hint.

That was the reason to check the pinscape configuration again and I have found the reason for that issue. At first some remarks to your points:

• yes, I have one chime-board and one power-board configured
  but that has nothing to do with the night-mode problem, thats a problem of the input-part, all inputs are on the pinscape-mainboard.
• the knocker is correct, as you can see in the pics, the knocker is connected to the knocker-output of the mainboard, it has one  special power output with mosfet and timer

the reason is a strange behaviour of the pinscape for the config. of the input buttons (input-button configuration settings)

I had set the ports that I don't need (f.e. coin4-slot) to "not connected" because I was of the opinion that  the allocation between the port# , GPIO# and the pin# is free configurable. And configured it further down using the button allocation

Because of the "not-connected" ports the other ports slide up in the numbering and this port is no longer considerd by the software. I had configured this released port further down for the night-mode button. The trap for me was that in the button test section this input works well but the pinscape ignores it.

rather complicate to explain hope you know what I mean.

 

Some hints to the pinscape-configTool:

• in the config section you cannot switch the software to display the Button# configuration for the inputs and the port# configuration for the outputs. When you choose "Revert" - whitout changed anything - the software shows the button- and  port- designation
• when noght-mode is configured, all "noisy-configured " single outputs cannot be tested with the  output tester. They can only tested with the button "night mode" in the output tester.

be aware of fake-chips for the TLCs in DIL-package. They are no longer produced, TLCs with SMD-package are available at distributors like mouser or digikey

You can mechanically test the IC by wiping the top surface with a Q-tip with Acetone. The type designation must not be wiped out and the Q-tip must not turn black.

 

If you have quetstions concerning the pinscpae-PCBs don't hesitate to ask.

[svorak]

be aware of fake-chips for the TLCs in DIL-package. They are no longer produced, TLCs with SMD-package are available at distributors like mouser or digikey

You can mechanically test the IC by wiping the top surface with a Q-tip with Acetone. The type designation must not be wiped out and the Q-tip must not turn black.

 

If you have quetstions concerning the pinscpae-PCBs don't hesitate to ask.

 

Thanks for your acetone tip.

 

Yes, very aware that TI has discontinued production of the DIP TLC. I've already had 2x orders from AliExpress and one from Ebay cancelled (and refunded) by the suppliers. One order has actually found its way to shipping, and my tracking tells me its scheduled to arrive this week. Hopefully they work and are not just plastic blocks with legs.

 

Considering my cabinet build is still in progress, but I do have the assembled PCBs, an operational PC, most of the output devices (RGB LEDs, solenoids etc) what is the easiest way to jury-rig up some wiring/devices to test/verify myTLCs actually do work?

 

Given the limited supply of TLCs I'm using IC sockets on my PCBs so I can switch them out easily. Hoping not to have to do so though

[fhjui]

@svorak: because this is OT and we don't want to hijack this thread here and make mjr angry..

I have posted a new thread https://www.vpforums...showtopic=49907, a suggestion how I have tested the pinscape boards

[fhjui]

mjr - perhaps you haven't seen my thread https://www.vpforums...showtopic=49941 ? ok so be it.

haven't found a way to implement this.

 

I'm missing the source code for "pinscapecmd". It would be nice if you would release the source code as open source, because I'm missing the option of pinscaspecmd to switch outputs on/off.

I would try by myself to extend this feature.

A much more inelegant solution would be to change the pcb itself and mapping an additional 2nd output to the night mode output.

[mjr]

I'm missing the source code for "pinscapecmd". It would be nice if you would release the source code as open source, because I'm missing the option of pinscaspecmd to switch outputs on/off.

 

https://github.com/m...scapeConfigTool

 

See the PinscapeCmd/ subfolder.

 

But the approach you have in mind probably won't work.  The problem is that DOF sends commands to turn everything off every time it starts up and shuts down - that is, every time you launch or exit a game, every time you enter or exit your DOF-capable menu system, etc.  So you'd be constantly fighting with DOF over who gets to turn your control output on or off.

 

I can think of two more workable approaches.  The hard way would be to modify the firmware to add a second night-mode-status output that always does the same thing as the first night-mode-status output.  The easy way would be to wire things externally on your system to use the existing single night-mode-status output, to connect it to the two external things you want it to control - the amplifier power switcher and an indicator light.  It seems to me that if you're going to use a Pinscape output to switch power to an audio amplifier, you're probably going to have to have a physical contactor or relay involved, right?  I'm presuming that what you have in mind is to switch the AC mains power to the amplifier, and the only way to do that with a Pinscape output would be via a relay/contactor.  So as long as you're going to have a relay involved, why not just get a DPDT relay and use the other pole to control the indicator light?

[fhjui]

mjr - many thanks for your answer and for your suggestion concerning the DPDT-relay, a pragmatically good idea. Haven't seen that the source is implemented in the part of the configtool at github. Sorry for that.

I didn't think of that DOF switches off all outputs at exit. The other conceivable way would be to start pinscapecmd every time a game is loaded within Pinupsystem, but that assumes that pinscapecmd can switch outputs and in addition some parts/options of the batch commands of pinupsystem are a mystery for me..yet.

 

For that reason I prefer your suggestion to use a DPDT-relay for switching both parts.

 

I'm using these Lepy-amplifiers which use 12V, no amps with mains powersupply.

 

Especially first many thanks for your great work with this challenging part of hardware and software. I follow your thread since the beginning and have build up all your pinscape-pcbs using your layouts and schematics, only converted it to KiCAD.

Edited by fhjui, 16 September 2022 - 08:24 PM.

[mjr]

For that reason I prefer your suggestion to use a DPDT-relay for switching both parts.

 

Sounds good - that should be straightforward to set up, no software mods required. 

 

 

I'm using these Lepy-amplifiers which use 12V, no amps with mains powersupply.

 

Even in that case, I'd still probably want to do the power switching to the amps through a relay, as opposed to connecting the amp's power supply ground directly to a MOSFET on the Pinscape board.  That way you don't have to worry about any weird interactions between the amp's internal circuitry and the MOSFET.

[fhjui]

 

That way you don't have to worry about any weird interactions between the amp's internal circuitry and the MOSFET.

mjr is right - as usual- connecting the LP-838 amp directly to the pinscape output works, but gives a very slight hum.

Because that bothers me, I have ordered a Dual-relay module from az-delivery that includes optocouplers

https://www.az-deliv.../2-relais-modul

 

For these who are interested in the data of the LP-838 amplifier which is often uses for SSF:

Measured with 1kHz sinus input of app. 0,3V input voltage

max. output power: 15W eff at 12V til clipping

current consumption: 1,5A

the bass output is more sensitive and easily overdriven with 0,2-0,3V input

 

the Lepy-838 is offered by different companies at amzon for app. 20$

[rickh]

 

 

That way you don't have to worry about any weird interactions between the amp's internal circuitry and the MOSFET.

mjr is right - as usual- connecting the LP-838 amp directly to the pinscape output works, but gives a very slight hum.

Because that bothers me, I have ordered a Dual-relay module from az-delivery that includes optocouplers

https://www.az-deliv.../2-relais-modul

 

For these who are interested in the data of the LP-838 amplifier which is often uses for SSF:

Measured with 1kHz sinus input of app. 0,3V input voltage

max. output power: 15W eff at 12V til clipping

current consumption: 1,5A

the bass output is more sensitive and easily overdriven with 0,2-0,3V input

 

the Lepy-838 is offered by different companies at amzon for app. 20$

 

The hum is caused by a ground loop which creates common mode noise.  This occurs when both grounds are shared.   Best way to deal with this is to use an audio isolator > https://www.amazon.c...,90&sr=8-1&th=1

or 

https://www.amazon.c...r,aps,90&sr=8-3

 

Regards,

 

Rick

[cjolly3053]

So little frustrated I got all my stuff built and bought and built some pinscape boards and trying to program my KL25Z for the first time and getting an error and can't get any further. Tried a number of times and just can't get to config the setting without getting the following error:

 

Internal error. An error has occurred within the configuration tool. This is probably due to a bug in the program, not anything you did wrong.

Technical details for debugging.

html/configure.htm Line 9092 col17
Type error: Unable to get property type of undefined or null reference.

 

I seen a couple posts about this but no real help??? This is brand new board and first time trying to program. Tried a number of known good usb cables all the same result.

 

Bootloader version 1.12, debug app version 1.18

 

Anybody able to solve this???

 

 

[WadeZ]

Can somebody tell me where I can get help installing pinscape? I get an error every time I have tried to install it. It seems to install but when I click on the configuration button, I get an window that says

: An error occurred loading the device settings.(Error retreiving value for var 4) Do you want to try again.

When I cancel I get a greyed out configuration utility with this error:

Internal error has occurred within the config tool. This is probably due to a bug in the program, not anything you did wrong. Technical details (for debugging): html/Configure.htm, line 9092, col 17 TypeError: Unable to get property 'type' of undefined or null reference. I have tried 6 times and can't get past this

[mjr]

Can somebody tell me where I can get help installing pinscape? I get an error every time I have tried to install it. It seems to install but when I click on the configuration button, I get an window that says

: An error occurred loading the device settings.(Error retreiving value for var 4) Do you want to try again.

When I cancel I get a greyed out configuration utility with this error:

Internal error has occurred within the config tool. This is probably due to a bug in the program, not anything you did wrong. Technical details (for debugging): html/Configure.htm, line 9092, col 17 TypeError: Unable to get property 'type' of undefined or null reference. I have tried 6 times and can't get past this

 

If you're starting with a brand new board, and it won't install, it seems like the only possibilities are that you somehow got a non-working copy of the software, or there's a hardware problem.  Sorry to ask the dumb obvious questions, but...

 

- Are you sure you have the latest version of the software?

- Have you tried deleting the old copy and downloading a new one, to make sure something didn't get corrupted in the download process?

- Does the KL25Z appear to be working correctly as far as appearing as a thumb drive in Windows Explorer when you plug it in?

- The board is a KL25Z, and not one of the siblings with a very similar but not quite exactly the same name, like KL26Z or one of those?  (I ask because the KL25Z has been so hard to buy lately that some people have tried one of the similar boards, thinking "26 is close enough for government work", but unfortunately it's not; the software only works on the KL25Z, that exact model only.)

 

If you've already covered all of those basics, maybe you could lead me through the exact steps you're attempting in as much detail as possible.  

[WadeZ]

MJR

Thanks for responding.

I do have the latest version and I downloaded it twice and both times it did the same thing.

It does show up in explorer and it is a KL25Z.

When I plug it in the programming port and open the config tool, I choose setup a new KL25Z.

It then tells me that the bootloader is up to date and proceeds to install the firmware. It runs through it's routine and tells me the firmware was successfully installed and tells me to change ports, which I do. It shows me a screen where I choose the setup, which for me is the stand alone KL25Z. But before I can click on that, I get the error message: An error occurred loading the device settings.(Error retreiving value for var 4) Do you want to try again

 

I try again which doesn't work and I close that window and then get this message:

 Internal error has occurred within the config tool. This is probably due to a bug in the program, not anything you did wrong. Technical details (for debugging): html/Configure.htm, line 9092, col 17 TypeError: Unable to get property 'type' of undefined or null reference