Search results

Thanks for the feedback. No obstructions - line of sight between central point and sensors. I rechecked the distances and the furthest sensor from the central point is about 600m. 915MHz ISM, here in the US, is probably the best choice.

I'm working on a project that involves several low power sensors that will report data back to a central point. Sensors will be up to 1km from the central point. There are a number of different radio options for Arduino/Teensy, but I'm not sure which one to select. I'm leaning toward LoraWAN...

Maybe use a conformal coating in the future?

Very nice! Do you have a BOM and/or schematic available?

Not knowing what is already being brought out, here is what I'd like to see at a minimum (based upon the K66 specs): - Two SPI busses - Two I2C busses - 1 CAN bus - 4 UART, with at leat one having RTS/CTS available - 1 I2S - 2 DAC - 8 analog (spead across the ADCs and comparators) - SDHC -...

Here is an example of a slightly bigger footprint: https://www.youtube.com/watch?v=BkJ2WbzO6dI A Teensy ++ with a 22x9 pin dimension would be good. Or, stop worrying about breadboard compatibility (sell a ++ specific bread/breakout board?), which frees you up quite a bit when it comes to form...

That looks like a nice chip! Please, for the love of dog, no bottom pads! They really are not that easy to use and are almost a waste. I really wouldn't mind a significantly larger form factor for this much more powerful processor. I think this becoming less of a concern that it was a year...

As someone who has dabbled with developing my own Teensy 3.1 PCB for a project I'm working on, but here are my thoughts for a ++: - If the 3.1 would have had all the pins broken out in a manner where they were easily usable, I wouldn't have even considered building my own (conversely, building...

Specifically, I'm using U8Glib and SDfat on the SPI bus (spi4teensy3, Arduino 1.6.5 and TD 1.24). With the hardware using CS pins 6 and 10 and specifying that in the appropriate code location, it works. I try pins 15 and 20 and the same hardware and changing the CS pin in the code, it doesn't...

Is there any trick to using the "alternate" CS pins for SPI (2,6,9,15,20,21,22,23)? I'm trying to use 15 and 20 as CS pins, but not having any luck. Same setup using pin 10 works fine. Thanks!

I want to replace a micro sd card.

What method are you using to read/write? Any possibility of accessing these memory chips using a FAT files system or similar? How about across multiple memory chips?

So I had some time today to look into this further. I put hot air to the Mini54 trying to make sure all the solder points were good, but that made no difference. I pulled the Mini54 and checked the traces to it while powered up without the Mini54 and everything appeared OK. I installed a new...

Yep, been down that road. I'm using the 5mm QFN Mini54, so checking pins for shorts is a bit more difficult, but I don't see any shorted pins under magnification. Time to triple check everything again. What other signals should I be seeing on the various Mini54 pins?

I saw that in one of the other threads. Pointers to where I should look for a problem are appreciated. Thanks!

I've built a custom PCB based on the Teensy 3.1 schematic from PJRC and I am using a Mini54 purchased from PJRC. On power up, it doesn't appear the Mini54 is properly communicating with the Mk20. I've read through the links on the PJRC Mini54 page and I don't appear to have any of the issues...

Are there any practical solutions currently available that can be used to replace a modest size (4GB) SD card?

She's self mounting!

Take a look at the examples in the TinyGPS library. There are several there. You'll also want to look at the Time library for Teensy 3 specific time related code. Don't forget to add the appropriate crystal to the Teensy 3 board as well.

Unless you have space constraints...

Those are the only ones I'm aware of. I have the Osh Park one.

We need to see the full code and a hardware schematic wouldn't hurt.

Let us know how it goes! I have one of the modules, but I haven't used it yet. Soon hopefully.

Bluegiga WF121

Yes, that should work.

I found a new 6DOF sensor. Properties: Optical analog output Low power consumption The gyro tends to tumble above 5g, but it is self resetting Output is inverted Surface mount I call it the JRT-6DOF. Scroll down for a photo. That's Chloe the Jack...

One thing I noticed is the signal line under the 16MHz crystal. I remember reading somewhere that you shouldn't have a signal line running under it. Not sure if it's related or not.

Thanks. The application is for a motorcycle - acceleration, lean angle, compass. I probably bodged something on the last one, plus I soldered pin 33.

Onehorse, what 9/10DOF boards do you have available right now?

I'm looking at buying a hot air rework station and am looking for recommendations. I don't want to spend a crazy amount of money, but I am willing to buy quality if it's not a huge amount. Ideally I'd like to be under $300 for a combined hot air/solder station. I think I want a vacuum pickup...

Thanks Paul!

Thank you everyone! Any info on the ferrite beads?

As part of a project I'm working on, I may want to build my own integrated Teensy 3.1 (using a MINI54 from Paul) and I have questions about what components are used on the Teensy 3.1. Based on the schematic available, I'm looking for make/model/value for the following components: - Diodes...

Yeah, the Teensy is in some odd state now. The PC only sees it as a "USB input device" (or something like that). I'm out of time for the next few days to mess with it, but I'll get back to it next week.

Yes, the Teensy itself isn't recognized by the PC. I thought I got one of the newer boards where you fixed the pin 33 issue, so I soldered all the pins. Of course, trying to unsolder it from the Teensy was pretty much impossible and I ended up pulling a pad off the Teensy and the copper out of...

Onehorse, I bought a LSM9DS0 Teensy 3.1 Micro Shield a while back and finally got around to soldering it on to a Teensy 3.1. However, I'm having an odd behavior with it - my computer running Arduino IDE doesn't see it on the USB port. Another Teensy 3.1 plugged in to the exact same setup is...

Getting hardware SPI working for both the display and the SD card makes things "just work." The display works great and data is being recorded to the SD card properly. I'm finally making good progress on the software side of things now! Just a few more things to get done in software and I'll...

Getting hardware SPI working with U8Glib at least has allowed the display to work. Now, SDfat is sort of working - empty log files are being created. Not sure if it's an SPI problem or a code related problem, yet. Off to dig some more...

I finally figured out how to make hardware SPI work with the NHD-2.7-18650 display. I had the following statement in the code: pinMode(15, OUTPUT); // Data out to OLED display - SPI2_SI on NHD display Removing that line fixed it and it now runs great. Not sure why it causes a problem, but...

I'm using a Teensy 3.1 along with a SPI based SD card using SDfat and a SPI based OLED display using U8Glib on the same SPI bus (with separate SS/CS lines). So far, each one works by itself, but both together do not work (as I expected.) The display is using software SPI, as I haven't been...

The only correction was to use proper address spacing. For a byte, I used a spacing of 8 bits, a float 64 bits, and a double 128 bits. const unsigned int doubleVal = (sizeof(double) * 8); const unsigned int floatVal = (sizeof(float) * 8); const unsigned int intVal = (sizeof(int) * 8); const...

Had some more time to dig into this. Of course, it turned out to be something simple - I got "bit" by the bit vs byte size difference. I thought I was giving the NVRAM addresses in bytes, but I was actually specifying the address in bits. This caused the data addresses to overlap which in...

Ok, so adding a delayMicroseconds() didn't help. Time to dig into it deeper...

Pete, thank you for the pointers. I'll try hacking with a delayMicroseconds() first to see if that solves the problem and if it does, then go for a solution that waits for the NVRAM to to acknowledge the write being complete. I should probably look at page writes as well.

OK, I finally had time to get back to this. I can write and read a single byte value without problem, but I'm still having problems with multi-byte values not writing and/or reading properly. Again, any ideas are appreciated! Here's the current code: // //#include <i2c_t3.h> //#ifdef...

Just a quick follow up - replacing the NVRAM chip fixed the problem.

Looks like the timing is right. Here's the results from a speed test: Going to test single byte writes and reads Time taken for 1000 writes with one byte was: 44299 us Write time per byte, in microseconds: 44 ------------------------- Time taken for 1000 reads with one byte was: 93049 us Read...

Thank you! I'm pretty much a hack programmer, so I really appreciate the feedback. I modified my code, using your example. However, I'm still getting essentially the same result. Again, any ideas are appreciated. #include <i2c_t3.h> //#include <Wire.h> #define DEBUGNVRAM const int...

OK, now that (I think) I fixed my I2C issues, I'm seeing odd behavior read/writing data to the NVRAM (Adesto RM24EP32). If I write values of zero to the NVRAM a subsequent read returns zeros. But, if I write non-zero numbers to the NVRAM, it returns either 0, 4294967295.////// or...

I bread boarded a Teensy 3.1 and the NVRAM chip. I used the same 3.3v dc-dc power and used 4.7k pull ups on SDA/SCL and the Teensy sees the NVRAM chip using a basic I2C scanner sketch. It's wired exactly as shown above in the schematic. Now I'm really stumped. Only thing I can think of is...