Thank you for another wonderful build. Greatly appreciated.
I have just finished building mine and have noticed few things with the software:
1. The connection via Bluetooth can be done only once. Once disconnected any attempt to connect again will result in an error (at reading firmware). The Nano has to be reset to recover.
To reproduce, simply connect via Bluetooth, disconnect and try connecting again.
The Tracking Mode Offset
The PC software allows setting of values between -4 and 4. However, the controller only uses values between -4 and 3. In other words if you set TMoffset=4 the controller will use the value of 3.
Channel Offset
The offset seems to be doubled from what is set. For example, setting an offset of 1 increases the temperature by 2 degrees, setting an offset of 2 increases the temperature by 4 degrees and so on. Is this by design or a software bug?
(I tested this only on channel 1)
Using the latest 3.0.5.8 version of the Windows software and 331 firmware with the latest Gerbers (rev5).
Thank you again,
Luke
Last edit: Luke 2019-09-26
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Robert,
Thank you for another wonderful build. Greatly appreciated.
I have just finished building mine and have noticed few things with the software:
1. The connection via Bluetooth can be done only once. Once disconnected any attempt to connect again will result in an error (at reading firmware). The Nano has to be reset to recover.
To reproduce, simply connect via Bluetooth, disconnect and try connecting again.
The Tracking Mode Offset
The PC software allows setting of values between -4 and 4. However, the controller only uses values between -4 and 3. In other words if you set TMoffset=4 the controller will use the value of 3.
Channel Offset
The offset seems to be doubled from what is set. For example, setting an offset of 1 increases the temperature by 2 degrees, setting an offset of 2 increases the temperature by 4 degrees and so on. Is this by design or a software bug?
(I tested this only on channel 1)
Using the latest 3.0.5.8 version of the Windows software and 331 firmware with the latest Gerbers (rev5).
Thank you again,
Luke
Last edit: Luke 2019-09-26