Teensy USB driver

Hello all,

this is a question/feature request.

I have built a Lighthack-Box with 8 encoders for my element. This box uses a teensy 3.5 to send OSC via USB.

Unfortunately EOS does not recognize my teensy - eos on my PC does recognize it.

Only after I install the teensy serial driver from the teensy Homepage on my console, I can use the Box.

However, when I updated to 2.8 this driver seems to have been removed...

I will install it again before the next programming session starts and hope it works again.

It would be very helpful, if not only the arduino usb driver but also the teensy usb driver would be included into the eos software...

Or am I missing something?

Top Replies

Parents

0 sstaub over 5 years ago

Please, can you share the project as a .zip file attached, including the libraries you use (are they downloaded with the Arduino Library Manager,
or Teensy libs ?).
I tried using my Teensy 3.5 with PlatformIO on macOS with v2.8 without problems.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Orlando over 5 years ago in reply to sstaub

box_8_src.zip

I use all the same libraries as the box1.

additionally:

#include <LiquidCrystalFast.h> because my display is 80x4
#include <Bounce2.h> for debouncing....

All downloaded within Arduino Lib Manager.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 sstaub over 5 years ago in reply to Orlando

The problem is the LiquidCrystalFast library, it is blocking. When you use the standard LiquidCrystel library it should work.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Orlando over 5 years ago in reply to sstaub

Thank you. The standard LiquidCrystal lib does not support my 80x4 characters display as far as I know... I will search for an alternative...
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 sstaub over 5 years ago in reply to Orlando

80x4 char display are very rare, it seems that there is a bug in the library, handling two chips is very unusual.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Orlando over 5 years ago in reply to sstaub

Well apparently the bug was no problem with 2.7.4.
Unfortunately I need a big display.
I'll find a way...
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 Orlando over 5 years ago in reply to sstaub

Well apparently the bug was no problem with 2.7.4.
Unfortunately I need a big display.
I'll find a way...
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

0 sstaub over 5 years ago in reply to Orlando

First, you set the LCD size to 40x4, I never seen a 80x4 char display.
If you init the class with
LiquidCrystalFast lcd(12, 11, 10, 9, 5, 4);
the connection works, but I don't know it the display works in real.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Orlando over 5 years ago in reply to sstaub

Sorry, I meant 40x4 got carried away

When I init the class as you wrote, half the display does not work.

However I just found another lib that supports 40x4 (multilcd).
I'll check what I can do with this...
Cancel
Vote Up +1 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Orlando over 5 years ago in reply to Orlando

I just tried again initializing with LiquidCrystal () (not Fast).

Still no handshake, so I guess this is not the problem...
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 sstaub over 5 years ago in reply to Orlando

I have the seem display, but not used yet, so I will investigate further.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Orlando over 5 years ago in reply to sstaub

I think it has nothing to do with the display.
As I wrote in my other thread, even the original ubs_test_sketch provided by etc (or etclabs or whoever) does not get me a handshake....
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 sstaub over 5 years ago in reply to Orlando

Can you try to change the USB PID and VID numbers in the board.txt from Teensy ! (don't forget to make an backup) to following:
PID 0x0043 VID 0x2341, this emulates an UNO, which normally works on consoles.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Orlando over 5 years ago in reply to sstaub

The board is recognized.

In Tab99 it says:
IoCard "OSC USB Device connected (Handshake Required)"

and later:

IoCard "OSC USB Device Handshake initiated [ETCOSC?]"

But after that nothing....

But I will try the change you suggested....
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 sstaub over 5 years ago in reply to Orlando

If the the device is detected the boards vid/pid seems ok. It is a workaround for boards which are not detected by console/nomad.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Orlando over 5 years ago in reply to sstaub

somehow the board does either not get the "ETCOSC?" or does not send the "OK".

Maybe it has something to do with the SerialUSB?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 sstaub over 5 years ago in reply to Orlando

Get you the startup messages on your lcd starting at line 1758?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel