Search results

I may as well follow the trend I probably set way back then. Your serial monitor output suggests you rolled the encoder about four clicks each way up to a couple of times and then ended by rolling the encoder in a single direction several times in a row. Did any of you guys solve this...

In AVR stuff you could set the exerted pin state (low or high) before selecting exertion (pinmode OUTPUT) - I wonder if 'pinMode' clears the state if you digitalwrite[fast] a high and then set the pinMode? Pity if so - I can't check right now; I usually want the reset to occur, they are usually...

When I initially wrote it I thought that testing and debugging would corner me into disabling interrupts and storing mTimer.value, to return with after re-enabling interrupts, but it never became an issue due to what I did with the returned values; taken as a group of 8 samples, find samples...

It is a while since I touched this much, I have lifted it out of a complete program which I am not at liberty to share in whole and I haven't tried to compile this copy so I apologise if it isn't as intact and complete an example as I hope to be posting you; typedef union { uint32_t value...

Unless I have missed something about the LC; that is not a reset button, it is a reprogram button and when you press it the LC will go into a non-responsive looking mode until either the teensy loader program sends it a nice batch of code or until the power to the unit is cycled. I wouldn't...

expected: Serial device (including, certainly not limited to, another Teensy) connected to the appropriate pins on Teensy AND transmitting appropriately.

Try connecting the module's '5V' pin to the 3.3V pin on the Teensy LC instead - this should bring the 'resting' reading much closer to 511, the 'minimum' figure will very likely reduce but it should already be capable of a zero reading even using 5V on a 3.3V ADC. Makes me suspicious of the pots...

while (!Serial) ; waiting for a serial connection. Won't happen without connecting to PC via USB. Look at post #4 by defragster a bit longer.

sorry, had a squiz at the circuit and just did not look at those (glaringly obvious) 2k2 resistors clear as crystal on the schematic - that I2C library enables the pullups on the I2C pins on the MCU tho doesn't it?

The I2C library uses the internal pull-ups in Teensy's processor - effectively plug and play.

My LC, one of the first batch afaik, ran your sketch with expected result; sequentially every 1/4 second no misses - maybe your LC is defective?

https://github.com/FrankBoesing/Arduino-Teensy3-Flash/blob/master/examples/LockoutReadBack/lockoutReadBack.ino All in Frank's library for a while now... https://github.com/FrankBoesing/Arduino-Teensy3-Flash

Hey nhk, I have an old pull request in on Paul's work on github that does that, you might be able to find it, might even be able to egg Paul into accepting it although it would probably be a bigger pita to him now that it has aged somewhat. I made an object for noise canceling purpose that may...

Are you still subscribed to this thread kpc? I hope you are well. I also hope I can be forgiven for being basically completely off topic here. Drop us a line mate. I am not the only one who misses you around here.

lol, good one mate - I can access my cats, and other peoples dogs, easier than a bunyip so I will hug my cats and tell them that you love them ;) (:p) Thanks for playing :D I might have an email address for KPC, if I do I will flick off an email very much hoping for a reply... I've been...

Go figure that seemingly half of my top ten favorite posters here decide to reassure, as publicly as I decided to make attempt to apologise, me so kindly :D Thanks guys, I am very glad to (at least virtually) know you all indeed. Including you folk who merely read and smiled and made no further...

hmmm. OK. Clearly I done it wrong then - the fact that I feel strong enough to apologise is (imho, at least) fair indicator that I am practically completely recovered from whatever detailed description I could give of what was not OK for me. (facepalm) re-reading this one I sense it isn't good...

EDIT: Sorry, below is obviously not well written - I am OK, if I was still at my weakest I would still just be staying away (basically). - BUT, thanks for being concerned; honestly - I have been well taken care of and have barely suffered even a little aside from embarrassment and a tiny little...

oh, just noticed that I managed to link the same page twice, I was trying to link the two I linked and the GUI: http://www.pjrc.com/teensy/gui/

I had a flick through the obvious places for this to be stated ( http://www.pjrc.com/teensy/td_libs_Audio.html http://www.pjrc.com/teensy/td_libs_AudioConnection.html http://www.pjrc.com/teensy/td_libs_AudioConnection.html ) and have to admit that it isn't explicitly stated (that I spotted for...

Yeah, when I say nuke like that I do mean your interpretation - it may be that the uninstall option is there, it may only be offering 'remove' or similar; take the strongest form you can find (uninstall should be strongest, but if remove is best offer it should suffice).

While a Teensy is plugged in you may be able to nuke the driver in 'Device Manager'; if you can boot into safe mode and access the device manager you may be able to find and nuke it without having to plug a Teensy in. If neither of those work you can take the risk which is messing with the...

It won't have less lag no matter how well you cut out the keyboard and mouse stuff mate - no quicker will it anything about it be.

You should not have to go to HID level if all you are really doing is a reasonably straightforward joystick - Tools->USB Type->*Pick one with Joystick* Beauty of "Keyboard + Mouse + Joystick" is that you can have a variety more controls on your joystick and have them drive keyboard and mouse...

Did you try just compiling GGmmGG's sketch above and testing that? If so I am reasonably convinced that your wiring must be a little off or something. Your post does not indicate that you are talking about the result of trying GGmmGG's code.

Good on you GGmmGG, very sporting of you indeed :)

Realterm has functionality to send 'any file' over any serial connection you establish with it, assuming you can stand to use Windows coz I haven't seen a Linux port; should probably admit that I haven't tried to find it for Linux because practically everything I've ever actually done with it...

1) looks like you just 'shoved' a series of usbMIDI send commands into your sketch, just after the loop() function - if you move them into the loop function it may compile but it will still fail. 2) If I tackled this I would write it as event (callbacks!) driven and I'd probably try to cater it...

If you promise yourself that Teensy will never ever be connected to both simultaneously (not even accidentally when you have been drinking or something) then you can probably get away with leaving the pad uncut - if there is even the slightest chance that ANYBODY might accidentally connect both...

I think I might Paul; I suppose just my guess being that what LERAY is asking is for somebody to modify play_sd_wav.cpp/h not only enough to allow starting playback at a given time position in the file but also to be able to specify a duration with either terminate or loop to previously given...

Yes, just the momentary pushbutton connection to ground is all you need to add to have 'reset' functionality in your project. by memory the bootloader chip is using an internal pull-up on the reset line but this memory is probably flawed - doesn't matter either way, in the overall design...

You can check 'Thread Tools', towards right of light grey bar just under the main thread title, for 'mark thread as solved' (or some similar) and click it if it is there in the installation of this forum

You need to tie their grounds together if they connect in any other way - the only way you can dodge connecting their grounds, if you want them to communicate with each other, is if you use proper isolation.

I can't see where this got corrected so I better correct myself this time: Pulling reset low halts the processor, releasing (or driving back high) the reset line will cause the processor to restart.

Answering #2 first: Provided you connect correctly, yes, you can wire your own USB connection using those pads. Pretty sure 5th line is effectively for (at least simile of) chassis GND but I should probably review the schematic in question, maybe even consult my favourite EE, before saying that...

lol, I spose I type too fast: I just type CODE HERE and, for anyone interested, I get the PHP to ignore it by wrapping the whole thing with [noparse] pseudo-tags (an unmatched tag will just display but to show the closing tag noparse is required).

What I asked you to do in my previous post would establish that your Teensy is functional, executing the sketch, and still able to communicate via USB - keeping it connected to everything you currently have it connected to would make this test more relevant; adding a little to your loop instead...

This question will attract better answers if you specify which wifi or ethernet device/module you are going to use to communicate via a network like that.

Good to see I am not the only one who misses relevant details in such posts, so, it works fine with an example, good. I reformatted your code to make it easier to hand parse - would you remove your micro SD card from the holder and run your sketch please? Interest being; do you see the "Unable...

@mxxx: I was talking about the field of amplifying signals and I was probably being silly (hardly a 'first time' if so) - just the DC blocking capacitor and a little other mitigation and it is probably safe as houses to use an opamp instead of a pair of opposingly matched transistors set up in...

I'll apologise I didn't read your post well enough to go ahead and try a reply; PC side you have far greater speed and very likely much bigger buffers, Teensy side it isn't wise to rely very much on the buffers at all - as part of my apology I wrote you the following for Teensy side; if you make...

if you break the larger data into 588 (reasonably) equal packets and then PC sends 1 byte of data to Teensy and Teensy responds with 192K/588 bytes back and when PC has those it sends the 1 byte 'request' again - PC remains in charge of the conversation at all times, conversation is reciprocal...

Opamp based circuits have a problem in this field as far as I am concerned: All too easy to get the big voltage(s) all the way back to the MCU (mitigating this is more actives than should be needed for actual purpose imho), much less likely with a well chosen pair of transistors of opposite...

Very welcome. Re: Mouse movement speed; In the last batch of code look forint responseDelay = 20; // response delay of the mouse, in ms // I made responseDelay bigger, maybe I should not have, try other values till you like movement of mouse for thumbstick - Rob.Make responseDelay...

It will probably help whoever is going to end up helping you the most with this if you post the batch of code you are compiling for this and if you have wired any connections on Teensy (not just USB MIDI after all, for example) then pictures of your wiring will help alleviate some questions like...

A reasonably basic class B amplifier ( http://sub.allaboutcircuits.com/images/quiz/00972x01.png ) circuit can be deployed to boost Teensy 3.1 0V to 3.3V DAC output to -10V to +10V range but you have problems; only 1 DAC on Teensy 3.1 and when you find satisfactory way to add 5 more DACs you need...

Try this; whether or not it does any nearer what you want, I am very tempted to write a complete sketch up for you to play with.#include <Bounce.h> /// Define Pins const int startEmulation = 2; // switch to turn on and off mouse emulation...

This is not directly compilable and I have not followed all your names nor used your readAxis function but I think this will give you more desirable control over the mouse cursor using the stick. elapsedMillis timeThis; loop() { if(timeThis>29) { timeThis=0; int16_t...

OK, so it is Adafruit's example. Open Arduino (which has been 'fitted' with a recent Teensyduino) and go to "File->Examples->ILI9341_T3" to find the example again but this time using a version of the library that has been optimised for Teensy 3.x The micro SD slot on the ILI9341 display (which...

Is this happening with code you wrote? An example? Being that I cannot see the code I am going to conclude that there must be a mistake in the code. Did you notice the forum rule above?