Jump to content



Photo
- - - - -

Teensy question regarding addressable LEDs


  • Please log in to reply
7 replies to this topic

#1 DDH69

DDH69

    Pinball Wizard

  • Platinum Supporter
  • 3,025 posts
  • Location:DOFLinx HQ, Adelaide

  • Flag: Australia

  • Favorite Pinball: Monster Bash

Posted 17 June 2017 - 02:31 AM

While waiting for may addressable LEDs themselves to turn up I'm setting up my Teensy. Before I solder the Teensy to the Octo, do I need to cut the 5V USB supply joiner on the underside?  I think I do as I'll be supplying the common 5VDC via the terminal I will add to the Octo board, but want to be 100% sure.  I just don't seem to be able to find a definitive answer on this in the write-ups and guides I've found.


DOFLinx
Contributions for equipment to help with ongoing DOFLinx development can be made here

#2 kiwiBri

kiwiBri

    Enthusiast

  • Members
  • PipPipPip
  • 369 posts
  • Location:Ontario, Canada

  • Flag: Canada

  • Favorite Pinball: STNG/TAF/IJ

Posted 17 June 2017 - 05:44 AM

While waiting for may addressable LEDs themselves to turn up I'm setting up my Teensy. Before I solder the Teensy to the Octo, do I need to cut the 5V USB supply joiner on the underside?  I think I do as I'll be supplying the common 5VDC via the terminal I will add to the Octo board, but want to be 100% sure.  I just don't seem to be able to find a definitive answer on this in the write-ups and guides I've found.

 

 

hey mate!  NO! You don't need to do that. Its powered by the USB cable to the PC. I too had the same issue trying to figure out this as well. I soldered my  octo board to the teensy via the header pins. I then programmed the board. I next hooked up a single LED strip to the Twisted pair (Orange)  and GND from the Ethernet cable, AND also connected the LED strip to 5v and GND. Worked great :)  . This will be the last thing I implement when I finish the final phase. 

 

 

Updated post to reflect correct connections


Edited by kiwiBri, 26 June 2017 - 03:15 PM.

Completed: (For now ;) )  - My 46/30/DMD Judge Dredd Cab Build


#3 BritXpatUSA

BritXpatUSA

    Hobbyist

  • Members
  • PipPip
  • 48 posts

  • Flag: United Kingdom

  • Favorite Pinball: wizard

  • 360 Gamer Tag: BritXpatUSA

Posted 18 June 2017 - 02:20 AM

hey,

 

Im installing the same this weekend...well atleast trying too....

I have bee researching and found this link tonight...

http://vpuniverse.co...e-rgbs/?page=18

 

good luck.....Im stuck with the leds being on all the time even when the PC is off...

 

BTW..and im trying Doflix with ipaq I/O and 16 port sainssmart...1step forward 10 back so far! :-)



#4 DDH69

DDH69

    Pinball Wizard

  • Platinum Supporter
  • 3,025 posts
  • Location:DOFLinx HQ, Adelaide

  • Flag: Australia

  • Favorite Pinball: Monster Bash

Posted 18 June 2017 - 02:36 AM

hey,

 

Im installing the same this weekend...well atleast trying too....

I have bee researching and found this link tonight...

http://vpuniverse.co...e-rgbs/?page=18

 

good luck.....Im stuck with the leds being on all the time even when the PC is off...

 

BTW..and im trying Doflix with ipaq I/O and 16 port sainssmart...1step forward 10 back so far! :-)

 

Thanks and best of luck.

 

I soldered my Teensy and Octo together this morning.  Now I need to wait until I get my LEDs delivered.

 

If you have any issues with DOFLinx just start up a thread in the DOFLinx forum, always here to help.  :help:


DOFLinx
Contributions for equipment to help with ongoing DOFLinx development can be made here

#5 BritXpatUSA

BritXpatUSA

    Hobbyist

  • Members
  • PipPip
  • 48 posts

  • Flag: United Kingdom

  • Favorite Pinball: wizard

  • 360 Gamer Tag: BritXpatUSA

Posted 22 June 2017 - 03:49 PM

can you share what your dofflinx xml looks like? 

here is mine and its not seeing the teensy?i have an ultimate IO board and from what i have read it doesnt look like that is supported either?

hardware:

Ultimate IO board

Sainsmart 16 port relay

teensy with octo

 

I have add the command below thinking it might pickup the IO board?

C:\DirectOutput\DOFLinx.exe PATH_INI=C:\DirectOutput\DOFLinx.exe PACLED64=1

 

22-Jun-17 11:44:10.849 - DOF Linx for Pinball Emulators - DOFLinx by DDH69
22-Jun-17 11:44:10.855 - Starting up - version 4.30
22-Jun-17 11:44:10.869 - 0 LEDWiz device(s) found
22-Jun-17 11:44:10.873 - 0 FTDI (Sainsmart) device(s) found
22-Jun-17 11:44:10.876 - DOFLinx device: 1 Initialising as PacLed64 #1
22-Jun-17 11:44:10.888 - DOFLinx device:1 PacLed64 setup with 64 outputs
22-Jun-17 11:44:10.893 - Reading DOFLinx.INI startup config file details
22-Jun-17 11:44:10.901 - Reading DOF config file
22-Jun-17 11:44:10.906 - Reading DOF config file
 
i left the game data to save rolling space :-)
 
####
# The config file for DOFLinx
# A mad idea by DDH69 to have some flipper sounds, RGB display and turn buttons on when playing Pinball FX2 via Steam
# Its grown a lot since that silly start!
# Note - this works with LEDWiz, PacLed64, KL25Z and Sainsmart (FTDI devices)
# Edit this file as you see fit, lines that start with a hash (#) or are blank are not processed.  This blurb and comments can be cut out if you want.
#
# Output devices outputs are entered in the format of
# device (D) and output number (#) in the format D##, so controller device 1 and output 3 is "103" without the quotes, controller board 2 output 23 is "223" without quotes
####
 
# location of your standard DOF outut configuration file.  Keep this as the first item in the file
DIRECTOUTPUTCONFIG=c:\DirectOutput\config\directoutputconfig27.ini
DIRECTOUTPUTCONFIG=c:\DirectOutput\config\directoutputconfig30.ini
 
# If you want to list the processes that will wake up DOFLinx, comment it out if you just want Pinball FX2
PROCESSES=Pinball FX2,Future Pinball,VPinball921,VPinball99_PhysMod5_Updated,VPinballX,VPinball994
 
# Which DOF Controller output for the flipper solenoids / contactors
L_FLIPPER_OUTPUT=101
R_FLIPPER_OUTPUT=102
# The keyboard hex code for the key that is used for each flipper from https://msdn.microso...1(v=vs.85).aspx
# Left Shift = A0, Right Shift = A1
L_FLIPPER_KEY=A0
R_FLIPPER_KEY=A1
# Just in case things go wrong (ie no keyup signal is detected, flipper held down for a long time), what is the maximum time a flipper solenoid / contactor can be in in milliseconds
MAX_FLIPPER_ON=5000
# What LEDWiz output(s) are used for RGB devices.  Just enter the Red output number.  Multiples can be entered seperated by a comma
RGB_OUTPUT=109
# Rainbow - cycle through the colours, Random - pick a random next colour, A colour name as it appears in the DirectOutputConfig.ini file
RGB_STYLE=RANDOM
# What changes the colour?  Time - set time period, Flipper = flipper press after the RGB_TRIGGER minimum time (to stop rapid colour changes)
RGB_TRIGGER=FLIPPER
# Dependent on trigger selection the period between changes or the minimum time for change between flipper flips
RGB_MIN_TIME=1000
# The button(s) to turn on when DOFLinx starts, ie the exit button LED
#BUTTONS_ON=102 104
# Make the "1" (31) key (Start in VP) pulse LEDWiz 120 and "4" (34) to pulse controller/output 121
KEY_TO_OUTPUT=32 101 35 106 36 105
# Set a key to turn on a specific colour for your RGB.  The line below makes the Left Control (A2) and the Right Control (A3) turn my undercab RGB strip red.
# In Pinball FX2 this means when I nudge it all goes red.
#KEY_TO_COLOUR=A2 109 Red A3 109 Red
# Setting FORCE_ACTIVE=1 will cause DOFFX2 to not listen for processes and just run until you kill the process.  Handy for using it for things other than PinBall FX2
FORCE_ACTIVE=0
# If you want the program to stop when your named process stops then set this to 1.  If you want it to run in the background all the time leave it as 0
QUIT_AFTER_PROCESS=0
# Set to 1 to output the game name to the log regardless of the DEBUG flag setting.  Set to 0 to simply follow the DEBUG flag.
# Quite useful when you trying to get the FX2 window game name for setting game specific colours
OUTPUT_GAME_NAME=1
 
####
# Sample setup to enable the Future Pinball Link.  Edit the LINK_ items to be your ports and settings.
####
FP_ATTEMPT_LINK=1
# Use the line below if you need to extend the wait time for a FP table to load
#FP_LINK_WAIT_TIME=60000
LINK_LF=101,50,10000,255  left flipper on port1 of IO and port 1 of sainssmart?
LINK_RF=102,50,10000,255 right flipper on port2 of IO and port 2 of sainssmart?
#LINK_LS=118,50,500,255
#LINK_RS=126,50,500,255
#LINK_ML=127,50,500,255
#LINK_MC=128,50,500,255
#LINK_MR=129,50,500,255
#LINK_BL=130,50,500,255
LINK_BC=101,50,500,255
#LINK_BR=132,50,500,255
LINK_SH=111,1000,5000,255 on port11 of IO and port 11 of sainssmart?
#LINK_GR=116,750,10000,255
#LINK_KN=124,120,500,255
#LINK_ST=102
#LINK_EB=101
#LINK_CN=106,105,103
#LINK_EX=104
 
####
# 0 = OFF (normal operation), 1 = ON - When ON a window will appear and a log file will be created in the EXE directory.
DEBUG=1


#6 DDH69

DDH69

    Pinball Wizard

  • Platinum Supporter
  • 3,025 posts
  • Location:DOFLinx HQ, Adelaide

  • Flag: Australia

  • Favorite Pinball: Monster Bash

Posted 23 June 2017 - 03:42 AM

I am setting up my Teensy so that I can experiment on its use within DOFLinx.  DOFLinx has no support for it as yet.

 

There is no native support for the Ultimate IO board in DOFLinx.  I've seen a branch of the DOF Framework R3 where support if being added, but have no insight into that.  I am unsure of the Ultimate IO emulation as multiple PacLED64's.  I'm in the process of adding Pinscape support (done, not tested) at present.

 

It looks like your DOF R3 Framework is detecting some sort of PacLED64 emulation if DOFLinx can open device #1 as a PacLED64.  If the Ultimate IO board is recognised as emulating multiple PacLED64's then you may be able to use PACLED=1,2 to get the other outputs - really not sure.


DOFLinx
Contributions for equipment to help with ongoing DOFLinx development can be made here

#7 kiwiBri

kiwiBri

    Enthusiast

  • Members
  • PipPipPip
  • 369 posts
  • Location:Ontario, Canada

  • Flag: Canada

  • Favorite Pinball: STNG/TAF/IJ

Posted 26 June 2017 - 03:16 PM

would be great to have this work in DOFLinx - I haven't event got as far to install it, but can see the potential of it. 

 

thanks


Completed: (For now ;) )  - My 46/30/DMD Judge Dredd Cab Build


#8 rambo3

rambo3

    Enthusiast

  • Members
  • PipPipPip
  • 53 posts

  • Flag: Norway

  • Favorite Pinball: Attack from Mars!

Posted 01 July 2017 - 02:57 PM

Me too me too :)

 

The UIO ain't two PacLEDs, it's its own device. That was the whole point why I had to branch R3 into ultimateio to add native UIO support for it. What they do share is a similar use of its PacDrive DLL. ConfigTool added support for its outputs, some tweaks were done in the DOF UIO-classes to have the UIO perform faster with less load on the system, and that was it. I'd love to add support or helpers to the ultimateio-branch for DOFLinx if it can help.