Recent Posts

Pages: [1] 2 3 ... 10
Deutsch / Re: Spannungsversorgung Laufsc...
Last post by Rentner - Today at 08:59 pm

Bei 2,5mm² hätte ich mit 20A keinerlei Bauchschmerzen - eine egal wie geartete Schmelzsicherung wird hier aber wohl NIE auslösen, da vom Netzteil einfach nicht genug 'Dampf' kommt - die Schmelzsicherung benötigt VIEL MEHR Strom um auszulösen.


ich glaube da haben wir uns falsch verstanden.

Der T0 hat an 40A Netzgeräte gedacht und er will mehrfach an verschieden Stellen einspeisen. Damit sind die Einzelströme für jede Einspeisung kleiner. Wenn man das vernüftig in Gruppen aufteilt kommt man mit einer 6A Sicherung aus und kann die Leitung damit gegen Kurzschluss schützen.

Das ganze Ding soll 7,5m lang werden. wenn man das in 3 Teile a 2,5m aufteilt kann man ea auch noch händeln. In jedes dieser Teilstücke würde ich ein 40A Netzgerät einbauen. In diesem Teilstück sind vorne 8 Streifen mit je 75LEDs und hinten ebenfalls. Das ergibt 16 Einspeisepunkte.

75LED*60mA*50% etwas 2,3A

die man gut  mit 6A absichern kann.  An jedem Netzgerät gehen 16 Drähte ab auf eine je Sicherung. Die Anzahl der Sicherungen kann man dann auch noch halbieren. Das  geht dann mit 6A auch noch. Bei Kurzschluss im Kabel oder am Anschluss wir die Sicherung auslösen. Je nach Defekt auf einem Streifen allerdings nicht das ist schon richtig.



I am fairly new to arduino in general. I am undertaking a project in which a pressure must be recorded from a pressure transducer and stored on a server. I am unsure how I will read data from this specific type of pressure transducer.

The pressure transducer I have to read pressure data from is a Edwards Lifescience PXVK0996 "TruWave pressure monitoring set".

Some details on the pressure transducer:

Some details on the general schematics of these transducers:

I am also in possession of a converter for the plug that goes to VGA.

If anyone can offer any guidance on how I can read data from the pressure transducer, please let me know. I am not too good with the hardware side of these projects.
Might I suggest using bitWrite() to shorten your repetitive code.


Code: [Select]
bitWrite(bitsToSend, 0, digitalRead(inPin0));
bitWrite(bitsToSend, 1, digitalRead(inPin1));
bitWrite(bitsToSend, 2, digitalRead(inPin2));
bitWrite(bitsToSend, 3, digitalRead(inPin3));
bitWrite(bitsToSend, 4, digitalRead(inPin4));
bitWrite(bitsToSend, 5, digitalRead(inPin5));
bitWrite(bitsToSend, 6, digitalRead(inPin6));
bitWrite(bitsToSend, 7, digitalRead(inPin7));


Code: [Select]
bitsToSend = 0;
  // Read the inputs and send HIGH bit values to the corresponding pin on the shift register

if (digitalRead(inPin0) == HIGH)
     bitSet(bitsToSend, 0);
if (digitalRead(inPin1) == HIGH)
     bitSet(bitsToSend, 1);
if (digitalRead(inPin2) == HIGH)
     bitSet(bitsToSend, 2);
if (digitalRead(inPin3) == HIGH)
     bitSet(bitsToSend, 3);
if (digitalRead(inPin4) == HIGH)
     bitSet(bitsToSend, 4);
if (digitalRead(inPin5) == HIGH)
     bitSet(bitsToSend, 5);
if (digitalRead(inPin6) == HIGH)
     bitSet(bitsToSend, 6);
if (digitalRead(inPin7) == HIGH)
     bitSet(bitsToSend, 7);

Thank you for your interest.

I'm afraid I dont have your sharp debug eyes on the 0 pin.

But I have come so far that i have managed to see in the Serial Printer that inPin0 gets recorded by pressing, I also switched some cables to see and it is reacting. The 0 pin on the ShiftRegister doesnt seem to ever go high though, I guess adwsystems has spotted why.

I have also gotten the outputs to turn off when released, thank you for that UKHeliBob.

Actually I was referring to the problem with not going low.

As for bit 0, not being set. Is bit 0 set first or last? If you send 0xFF, what do you get? (delete the input buttons, move all logic to Setup() to run once. What comes out of the shift register?
boa tarde giova014

Comparador do que? Que saída de dados?

Code: [Select]
int incomingByte =;
void setup() {


Você está lendo do Serial antes de tê-lo inicializado, já que o código em escopo global é executado antes do setup(). Ainda mais: você não lê do Serial em nenhum outro lugar do seu código.

Code: [Select]
if ( incomingByte == '2.46') {
if ( incomingByte == '2.19') {

Aspas simples são para caracteres, os textos 2.46 e 2.19 não são caracteres, então a comparação nunca vai ser igual.

Code: [Select]
for (i=0;i<23;i++) {
Porque 23?

Code: [Select]
De onde veio esse número mágico 3856.8376068376?
Onde estão os servos no seu código? O que são esses números 2.12, 2.45, 2.45 e 3.19?

Explique melhor o projeto, o que o código deveria fazer e o que faz.

Comparador do que? Que saída de dados?

este é um relogio comparador com saida de dados, é mais ou menos isso que preciso so que com algumas funçoes a mais no codigo do arduino

Code: [Select]

for (i=0;i<23;i++) {

esse 23 eu nao sei, pois como eu disse eu sou iniciante e peguei o codigo pronto so tentei modificar olhando outros codigos com a funçao que eu precisava e tentei juntalos

Code: [Select]


esse valor é utilizado para converter o sinal recebido para MM

Onde estão os servos no seu código? O que são esses números 2.12, 2.45, 2.45 e 3.19?

Explique melhor o projeto, o que o código deveria fazer e o que faz.

esses valores sao o resultado da conversao do sinal para MM eles no caso estao em MM ja

o que eu preciso é que uma caneta risque uma esteira que o servo 1 movimentara quando o arduino estiver dentro do valor de 2.12 e 2.45 mm e o servo 2 risque entre os valores de 2.45 e 3.19 mm

ainda nao coloquei o codigo dos servos no programa por que nao sei mas estou tentando

por enquanto meu codigo so esta lendo os valores do relogio comparador sem muita precisao nao sei muito bem o porque mas da valores parecidos entao para testes esta bom.

Desde-ja agradeço a resposta e me desculpe pela minha ignorancia quanto a programação, estou tentando aprender mas é dificil
MKRWIFI1010 / Re: Antenna booster?
Last post by ballscrewbob - Today at 08:53 pm

Just two right off the bat.
Also search the MKR1000 section as it has also been covered there too.

Programming Questions / Re: Remembering last State
Last post by johnwasser - Today at 08:52 pm
Let say you want to pass 20 parameters. That is 20 EEPROM cells. Then, if you address the cells in sequence (each time the next 20 and over from beginning), your 27 years (as told above) come 27 *50 = 1350 years

Is this ok?
(50 comes from 1kbyte eeprom and 20 "byte" parameters)
That only works if you have a way of storing which set of bytes your parameters are stored in.
For saving a single bit, at startup or reset:
Read EEPROM address 0.  If the value is 0, read the next EEPROM address.  Repeat until you find a non-zero byte.  The top bit is your value and the bottom 7 bits are the number of times the byte has been written.
When you need to change the value, you know the address and the number of times it has been written.  Increment the number of times it has been written.  If the result is <= 0x7F store the write count and data bit in (address).  If the result is greater than 0x7F (127), store the data bit plus a write count of 1 to ((address+1) % 1024) and store a 0 at  (address).  This spreads the wear over all 1024 locations so the EEPROM won't wear out for  over 27000 years (assuming ten updates a day, every day).
Audio / Re: How to close;
Last post by seby20 - Today at 08:51 pm
Anyone please?
I have the same problem and also asked a questing about it. Maybe the suggestioned i got work for you. The topic is called 'Arduino uno wifi rev 2 and LiquidCrystal_I2C (repost in right place)'. Here is the link:
Software / Re: Problema Assurdo...SKetch ...
Last post by gpb01 - Today at 08:50 pm
Ah allora aspe, mi sa che ci sia un malinteso. Non è il mio il problema del programma che non si avvia, ma dell'utente bruco1987.
Ooooppppsss ... vero, ho letto il tuo post in cima alla pagina e, di getto, ho scritto a te :D :D :D  Scusa il disturbo ;)

>bruco1987: la domanda era allora per te ;)


Thread moved as  requested.

Pages: [1] 2 3 ... 10