Search results

Well, looks like I'm rather late to this party! I haven't read through the thread yet, but definitely interested to get one of the round 3 boards! I'll probably try and do some weird MIDI things with it, specifically seeing how easily I can port over my multi-port MIDI stuff, that kind of...

I'll just chime in, and note that USB data lines should be kept in parallel (in Eagle you can 'link' two traces by labeling one _N and one _P, I believe). There's also a function to add a little bit of length to only one side of this differential dual-trace, so that both traces are the exact...

I would like a build tutorial for this! Have a few floppies sitting around, would be fun to play with. *Edit: because it looks very cool!

Ooooooh! Works here fine, OSX 10.9.5. I built using the OSX 10.6 SDK (10.5 SDK was giving me a 'clang' error). Tested uploading to a custom-PCB teensy, works a charm! I can attach my built file, if anyone wants it.

From what I recall, it's something along the lines of this: On Mac, the USB/IO library doesn't actually work as documented. Specifically, a function that is designed to wait/callback after a request is sent doesn't actually do anything. Nothing I've found seems to indicate it's been fixed (Paul...

How's the inventory looking like on the old MINI54 preprogrammed chips?

I'd be interested in that 'hello world' swift app - i think. I haven't bit the bullet and upgraded to Yosemite yet, so apparently Swift 2 is unavailable to me. Mostly I'm interested because I'm, at some point in the nearish future, attempt to get the teensy_loader_cli working in OSX (somehow...

Probably half of those views are from people like me, who just enjoy the drama this thread has created. If you want to run a company that way, you're free to - Paul has no obligation to run his company to your standards. Paul can do what he likes with his company, and there's really not much...

Well, playing devil's advocate to myself from earlier in the thread, there ARE moments when custom PCBs are necessary. Since my latest version of this device is almost entirely SMT, there were a couple components that just... didn't have a breakout board. At all. Namely, my cypress USB hub...

@mxxx, I guess you and i go about things very differently - I'd much prefer to breadboard something first, and then make a PCB once I've confirmed the breadboard schematic. That's what breakout boards are for. Yes, PCBs are pretty cheap, but I still can't design a schematic and get a PCB made...

I've only ever used a teensy on a breadboard for prototyping (and then designed a custom board around the Teensy 3.1 schematic). For prototyping, breadboards are... there's nothing better. Keeping the option for a teensy to sit in a breadboard is very, very important. It doesn't need to last...

Depending on the final goals for this project (are you planning to sell it? as a kit or a 'finished device'?) you might be fine and it might be terrible. USB can be finicky - if you do use jumper wires from the pads, make sure they're all *Exactly* (or very, very close) to the same length. USB...

I've been using these: http://www.digikey.com/product-search/en?keywords=HFZ040CT-ND in a product. They certainly aren't cheap, but they work very well and keep a very strong connection once locked. Pain in the ass to hand-solder, though.

The 144 (.5mm pitch) wouldn't work? I mean, i'm assuming it wouldn't work due to the sheer size of it, but .5mm pin pitch isn't bad at all. The current 3.1 chips are .5mm pin pitch. Edit: the .65mm/.4mm BGA pitch would be a nightmare to route - vias-in-pad would be the only way I could think...

I found this: http://makezine.com/2010/11/30/usbhacking/ So that should... work? I'm not sure. It seems a bit overly complex, to me - your whole collection of bits to get these two particular things talking to each other. I'd think it would be simpler (and probably cheaper!) to find something...

Most companies would also go out of business if they listened to every harebrained scheme from every single customer and tried to act on all of them. PJRC has been very clear that they're not interested in doing this - what they've been doing is working well for them, and it's not in their best...

I feel like t3andy is... overvaluing his own views on this. I am currently in the process of bringing a T3.1 based device (custom PCB using PJRC Mini54's) to market, and while it is a lot larger than what is being proposed here (my PCB is 280mm x 220mm), a lot of this stuff applies no matter...

This will be more difficult than you realize - there have been some advancements in this area, but I haven't used them so I can't comment on how well they work. Essentially, the Teensy (right now and 'officially') only works as a USB Device. You need it to act as a USB Host. Furthering that...

Heh, the Teensy Jumbo.

From PJRC's perspective (I'm assuming a lot of things here) it probably makes more sense to focus on the ++3.1, as opposed to devoting development time to the 3.1. As a power user myself, I would probably rather have a fully broken out ++ 3.1 compared to a fully broken out 3.1 - there's already...

Technically, there's nothing really stopping anyone else from making one - as long as you get the MINI54 (or whatever the replacement one is going to be in a few months) from PJRC. I've built a custom PCB (actually at this point I've made about 16-20 of them) with two 'teensy' sections on it...

Aha - it seems like it should be fine, then. Essentially, from the Teensy 3.1 schematic on the site, I've 'removed' the 470ohm resistor between VDDA and VREFH (I'm replacing it with a 0 ohm resistor). Since VREFH is now just linked to VDDA, it shouldn't ever go 'above' VDDA (they'll be...

So, I guess I did a dumb - my custom PCB has some potentiometers (from joysticks) running between GND and AREF, and other parts (motorized faders) running between 0 and 3.3V. This seems to be a problem, as the faders will hit a certain point (right at 2.65v) where they 'max out' the ADC and...

As far as I can tell (I've run into this issue as well) it's a strange bug in OSX 10.9 (and possibly 10.8). It doesn't seem to pop up in 10.10. The fixes I've managed for it are: You can try just hitting 'rescan MIDI' in the MIDI studio app, sometimes that works. Or, you can make a new...

Alright, one other question then - will Teensy Loader continue to recognize both types of chip? I could foresee myself ending up with two types of PCB, one MKL and one Mini54 - and it'd be nice if I don't have to have a different firmware updater for each 'type' (my end users wouldn't be able...

Will the MKL02Z32 used for the 3.1 keep the same form factor as the old Mini54? I have a design using the Mini54 that'll be going through FCC certification soon - while I'd rather not have to get it recertified due to the chip change, I'd REALLY rather not have to redesign my PCB around an...

I use an L293DD (might not fit your requirements exactly). I'm building mine directly onto a PCB alongside the two Teensy processor chips, so I have a bit more control over various things as well - I give it supply voltage direct from 'USB' voltage (or external voltage). It's got enough range...

I hope he comes back and informs us of the grade he got.

Can I vote twice? Either way, thought I'd pop in to say I have worked out a (rather roundabout) way of using the graphical Teensy Loader as a sub-process. My little app runs the various command-line tools as necessary, which pops up the GUI loader when it actually does the loading. Once it's...

To play devil's advocate to jakorten... I was never really able to bite into the actual arduinos. They never quite did what I wanted them to do, which made it much more complicated to try and force them to do things that didn't already have large, well defined tutorials and code bases. I only...

Oof, first I'm hearing of this. Wonderful! Is the DE a drop-in replacement for those of us with custom boards?

The big important ones: Crystal: http://www.digikey.com/product-detail/en/TSX-3225%2016.0000MF09Z-AC3/SER3628CT-ND/1802879 (Not the same one Paul uses, I don't think, but one I use that seems to work well) Processor: http://www.digikey.com/product-search/en?vendor=0&keywords=MK20DX256VLH7...

Just so it's known, I've noticed similar behavior from OSX 10.9.5. The name, and often the capabilities (I've been experimenting with multi-port MIDI again), won't refresh in OSX's System Report, or the Audio MIDI Setup app, without swapping out an ID number. Annoyingly, I've no idea WHERE OSX...

If you've changed the Vendor ID or Product ID from usb_desc.h, you lose the auto-reboot function (and thus auto loading sketches). The teensy loader app is looking for something with a specific range of ID#'s to send a reset signal too.

With the Teensy 3, the locations of the USB-type ID#'s, manufacturer names, and product names has changed. It's quite plausible that you could essentially make a 'fake' second MIDI type, which shares the exact some values as the original MIDI except ID# and product name. This thread...

Got my LC - I'll be testing the USB-MIDI library, as well as possibly testing an ILI9341 over parallel 8bit connection, and probably a number of other things! Blinky and USB uploaded work as expected.

It works just fine - and everything Paul has said in this thread is perfectly true. It's just not an AVR processor (you never mentioned that that was a requirement). The Teensy ++ 2.0 is AVR based, as is the regular 2.0 (AT901286USB and ATMEGA32U4 respectively). Coding for the 3.0/3.1 with...

Paul, is it this one? http://www.digikey.com/product-detail/en/TSX-3225%2016.0000MF18X-AC3/SER3636CT-ND/1825448 I kind of doubt it, but I would be tickled if it were (that's the one I use on my custom PCB).

Well, that's probably your problem then. Teensy 3.1 is not an AVR processor, it's ARM based. Trying to compile Teensy 3.1 stuff for AVR probably isn't going to work, and even if you somehow got it to compile it wouldn't run on the chip.

stevech - I'm in the opposite boat. I'd actually prefer if the 3.1 was a bit longer, so it didn't need to have those pads on the underside (which generally means I then need to also buy an adapter if I want to breadboard with them and not destroy the board when I yank it from the breadboard)...

As to the jumps... It's a lot more complicated, but whenever you take a reading, keep your previous reading as well (you'll need two variables). That way, you can then do something like this (again, pseudocode): prevValue = value; value = (prevValue * 0.1) + (analogRead(whateverThatPinWas) *...

I'm not completely certain, but I'm relatively sure that Map() doesn't like negative numbers at all - do an absolute on your negative numbers to remap them. It also doesn't like going 'backwards,' as I recall. You'd have to do something like (pesudocode): if(outty<0){ outty = outty * -1...

I haven't looked at your code (please encapsulate it in CODE tags, it's very hard to read otherwise). MIDI doesn't do negative numbers natively - it generally (except pitchbend) only deals in 7-bit number: 0-127. You can do tricksy things with that, though, such as taking a higher bit number...

Stevech, if it's fast enough 200KB of RAM and that much flash storage would probably make for a very, very nice, relatively large screen driver. Full 640x480 touch display with Alpha, mmm.

Sorry, but there are things Teensy is far, far better suited to than a Pi. Just because it's similarly priced and technologically more powerful, doesn't mean it's the best tool for the job. I've been struggling to come up with a project that would make sense to do with a Pi, but I have tons of...

Great, thanks Paul!

Quick question - what's the clock speed of the MINI54? Is it set to the default/maximum 24mhz? I ask mainly for EMI testing reference - last time I went into the test lab we didn't notice anything around that range, but I'd like to know what speed all my various processors are running at.

Thanks, Paul! Never actually expected to be one of those 'top contributors!' If there's still any available, I should have time to beta test now. I'll probably do some MIDI tests (especially to see how difficult it'll be to get it running my 3x-ports HID descriptor setup), and perhaps using...

Quoting some relevant seeming stuff from that document: Now, most of this doesn't make much sense to me. The way I understand it is that it'll essentially only update those pins' states at every 'filter clock' cycle, which can be made to be slower than the usual clock cycle? Basically a...

I'd also be curious if it'd be possible to... 'roll your own.' It'd be a bunch of trig, I'd expect, but it shouldn't be TOO hard to just wire up four capacitive sensors from Teensy directly, and use those to map a 3d position. Wouldn't be multi-touch, of course, but I don't think the Pimoroni...