Recent Posts

Pages: 1 ... 8 9 [10]
91
Sorry. I was want to say "board" instead "card". I'm using another language. I selected board and port correctly. Meanwhile when i wrote this code, there was a circuit that i had used 0 and 1 pins because of bluetooth module.

Sorry for my bad English. I hope you understand me.

I have %50 fixed this problem. When i don't use 5V, codes are being able to upload on Arduino. So first, i remove the 5V and Gnd pins and i'm uploading the codes, after those, i connect 5V and Gnd.

I'm using 0 and 1 pins because of Hc-06 Bluetooth module
92
When you're programming C++, for instance on a PC,  you're still using libraries to handle networking, or graphics or other things
So what I meant - I think I expressed myself unclearly - is, that I want to know how to write the whole thing and how everything works.

Compressed C++ File in Energia/Arduino

This is how the Energia and Arduino sketch looks like for BlinkLED but how to implement a libary and what libaries and what is inside of this libary stays unclear and I want to learn that, so I can understand this:

The C++ in Code Composer Studio

This is the BlinkLED sketch with plain C++. On the left side you have the file direcotries, which is supposed to be tough (from what I heard) in the middle is the code that tells to blink the LED on the microprocessor kit and on the right side there is the header file and I want to understand this header file and for what the header file is good.

I hope that was a little bit clearer
93
The SDA is the serial data and the SCL is the serial clock. When the clock is high the databit should be stable. Instead of 8 clock pulses a nineth clock pulse is added for acknowledge.
Both SDA and SCL go in both directions, they can be pulled low by both the Master and Slave. With that, a few extra special things can be done.
Many devices can be connected to the same SDA and SCL.

SPI uses seperate signals for data in, data out, clock, and chip select. There is a chip select for each seperate chip. It is often a lot faster than I2C.

There is also Serial communication with RX and TX signals.

Each bus has its own advantages and disadvantages.
It is not just these three, there are more ways to let Arduino boards communicate with other processors.
94
Deutsch / Re: Wort-Uhr und die Frage nac...
Last post by Mattn - Today at 01:29 pm
Ich nutze mal diesen Thread :-D

Ich hoffe es greifen genug Leute drauf zu.

Folgendes Problem:

Kumpel und ich habe uns eine Wortuhr gebaut.
Holzplatte 50x50cm

verbaut wurde ein raspberry pi.

Bauanleitung:
http://rpi-wordclock.readthedocs.io/en/latest/doc_hardware_setup.html

Holzplatte:
http://www.leuchtbildshop.net/epages/64015097.sf/de_DE/?ObjectPath=/Shops/64015097/Products/CL-50er-ZP-01


benötigte Buchstabenfolge muss so aussehen:


Hier unsere Datei dir wir versucht haben, auf 50x50 anzupassen....allerdings scheint noch was nicht zu stimmen. Habe das Gefühl sie meint immernoch 45x45 zu sein.
Denn wenn man sie in inkscape öffnet, sieht alles gut aus. Exportiert man als pdf...dann sind die Minutenpunkte genau am Rand (haben normal einen Abstand von 2,5 zum Rand)....
https://www.dropbox.com/s/rg8pki65x99kkzy/stancil_front_final.svg?dl=0

Kann da wer von euch helfen?

Danke

Martin
95
Arduino Yún / Re: Yun ADC resolution
Last post by ShapeShifter - Today at 01:27 pm
How can I know which is the real maximum voltage in the analog pins so I can do an accurate calibration?.
The most accurate way is to use a precision voltage regulator that feeds only the AREF pin, and then use the external reference mode.

The issue with using the Vcc reference is that it can vary, especially due to switching transients and other loads that are on the power bus. These transients will cause noise in your converted values.

Quote
There are some way to force any pin to give me always the maximum votage so I can calibrate every X time the YUN programatically?
I think you might be misunderstanding what I mean by calibration. It does not involve taking the reference voltage and calculating bits per volt, and then scaling that to the pressure reading. Those are all theoretical values. There will always be some part-to-part variations in the reference voltage, the analog converter, the sensor, and any conditioning circuitry. By calculating theoretical numbers, you will get close.

But to really calibrate it, you need to take a series of measurements at a wide range of known pressures. For each known pressure, record that physical value and the corresponding raw analog reading. When you have a bunch of such samples, calculate a linear estimation fit of the points to come up with a slope and offset values (y = ax + b) where "a" is your slope, and "b" is the offset. Once you have those calibration values, you can convert any raw analog reading "x" into a scaled physical value "y".

Using a method like this, you fine tune the theoretical scaling factors, and end up with a more accurate converted value. This will calibrate out any variations on the analog reference voltage, and any part-to-part variations. In reality, the actual reference voltage is not so important (as long as it covers the required range) as it will be taken care of during calibration.

If you are making multiple units, each one will need to be individually calibrated.

Quote
So If I take as a reference voltage i.e 4.5V I will get

0.5 V  --> -2000 Pa  --> 114  bits
2.5 V  -->       0 Pa   -->  568 bits
4.5 V -->  2000 Pa   --> 1023 bits

Am i right?
Theoretically, yes. But you won't necessarily get exactly these values due to the variations inherent in every part of the chain. That's why you calibrate, to get more exact values.

Quote
On the other hand with this sensors voltage range I couldn't use the 1.1V Internal reference voltage If I understood.  
Correct, the 1.1 volt reference will not be useful in your application, as it will severely limit your range of measured pressures. You could divide the sensor voltage to get it down to the 1.1V range, but that could increase the amount of noise in your samples.
96
Displays / Re: ILI9341 - Fast library wit...
Last post by casemod - Today at 01:26 pm
Edit like this:

Code: [Select]
static uint8_t conv2d(const char* p);  //.kbv add forward declaration.

uint32_t targetTime = 0;                    // for next 1 second timeout
uint8_t hh = conv2d(__TIME__), mm = conv2d(__TIME__ + 3), ss = conv2d(__TIME__ + 6); // Get H, M, S from compile time


Cool, that did the trick.

Regarding 1.06 I was referring to post #6, just to confirm whenever changes on the new version would make it compatible - Hopefully this will avoid others having issues and not knowing why.

The fonts load fine on the clocks its just a part of the screen is not initialized. Again, this works fine on 1.6.x

97
Quote
Everytime I open the Arduino IDE and create a new sketch I feel so dependent and I don't like this feeling
So use an external editor such as Notepad++ and start with a blank edit screen.  Write your own functions to read inputs, change the state of outputs etc by addressing the Arduino registers directly and while you are at it write your own main() function and another to initialise the hardware but don't cheat by looking at the existing ones.

You have access to all of the normal C++ functions such as sprintf(), and the str* functions to allow manipulation of strings for example.  I assume that you do not object to using those in your programs so why do you feel dependant on the Arduino environment ?
98
A shift register only has digital outputs, so that you can turn attached LED either on or off. As already mentioned, PWM can be used to turn a LED continuously on for a short time, then off again, to achieve a variable brightness. A dedicated PWM output pin produces such a signal in hardware, when you specify with analogWrite a duty cycle between 0 (fully off) and 255 (fully on). But this works only with specific PWM pins.

With a shift register you have two choices. If the shift register has an output enable pin, that allows to disable all output pins at the same time, you can connect a PWM signal to that pin, in order to control the brightness of all attached and turned on LED, at the same time.

Otherwise you have to shift out the on and off patterns continuously, so that the on time of every LED reflects their individual brightness.
99
Deutsch / Re: 2.42 I2C OLED funktioniert...
Last post by samlol - Today at 01:22 pm
Hi nochmal.

Also a) und b) kann ich ausschließen, da ich alles miteinander verlötet hatte und mit einem 5V 4A Netzteil betrieben habe.

Ich habe im Netz etwas gefunden, was anscheinend funktioniert:
Der Reset PIN des OLEDs muss anfangs LOW sein und dann HIGH.

Ich hatte den einfach an 10k pullup gesteckt...

Danke für Eure Hilfe!

Sam
Pages: 1 ... 8 9 [10]

Please enter a valid email to subscribe

Confirm your email address

We need to confirm your email address.
To complete the subscription, please click the link in the email we just sent you.

Thank you for subscribing!

Arduino
via Egeo 16
Torino, 10131
Italy