tenkiv / tekdaqc-firmware Goto Github PK

Issue by jwoolston from Tuesday Dec 03, 2013 at 18:14 GMT
Originally opened as https://github.com/Tenkiv/TekDAQC_Firmware_Old/issues/19

Resource: TekDAQC_Firmware_Development/TekDAQC_Libraries_Firmware/src/TekDAQC_CommandInterpreter.c
Location: line 758

Issue by jwoolston from Tuesday Dec 03, 2013 at 22:14 GMT
Originally opened as https://github.com/Tenkiv/TekDAQC_Firmware_Old/issues/39

Issue by Matrinica from Thursday Mar 07, 2013 at 17:36 GMT
Originally opened as https://github.com/Tenkiv/TekDAQC_Firmware_Old/issues/6

Provide a mechanism so that, when asked for register values, the driver can either get the local copy of the register or fetch the remote copy. It would be something like a switch, that could be implemented as a flag, or a parameter in related functions.

It can be configured to always get the local copy of the registers, so that it works like a cache. Read/Write will be done on the local copy, and the dirty copy due to write will be written to the remote.

Or it can be configured to always fetch the remote copy, so that the copy is always up-to-date. But this would create more traffic in the SPI, and sometimes not necessary.

Issue by jwoolston from Tuesday Dec 03, 2013 at 18:25 GMT
Originally opened as https://github.com/Tenkiv/TekDAQC_Firmware_Old/issues/34

Resource: TekDAQC_Firmware_Development/TekDAQC_Libraries_Firmware/src/AnalogInput_Multiplexer.c
Location: line 64

Issue by jwoolston from Tuesday Dec 10, 2013 at 05:10 GMT
Originally opened as https://github.com/Tenkiv/TekDAQC_Firmware_Old/issues/49

Issue by jwoolston from Tuesday Dec 03, 2013 at 18:18 GMT
Originally opened as https://github.com/Tenkiv/TekDAQC_Firmware_Old/issues/22

Resource: TekDAQC_Firmware_Development/TekDAQC_Libraries_Firmware/src/TekDAQC_CommandInterpreter.c
Location: line 833

Issue by jwoolston from Tuesday Dec 03, 2013 at 18:19 GMT
Originally opened as https://github.com/Tenkiv/TekDAQC_Firmware_Old/issues/23

Resource: TekDAQC_Firmware_Development/TekDAQC_Libraries_Firmware/src/TelnetServer.c
Location: line 511

Issue by jwoolston from Tuesday Dec 10, 2013 at 05:08 GMT
Originally opened as https://github.com/Tenkiv/TekDAQC_Firmware_Old/issues/47

• Find the free call for every malloc call.

Issue by jwoolston from Tuesday Dec 03, 2013 at 18:24 GMT
Originally opened as https://github.com/Tenkiv/TekDAQC_Firmware_Old/issues/33

Resource: TekDAQC_Firmware_Development/TekDAQC_Libraries_Firmware/src/ADS1256_Driver.c
Location: line 488

Issue by jwoolston from Tuesday Dec 03, 2013 at 18:20 GMT
Originally opened as https://github.com/Tenkiv/TekDAQC_Firmware_Old/issues/24

Resource: TekDAQC_Firmware_Development/TekDAQC_Libraries_Firmware/src/ADC_StateMachine.c
Location: line 67

Issue by jwoolston from Thursday Mar 07, 2013 at 16:07 GMT
Originally opened as https://github.com/Tenkiv/TekDAQC_Firmware_Old/issues/3

When changing sample rate, PGA settings, Buffer on/off status, a self calibration needs to be performed. The ADC by default does this automatically and we should ensure we wait for it to complete. If we decide to disable it for whatever reason, we need to make sure we perform it ourselves.

Issue by jwoolston from Tuesday Dec 03, 2013 at 18:26 GMT
Originally opened as https://github.com/Tenkiv/TekDAQC_Firmware_Old/issues/37

Resource: TekDAQC_Firmware_Development/TekDAQC_Libraries_Firmware/src/ADS1256_Driver.c
Location: line 1221

Issue by jwoolston from Tuesday Mar 12, 2013 at 03:28 GMT
Originally opened as https://github.com/Tenkiv/TekDAQC_Firmware_Old/issues/11

Issue by jwoolston from Tuesday Dec 10, 2013 at 05:04 GMT
Originally opened as https://github.com/Tenkiv/TekDAQC_Firmware_Old/issues/45

If there is no chance of an interrupt accessing a string it can be moved to a global buffer

Issue by jwoolston from Tuesday Dec 10, 2013 at 05:00 GMT
Originally opened as https://github.com/Tenkiv/TekDAQC_Firmware_Old/issues/44

• Each pass though the loop their status should be read
• Any time an error is encountered it should be reported over the communication connection

Issue by jwoolston from Tuesday Dec 03, 2013 at 18:23 GMT
Originally opened as https://github.com/Tenkiv/TekDAQC_Firmware_Old/issues/30

Resource: TekDAQC_Firmware_Development/TekDAQC_Libraries_Firmware/src/TekDAQC_CalibrationTable.c
Location: line 132

Issue by jwoolston from Sunday Aug 25, 2013 at 21:04 GMT
Originally opened as https://github.com/Tenkiv/TekDAQC_Firmware_Old/issues/15

Issue by jwoolston from Tuesday Dec 10, 2013 at 05:11 GMT
Originally opened as https://github.com/Tenkiv/TekDAQC_Firmware_Old/issues/50

• Simple verification that the chip can be communicated with properly.

Issue by jwoolston from Thursday Mar 07, 2013 at 16:05 GMT
Originally opened as https://github.com/Tenkiv/TekDAQC_Firmware_Old/issues/2

When converting using the /SYNC command, the result will be ready after a certain amount of time which is a function of the ADC clock period and sample rate. We know this in advance and should automatically wait for this amount of time before checking for results.

Issue by jwoolston from Tuesday Dec 03, 2013 at 18:17 GMT
Originally opened as https://github.com/Tenkiv/TekDAQC_Firmware_Old/issues/21

Resource: TekDAQC_Firmware_Development/TekDAQC_Libraries_Firmware/src/TekDAQC_Calibration.c
Location: line 36

Issue by jwoolston from Tuesday Dec 03, 2013 at 18:23 GMT
Originally opened as https://github.com/Tenkiv/TekDAQC_Firmware_Old/issues/29

Resource: TekDAQC_Firmware_Development/TekDAQC_Libraries_Firmware/src/TekDAQC_CalibrationTable.c
Location: line 116

Issue by jwoolston from Wednesday Dec 04, 2013 at 01:11 GMT
Originally opened as https://github.com/Tenkiv/TekDAQC_Firmware_Old/pull/40

jwoolston included the following code: https://github.com/Tenkiv/TekDAQC_Firmware_Old/pull/40/commits

Issue by jwoolston from Thursday Mar 07, 2013 at 16:18 GMT
Originally opened as https://github.com/Tenkiv/TekDAQC_Firmware_Old/issues/5

As we discussed, the initial idea for the main loop is:

1. Measure all the inputs
2. Evaluate the inputs to handle unexpected values, emergency, etc.. (Currently this function will just be empty, we have yet to determine the behavior in this situation)
3. Command parser reads from the communication FIFO, if one ore more commands are completely fetched, execute them (either reading measurements and sending them back, or doing some settings, setting outputs, etc). Also, please include some diagnostics here on the FIFO size so we can experiment with its size.
4. Feed the watch dog timer (again, please try and include some diagnostics here about what the count value is prior to feeding so we can begin to formulate an idea about what an appropriate setting for that will be.

Issue by jwoolston from Tuesday Dec 10, 2013 at 04:46 GMT
Originally opened as https://github.com/Tenkiv/TekDAQC_Firmware_Old/issues/42

Issue by jwoolston from Tuesday Dec 03, 2013 at 18:27 GMT
Originally opened as https://github.com/Tenkiv/TekDAQC_Firmware_Old/issues/38

Resource: TekDAQC_Firmware_Development/TekDAQC_Libraries_Firmware/src/ADC_StateMachine.c
Location: line 193

Issue by jwoolston from Sunday Nov 03, 2013 at 04:40 GMT
Originally opened as https://github.com/Tenkiv/TekDAQC_Firmware_Old/pull/17

jwoolston included the following code: https://github.com/Tenkiv/TekDAQC_Firmware_Old/pull/17/commits

Issue by jwoolston from Tuesday Dec 10, 2013 at 04:49 GMT
Originally opened as https://github.com/Tenkiv/TekDAQC_Firmware_Old/issues/43

Issue by Matrinica from Tuesday Apr 16, 2013 at 03:59 GMT
Originally opened as https://github.com/Tenkiv/TekDAQC_Firmware_Old/issues/12

provide separate control for fetching a register and specific setting value to avoid overhead due to repetition of fetching.

can probably do the same to SPI Driver.

e.g., need to get Factory ID and Data Output Bit Order setting, call a function to fetch the status register, and call two functions for extracting the two values from the register value.

Issue by jwoolston from Sunday Nov 03, 2013 at 18:48 GMT
Originally opened as https://github.com/Tenkiv/TekDAQC_Firmware_Old/issues/18

• Remove all Stellaris code
• Add license statements to all code files
• Ensure all code is documented
• Redo documentation of TekDAQC_RTC firmware files.
• Cleanup any extraneous files
• Cleanup history for initial release
• Remove all dates will be left in files

Issue by jwoolston from Thursday Mar 07, 2013 at 16:00 GMT
Originally opened as https://github.com/Tenkiv/TekDAQC_Firmware_Old/issues/1

We should be able to call a calibration routine on the ADC driver. It should take a parameter of whether this is a system calibration or ADC only calibration and perform the requisite commands accordingly.

Issue by jwoolston from Tuesday Dec 03, 2013 at 18:23 GMT
Originally opened as https://github.com/Tenkiv/TekDAQC_Firmware_Old/issues/31

Resource: TekDAQC_Firmware_Development/TekDAQC_Libraries_Firmware/src/TekDAQC_CalibrationTable.c
Location: line 175

Issue by jwoolston from Tuesday Dec 03, 2013 at 18:25 GMT
Originally opened as https://github.com/Tenkiv/TekDAQC_Firmware_Old/issues/35

Resource: TekDAQC_Firmware_Development/TekDAQC_Libraries_Firmware/src/TekDAQC_config.c
Location: line 25

Issue by jwoolston from Tuesday Apr 16, 2013 at 16:06 GMT
Originally opened as https://github.com/Tenkiv/TekDAQC_Firmware_Old/issues/13

Issue by jwoolston from Tuesday Dec 10, 2013 at 04:43 GMT
Originally opened as https://github.com/Tenkiv/TekDAQC_Firmware_Old/issues/41

• Should return any errors over the control connection as well.

Issue by jwoolston from Friday Mar 08, 2013 at 01:01 GMT
Originally opened as https://github.com/Tenkiv/TekDAQC_Firmware_Old/issues/7

Issue by jwoolston from Tuesday Dec 03, 2013 at 18:22 GMT
Originally opened as https://github.com/Tenkiv/TekDAQC_Firmware_Old/issues/27

Resource: TekDAQC_Firmware_Development/src/main.c
Location: line 83

Issue by jwoolston from Tuesday Dec 03, 2013 at 18:22 GMT
Originally opened as https://github.com/Tenkiv/TekDAQC_Firmware_Old/issues/28

Resource: TekDAQC_Firmware_Development/TekDAQC_Libraries_Firmware/src/TekDAQC_CalibrationTable.c
Location: line 166

Issue by jwoolston from Tuesday Dec 10, 2013 at 05:10 GMT
Originally opened as https://github.com/Tenkiv/TekDAQC_Firmware_Old/issues/48

Add them to the ADC state machine

Issue by jwoolston from Tuesday Dec 03, 2013 at 18:25 GMT
Originally opened as https://github.com/Tenkiv/TekDAQC_Firmware_Old/issues/36

Resource: TekDAQC_Firmware_Development/TekDAQC_Libraries_Firmware/src/ADC_StateMachine.c
Location: line 181

Issue by jwoolston from Friday Mar 08, 2013 at 01:02 GMT
Originally opened as https://github.com/Tenkiv/TekDAQC_Firmware_Old/issues/9

Issue by jwoolston from Thursday Mar 07, 2013 at 16:11 GMT
Originally opened as https://github.com/Tenkiv/TekDAQC_Firmware_Old/issues/4

Create a command parser which is capable of examining incoming data and making decisions about what it code should be executed as a result. You can assume that there is a buffer of character data. If we can figure out how to do it I would like this to be a std::queue because it automatically implements a FIFO structure, but this will require integrating with the C of the lwIP library. I don't immediately see any reason why we can't do this since it wont require function pointers which is the only real obstruction to this.

That said, it probably makes the most sense to pas a pointer/reference to the queue in the constructor of the parser.

Issue by jwoolston from Tuesday Dec 10, 2013 at 05:07 GMT
Originally opened as https://github.com/Tenkiv/TekDAQC_Firmware_Old/issues/46

• All added analog inputs
• All added digital inputs
• All added digital outputs
• All added everything

Issue by jwoolston from Tuesday Dec 03, 2013 at 18:20 GMT
Originally opened as https://github.com/Tenkiv/TekDAQC_Firmware_Old/issues/25

Resource: TekDAQC_Firmware_Development/TekDAQC_Libraries_Firmware/src/ADC_StateMachine.c
Location: line 185

Issue by jwoolston from Wednesday Aug 28, 2013 at 21:13 GMT
Originally opened as https://github.com/Tenkiv/TekDAQC_Firmware_Old/issues/16

Issue by jwoolston from Tuesday Dec 03, 2013 at 18:23 GMT
Originally opened as https://github.com/Tenkiv/TekDAQC_Firmware_Old/issues/32

Resource: TekDAQC_Firmware_Development/TekDAQC_Libraries_Firmware/src/TekDAQC_CalibrationTable.c
Location: line 190

Issue by jwoolston from Tuesday Dec 03, 2013 at 18:16 GMT
Originally opened as https://github.com/Tenkiv/TekDAQC_Firmware_Old/issues/20

Resource: TekDAQC_Firmware_Development/TekDAQC_Libraries_Firmware/src/TekDAQC_CommandInterpreter.c
Location: line 605

Issue by jwoolston from Tuesday Dec 03, 2013 at 18:21 GMT
Originally opened as https://github.com/Tenkiv/TekDAQC_Firmware_Old/issues/26

Resource: TekDAQC_Firmware_Development/TekDAQC_Libraries_Firmware/src/ADS1256_Driver.c
Location: line 932

Issue by Matrinica from Sunday Mar 10, 2013 at 01:35 GMT
Originally opened as https://github.com/Tenkiv/TekDAQC_Firmware_Old/issues/10

weird.. not sure what's going on..

Issue by jwoolston from Friday Mar 08, 2013 at 01:02 GMT
Originally opened as https://github.com/Tenkiv/TekDAQC_Firmware_Old/issues/8

Issue by jwoolston from Tuesday Apr 16, 2013 at 16:07 GMT
Originally opened as https://github.com/Tenkiv/TekDAQC_Firmware_Old/issues/14