OK, didn't think about that.. doh! I am not in front of it, and cannot double click the button...If 45 is updating the FW, then use 44 to open termite. Or open it manually by running the termite.exe file in the resources folder.
OK, didn't think about that.. doh! I am not in front of it, and cannot double click the button...If 45 is updating the FW, then use 44 to open termite. Or open it manually by running the termite.exe file in the resources folder.
If 45 is updating the FW, then use 44 to open termite. Or open it manually by running the termite.exe file in the resources folder.
Just an FYI -
in BC V1.1, I could use, but not add devices to my SonOff Dual interfaces. I loaded up the last RC version of BC and added the device I wanted and went back to 1.1 and it all worked... I will upgrade the FW on the SonOff, but they are mounted high up on a wall.
View attachment 626303
Ethernet devices (Wiznet based) do not have a MAC address hard-coded into the chip or onboard. Therefore, the firmware cannot poll the address - it can only assign it. The units which have a sticker are simply there to tell the user that specific address was reserved for that board (they paid for it). The units which don't require you to generate one, and in doing so, could create a duplicate one, though the risks of overlap are small as most devices will be behind private networks like ours.
So while your idea is a good one, it would not be possible. You mentioned your router found the MAC address, but possibly it found the default MAC in the firmware of AB:BC:CD: DE:EF:FA and IP of 192.168.1.100. WiFi devices do have MAC addresses hard-coded, and those can be polled.
ver 1.2 request
It would be really great for all Elements to have a new field TextDisplay that is a String.
Not sure I am following. Are you saying you want multiple elements to be able to use the same name? Or maybe not name but an alias?
We could probably do that... would need to think of the implications, if any.
That said, nothing should be changing the shield's MAC address. Maybe I don't understand the issue, but the shield's MAC and IP (if static) should never change.
I do not understand how you can or would use a Port for a Different Element:
For Example: My Port 2 is a Hall Effect Counter.
I can still select Port 2 for all of the Outs and as a Digital Input on a New Device.
Are there Restrictions? For example, you could use a Digital Input but not a Digits Out for Port 2 that had been used as a Hall Effect Counter?
It is a good idea to do this? Do you need any addition circuits? Why would you do it?
Just trying to wrap my head around it. Some practical application explanation would be nice.
in my case I use cheap ebay p100 sensors because I found out of all the different ones Ive bought they are all made by the same 2 manufacturers and most were the same manufacturer as aubrins uses (DTK I believe as they come in a labeled plastic bag) I use these currently on my 3bbl setupThe shield being grounded is what I have come to believe, but then the components guy says no, and he made the point of being in industry for 30 years so...
Cool, I will continue to chase down a 4 metre shielded 3-wire PT100 probe and ground it to arduino gnd.
We haven't even placed the PT100 in the thermowell in the fermentor (need long cable) so hadn't got to that point yet. Maybe heat-shrink the probe if the fermentor is grounded (no idea on that)
Awesome, thanks for your help again. I will update my software to use the BruControl API tonight instead of the logs. Initial API testing has worked well and it will be about a 10 minute job to update my in-between software to use the API.
Let's see if I got this:BC just gives you the flexibility to make whatever each pin/port is capable of. If you have a counter input on a pin, you would likely not create another element on that pin/port. However, if you had a heater element on a pin, you might make a PID Output as well as a Duty Cycle on that port. When you enable one device element, the others on the same port are automatically disabled.
Again, this is just there for ultimate flexibility. We don't tell you you "you have 8 inputs and 8 outputs and that's it"... we are saying "you have 16 I/O - do what you like with them". I suppose we could disable all output creation when a port is defined as an input - but we think you are all smart enough to know this and won't create conflicting I/O inconsistent with the hardware. Make sense?
Yes... I also setup something very similar, but I go between PID and duty cycle.
same here for BK.Yes... I also setup something very similar, but I go between PID and duty cycle.
Enter your email address to join: