Changeset 11666 for firmware


Ignore:
Timestamp:
Jul 27, 2011, 6:57:49 PM (8 years ago)
Author:
neise
Message:
 
Location:
firmware/FSC/doc
Files:
5 edited

Legend:

Unmodified
Added
Removed
  • firmware/FSC/doc/FSC.aux

    r10668 r11666  
    99\@writefile{lot}{\contentsline {table}{\numberline {2}{\ignorespaces composition of the sensor ID - ad exemplum}}{2}}
    1010\newlabel{tdl_sensor_id}{{2}{2}}
    11 \@writefile{toc}{\contentsline {subsection}{\numberline {1.3}Sensor Data}{2}}
    12 \newlabel{sec_sensor_data}{{1.3}{2}}
     11\@writefile{toc}{\contentsline {subsection}{\numberline {1.3}Sensor Data}{3}}
     12\newlabel{sec_sensor_data}{{1.3}{3}}
    1313\@writefile{lot}{\contentsline {table}{\numberline {3}{\ignorespaces sensor data format}}{3}}
    1414\newlabel{tbl_sensor_data_format}{{3}{3}}
     
    1616\@writefile{lot}{\contentsline {table}{\numberline {4}{\ignorespaces FSC commands}}{3}}
    1717\newlabel{tbl_FSC_CMDS}{{4}{3}}
    18 \@writefile{lot}{\contentsline {table}{\numberline {5}{\ignorespaces composition of FSC commands}}{3}}
    19 \newlabel{tbl_FSC_CMD_PACKAGE}{{5}{3}}
     18\@writefile{lot}{\contentsline {table}{\numberline {5}{\ignorespaces composition of FSC commands}}{4}}
     19\newlabel{tbl_FSC_CMD_PACKAGE}{{5}{4}}
    2020\@writefile{lot}{\contentsline {table}{\numberline {6}{\ignorespaces composition of FSCs acknowledgement}}{4}}
    2121\newlabel{tbl_FSC_ACK}{{6}{4}}
  • firmware/FSC/doc/FSC.log

    r10668 r11666  
    1 This is pdfTeX, Version 3.1415926-1.40.11 (MiKTeX 2.9) (preloaded format=pdflatex 2011.3.24)  9 MAY 2011 15:24
     1This is pdfTeX, Version 3.1415926-1.40.11 (MiKTeX 2.9) (preloaded format=pdflatex 2011.3.24)  16 MAY 2011 08:05
    22entering extended mode
    33**FSC.tex
     
    133133{C:/Users/neise/AppData/Local/MiKTeX/2.9/pdftex/config/pdftex.map}] [2] [3] [4]
    134134 [5]
    135 (E:\FACT\fact.isdc.unige.ch_svn_firmware\FSC\doc\FSC.aux) )
     135(E:\FACT\fact.isdc.unige.ch_svn_firmware\FSC\doc\FSC.aux)
     136
     137LaTeX Warning: Label(s) may have changed. Rerun to get cross-references right.
     138
     139 )
    136140Here is how much of TeX's memory you used:
    137141 1324 strings out of 494019
    138142 16155 string characters out of 3146498
    139  80978 words of memory out of 3000000
     143 82978 words of memory out of 3000000
    140144 4634 multiletter control sequences out of 15000+200000
    141145 14064 words of font info for 33 fonts, out of 3000000 for 9000
    142146 714 hyphenation exceptions out of 8191
    143147 25i,11n,19p,879b,238s stack positions out of 5000i,500n,10000p,200000b,50000s
    144  <C:\Users\neise\App
    145 Data\Local\MiKTeX\2.9\fonts\pk\ljfour\jknappen\ec\dpi600\ecrm0800.pk> <C:\Users
    146 \neise\AppData\Local\MiKTeX\2.9\fonts\pk\ljfour\jknappen\ec\dpi600\ecrm0600.pk>
    147  <C:\Users\neise\AppData\Local\MiKTeX\2.9\fonts\pk\ljfour\jknappen\ec\dpi600\ec
    148 bx1200.pk> <C:\Users\neise\AppData\Local\MiKTeX\2.9\fonts\pk\ljfour\jknappen\ec
    149 \dpi600\ecrm0700.pk> <C:\Users\neise\AppData\Local\MiKTeX\2.9\fonts\pk\ljfour\j
    150 knappen\ec\dpi600\ecrm1000.pk> <C:\Users\neise\AppData\Local\MiKTeX\2.9\fonts\p
    151 k\ljfour\jknappen\ec\dpi600\ecbx1000.pk> <C:\Users\neise\AppData\Local\MiKTeX\2
    152 .9\fonts\pk\ljfour\jknappen\ec\dpi600\ecbx1440.pk> <C:\Users\neise\AppData\Loca
    153 l\MiKTeX\2.9\fonts\pk\ljfour\jknappen\ec\dpi600\ecrm1200.pk> <C:\Users\neise\Ap
    154 pData\Local\MiKTeX\2.9\fonts\pk\ljfour\jknappen\ec\dpi600\ecrm1728.pk><E:/Progr
    155 am Files/MiKTeX 2.9/fonts/type1/public/amsfonts/cm/cmmi10.pfb><E:/Program Files
    156 /MiKTeX 2.9/fonts/type1/public/amsfonts/cm/cmr10.pfb><E:/Program Files/MiKTeX 2
    157 .9/fonts/type1/public/amsfonts/cm/cmr7.pfb><E:/Program Files/MiKTeX 2.9/fonts/t
    158 ype1/public/amsfonts/cm/cmsy10.pfb>
    159 Output written on FSC.pdf (5 pages, 121844 bytes).
     148 <C:\Users\neise\AppData\Local\MiKTeX\2.9\fonts\pk\ljfour\jknappen\ec\dpi600\
     149ecrm0800.pk> <C:\Users\neise\AppData\Local\MiKTeX\2.9\fonts\pk\ljfour\jknappen\
     150ec\dpi600\ecrm0600.pk> <C:\Users\neise\AppData\Local\MiKTeX\2.9\fonts\pk\ljfour
     151\jknappen\ec\dpi600\ecbx1200.pk> <C:\Users\neise\AppData\Local\MiKTeX\2.9\fonts
     152\pk\ljfour\jknappen\ec\dpi600\ecrm0700.pk> <C:\Users\neise\AppData\Local\MiKTeX
     153\2.9\fonts\pk\ljfour\jknappen\ec\dpi600\ecrm1000.pk> <C:\Users\neise\AppData\Lo
     154cal\MiKTeX\2.9\fonts\pk\ljfour\jknappen\ec\dpi600\ecbx1000.pk> <C:\Users\neise\
     155AppData\Local\MiKTeX\2.9\fonts\pk\ljfour\jknappen\ec\dpi600\ecbx1440.pk> <C:\Us
     156ers\neise\AppData\Local\MiKTeX\2.9\fonts\pk\ljfour\jknappen\ec\dpi600\ecrm1200.
     157pk> <C:\Users\neise\AppData\Local\MiKTeX\2.9\fonts\pk\ljfour\jknappen\ec\dpi600
     158\ecrm1728.pk><E:/Program Files/MiKTeX 2.9/fonts/type1/public/amsfonts/cm/cmmi10
     159.pfb><E:/Program Files/MiKTeX 2.9/fonts/type1/public/amsfonts/cm/cmmi7.pfb><E:/
     160Program Files/MiKTeX 2.9/fonts/type1/public/amsfonts/cm/cmr10.pfb><E:/Program F
     161iles/MiKTeX 2.9/fonts/type1/public/amsfonts/cm/cmr7.pfb><E:/Program Files/MiKTe
     162X 2.9/fonts/type1/public/amsfonts/cm/cmsy10.pfb>
     163Output written on FSC.pdf (5 pages, 130624 bytes).
    160164PDF statistics:
    161  273 PDF objects out of 1000 (max. 8388607)
     165 277 PDF objects out of 1000 (max. 8388607)
    162166 0 named destinations out of 1000 (max. 500000)
    163167 1 words of extra memory for PDF output out of 10000 (max. 10000000)
  • firmware/FSC/doc/FSC.tex

    r10668 r11666  
    5353\end{itemize}
    5454
    55 FSC uses an 8MHz ATmega32L micro controller(MCU) to readout the muxed 24bit sigma delta ADC (AD7719) which is connected to the RTDs. In addition the ATmegas internal 10bit ADC is used to monitor the humidity, LV-voltages and LV-currents.
     55FSC uses an 8MHz ATmega32L micro controller(MCU) to readout the muxed 24bit sigma delta ADC (AD7719) which is connected to the RTDs. In addition the 10bit ADC, which is part of the ATmegas32L, is used to monitor the humidity, LV-voltages and LV-currents.
    5656The muxers on FSC belong to analog devices ADG77xx family, and are controlled by the MCU.
    57 The User has access to FSC via Ethernet Interface, provided by WIZNETs W5100, the younger brother of W5300, which is used on FACTs FAD boards.
    58 
    59 AD7719 and W5100 communicate with the MCU via an SPI bus, which results in the fact, that a lot of user interaction might slow down temperature measurement or vice versa. Additionally the user should be aware, that sigma delta ADCs have a prolonged settling time, when muxed. Redout of all 64 temperature channels takes about 13s, while one single channel might be readout with at a rate of 10Hz. In addition FSC runs a 32bit timer, counting miliseconds since timer init. The timer is initialized to zero, when FSC is powered. User may synchronize FSCs timer to Unix time.
     57The User has access to FSC via an Ethernet Interface, provided by WIZNETs W5100, the brother of W5300, which is used on FACTs FAD boards.
     58
     59AD7719 and W5100 communicate with the MCU via the same SPI bus, which results in the fact, that a lot of user interaction might slow down temperature measurement or vice versa. Additionally the user should be aware, that sigma delta ADCs have a prolonged settling time, when muxed. Redout of all 64 temperature channels takes about 13s, while one single channel might be readout with at a rate of 10Hz.
     60
     61In addition FSC runs a 32bit timer, counting miliseconds since timer init. The timer is initialized to zero, when FSC is powered. User may synchronize FSCs timer to Unix time.
    6062
    6163\subsection{Measuring}
    6264\label{sec_measuring}
    6365The user may send a command telling FSC, what to measure. FSC will measure it and return the result, right after the measurement was finished. It is possible to tell FSC to measure several sensors at a time.
    64 Users may issue an 'activate' command (see table \ref{tbl_FSC_CMDS}), to specify which channel should be measured during the next measurement phase. In case one is not sure which channel was activated beforehand users may issue a 'status' command, to gather information about FSCs current status. Whenever the user completed the channel activation process the 'measure' commands may be issued. Since the high resolution ADC AD7719 used for resistance measurement and the 10bit ADC used for voltage measurement run independently on different time scales, different 'measure' commands are defined. 'measure resistances' will start a measurement possibly taking some seconds, while 'measure voltages' will be ready almost instantaneosly.
    65 Since a measurement might take some time, FSC generates an answer, once the 'measure' command received, informing the user about the command reception. The results are then submitted in a single message to the user, which is called a telegram.
     66Users may activate (see table \ref{tbl_FSC_CMDS}) beliebige sensor channels, by writing into the aproriate 'enable register', to specify which channel should be measured during the next measurement phase.
     67%In case one is not sure which channel was activated beforehand users may issue a 'status' command, to gather information about FSCs current status.
     68Whenever the user completed the channel activation process the 'measure' commands may be issued. Since the high resolution ADC AD7719 used for resistance measurement and the 10bit ADC used for voltage measurement run independently on different time scales, different 'measure' commands are defined. 'measure resistances' will start the measurement of all activated resistance channels possibly taking some seconds, while 'measure voltages' will start a measurement of the activated voltage channel and be ready almost instantaneosly.
     69Since a measurement might take some time, FSC generates an answer, once the 'measure' command received, informing the user about the command reception. The results are later submitted in a single message to the user, which is called a telegram.
     70Since the maximum readout data rate for the MCU from W5100 memory (~100kb/s) is substantially smaller than the data rate over ethernet, is is possible for the user to fill the W5100 receive memory, while FSC is still working on the first command. Although not extensivly tested, the reaction of W5100 to a completly filled memomry is not critical. It will stop acknowledging incoming TCP/IP packets, which ususally causes the sender to keep sending them. Eventually a time out on user side will occur and the connection will look like lost, but actually it was just given up by the sender.
    6671During a 'measure resistance' FSC is not checking for incoming commands. So incoming commands will pile up in W5100 input FIFO. Which means, sending a lot of on demand commands will delay FSCs reaction to the following commands consecutivly.
    6772The W5100 transmission FIFO can recieve 4kbyte. I am not sure what happens in case this FIFO is completely full, but I guess W5100 will reject incoming TCP/IP packets and the user side PC will constantly keep on (re)sending them. Since a typical command consists of less than 10bytes it is necessary to send a lot of commands without receiving any answer before the FSC FIFO is full.
  • firmware/FSC/doc/FSC.toc

    r10668 r11666  
    33\contentsline {subsubsection}{\numberline {1.1.1}RTD switching}{2}
    44\contentsline {subsection}{\numberline {1.2}The Telegram}{2}
    5 \contentsline {subsection}{\numberline {1.3}Sensor Data}{2}
     5\contentsline {subsection}{\numberline {1.3}Sensor Data}{3}
    66\contentsline {section}{\numberline {2}Ethernet Interface}{3}
    77\contentsline {subsection}{\numberline {2.1}FSC Registers}{4}
Note: See TracChangeset for help on using the changeset viewer.