Diky vsem za odpovedi, Kdyz mi to tu vetsina doporucuje zustanu u puvodniho zapojeni s otocenim HIGH-LOW na zdroji.
Elektronika neni bohuzel muj hlavni obor a analogova uz vubec ne. Tady je popis puvodniho signalu od jednoho manika co to zmeril :
The signal was 20ms long, with a 4ms gap between each. Within the signal itself, there were oscillations between 4V and 0V with the shortest mark or space taking around 300 microseconds. The first 5ms or so of the signal were roughly constant, but that was as far as I got.
Vlastne nevim jak "moc rychle to je", kazdopadne zpozdeni mi vadi, kdyz se takovy signal snazim vyrobit na Raspberry tak uz je s tim lehce problem, opet originalni citace :
Despite the sleep timers in the C program matching the observed timings from the TK board, the entire pulse train ended up being around 25ms long rather than 20ms. This is likely due to the time taken to switch the GPIO output, but it could also be due to the Pi servicing various interrupts that take priority over my application’s timing. If this proves to be a problem when interfacing with the tank, the sleep timers can be reduced to bring the pulse train back to the proper length. We must also keep a careful eye on interrupts in future, as right now the Pi is doing little other than running one simple program — but that will not be the case if the Pi gains webcams, WiFi etc. in enhanced versions.
