Difference between revisions of "FRAM Model AIO"

From OpenMotics
Jump to navigation Jump to search
Line 28: Line 28:
 
|}
 
|}
  
: This page is entirely used for output module 8-15.
+
: This page is entirely used for output module 8-15:
 +
: * Module 8: Byte0..31
 +
: * Module 9: Byte32..63
 +
: * ...
 +
 
  
 
{| class="wikitable sortable" border="1"
 
{| class="wikitable sortable" border="1"
Line 37: Line 41:
 
|}
 
|}
  
: This page is entirely used for output module 16-23.
+
: This page is entirely used for output module 16-23:
 +
: * Module 16: Byte0..31
 +
: * Module 17: Byte32..63
 +
: * ...
 +
 
  
 
...
 
...
Line 48: Line 56:
 
|}
 
|}
  
: This page is entirely used for output module 72-79.
+
: This page is entirely used for output module 72-79:
 +
: * Module 72: Byte0..31
 +
: * Module 73: Byte32..63
 +
: * ...

Revision as of 14:25, 30 July 2019

Introduction

The AIO has an onboard FRAM connected via I2C to the DSPIC33E (The Master). FRAM is used to keep track of the real-time change, Eeprom is used to store the settings. This document describes the FRAM memory locations used.

General Configuration Bytes

Page 0 -> General data

Data output modules

Page 1 – 10 -> Contains data of the output modules, 32 bytes per module, 8 modules per page, 10 pages (80 modules maximum, 640 outputs -> 0-639)
Page Byte
1 x
This page is entirely used for output module 0-7:
* Module 0: Byte0..31
* Module 1: Byte32..63
* ...
Page Byte
2 x
This page is entirely used for output module 8-15:
* Module 8: Byte0..31
* Module 9: Byte32..63
* ...


Page Byte
3 x
This page is entirely used for output module 16-23:
* Module 16: Byte0..31
* Module 17: Byte32..63
* ...


...

Page Byte
10 x
This page is entirely used for output module 72-79:
* Module 72: Byte0..31
* Module 73: Byte32..63
* ...