Libraries v0.8.5.17
Posted: Mon Sep 26, 2011 6:25 am
I just released the latest version of the libraries: v0.8.5.17
There has been lots of fixes and changes made to this release. You WILL want to look over the change list and plan accordingly. There are several changes that will affect people. The most notable changes are:
The rest of the significant changes are here:
You can update with the Update utility (recommended for simplicity), manually update the libraries by downloading them or by running the RAGen installer and updating the libraries.
curt
There has been lots of fixes and changes made to this release. You WILL want to look over the change list and plan accordingly. There are several changes that will affect people. The most notable changes are:
- MoonPhase() added to the globals file - For those people who manually added the function to their PDE file, you can safely remove the function definition from your PDE file. You can still use the function, you just don't have to add the entire function.
- CovertNumToString() added to the globals file - Same comment/note as with MoonPhase()
- Feature PWMExpansionRelay is changed to just be PWMExpansion - for better and more logical reading in the code as to what it does.
- DelayedOn is not part of the Relay class - Currently, if you use the DelayedOn function, you would call it ReefAngel.DelayedOn(Port, Delay). Now, it's moved to the relay class to make it more logical (like with the On & Off functions). So now, you call it this way
Code: Select all
ReefAngel.Relay.DelayedOn(Port, Delay);
The rest of the significant changes are here:
- Faulty temp sensor check
- Display an error when the temp sensor reads 0 and not when PWM displays 0
- Added in unknown request handling via wifi
- Handle HTTP feedback from external servers
- Wifi response fixes
- Fixed setting date & time via wifi
- Fixed SaveRelayState compilation error
- Ability to change the overheat temp monitoring probe from temp2 to whatever temp you want. This is handled inside the setup() function. The default is to use temp2 probe, but if you want to change it, use one of these lines:This has to be called after ReefAngel.Init(); otherwise it will not work.
Code: Select all
// To use Temp1, add this line to setup(): ReefAngel.OverheatTempProbe = &ReefAngel.Params.Temp1; // To use Temp3, add this line to setup(): ReefAngel.OverheatTempProbe = &ReefAngel.Params.Temp3;
- Added in flag storing for exceeded values (with ATO Timeout & Overheat Temp) - You can now distinguish what event caused the red LED to turn on. This must be enabled inside the features file to work. Use this line to enable it:Once enabled, you will have to manually check to see what event triggered the red LED. This is done by reading the internal memory. It is designed to be incorporated into a custom main screen but can be put into a menu or queried manually via the wifi interface. Here's the commands to read it from memory on the controller:
Code: Select all
#define ENABLE_EXCEED_FLAGS
You can use any of the checks. The ATO check is for the standard ato. The ATO Single check is for the single ato functions (no distinction currently for high or low ato). The Overheat check is for the overheat temp checks.Code: Select all
// Check for ATO (byte, location 748) InternalMemory.read(ATO_Exceed_Flag); // Check for Single ATO (byte, location 747) InternalMemory.read(ATO_Single_Exceed_Flag); // Check for Overheat (byte, location 749) InternalMemory.read(Overheat_Exceed_Flag);
- ATO Event logging added - This will be able to log the last 4 ato events (either standard or single). If using single ato, it will log the low and high events separately. If the events are not cleared out (by querying the controller), the oldest event is cleared first and so forth in a cyclic manner. This is enabled with the following line inside your features file:You can then query the controller for the standard relay status plus the ato logging events with this command, /sa, instead of the typical /r99 command.
Code: Select all
#define ENABLE_ATO_LOGGING
- Custom Menu Creation added - You can now create a custom menu from within your PDE file. The menu is only a single menu (like SIMPLE_MENU) but can be customized as you desire. There are several things that you must enable in the features file and add to you PDE file. A guide has been created and a separate topic will be created for how to enable and use a custom menu. Here's a link to the guide:
http://curtbinder.info/ragen/docs/RA_Custom_Menu.pdf
You can update with the Update utility (recommended for simplicity), manually update the libraries by downloading them or by running the RAGen installer and updating the libraries.
curt