Search:

LIFA has been deprecated. Sam's current development is happening on LINX. That's mostly what I've contributed to. See the home web page here.
...

Here's an Eagle 7 library with the Teensy 3.0 and 3.1 in it. I haven't had the need to make one for the others. Feel free to add them. :)

Mark

Just an FYI, LINX 1.2alpha is available. If you use it for production you're crazy, but so far it looks like it's working. It's not 'user resistant', but it's alpha, duh. I'm playing with it, so...

The reason I2C Close.vi wasn't working right is timing. It's like for the blink example earlier. Driver doesn't unload quickly - at all. :( Otherwise, 3.1 is working just fine. I'm working on my...

Teensy 3.1 I2C works on LINX!! Mostly... The I2C Close.vi isn't working right. I haven't taken a look at it yet. I suspect <cringe> a timing problem since it worked once with execution...

I don't have a Teensy 2.0++, so I really can't debug it if it's not working. I've sent the revised firmware up to the LINX git, so hopefully it's included. If not, I've made note of the changes I...

Hi Paul,

I'll take a crack at it. I mean, what's the worst that could happen other than it's still no-worky? :)

Was there something fundamental which kept it from working on Windoze other...

I'll try to answer what happened in LabVIEW. It happened using LIFA and LINX. It didn't have a problem with an Arduino UNO nor Teensy 2.0, but did with a Teensy 3.x.

Instead of rehashing the...

I think we've reached a milestone. We can talk to a Teensy through LabVIEW + LINX! I opened a serial port to a Teensy 3.1, read the device name from the installed LINX firmware, then closed the...

Yep. I jumped from LIFA (ni.com/arduino) to LINX (labviewhacker.com).

I've gotten Teensy's to compile the firmware ok, and they seem to communicate ok, but I need to get a little smarter in...

Don't know why it makes a difference for Teensy 3, and not Teensy 2, but correcting <?> a declaration in LabVIEWInterface.ino:

unsigned char checksum;

to

unsigned char checksum = 0;

seems...

Been busy with other stuff... Back now for awhile (hopefully).

Running 2 USB-RS232 adapters and a null modem cable, I'm able to confirm the data is getting through to the serial port ok. The...

I'll poke around a bit on the hardware side, just to see what's getting thru. I'll try your 'softer' suggestions too.

Again, for 2.0 this works fine. Sending the sync string (~FF0000000000000) doesn't get a response back of 'sync'. I'm thinking the LIFA and LabVIEW code is ok, but I'm at a loss where to proceed...

Reported it twice I think. I don't expect they'll listen to me either ;)

For what I'm seeing in LIFA now I'll try to build a test case again to isolate it.

'duff' got it right when suggesting moving the serial open and close vi's out of the loop would fix it. No problems after thast. I musta been making it bonkers opening and closing the port that...

Looks really good. Ran the vi with minimal delays for a couple thousand runs. No errors. No BSoDs. Ship it! :)

Last rev to the vi attached. All old ones removed.

Fair enough. I'll make the change and run it over lunch. I think that tracks with the error too , "failed to open usbser.sys". I'll see if I can just replace the file above with the mod'd one. ...

I can't get it to 'reliably crash', so for now I'm going to guess it's a Windows system thing and drive on unless you want me to check something else.

Here's the 'Torture Test' vi in case...

I haven't exhaustively checked it, but just beating around different values for timings and the string, no problems. At least not after I put a delay in the loop. Before that, it appears LabView...

Looks good. Now I'll play with it to see how robust it is - playing with the timings duff and I were kicking around.

Yea! Thanks a bunch for looking at it Paul.

Ok, but turning on Execution Highlighting (Paul - the light bulb looking button in the block diagram's button bar) doesn't affect it. I set a breakpoint on the 'break write', let it sit a couple...

Just uploaded EcoString.ino to a Teensy 2.0, changed to the correct serial port, got this result.

1690

1691

At the write with break. Again, this works ok with a Teensy 2.0. (that'll be the next post)

Showing the probes:
1688

The values:
1689

@duff: Interesting. I guess that's not the first time Mac and PC don't act the same :)

@Paul: If it's not giving you an error, the demo install probably already installed NI-VISA by default. To...

@Paul: Wow! Too much work! To think I was appalled at the 217MB installer I generated. It didn't work first try, natch.

You'll of course need the Teensy drivers installed, and load the...

LV invasive? It's amazing how bloat-y it feels that way, isn't it?

I'd forgotten about the installer option. I just upgraded to Developer so it's supposed to be in there. I gotta learn it...

Yes, yes and no. I can turn the break off, and the echostring.ino returns the written string just fine.

The Serial Break is actually a VISA function (vi) used in LIFA. I dug down into that and found where it broke. To simplify it, I wrote a sample vi to test it.

1673

Digging down into the VISA...

The LIFA LabVIEW libraries use a Serial Break during the initialization. Why? Dunno. That's just where I found it breaks.

On some test equipment, I believe it's the equivalent of...

Paul, thanks up front!

I can send you the vi, which works for an Uno & 2.0, but breaks for a 3.1. Same for the simple firmware, which works for all. Let me know if you want me to post them here,...

Arduino Uno and Teensy 2.0 work ok with a break sent to their 'serial port'. Teensy 3.0 doesn't appear to - at least the way LabVIEW implements it.

Is this a known Teensy 3.1 limitation?

Still working on LIFA, but found a question of a more general nature.

When LabVIEW sends a break terminated string to the Teeny 3.1's serial port, I get an I/O error. Without the break, or on...

Took some time off from it. All the code was starting to look the same :(

@mknix: Last I'd looked, Teensyduino libs are verified working with 2.0 & LIFA. Not yet with LYNX. That's why I'm...

This isn't XDA <thankfully>, but they're right about one thing. If you wait for someone else to learn it and do it for you, you might be waiting a long time.

Seems to me LIFA is way closer to...

Main sticking point looks like it's the same as for LIFA. Getting LV to recognize the 3.x board properly. I can get the firmware compiled, but the VISA clear is choking on something. Also getting...

Was able to connect with the COM port using PUTTY, but didn't get any reply/echo. Maybe because I don't know what to send the LIFA firmware, or the firmware opens the port but isn't working...

Played with it a bit more now. The error in LV is happening when the COM port is first being opened. Looks like the baud rate, etc, are all properly getting to the vi. This does not happen with...

I was gonna write a quickie how to, but there's stuff already out there.

A short explanation and a calculator.
http://www.daycounter.com/Calculators/LED-Tutorial-Calculator.phtml

A more...

Dunno. I'm running LabVIEW Full / Developer (but probably not well yet).

Don't worry about it. Looks like it's a LabVIEW / LIFA thing, so it's not your onion to peel. ;) I have more software...

<edit> Looks like it is something related to LabView / LIFA. Doesn't happen unless I load LabView. Sorry - different onion to peel...

<I'd strikethrough all this - but don't see it in the font...

I'll have to play with it more, but the serial driver seems to hang more easily with rc4. I mean when loading onto the 3.1, I can't select the port using Arduino IDE until after rebooting. The IDE...

blink.vi

1439

Text in the lower block was greatly copied from somewhere. (teensyduino pin definition file?)

AFMotor.h - modded



// Adafruit Motor shield library
// copyright Adafruit Industries LLC, 2009
// this code is public domain, enjoy!

#ifndef _AFMotor_h_
#define _AFMotor_h_

Took inspiration from the latest AFMotor from Adafruit and modded the AFMotor.h file to check for the arm processor. It Compiles! Of course, I haven't been able to get it working on 3.1 - yet.
...

Got 2.0 working on my setup. Started messing with 3.1 in the same thread, but couldn't figure to rename the thread. (if someone tells how I'll delete this one - if possible)

Starting at here in...

Not seeing the BSOD on Win7-64Pro. I've been pulling software on and off while working to get LIFA to work with 2.0 and 3.1, and swapping between boards. Just swapped between an Uno, 2.0 and 3.1...

Being a newb, figured I'd ask. Thanks for the explanation.

Typo in Teensyduino 1.18rc3?

arm-none-eabi-g++ -c -g -Os -Wall -fno-exceptions -ffunction-sections -fdata-sections -mcpu=cortex-m4 -DF_CPU=96000000 -MMD -DUSB_VID=null -DUSB_PID=null...