Show Posts
Pages: 1 2 [3] 4 5 ... 41
31  Products / Arduino Due / Re: DUE PWM Frequency on: March 22, 2014, 01:01:36 pm
.... wanted to solve my problems in small steps this is why I didnt say from the bgegninning all what I need.. I thought that It could be a good way solving my problem..

What words or images could have shown you the error of this assumption?

When someone else comes here with questions and again would make this same mistake, how could this forum (or similar technical forums on other sites) instruct people to ask their questions in a more effective manner.

Obviously, this lengthy "How to use this forum" page did not help.  Did you ever see that page, or read it, before posting?  What could have helped you to understand the proper way to ask technical project questions?
32  Products / Arduino Due / Re: DUE PWM Frequency on: March 21, 2014, 06:30:27 pm
Quote
This guy is a bit of a time waster, he keeps asking the same questions and never ever states what his requirements are.

Yes, you're absolutely right.  Many people ask questions in this very ineffective style, but this guy is particularly bad.

I keep hoping to find a way to impress on people like this how to better ask their questions.  Sticky threads help a bit, but obviously some people do not read them.  On the PJRC forum, I've been intending to look into how to edit the HTML templates for the forum, so posting guidelines can appear right above the text entry box when starting a new thread, and perhaps a reminder can appear right next to the button to submit the message.

These people not only ruin their own chances for getting useful help, but they waste a LOT of time from everyone else... time that could be better spent actually helping people who've posted sincere questions with adequate detail.

@so3ody - If you're still reading this, *why* have you posted so many questions with so little detail?  You seem to want help with your PWM waveforms.  Can you see how your poor writing has ruined your opportunity for good answers from knowledgeable and helpful people?  What words or messages might have inspired you to write better questions?

If anyone has any other ideas about what arrangements of pixels might somehow inspire people like this to write better questions, I'm really, really interested to hear.  It's a tough problem, and perhaps can never be fully solved, but even small improvements could really help a lot of people in the long run.
33  Products / Arduino Due / Re: How to generate SINE PWM on: March 18, 2014, 06:54:18 pm
You have a 2 channel scope.  Use the 2nd channel to look at one of the 2 other waveforms, while still showing the 1st waveform.
34  Products / Arduino Due / Re: Comunicating ADC+ Arduino DUE with the protocol 1-wire on: March 18, 2014, 03:15:46 pm
30 meters is a very long distance for 1-wire communication.  If you get this to work, which is unlikely, it may not be very reliable.

(I am the current maintainer of the OneWire library, by the way...)

Usually such long distances are done with 4-20 mA analog current or RS-485 serial.

35  Development / Suggestions for the Arduino Project / Re: Compile Speed - testing & feedback needed! on: March 16, 2014, 01:01:25 am
Oh, yeah, I fixed this a very long time ago.  But the fix has never worked its way back into the official Arduino sources.

Here's the code with the fix, if anyone's interested.
36  Products / Arduino Due / Re: DUE PWM Frequency on: March 14, 2014, 04:38:40 pm
Is that really all you need?  Just a moment ago you threw in a H-bridge requirement, but without specifying what signals it needs.

Maybe you really need 6 waveforms, with some sort of non-overlapping dead time?
37  Products / Arduino Due / Re: DUE PWM Frequency on: March 14, 2014, 03:54:02 pm
Usually H-bridge driving is done with a pair of PWM signals that have a "dead time" between them, rather than the overlapping "phase correct" type of signal on 8 bit AVR chips.

But then, who knows what's really needed here.  There's very little accurate description and a lot of complaining, which is hardly a good approach to asking for free tech support / help on a forum!
38  Products / Arduino Due / Re: DUE PWM Frequency on: March 14, 2014, 02:47:45 pm
Are you now saying you need two PWM outputs, with some special timing relationship to each other?
39  Products / Arduino Due / Re: DUE PWM Frequency on: March 14, 2014, 02:30:46 pm
I should mention this works on Teensy 3.1, but hasn't been ported to Arduino Due (and may never work on Due, since Due has the Cortex-M3 chip and a lot of this code depends on the DSP extensions on Cortex-M4).  With that caveat in mind, here's the link.

https://github.com/PaulStoffregen/Audio

To get a sine wave, you'd write a sketch with an AudioSynthWaveform object, an AudioOutputPWM object, and one AudioConnection object to feed the sine wave from the synth to the pwm.
40  Products / Arduino Due / Re: DUE PWM Frequency on: March 14, 2014, 02:16:56 pm
The PWM output object on the (currently beta test) Teensy audio library supports this.
41  Products / Arduino Due / Re: DUE PWM Frequency on: March 14, 2014, 02:11:50 pm
What exactly is a "SINE PWM" wave?
42  Products / Arduino Due / Re: WS2801 and WS2811 based RGB LED Strips with Due? on: February 26, 2014, 08:22:26 am
Flickering problems might be timing related, or they might be voltage related.

If the strips are just barely able to recognize a 3.3V signal, flickering can happen when they draw enough current to cause small (or perhaps not-so-small) changes in their ground voltage, due to the resistance and inductance of the wires between the LEDs and power supply.

Some of the newest strips are having more trouble with 3.3V signals.  I have one "grumpy" strip here that won't recognize any 3.3V signal, even under perfect power conditions.  Most do work, but the margin for error in voltage is very small.

I'm making a little shield for Teensy 3.1 that has the 74HCT245 buffer, the 100 ohm resistors, and RJ-45 connectors.  It'll be available in 2-3 weeks.

You might need to do something similar for Due.  The 74HCT245 chip and resistors are cheap, so I'd suggest you do that before fiddling with the timing.  If you do get into timing stuff, you really need an oscilloscope or logic analyzer to view the waveforms.
43  Products / Arduino Due / Re: Building a CAN API for Arduino DUE on: February 22, 2014, 08:18:24 pm
Did you select Arduino Due in the Tools > Boards menu?

Those errors look suspiciously like the kind that occur when compiling Due-specific code for an AVR-only board.
44  Products / Arduino Due / Re: Building a CAN API for Arduino DUE on: February 19, 2014, 12:15:01 pm
I know this might be nitpicking and it's probably far too late to change now, but...

A common convention for names in all caps and with underscores (eg, "CAN_FRAME") is for constants from #define.
45  Development / Other Software Development / Re: Rotary Encoder Library on: February 14, 2014, 08:31:14 pm
The other other possibility (if my AltSoftSerial library doesn't solve the interrupt latency conflicts) would be using a different Arduino compatible board which has an available hardware serial port.  Since I'm the creator of Teensy (full disclosure), of course I'd recommend using a Teensy.  All of them have a free serial port.  Teensy 3.1 has 3 hardware serial ports, yet it's very affordable.

I believe Arduino Leonardo, Micro, Mega and Due also have extra serial ports.

But since you said you were already using an Uno clone, I'm guessing buying a more capable board is not an option?

I'm also curious, did you buy a cheap clone?  Not even a single penny goes to support the Arduino project, nor 3rd party developers, who write the libraries you're using, like Encoder and AltSoftSerial (I'm the author of both, and I can tell you both Encoder and AltSoftSerial development was funded through sales of Teensy boards).  The people who make those extremely cheap clones don't develop any software or libraries.  They usually don't answer any technical questions.  They usually don't even host a forum for questions, instead sending their customers to get support here, from those of us who are funded by sales of the name brand boards.

The extra cost of those boards pays for all this software and library development and resolving of technical issues.  I hope anyone reading this will keep that in mind when considering cheap no-name clones.
Pages: 1 2 [3] 4 5 ... 41