Search results

Hi Paul, Just wondering if you use the long datatype in TeensyControls, and did you build it against the latest (v2.1.3, Nov 2013) X-Plane SDK? long is not portable, apparently, and the SDK was updated in November to fix a bug which caused plugins to crash each other. Per this article...

Ah yes, I have similar encoders. My current setup has two pushbutton encoders and a 16x2 LCD. The left encoder is coarse changes, the right encoder is fine changes, and clicking on the left or right encoder buttons (or both together) cycles through a list of different things the encoders can...

That's a good idea too. I'll check there isn't already an Arduino class for this, it seems like there ought to be one.

Using Teensy boards to build flight simulator interface hardware, I normally use two encoders - one for coarse changes, one for fine changes. For example, to set a heading, I have one encoder making 4° changes and another making 0.25° changes. This allows the setting to be made rapidly and with...

From the mbed website: Is that C/C++ SDK something that was added very recently? I admit, I've never used an online dev environment, it can't be as absurd as my gut reaction says it is.

Great! These are for my X-Plane interfacing classes, so it's very unlikely they'll be portable to Arduino without a struggle anyway. I'll put a note in the source to inform future generations to add a slew of new class constructors if they want to try anything like that.

If I do this: pinMode(100, OUTPUT); or digitalWrite(-1, HIGH); does anything bad happen? It appears to work fine.

I'm trying something which might be vaguely related. I got into Teensy boards for building flight simulation interface hardware. Most flight sim enthusiasts have a horror of programming, which is fairly understandable, so I've begun writing helper classes which integrate the Teensy's...

Ah, thanks for the explanation Paul! Interesting to see how this was seen as a 'feature' to make dependencies explicitly visible. Instead of #include <foo.h> in my headers, I'll leave an allcaps comment // YOU MUST #INCLUDE <FOO.H> IN YOUR MAIN SKETCH!! instead.

Hi all, Today I made a class which does this: typedef const double ScaleMap [][2]; ScaleMap myMap = { {0.0, 120}, //left column is input values. Right column is output values. {0.34, 90}, {1.0, 45} // indefinitely many pairs, but probably less than 20. }; SimServo::SimServo (...

Why can't I do this: SimObjectsDev.ino: #include "SimServoDev.h" SimServo myServo (blah blah blah); setup() ... loop()... SimServoDev.h: #include <Servo.h> // behold the vanishing #include statement! class SimServo { ... private: Servo _servo; }; I'm writing a wrapper for the Servo...

Yes, I believe so. Open the Arduino IDE (wear latex gloves to keep your hands clean :p ), after installing Teensyduino into it. Open the 'Tools' menu, look under 'USB Type', and there's a 'Serial + Keyboard + Mouse + Joystick' entry in there.

enum Bool { true, false, FILE_NOT_FOUND }; Bool answerQuery(const char* query); int main() { Bool answerQuery("can I use this with Teensy* 2.0 to make Flight Sim Controls devices?"); return 0; }

I'm not asking for estimated completion dates. Just 'X is ready, Y is not ready yet', perhaps listing Y by intended completion sequence.

Thanks Paul!

Hey, PJRC has a forum. Great! I can share my Teensy code with people who know lots about Teensy code-writing, rather than only with other X-Plane users. Is there a list somewhere of Teensy 2.0 code features which are not yet ported to Teensy 3.0? I understand X-Plane support is on that list...

Hooray, a forum! I can bother other people with questions instead of just emailing Paul. :-)