Teensy/Ledmatrix issue- seems to require manual start

[Felsir]

I followed the MJR guide to get addressable matrix to work http://mjrnet.org/pinscape/BuildGuideV2/BuildGuide.php?sid=addressableLightStrips

So- I had the “all white LEDs” problem. Instead of soldering the two connections (pins 15 and 16)- I added a jumper. This seems a smart move to me, as I wasn’t sure I was doing it correctly. So- I close the jumper and: succes! It works! The matrix was no longer all white and it shows the patterns I expected when testing on a few tables. Real nice.

Now comes the issue:

1. I reset the computer.
2. I start a VPX table.
3. The small light on the Teensy, indicates it is processing commands (slow blink at boot- quick blinks when effects are expected, etc)
4. Nothing happens on the LED matrix. Not a single effect is showing.
5. I remove the jumper.
6. Still nothing happens.
7. I remove the Teensy USB (still without the jumper)
8. The Teensy is plugged back in.
9. The matrix shows all LEDs in bright white.
10. I place the jumper
11. Now start a VPX table: Everything works!

So far it seems I cannot get the LED effect to work without manually closing the connection between pins.

The cabinet.xml and dof config seems to be okay as the Teensy light blinks as expected when testing it with the DOF testing table (ie. pressing ‘w’, causes the small light to blink quickly for a second).

Any suggestions to fix this problem?

Edit:

After some testing- it appears that sometimes just unplugging and replugging the Teensyboard also fixes the issue; strangely before unplugging, the board seemingly reacts as expected on the DOF test table, just the LEDs don’t light up. After plugging it back in, the LEDs react as expected.

You need to login in order to like this post: click here

[Numiah]

What does the Directoutput.log file state?
Is the comport setting correct in your cabinet.xml file?

 

Bally widebody - i5-4690 - 16Gb - Gigabyte Z97X-SLI-CF - Nvidia GTX1660Ti 6Gb - 256GbM.2 - 60Gb SSD (Win10Pro) - Samsung 49" 4K UHDR - 30" LG Backglass - 17" LCD dmd - iPad as topper - Ledwiz - Teensy - iPac32 - 8 Contactors - 5 Flashers - Gear - Shaker - Knocker - Addressable strips and matrix - 2 Strobes - RGB under cab - RGB buttons - 3-axis Tiltbob

Bally widebody - i5-4690 - 16Gb - Gigabyte Z97X-SLI-CF - Nvidia GTX1660Ti 6Gb - 256GbM.2 - 60Gb SSD (Win10Pro) - Samsung 49" 4K UHDR - 30" LG Backglass - 17" LCD dmd - iPad as topper - Ledwiz - Teensy - iPac32 - 8 Contactors - 5 Flashers - Gear - Shaker - Knocker - Addressable strips and matrix - 2 Strobes - RGB under cab - RGB buttons - 3-axis Tiltbob

You need to login in order to like this post: click here

[Felsir]

Thanks for the response. It has been a while so I was about to give up.

The weird thing is that the output looks absolutely normal. The teensy itself blinks as expected (if using the DOF test table, the teensy responds to the keypresses like ‘R’ by blinking its on-circuit led). The DOF output looked like below. I know it works (see this clip) so the config seems to be correct.

I have focussed on building the cabinet for the past few weeks; so I’m going to rewire the matrix and see if the problem persists. I’ll get back with an update when I’ve soldered the matrix wires.

---------------------------------------------------------------------------------
DirectOutput Version 3.1.7527.20768, built 2020.08.10 11:32
MJR Grander Unified DOF R3++ edition feat. Djrobx, Rambo3, and Freezy
DOF created by SwissLizard | https://github.com/mjrgh/DirectOutput
2020.10.18 11:51:33.505	DirectOutput Logger initialized
2020.10.18 11:51:33.489	Global config filename is "C:\DirectOutput\Config\GlobalConfig_B2SServer.xml"
2020.10.18 11:51:33.505	Global config loaded from: C:\DirectOutput\Config\GlobalConfig_B2SServer.xml
2020.10.18 11:51:33.506	Loading Pinball parts
2020.10.18 11:51:33.509	Loading cabinet
2020.10.18 11:51:33.511	Will load cabinet config file: C:\DirectOutput\Config\cabinet.xml
2020.10.18 11:51:33.633	1 output controller defnitions and 1 toy definitions loaded from cabinet config.
2020.10.18 11:51:33.633	Cabinet config file has AutoConfig feature enabled. Calling AutoConfig.
2020.10.18 11:51:33.634	Cabinet auto configuration started
2020.10.18 11:51:33.657	PhilipsHueAutoConfigurator.AutoConfig started...note, actual connection detection will happen asynchronously, and device disabled if not succesfull (check further down in the log)
2020.10.18 11:51:33.668	LedWiz-like device at VID=5215, PID=536, product string=GXT 860 Keyboard, manufacturer string=SEMICO
2020.10.18 11:51:33.670	LedWiz-like device at VID=5215, PID=536, product string=GXT 860 Keyboard, manufacturer string=SEMICO
2020.10.18 11:51:33.672	LedWiz-like device at VID=5215, PID=536, product string=GXT 860 Keyboard, manufacturer string=SEMICO
2020.10.18 11:51:33.678	Cabinet auto configuration finished
2020.10.18 11:51:33.678	Autoconfig complete.
2020.10.18 11:51:33.678	Cabinet config loaded successfully from C:\DirectOutput\Config\cabinet.xml
2020.10.18 11:51:33.678	Cabinet loaded
2020.10.18 11:51:33.678	Loading table config
2020.10.18 11:51:33.678	No TableFilename specified, will use empty tableconfig
2020.10.18 11:51:33.678	Will try to load configs from DirectOutput.ini or LedControl.ini file(s) for RomName sttng
2020.10.18 11:51:33.680	Loading LedControl file C:\DirectOutput\Config\directoutputconfig30.ini
2020.10.18 11:51:33.695	Min DOF Version is 0.8 for file directoutputconfig30.ini
2020.10.18 11:51:33.695	Resolving Tables Variables
2020.10.18 11:51:33.696	Resolving Global Variables
2020.10.18 11:51:34.412	EXCEPTION: Table with ShortRomName Big_Shot_1974 has already been loaded (Exists more than once in ledcontrol file).
2020.10.18 11:51:34.413	EXCEPTION: Thread: 
2020.10.18 11:51:34.710	EXCEPTION: Table with ShortRomName SpotPool_1976 has already been loaded (Exists more than once in ledcontrol file).
2020.10.18 11:51:34.710	EXCEPTION: Thread: 
2020.10.18 11:51:34.969	1 directoutputconfig.ini or ledcontrol.ini files loaded.
2020.10.18 11:51:34.971	Config for RomName sttng exists in LedControl data. Updating cabinet and config.
2020.10.18 11:51:34.981	Table config loading finished: romname=sttng, tablename=sttng
2020.10.18 11:51:34.982	Pinball parts loaded
2020.10.18 11:51:34.982	Starting processes
2020.10.18 11:51:34.982	Initializing cabinet
2020.10.18 11:51:34.982	Debug: Initializing output controllers
2020.10.18 11:51:34.989	TeensyStripController TeensyStripController1 intialized and updater thread started.
2020.10.18 11:51:34.989	Debug: Output controllers initialized
2020.10.18 11:51:34.990	TeensyStripController TeensyStripController1 updater thread  started.
2020.10.18 11:51:34.993	Initializing ComPort COM3 with these settings :
2020.10.18 11:51:34.993		BaudRate 9600, Parity None, DataBits 8, StopBits One, R/W Timeouts 200ms
2020.10.18 11:51:34.993		Handshake Timings : Open 50ms, Loop Start/End 20/50ms
2020.10.18 11:51:34.993	Cabinet initialized
2020.10.18 11:51:34.996	Loading shape definition file: C:\DirectOutput\Config\DirectOutputShapes.xml
2020.10.18 11:51:35.025	Framework initialized.
2020.10.18 11:51:35.025	Have fun! :)
2020.10.18 11:51:35.094	TeensyStripController TeensyStripController1 updater thread  has connected to TeensyStripController TeensyStripController1.

 

You need to login in order to like this post: click here

[Author]

Posts