forked from youen/OneWireArduinoSlave
You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
43 lines
2.5 KiB
43 lines
2.5 KiB
7 years ago
|
This library allows you to emulate existing 1-wire devices with an Arduino, or to create your own protocol. All low-level details are handled by the library, such as reset detection, ROM matching, byte sending and receiving. Look at the demo sketch to see an example.
|
||
|
|
|
||
|
|
# Compatible boards
|
||
|
|
|
||
|
|
If you have tested the library on another board, please send a pull-request (or just tell me which board) to update this list.
|
||
|
|
|
||
|
|
## ATmega328
|
||
|
|
|
||
|
|
- Arduino Uno (tested by [neuoy](https://github.com/neuoy))
|
||
|
|
|
||
|
|
# Getting started
|
||
|
|
|
||
|
|
See example "FakeDS18B20", and the associated [documentation](examples/FakeDS18B20/README.md), for a working use case of the library.
|
||
|
|
|
||
|
|
# Reference
|
||
|
|
|
||
|
|
## setReceiveCallback
|
||
|
|
|
||
|
|
`void setReceiveCallback(void(*callback)(ReceiveEvent evt, byte data))`
|
||
|
|
|
||
|
|
Sets the function that will be called back when an event occurs, such as when a byte is received.
|
||
|
|
|
||
|
|
## begin
|
||
|
|
|
||
|
|
`void begin(byte* rom, byte pinNumber)`
|
||
|
|
|
||
|
|
Starts the library, which will respond to the provided ROM (must be unique on your network) on the specified Arduino pin. The ROM is cloned by the library, so you can discard your buffer immediately if you want.
|
||
|
|
|
||
|
|
## write
|
||
|
|
|
||
|
|
`void write(byte* bytes, short numBytes, void(*complete)(bool error))`
|
||
|
|
|
||
|
|
Starts writing one or more bytes, and will call the provided callback (optional) when it's done. The buffer you provide here must stay available until the end of the write operation, which happens in background. Do not use local variables.
|
||
|
|
|
||
|
|
# Notes about the interrupt-based implementation
|
||
|
|
Since the library is implemented using interrupts, none of its functions will block: you can continue execute your code immediately.
|
||
|
|
|
||
|
|
This also means callbacks are called from interrupt handlers, so you must make them very short to not block further communication.
|
||
|
|
|
||
|
|
You must also be careful when you explicitely block interrupts, as the 1-wire protocol has very tight timings, especially when writing bytes (which also happens when searching for device ROMs): a delay of 3 microseconds (yes, microseconds, not milliseconds) can be enough for some (quite intolerant) masters to miss a bit.
|
||
|
|
|
||
|
|
But if your code only blocks interrupts for reasonably short time, the probability to block exactly at the bad moment is low, so you can easily mitigate the issue by adding CRC checks in your high-level communication protocol, and retrying when an error is detected. This is an important thing to do anyway because 1-wire does not natively perform any error checking (excepted for ROM operations which already contain a CRC byte). Standard 1-wire devices also include CRC checks in their specific protocols.
|