Show Posts
Pages: 1 2 3 [4] 5 6 ... 42
46  Products / Arduino Due / Re: DUE PWM Frequency on: March 30, 2014, 10:28:11 am
Even if these things are difficult or impossible today and here on this forum, they may not always be so unattainable always and everywhere.

Incomplete, time-wasting questions are a huge problem on every forum that tries to offer support for novices on technical platforms.  As the technology becomes more advanced and even more absolute beginners enter the community, it's an ongoing problem that's becoming more and more worthy of difficult work to customize forums.

Of course, as the creator of Teensy, I'm interested in trying to improve the PJRC forum.  I'm also interested in sharing these types of improvements, just like I try to contribute Teensy's improvements back to Arduino (which is another excellent example of something that isn't always easy or even possible, but still worth trying).  Helping beginners is something I care about doing.  Every day I answer lots of questions.  Every day, I waste time asking people to post info they should have put in their original question.  Every day, I see conversations that would have produced useful or more relevant answers if only the question had included better info.

Even if the ideas get tried first on my own forum, or any of the many other forums for various arduino-compatible boards, I think it's worthwhile to brainstorm ideas.  Even if they're "hard" in the context of today's forum software, in the long term some way to improve is needed.

Things will only get better if someone tries.  I know I want to, even if I have to dig into thorny forum customization/programming.  I'm really interested to hear any ideas of how forums could guide novices to ask better questions, so they get better answers and everyone's time is wasted less.  Even if those ideas seem impossible on today's forum systems, time, persistence and ingenuity have a way of making anything possible in the long run.
47  Products / Arduino Due / Re: DUE PWM Frequency on: March 22, 2014, 01:09:05 pm
You did not answer my question.

I want to improve how new people, like you (only days ago), see forums *before* posting their first question.  If you had known this before writing all those questions, you could have received better answers and avoided wasting so much time from the most knowledgeable and helpful people.

The question: how can these forums help new people, like you, to post better questions?

Please, consider you have consumed so much time from so many people.  The least you could do is offer a little help to improve the process for everyone in the future.

What could have shown you, only a few days ago, how to ask a better question *before* you wasted everyone's time?
48  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?
49  Products / Arduino Due / Re: DUE PWM Frequency on: March 21, 2014, 06:30:27 pm
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.
50  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.
51  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.

52  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.
53  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?
54  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!
55  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?
56  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.

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.
57  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.
58  Products / Arduino Due / Re: DUE PWM Frequency on: March 14, 2014, 02:11:50 pm
What exactly is a "SINE PWM" wave?
59  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.
60  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.
Pages: 1 2 3 [4] 5 6 ... 42