• Joined on 2020-12-04
jbqubit commented on issue M-Labs/thermostat#21 2020-12-17 01:53:05 +08:00
document postfilter

What you've got exposed now is fine. But documentation should say what is being set by the command.

jbqubit opened issue M-Labs/thermostat#27 2020-12-15 02:20:35 +08:00
single repository for thermostat, thermostat_EEM
jbqubit commented on issue M-Labs/thermostat#21 2020-12-15 02:19:29 +08:00
document postfilter

It wasn't clear to me that this was a hardware filter until this comment just now. I gather this relates to register ENHFILTEN0 on AD7172.

This bit enables various postfilters for enhanced 50…

jbqubit opened issue M-Labs/thermostat#26 2020-12-10 07:35:53 +08:00
software activation of boot-into-DFU mode
jbqubit commented on issue M-Labs/thermostat#11 2020-12-09 01:11:38 +08:00
loop servo time step / PID autotune

but please don’t push for changes that would increase the design complexity until you’ve really engaged with how the design works.

Agreed. Asking questions helps clarify design intent and…

jbqubit commented on issue M-Labs/thermostat#24 2020-12-09 01:05:09 +08:00
review (firmware-hardware) vs (Thermostat design goals)

Curious who besides Oxford, oxionics and I are using Thermostat?

jbqubit pushed to flashdoc at jbqubit/thermostat 2020-12-09 01:00:10 +08:00
7af5d8582d not yet ready note
jbqubit commented on issue M-Labs/thermostat#23 2020-12-09 00:54:43 +08:00
README.md not-ready-for-lab-use warning

I haven't looked at the consumer-facing side of the M-Labs website in a long while. Looks pretty slick!

Best if project status is reflected in README.md as this is where we put authoritative…

jbqubit opened issue M-Labs/thermostat#24 2020-12-09 00:49:54 +08:00
review (firmware-hardware) vs (Thermostat design goals)
jbqubit opened issue M-Labs/thermostat#23 2020-12-09 00:39:31 +08:00
README.md not-ready-for-lab-use warning
jbqubit commented on issue M-Labs/thermostat#11 2020-12-09 00:31:53 +08:00
loop servo time step / PID autotune

So there is some jitter introduced to the loop by all of this….however, do we care?

Agreed that ms scale changes in loop filter period don't matter for controlling temperature of devices with…

jbqubit opened issue M-Labs/thermostat#22 2020-12-09 00:26:28 +08:00
gain independent of sample period
jbqubit opened issue M-Labs/thermostat#21 2020-12-09 00:24:18 +08:00
document postfilter
jbqubit created pull request M-Labs/thermostat#20 2020-12-09 00:13:09 +08:00
flashing with dfu-util
jbqubit pushed to flashdoc at jbqubit/thermostat 2020-12-09 00:10:48 +08:00
fca2de665c flashing with dfu-util
ffcc3f661b README: add pid units
2a6f8ed874 pytec: use py3 dict methods
5e8bf0e765 README: add Debugging and Flashing
5ddd4d250e channels: swap adc inputs
jbqubit commented on issue M-Labs/thermostat#14 2020-12-08 08:54:41 +08:00
python 2.7 dependencies in pytec

Confirmed that this works. Thanks!

jbqubit commented on issue M-Labs/thermostat#11 2020-12-08 08:48:10 +08:00
loop servo time step / PID autotune

At present if there's an edit to the firmware that computes feedback, the loop filter periods may change. This would then require edits to kp, ki, kd as used in the lab. Better to choose a…

jbqubit commented on issue M-Labs/thermostat#16 2020-12-08 08:40:44 +08:00
after reset first call to report is empty

What is the reason for resetting the device?

I would like that my configuration script start with Thermostat in a well defined state priod to setting registers.

jbqubit commented on issue M-Labs/thermostat#17 2020-12-08 08:38:17 +08:00
save does not preserve pid_engaged

Fully autonomous operation is highly desirable. Once initial configuration is complete it will be rare to work with Thermostat interactively. Ideally this recovers after power failure and continue…

jbqubit closed issue M-Labs/thermostat#18 2020-12-08 08:35:59 +08:00
ipv4 lost at power cycle