For information about version 4.0 and the public betas, please see the post announcing 4.0 Public Beta 1. All information included in that post is still relevant to this release.
Attached to this post is Public Beta 2 which has resolved the following issues from Public Beta 1:
Make UI properly update process state after using All Stop button. Fixes #172
Remove Web Input from Exit Conditions source type drop down. Fixes #168
Do not allow setting a negative setpoint for duty cycle. Fixes #173
Write system config to flash if led_display is updated
Allow entering tenths for values that support them. Closes #178
Divide duty cycle by factor of 10 when setting outputs. fixes #169
Use value * 10 for PID integer settings. fixes #174
This build can be identified by the version number: 4.0.0 build ec24318 on the Settings page.
Can't seem to get Beta 2 to take. Used same process as Beta 1, even choosing different target directories including directory used for Beta 1 after deleting Beta 1 .bin file and redownloading, nada. TFTP log shows success, but fixes aren't fixed and still shows Beta 1 build number on settings page.
Did system reset, reset to defaults and repeated above. Still nada.
Any ideas?
I was going to say make sure beta 2 doesn't get saved as bcs460(1).bin. My next guess is that tftp is not using the directory you intend. It loaded fine on my bcs 460.
Closed and restarted tftp, reselected target directory and file, still nada.
I just spoke with someone in India. They recommended that I reboot.
Switching to red wine and rebooting.................
*edit*
Red wine worked, reboot, eh.
Moron here.............
tftp I'm using apparently (with BCS?) needs target file in tftp root directory.
All is well, back to learning curve.
Thanks for suggestions.
Does fix #169 mean that the duty cycle works now? In beta1 I observed that the output would be on 100% of the time no matter what I set the duty cycle to. Its not clear from the comment in the OP whether it will actually cycle the output at the desired duty cycle or not.
In beta 1 the duty cycle was off by a factor of 10. If you look around you can find a post explaining it. So anything over 10 was running at 100%, 5.0 would have been 50%. That's been fixed in beta 2, so that 50 is 50% duty cycle.