Serial over webaudio
substack.net
substack.net
So if you want to take this experiment one step further, consider doing FSK or PSK audio and add a non-return-to-zero (or NRZ) serial protocol. With NRZ the clock is actually embedded in the prototcol so with a software implementation of a phase locked loop you can recover the clock and data signal and reliably transmit from two different clock domains. (the article depends on you being able to hit one of the known baudrates accurately enough for the serial code to recognize it.)
Then for extra credit you can embed multiple frequencies in your tones, so that instead of sending ones and zeros you're actually sending 2 or 4 bit equivalent bauds. Then you can have fun doing a quick FFT on the receiving end and clock recovery to pull out multiple bits and the clock.
FWIW, the path goes very very very far down the rabbit hole.
[0] - https://en.wikipedia.org/wiki/Frequency-shift_keying
[1] - http://www.creativedistraction.com/demos/sensor-data-to-ipho...
The old 300 baud did, and at that data rate you can transmit a 19 character URL in 0.5s or for that matter a 128-bit UUID/GUID.
[1] http://skeptophilia.blogspot.com/2011/02/ghost-in-machine.ht...
https://chrome.google.com/webstore/detail/nacl-development-e...
With 3.3v logic, it turns out you don't even need the transistor - just a capacitor and bias resistors.
Then you AFAIK need an additional chip for the programming. Which e.g. the Arduino has, but you'd not necessarily add to your own design.
> However, if you've got an android device, the easiest, most reliable, way to program it would be to get a $3 usb otg dongle and just plugging your arduino into that. There are tons of free apps that will burn a new program on from there.
+ "there is an android app for that" is exactly the thing you can avoid with such a setup, once WebAudio is reliable enough you just can distribute a link to your users and they don't need any third-party software, you don't need to maintain documentation for it, ... Having seen quite a few support discussions for DIY projects that distributed pre-programmed chips this would be useful in some cases.
With the webaudio setup, I guess that's fair enough. For being absolutely foolproof being able to say to go to a specific webpage and then press play on tape is something we've been doing for a while. I personally prefer USB/Serial programming, but that's possibly just me having dealt with too many hand-me-down radios with scratchy headphone jacks over the years.
Upgraded Phone System (As opposed to POTS.)
Internet Protocol
TCP/BSDSockets
WebSockets
WebAudio
A final layer so that you can emulate a POTS over WebAudio.
That's not really any fault of the authors, I'm just curious how many layers we're going to stack up before we start unwinding the coil for performance reasons.
Certainly there are implications that this data (once generated by the browser) could be retransmitted over the web to some remote hardware, but it's not critical to get this to work.
> "It uses a VLAN-like encapsulation technique to encapsulate MAC-based OSI layer 2 Ethernet frames within layer 4 UDP packets, ..."
-- https://en.wikipedia.org/wiki/Virtual_Extensible_LAN
Before that, MPLS: IPv6-in-IPv4 over PPPoE over HDLC over MPLS over an Ethernet VLAN inside a service provider's VLAN (Q-in-Q) over MPLS CSC to another ISP halfway across the country to ...