We messed around with this driver and got it working but dumped it because it was slow. We can add it back but I don't know what will happen with other operations when writing to it.
I may tinker with it being standalone, not like I can't switch it back to BC if you get a bug to make it work.... I will crawl the m5 search results in this thread to see any potential differences, and tinker... thanks!We messed around with this driver and got it working but dumped it because it was slow. We can add it back but I don't know what will happen with other operations when writing to it.
Will give it a look after some other projects wrapped up.
I don't see an Ethernet port on that mini-pc, will this one work with BruControl?Pretty cool (and mini) mini-pc if anyone is in the market: : https://www.amazon.com/dp/B08KCZPQ3P
No worries @BrunDog. Basically Digital Outputs aren't responding to the UI on 45O firmware for me, I'll just repost below from last week rather than paraphrase.Sorry, I didn’t see a notice there was a new post to this thread...
Can you be more specific? I don’t know about any issues.
Hi @BrunDog, sorry for another message today but Digital Output Devices seems to be broken on 45O on my ESP32. I've got v1.1.9 running, and two ESP32s connected, one on 45O and one on 45N. I've added a new device to BruControl port 4 on each to test, state changes work fine on the 45N interface but don't stick on the 45O interface. Setting the device to the LED indicator, red for OFF and green for ON, the "LED" graphic stays grey on 45O. No signal is received by the relay board (it has an indicator light on the board) on the other end of Port 27 on the 45O interface, which was working fine last night on 45N.
Cheers,
Edit: another data point - I've flashed that ESP32 back to 45N and the digital output devices are responding correctly again.
Thank you, much appreciated.Hmm ok I must have overlooked that.
We’ll test it and see where the problem is.
Sneak peek of my UniCon build, waiting on parts still but it’s getting more complete every day!
View attachment 706640
Thank you, much appreciated.
Good stuff, thank you!Figured it out... we made changes to 45O to accommodate a protocol change in application v1.1 Build 12, which we didn't actually post. Big duh moment - sorry.
We should be posting Build 13 this week, so will update all the FW's to 45O to match and push it all together.
Anyone use Load Cells with BruControl?
Interesting read. Do I read this correctly? You need a UNO or other Audrino to accept the code and that send the data to you BC Mega?
Sure it would be great to perhaps integrate this into a controller connected to BC directly and perhaps someday that will be possible. Considering the low cost of these controllers and how I wanted a local display with local tare functionality from that local UI, the separate controllers, lcd displays, and feeding an analog output to the BC controller via the 12-bit MCP4725 DAC works really well. That kind of detail would not be easy within the confines of a BC element for example nor would driving a local display to show the units I want, etc..
Sounds like a great application for my back door data exchange framework I provided instead of sending the data as an analog signal to a Brucontrol enabled board.
Interesting... Atmel ATMega32U4 in a PiZero form factor... not sure if it will get any traction.... but interesting....
https://shop.atmegazero.com/products/atmegazero-header-pins-included
Could you post a Part's List and where you got them?For anyone interested in putting together an Arduino Uno based load cell controller with a local LCD display, local tare and calibration functions via the LCD buttons, with an analog output via a 12-bit DAC that can be connected to a controller running a BC firmware, the Arduino sketch in the attached text file will get you there. There are many ways to do things so feel free to make changes as you see fit.
What version of BC?
And whilst disconnected, you can ping them?
Enter your email address to join: