Search results

This sketch outputs DShot600 at 50 Hz update rate on Pin 22. Throttle is set with a 10k pot + 1µF cap to ground on pin 14 (A0). The lower and upper 5% of the ADC range are a deadband (zero or max throttle), and the sketch waits for the potentiometer to be turned to 0V before it actually uses the...

I'll check this out, but only at DShot600. I'm building a BLHeli_S-based ESC known to support at least DShot600 and I don't want to bring in another unknown. See here for ESC hardware and progress: https://www.rcgroups.com/forums/showthread.php?3494907-Building-a-BLHeli_S-ESC Might be cool to...

I modified the code above to generate one DShot frame every 10 ms, for checking with a scope: #include <DMAChannel.h> #include <array> DMAChannel dma; const uint16_t short_pulse = uint64_t(F_BUS) * 625 / 1000000000; const uint16_t long_pulse = uint64_t(F_BUS) * 1250 / 1000000000; const...

hmmmm.... I guess my T4 arrived just fine, now I can start figuring out what exactly I just unpacked

It's UPS via cologne.

I imagined that too. The customs imagine differently.

My T4 is stuck in customs because they want me to name a "realistic value" for the device. Any pointers from people in germany who successfully got their T4? What did you suggest to them? Any idea from pjrc?

Before I dig deeper: - is there a chance that I can use the T4 to control a TFT with 6800- or 8080-style parallel interface? The display I'm considering needs at least 8 data lines. 9, 12, 16, 18 and 24 are also supported - if the T4 provides them. - How much memory would I have available for a...

I like the idea of having a cpu and an fpga in one package, and many of those are available. Maybe it's just a matter of picking the right line? That way we wouldn't need to think so much about which pins to break out. I'm sure antti from hackaday would be able to point at exactly the right...

Also keep in mind that, if you create a custom teensy PCB, you can move the bootloader chip to an external (non-automotive) programmer PCB. Maybe not a nice move towards Paul, but as far as I remember, he repeatedly clarified that he doesn't have a problem with that. That might have changed...

What "same" are you interested in?

I don't think the HC4050 is really limiting speed, it's the SSD1351.

I can confirm at least 12 MHz clock on a breadboard with the adafruit 1.5“ OLED breakout board, which uses the SSD1351

The SSD1351 Max SPI clock speed is documented in the datasheet but I don't remember the exact value. It's not very high though

I think it's going to be a bit more difficult. Both libraries (the standard Adafruit_MCP21037 and your custom Adafruit_MCP210371) define the same class named "Adafruit_MCP23017", so the names clash. When you create an instance of it, which will it be? But you don't even get that far because the...

Please also show us the modified library code. It's part of the code we can't get from any other source.

You just do it, really. SCL0 and SDA0 belong to Wire0, SCL1 and SDA1 belong to Wire1 (they are broken out to the bottom layer, though, so they are harder to reach). You can use both busses in the same application.

Regarding the two datasheets: the smaller one each is not a slimmed down version of the other, they have a completely different scope: one specifies all the electrical details (speeds, currents, voltages and so on) while the other has the programming info.

I plan to support all teensy 3.5 SPIs and even ordered the board for just that. Now I just need to find time to do it. Regarding oddly sized transfers: it would probably make sense to write a totally custom implementation. The DMASPI library can't do it as it is

Please post the code that is not working (and use code tags around it to make it more readable). Are you sure that the receiver works reliably at 3.3 V? Do you have access to a scope to check if the receiver output has sane voltage levels?

https://github.com/duff2013/Snooze/issues/41

I ordered the board mentioned in the first post and hooked it up to a Teensy 3.6 with VUSB cut. No regulator. My test sketch calculates Vdd by measuring the internal 1.2V reference and then extrapolating. So the measurement is not very accurate, but should give me a rough impression of what Vdd...

I'd like to read data from a slave asynchronously. Your API explanation seems to indicate that this is possible using sendRequest(address, length, i2c_stop), but I can't find an example. There seems to be no callback when a request has been handled, so I'd have to use done() to determine if data...

we might add the constants to the header as well, to make the magic numbers disappear here it is: https://github.com/PaulStoffregen/cores/pull/255

oh apparently I totally got you wrong there. You'll need some template trickery here: https://stackoverflow.com/questions/2226291/is-it-possible-to-create-and-initialize-an-array-of-values-using-template-metapr

I have not tested this, but placement new comes to mind: http://en.cppreference.com/w/cpp/language/new I've even found an example:https://stackoverflow.com/a/4756306/692359

I'm really not sure what you are aiming for some graphical output with a touchscreen so that the user can interact with your application, or a way of graphically "programming" your application? LabView can do both, which is probably why I'm confused now.

Back then there was a bug in the Teensy 3.0 chip which made the SPI's hardware chip select pins useless for DMA usage. IIRC I read somewhere here that this has changed in newer chips. Does anyone have an overall picture of the situation? Which hardware SPI features (especially chip select) work...

disclaimer: I didn't test that suggestion. If the RAR library is trying to be smart about duplicate analog pins, we have to use RAR::update(value) which allows to use values obtained from anywhere, not just the ADC. Looks useful for values from SPI or I2C devices (anything, really). In the RAR...

responsiveAnalogRead (short: RAR) should be fine as long as it's used properly. If you feed every value into the same RAR object, it won't work for the reason you stated. Instead, create one RAR object for ech channel and use them in turn: create an array of n RAR objects: RAR_array[n] every...

From the schematic it looks like PTD10 is not broken out. If you really need it, you'll have to create your own custom PCB (which will be hard for a BGA package). You can't really "adjust pins" since PTD10 is only available on one of the BGA pads. What you can try is some sort of DMA trickery...

Is this only for products that are specifically designed for the Teensy pinout or also for products which have been found to be a good match in general?

Patched yield() declaration (https://github.com/PaulStoffregen/cores/commit/2d7cf7acddd4d2d5fcf7e13fe98c3f8b8151bf81) also helps with the Zilch library (cooperative multitasking).

I just unpacked a new SD card and plugged it into a Teensy 3.6. SdInfo: Assuming an SDIO interface. type any character to start init time: 126 ms Card type: SDHC Manufacturer ID: 0X3 OEM ID: SD Product: SC16G Version: 8.0 Serial number: 0XA4010BE8 Manufacturing date: 6/2011 cardSize...

Well if it's really way out of whack the chip will probable release magic smoke, wouldn't it?

It only took about two years to convince you: https://forum.pjrc.com/threads/28155-Why-is-SPI1-an-extra-class?p=68641&viewfull=1#post68641 Would probably be longer if this was standard arduino...

The 511 byte limitation is nasty but won't be a show stopper. Maybe I can even get rid of the 32767 byte limitation with the same "reloading pattern" in my transfer descriptors... I've ordered a Teensy 3.5 now and will look into your code and the datasheet. If your code gets it right I'm sure I...

Looks like I need to get a t3.5 after all...

DMASPI was updated and tested on a T3.6 (SPI0 and SPI1). Thank you for creating a common base for the SPIs, Paul!

Teenyduino 1.39 release, further development Now that teensyduino 1.39 is released and KurtE pull-requested me towards the fact that there's apparently a common base to all SPIs, some changes to the code were needed. What I've done now: updated the code to work with a common SPI base. This...

Success (apparently)! I think I fixed it: enable VREF_OUT and low-power buffer wait for VREF_OUT to stabilize #include <ADC.h> ADC* adc; void setup() { Serial.begin(9600); adc = new ADC(); // enable VREF_OUT and wait for it to stabilize VREF_TRM |= VREF_TRM_CHOPEN; VREF_SC =...

Problem persists, this is the code I've tried: #include <ADC.h> ADC* adc; void setup() { // put your setup code here, to run once: Serial.begin(9600); adc = new ADC(); } void loop() { // put your main code here, to run repeatedly: int value =...

Just to chime in: Some time ago I wrote an implementation of the observer pattern called signals: https://github.com/crteensy/Signals You can create a signal object that others can connect to. Both functions and methods can be connected. There has been some discussion, but I'm not sure if the...

No other opinions on this?

It seems that for the teensy 3.6, VREF_OUT can only be measured with the second adc on channel 18 (chapter "ADC1 connections/Channel Assignment"). I'll try that later today when I'm back home. Edit: for all chips: Teensy 3.2 (MK20DX51VLH7) ADC0: VREF_OUT on channel AD22 ADC1: VREF_OUT on...

Same effect when breaking it into two operations. The usage of analogRead is mentioned in the first post of this thread, in section "Other conversion sources". This usage is also in the datasheet, ADC chapter, register ADCx_SC1n[4..0] (ADCH), bandgap input. Edit: now as I had a closer look at...

So I picked a board and ran the following: #include <ADC.h> ADC* adc = new ADC(); void setup() { // put your setup code here, to run once: Serial.begin(9600); } void loop() { // put your main code here, to run repeatedly: int value = adc->analogRead(ADC_INTERNAL_SOURCE::VREF_OUT)...

@jwatte: I don't want to use the internal reference as reference for the ADC. You're right in that I'd have to scale down the supply voltage then. My plan was different: VDD (battery voltage) is used as ADC reference (as it is by default). Then I measure the internal reference voltage when it is...

Not quite. I want to run the teensy off a battery with not more than 3.6 V, probably without the regulator in between. So the controller's supply voltage is not known as it would usually be. That's why I want to compare it with a known reference, hence my question.

Before I break things: I'd like to measure the supply voltage, which won't work without some fixed reference. Can I do a conversion from ADC_INTERNAL_SOURCE::VREF_OUT (10-bit result for 3.3 V supply would be approximately 372) and calculate the supply voltage from there? Like so: value =...