Ya, I could see where that would be a trip-up. I suppose adding a time to a date/time tells the interpreter to blend these two but a straight add doesn't.
Hi BC users,
I received a couple of questions about date/time manipulation, so wanted to post up a sample that may shed some light. In this "Test" script example, we define a date/time variable named 'trigger', assign it to a date/time, then print it (to the Output tab). We then define a time variable 'change', and make it one hour. We then define another date/time, and add the 'change' time variable to it, then print it. Finally, we compare the two date/time variables and generate a print out as a result (will always resolve to "Yes" here).
If you wanted to do a comparison to the current time, use the intrinsic 'now' variable (for example: trigger = now). Also, if you wanted to add days rather than hours, you can include days in the time variable (for example: change = 1:00:00:00).
.....
Website shows 1.0 as the 5/7/19 update. I assume it should be 1.1.
FYI, the link for the ESP32 wiring map is dead... link looks malformed.
Just a thought while looking over the v1.1 wiring map for the MEGA 2560. Please correct me if I am wrong but the wiring map states that interface pins 50, 51, and 52 are not connected (N/C). That is true unless you need to connect RTDs (perhaps via a RP2) as I understand it. As indicated in the RTD via SPI schematic, something actual IS connected to 50, 51, and 52. So why is the wiring map not reflective of this fact that to wire RTDs you need to connect to the SCK, MISO, and MOSI pins on the MEGA 2560 physically at pins 52, 50, and 51? This appears unnecessarily muddy.
One big FYI for RTD users... since we moved away from a discrete "w/RTD" wiring map, this map will not exist any longer, which will render your configuration null. Please either use the legacy interface definition files included in the v1.1 distro, or email us your configuration, and we'll edit it to work with the new RTD integrated interface definition file.
I had a thought that might help setting up brand new interfaces.
With the genuine Arduino devices I bought for my client, it was easy enough to grab the MAC address from the shield. I purchased a "DuinoTech" (Aus Arduino clone) Mega R3 and their Ethernet shield does not have the MAC address on it. I had a little bit of fun finding it in my router DHCP lists.
Maybe you could write the devices' current IP address to the LCD screen if connected. BruControl won't be writing to it as it doesn't know about it yet. That would make it easier to find the device in the router DHCP lists and assign a reservation for it. Maybe write the MAC address to the LCD as well.
Are you saying that if I have RTDs then the only way to make them work with 1.1 is to contact you for a special map or use a legacy map?One big FYI for RTD users... since we moved away from a discrete "w/RTD" wiring map, this map will not exist any longer, which will render your configuration null. Please either use the legacy interface definition files included in the v1.1 distro, or email us your configuration, and we'll edit it to work with the new RTD integrated interface definition file.
Are you saying that if I have RTDs then the only way to make them work with 1.1 is to contact you for a special map or use a legacy map?
So If I use RTDs I should probably just stick with version 1.0 and not expect any further support in future updates?
Using PIDS vs this is looking like the thing to do if I don't want to deal with headache after headache. This is moving further away from being an alternative to the mainstream approach and more and more looking like a hobby within a hobby for a select few.
Are you saying that if I have RTDs then the only way to make them work with 1.1 is to contact you for a special map or use a legacy map?
So If I use RTDs I should probably just stick with version 1.0 and not expect any further support in future updates?
The original version works as well as it always did. Theres no need to update unless you want to take advantage of some new upgrade feature or fix a bug that someone using scripts may have found. Its just like those who choose to replace their auber pids with the latest and greatest version of the EZboil only you dont have to pay to replace the hardware... aubers upgraded the ezboil what 3-4 times now?Using PIDS vs this is looking like the thing to do if I don't want to deal with headache after headache. This is moving further away from being an alternative to the mainstream approach and more and more looking like a hobby within a hobby for a select few.
Are you saying that if I have RTDs then the only way to make them work with 1.1 is to contact you for a special map or use a legacy map?
So If I use RTDs I should probably just stick with version 1.0 and not expect any further support in future updates?
You need to double-click the M0 so the LED blinks bright and dim. Then it will take the FW.
My apologies. Thank you for the info. I've started working nights again and I have a tendency to be irrational and cranky when I work nights. Nothing to see here folks, please move along.Sorry, perhaps I didn't explain it correctly. We removed the need for a separate firmware and interface map to use RTDs. In the process, made essentially every digital pin RTD capable (thanks @clearwaterbrewer for the push). Because we removed the map, when you migrate to v1.1, BC will look for a map that doesn't exist. To fix that, we just need to redirect the map name in your configuration. We offered the service to it for you - and I posted instructions to do it yourself via a text edit sequence above. Or you can copy over the old map and use it (though we don't suggest this - we provided it for assured compatibility).
Sorry it's not automatic - we think this is a improvement, and forward movement sometimes needs some quick adjustments. I actually think we have made it a lot easier to adopt by consolidating maps and firmware versions.
I'm sincerely sorry you feel that way - can you expand on your "headache after headache" comment? I personally don't see how wiring discreet PIDs and their limitations is better than software based controls, but I can appreciate your opinion.
Ok... tested, works correctly on my end. Are you saying Termite never starts when you select main menu option 2 and follow the prompts?
Enter your email address to join: