Search results

You might want to delete your email. Bots will grab it and send you spam.

I tried searching the forums for Schematic Capture. All I found was a reference to some cloud based stuff. I don't want that. I am looking for a simple and cheap (less than $500, $500 is still high, but I understand good stuff costs) version of Schematic Capture and PCB Design software. It...

And this whole time I thought PJRC was Santa Claus and the boards were built by elves at the North Pole.

What awg of wire is feeding the relay board? It could be if the wire is small enough and long enough it cannot handle the surge. Using a cap at the device will help. Not sure what size of wire you might need. Car battery should be consistent unless it is drained, low on power. Is the...

I will be going down this route soon. Thanks for the warning. I plan on doing BT audio via I2S to the Teensy 4. I really am starting to dig wireless audio.

Okay, I see you are checking for a range. I was curious if the fully on PPM signal was moving around enough to cause it to move into and out of detection. That doesn't sound like the case. Do you have a scope to see if any of the control signals are dropping out? Does it do the same thing...

Isn't 2mS on the upper end of a RC PPM signal? Have you tried 1.75mS or 1.5mS to check if the signal is on the edge? Can you adjust the PPM signal trim to more than 2mS? This would ensure it is fully on.

To add to this discussion. Is the bit resolution 16 bit for all frequencies on the Teensy 4? I have looked through the chip specs and cannot tell definitively, but it looks like it always has 16 bit counter.

Yes it has the card and nice little anti static bag. Okay, good to know. Love this board so far! Nice upgrade!

I bought a Teensy 4.0 by the seller PJRC. I didn't even think about if it was legit or not. It looks like it was fulfilled by "Sports Internet Solutions LLC" even though the listing says "by PJRC". It seems to work as advertised though. How can I tell if its official?

Are you using the DMA library? Because there is/was a bug in the reference inside the library when sending the ADC0_RA reference to it: https://forum.pjrc.com/threads/26304-DMA-SPI-and-SPI-transactions?p=53378&viewfull=1#post53378 In the posted above it mentions the methods I added to get...

On what side of the chip are we talking about? The computer side or the Teensy side? If changes are made on the Teensy side that break backwards compatibility with older USB that is just stupid. Most devices have some sort of fallback. If you modify the firmware to fit MS Windows what does...

If you are slowing things down for power consumption you can do what a lot of low energy applications do: Turn off all peripherals and assign wakup interrupts to specific peripherals. Go into a low powered sleep mode. When specific events occur via wakeup interrupts process the events...

How about feeding the power supplies via diodes into something like this: http://www.ti.com/lit/an/slyt256/slyt256.pdf That will allow your battery voltage to drop really low, and give your high end some room at 5.5V. I am sure there are other regs out there to get higher voltage input than...

I am not picky. So just "PLEASE!!!". ;)

Hey Paul, I think I am starting to understand your code raw hid implementation. I think the device I am trying to emulate has multiple endpoints. So in order to see a response from the rawhid I do this: import sys import array import hid import exceptions from time import sleep VID = 0x16C0...

I did try before. Here is what it puts out when I just ran that: C:\arduino-1.0.5-r2 1.20 rc2\hardware\tools\arm-none-eabi\bin\arm-none-eabi-g++ -c -g -Os -Wall -fno-exceptions -ffunction-sections -fdata-sections -mcpu=cortex-m4 -DF_CPU=96000000 -MMD -DUSB_VID=null -DUSB_PID=null...

I am soooooo close to what I want. I have added a new entry for the raw HID device into the menu of the IDE for Teensy: teensy31.menu.usb.rawhidrt.name=Raw HID (RT) teensy31.menu.usb.rawhidrt.build.define0=-DUSB_RAWHID -DUSB_RAWHID_OVERRIDE...

Awesome, thanks for the info.

Wow! Some really great options here. @onehorse, Those EEPROMs are very nice! @Paul, I also like the idea of being able to use an SD card so that is a great surprise. My data will probably be 5 to 10 Hz, perhaps less. I still need to calculate the storage capacity I will need. Right now...

@mjhilger, I used to program PICs at an assembler level so I sort of remember some of what you are asking about. What I have found with the Teensy 3.1 is that I can read through Paul's libraries and datasheet for the micro to get some ideas how to accomplish something. There are LOTS of...

@Paul, If you do decide to add silkscreen to the product I would use a product code with possibly a batch number/date. This could only help you in the future as you can identify when and where it was assembled. Words like Teensy 3.1 are nice, but only really for a quick ident. A product code...

If these are used in a class they should be labeled according to the needs of the teacher, by the teacher. I would in addition make sure they are stored in static bags (original or new ones). There is a LOT of room on the main processor for a nice little sticky label. I think I may actually...

@kig, I was wondering if some virtual port stuff would work as well. I have a program called com0com (Windows) that will allow connections to a port and creates its own port. I think it is also smart enough to know when a port is gone. So it can help recover from misbehaving (development)...

I just created one yesterday and posted to the other thread: http://forum.pjrc.com/threads/27183-Arduino-IDE-1-0-5-r2-(windows)-serial-monitor-problem?p=59335&viewfull=1#post59335 Maybe this will give people some options.

Here is a Python 2.7 program that should do the trick: import time from multiprocessing import Process, Queue def serialProcess(oQueue): import serial #import time oQueue.put("Starting serial process") running = False # connect while not running: try...

You could write a fault tolerant serial console in Windows. It would just need to be written to expect an exception when the link fails. Doing one in Python would be simple. That is, of course, if the failure could be detected when the link actually dies. Is that the issue here? Not the...

Run the pots from 3.3V pin available on the Teensy. If they are just input there is no reason to run them from 5V.

One (1) clock cycle at 96MHz is 10 nano seconds. I don't know how long an instruction takes, but it is probably at least one clock cycle. So a NOP (if that instruction exists) could do that. This is a very fine amount of time and not really practical to provide a nanosecond function. You...

I would think this would depend upon the actual application rather than the complexity of the added circuitry. @sermad, What exactly is the "application"? On a wild hunch I searched for reading quantum states (yes, I know reading it changes it). I found some stuff on quantum randomness being...

When I read this I thought it would be good to use a transistor noise generator: http://holdenc.altervista.org/avalanche/ http://imotp.sourceforge.net/noise.pdf https://www.circuitlab.com/browse/by-tag/white-noise/ Are a couple I found searching the web. However those need quite a bit of...

Actually I saw an article somewhere on doing this with DMA transfers. It talked about creating really fast clock outputs by setting up continuous DMA transfers to a port. You will have to search, but it was ARM related and was related to the micro class used with the Teensy 3.1. Edit: Ooh! I...

Or use a MOSFET driver like the TC442x series. I am actually using these (TC4425) 3A MOSFET drivers with the Teensy 3.1 and a PWM signal on a small inductive load. If you need more than 3A you can use the TC442x drivers to control the MOSFET itself.

Why would you need RMS for DC? if you know the PWM value 0 to 255 and the voltage potential you can calculate the approximate voltage. No need to measure anything. So if your mosfet is controlling 12VDC and you set the duty cycle to 50% (127 in 0 to 255 range) then your approximate voltage...

I am successfully using analogWriteFrequency on pins 3 and 5 to have separate frequency outputs. I know if you call the function with the same value more than once it does some wonky things. So in my code I have to make sure what I write to the frequency output (for each timer) is different...

I did a quick search about malloc for MCUs and found this: https://forum.sparkfun.com/viewtopic.php?f=4&t=37114 Check out the link that is referenced inside that link. I also found this: https://community.freescale.com/thread/312130 Not sure if that is related or not. I find it interesting...

Then modify the code to read 2 analog inputs at once: //make val1 and val2 global outside of all the functions int val1; int val2; ... // inside the readMux function val1 = analogRead(analogPin1); val2 = analogRead(analogPin2); Or rework the function to accept the array itself and have it...

Ooh it is another ARM chip: http://www.keil.com/dd/chip/6142.htm This is cool. Similar to the Uno R3 with its serial Atmega interface. Thanks for the clarification.

I am confused by this thread. Does the MK20DX256VLH7 require a boot loader from PJRC or not? Or did you buy one from mouser with the PJRC bootloader on it? I don't understand that part of the discussion. Great job on doing the chip replacement. I have a Sparkfun Heaterizer XL-3000 that I...

These will NOT return a reference to the underlying code: txChannel.destination((volatile uint8_t&)SPI0_PUSHR); rxChannel.source((volatile uint8_t&)SPI0_POPR); SPIO_PUSHR and SPIO_POPR are not objects. You will have to do something like this: txChannel.transferSize(2); // or however many...

Okay, I have updated the code: #include <DMAChannel.h> DMAChannel dmaChan0; DMAChannel dmaChan1; #define ABUFFERLEN 64 DMAMEM static uint16_t analogChan0Buffer[ABUFFERLEN]; DMAMEM static uint16_t analogChan1Buffer[ABUFFERLEN]; //const volatile uint16_t* analogReg0 = (const volatile...

It all came down to pointer issues with ADC0_RA: /* Testing DMA functions of Teensy 1.20 rc2 */ #include <DMAChannel.h> DMAChannel dmaChan0; #define ABUFFERLEN 64 DMAMEM static uint16_t analogChan0Buffer[ABUFFERLEN]; #define ADCRES 16 // 16 #define ADCAVG 4 #define PDB_CONFIG...

Yep, that is one example I am looking at. You helped me a lot. When I get the everything working I will post the whole thing as an example with comments.

I got DMAMUX_SOURCE_ADC0 to work by removing the averaging settings. Now it still does not seem to capture any valid analog data it is triggering the DMA transfer. So something with the analog is still messed up. I am reading through the chip settings and trying to understand what is still...

1. Okay, I see that it is set for that in the function itself. 2. Well, when that was set to the ABUFFERLEN it would only fill half the buffer. When I set it to twice it filled it up completely. So I figured it was in bytes not number of transfers. 3. Okay, I can see that too. 4. Just tried...

***bump*** I had it "setup" the AD to channel by doing an analogRead() to at least get the input setup and fed it into the array as the default data. That data is getting overwritten by 0's so I think the DMA is working. I have no idea why the analog is not getting captured though. I think...

@zalterman, For the OP of this thread. ALL inputs to CMOS devices MUST have an input applied or you will get UNDEFINED operation of the device. I see on the breadboard only some of the inputs have connections. Use a ground and pull the rest of the inputs to ground. I have a CMOS book...

Sorry Michael, I was thinking of this chip: 74165 when i wrote that. I meant to go back and compare to see if it was indeed a shift register. I think though, that if the application is starving for processing speed using something that uses I2C or SPI is probably a good idea. Since you can...

Internally 8-bit NES controllers user 4021 CMOS shift registers. The Super NES used the equivalent of 2 in series for 16 bits. You could put as many as you want in a string. It requires 3 lines: clock, latch, and data. So 2 outputs and one input. It can be expanded to only need one...

I "think" the DMA is working, but I am getting all zeros in the analog data. So I do not think I am getting any data for some reason. #include <DMAChannel.h> DMAChannel dmaChan0; const unsigned short &analogChan0 = ADC0_RA; // to be set to proper register location #define ABUFFERLEN 64...