AVR-IO-M16FirmwarePCControlAVR-IO-M16.AVR-IO-M16FirmwarePCControl HistoryHide minor edits - Show changes to output Changed lines 12-13 from:
Here is the description of the to:
Here is the description of the protocol. Changed lines 51-52 from:
-> '(' or ')' then '/' or '*' to inform the new current state to:
-> '(' or ')' then '/' or '*' to inform of the new current state '#' : Read present Configuration -> '(' or ')' then '/' or '*' to inform of the current state Changed lines 57-58 from:
-> '(' or ')' then '/' or '*' to inform the saved/current state to:
-> '(' or ')' then '/' or '*' to inform of the saved/current state Changed lines 60-62 from:
-> '(' or ')' then '/' or '*' to inform the new current state to:
-> '(' or ')' then '/' or '*' to inform of the new current state '#' : Read Stored on EEPROM Configuration -> '(' or ')' then '/' or '*' to inform of the stored on EEPROM state Changed lines 12-13 from:
Here is the description of the used protocol to:
Here is the description of the used protocol. Changed lines 16-17 from:
Answers from the board have multiple bytes but every byte can be decoded independently to:
Answers from the board have multiple bytes but every byte can be decoded independently. Changed line 7 from:
The protocol is very simple as the payload is 4 bits so all commands can be only one byte long. The only exception is on the confirmed version where the write to:
The protocol is very simple as the payload is 4 bits so all commands can be only one byte long. The only exception is on the confirmed version where the write command has an extra byte to validate the request. Changed lines 5-6 from:
The %newwin% [[http://www.olimex.com/dev/avr-io-m16.html | AVR-IO-M16]] board id a development board with four relay outputs and four optoisolated inputs. It has an ATMEGA16 and can be connected to a PC by a serial port. I wrote a simple firmware ( to:
The %newwin% [[http://www.olimex.com/dev/avr-io-m16.html | AVR-IO-M16]] board id a development board with four relay outputs and four optoisolated inputs. It has an ATMEGA16 and can be connected to a PC by a serial port. I wrote a simple firmware ([[(Attach:)M16Simple.zip]]) and a PC client ([[(Attach:)M16_PC.zip]]) to control the board. The PC client can also relay those commands from/to the board over a network connection. Changed lines 5-6 from:
The [[http://www.olimex.com/dev/avr-io-m16.html | AVR-IO-M16]] board id a development board with four relay outputs and four optoisolated inputs. It has an ATMEGA16 and can be connected to a PC by a serial port. I wrote a simple firmware (([[(Attach:)M16Simple.zip]])) and a PC client ([[(Attach:)M16_PC.zip]]) to control the board. The PC client can also relay those commands from/to the board over a network connection. to:
The %newwin% [[http://www.olimex.com/dev/avr-io-m16.html | AVR-IO-M16]] board id a development board with four relay outputs and four optoisolated inputs. It has an ATMEGA16 and can be connected to a PC by a serial port. I wrote a simple firmware (([[(Attach:)M16Simple.zip]])) and a PC client ([[(Attach:)M16_PC.zip]]) to control the board. The PC client can also relay those commands from/to the board over a network connection. Changed lines 19-20 from:
to:
(-> xx : the answer from the board to the PC) Changed line 23 from:
if confirmation is enabled this command must be followed by a compatible Confirm Write to:
if confirmation is enabled this command must be followed by a compatible Confirm Write Outputs (0x7n) Added lines 59-74:
From the board to the PC: 0x4n : Outputs State: n is a nibble (4 bits) indicating the actual status of each output line 0x5n : Inputs State: n is a nibble (4 bits) indicating the actual status of each input line ' ' : Dummy response when a confirmation is pending '(' : Confirmation Enabled ')' : Confirmation Disabled '*' : Continuous inputs state broadcast enabled '/' : Inputs state broadcast disabled Changed lines 3-4 from:
!! %blue% AVR-IO-M16 Firmware + PC Control - Firmware and PC Software to control to:
!! %blue% AVR-IO-M16 Firmware + PC Control - Firmware and PC Software to control an AVR-IO-M16 Board. Changed lines 3-4 from:
!! %blue% AVR-IO-M16 Firmware + to:
!! %blue% AVR-IO-M16 Firmware + PC Control - Firmware and PC Software to control a AVR-IO-M16 Board. Changed lines 5-6 from:
The [[http://www.olimex.com/dev/avr-io-m16.html | AVR-IO-M16]] board id a development board with four relay outputs and four optoisolated inputs. It has an ATMEGA16 and can be connected to a PC by a serial port. I wrote a simple firmware (([[(Attach:)M16Simple.zip]])) and a PC client ([[(Attach:)M16_PC. to:
The [[http://www.olimex.com/dev/avr-io-m16.html | AVR-IO-M16]] board id a development board with four relay outputs and four optoisolated inputs. It has an ATMEGA16 and can be connected to a PC by a serial port. I wrote a simple firmware (([[(Attach:)M16Simple.zip]])) and a PC client ([[(Attach:)M16_PC.zip]]) to control the board. The PC client can also relay those commands from/to the board over a network connection. Changed lines 5-6 from:
The [[http://www.olimex.com/dev/avr-io-m16.html | AVR-IO-M16]] board id a development board with four relay outputs and four optoisolated inputs. It has an ATMEGA16 and can be connected to a PC by a serial port. I wrote a simple firmware (([[(Attach:)M16Simple.zip]])) and a PC client ([[(Attach:)M16_PC. to:
The [[http://www.olimex.com/dev/avr-io-m16.html | AVR-IO-M16]] board id a development board with four relay outputs and four optoisolated inputs. It has an ATMEGA16 and can be connected to a PC by a serial port. I wrote a simple firmware (([[(Attach:)M16Simple.zip]])) and a PC client ([[(Attach:)M16_PC.7z]]) to control the board. The PC client can also relay those commands from/to the board over a network connection. Changed lines 8-9 from:
to:
The serial port is configured with a baud rate of 38400, 8 bits, no parity. Changed line 13 from:
This protocol to:
This protocol uses one or two byte commands. Changed lines 15-16 from:
Answers from the board to:
Answers from the board have multiple bytes but every byte can be decoded independently Changed lines 20-21 from:
if confirmation is disabled this command refreshes the outputs to:
if confirmation is disabled this command refreshes the outputs immediately if confirmation is enabled this command must be followed by a compatible Confirm Write outputs Changed line 26 from:
n must be equal to the to:
n must be equal to the previous Write output command (0x4n) Added line 18:
Added line 24:
Added line 29:
Added line 32:
Added line 35:
Added line 38:
Added line 41:
Added line 44:
Added line 47:
Added line 50:
Added line 53:
Changed lines 9-45 from:
to:
!!Protocol Here is the description of the used protocol This protocol use one or two byte commands. If the confirmation is turned off all commands have only one byte. Answers from the board can be multy byte but every byte can be decoded independently From the PC to the board: 0x4n : Write outputs where n is a nibble (4 bits) indicating the status of each output line if confirmation is disabled this command refreshes the outputs imeaditly if confirmation is enabled this command mut be followed by a compatible Confirm Write outputs -> 0x4i where i is a nibble (4 bits) indicating the actual status of each output line (confirmation disabled) -> ' ' as a dummy response if confirmation is enabled 0x7n : Confirm Write outputs where n is a nibble (4 bits) indicating the status of each output line n must be equal to the previouos Write output command (0x4n) if confirmation is disabled this command is not necessary -> 0x4i : i is a nibble (4 bits) indicating the actual status of each output line '+' : Read outputs state -> 0x4i : i is a nibble (4 bits) indicating the actual status of each output line '-' : Read inputs state -> 0x5i : i is a nibble (4 bits) indicating the actual status of each input line '*' : Enable continuous inputs state broadcast -> '*' indicating continuous inputs state broadcast '/' : Disable inputs state broadcast -> '/' indicating disabled inputs state broadcast '(' : Enable confirmation check -> '(' indicating enabled confirmation check ')' : Disable confirmation check -> ')' indicating disabled confirmation check '!' : Reset Configuration -> '(' or ')' then '/' or '*' to inform the new current state '$' : Save Configuration to EEPROM -> '(' or ')' then '/' or '*' to inform the saved/current state '%' : Load Configuration from EEPROM -> '(' or ')' then '/' or '*' to inform the new current state Changed lines 5-6 from:
The [[http://www.olimex.com/dev/avr-io-m16.html | AVR-IO-M16]] board id a development board with four relay outputs and four optoisolated inputs. It has an ATMEGA16 and can be connected to a PC by a serial port. I wrote a simple firmware and a PC client ([[(Attach:)M16_PC.zip]]) to control the board. The PC client can also relay those commands from/to the board over a network connection. to:
The [[http://www.olimex.com/dev/avr-io-m16.html | AVR-IO-M16]] board id a development board with four relay outputs and four optoisolated inputs. It has an ATMEGA16 and can be connected to a PC by a serial port. I wrote a simple firmware (([[(Attach:)M16Simple.zip]])) and a PC client ([[(Attach:)M16_PC.zip]]) to control the board. The PC client can also relay those commands from/to the board over a network connection. Changed lines 5-6 from:
The [[http://www.olimex.com/dev/avr-io-m16.html | AVR-IO-M16]] board id a development board with four relay outputs and four optoisolated inputs. It has an ATMEGA16 and can be connected to a PC by a serial port. I wrote a simple firmware and a PC client to control the board. The PC client can also relay those commands from/to the board over a network connection. to:
The [[http://www.olimex.com/dev/avr-io-m16.html | AVR-IO-M16]] board id a development board with four relay outputs and four optoisolated inputs. It has an ATMEGA16 and can be connected to a PC by a serial port. I wrote a simple firmware and a PC client ([[(Attach:)M16_PC.zip]]) to control the board. The PC client can also relay those commands from/to the board over a network connection. Changed lines 7-9 from:
The protocol is very simple as the payload is 4 bits so all commands to:
The protocol is very simple as the payload is 4 bits so all commands can be only one byte long. The only exception is on the confirmed version where the write commands have an extra byte to validate the request. Added lines 1-9:
(:notitle:) !! %blue% AVR-IO-M16 Firmware + PCC Control - Firmware and PC Software to control a AVR-IO-M16 Board. The [[http://www.olimex.com/dev/avr-io-m16.html | AVR-IO-M16]] board id a development board with four relay outputs and four optoisolated inputs. It has an ATMEGA16 and can be connected to a PC by a serial port. I wrote a simple firmware and a PC client to control the board. The PC client can also relay those commands from/to the board over a network connection. The protocol is very simple as the payload is 4 bits so all commands are only one byte long. The only exception is on the confirmed version where the write commands have an extra byte to validate the request. |