I know many are waiting but seems like little issues keep cropping up...
So here is the present status:
I got lazy in the initial code and the way I was getting data from the devices. See, the CANBUS has hundreds of packets of data being "streamed" every minute. Me not wanting to sort through all this data for the few bits of information I needed, I decided to just "ask" the devices for what I wanted. Well, seems the MNGP2 does not like "others" asking for data that is available on "the stream", it gets confused as it thinks it should be the only one "asking". Now I had to rewrite the whole code base, building "CANBUS Engines" to filter out and grab only what data I wanted for each device. The new engines run in the background and update data periodically and it is stored in the database. I also optimized code to shut down and release memory & resources for devices that are not actively running on the system.
The new system has been running for 4 or 5 weeks now with almost no glitches, it's time for me to go back over and double check the new code. The Classic module is a big mess so I started from scratch on it and while I'm at it, adding code to get it as a device on the new MNS CANBUS as another supported MPPT device. This is a daunting task but I'm making progress. I have built almost a complete MPPT Charge Controller in software that the MNGP2 can't tell from a real one. All I need to do is read the MODBUS data from the Classic and "attach" it to the proper CANBUS registers and bing! Classic on the CANBUS.
Everyone have a nice Holiday and I will try and post updates more often...
JIm
Is it possible to support CanBus batteries (such as EG4-LL V2 48v) in a similar fashion, or are they already supported by Rosie/Barcelona?
R.
Quote from: Raster on December 23, 2023, 02:44:41 AMIs it possible to support CanBus batteries (such as EG4-LL V2 48v) in a similar fashion, or are they already supported by Rosie/Barcelona?
R.
I don't believe any battery systems are supported as yet in a closed-loop connection to the CANBUS. But, it's a great question. I have the new Pytes V5 batteries and would like to have closed loop capability as well. Perhaps the re-written software will allow the data from these streams to be "attached" to the CANBUS registers just like the Classic data?
"I don't believe any battery systems are supported as yet in a closed-loop connection to the CANBUS"
Actually, some of this has been done but I don't remember how many different batteries ? Maybe I never knew ? But there is some work going on here. I'm just not privy to knowing which one(s)
No EG4 closed loop yet as far as I know.
It's going forward though and more and more BMS's should be added
boB
Quote from: boB on December 23, 2023, 05:06:04 PMActually, some of this has been done but I don't remember how many different batteries ? Maybe I never knew ? But there is some work going on here. I'm just not privy to knowing which one(s)
Great news! Looking forward to this update.
Dave
Yes, it's been a while since I posted an update, I work part-time helping out in the tech support department, things are really busy with the new products... and old...
Okay, here is where we are at:
HARDWARE MODIFICATIONS - Adding a 9V battery, charging circuit and detect for power gone for safe shutdown to avoid LINUX file system corruptions. I updated my Rosie's yesterday and forgot it shuts off the power and BAM, crashed the COMBOX LINUX file system. I had to make a new Micro SD card and set it back up. I suspect only a small percent of our COMBOX owners will be able to do this and we would need to mail out a replacement Micro SD card every time. I have a prototype on my bench with a bread board working on it now. Maybe an option for user supplied 9V non-rechargeable battery, I'm using a slightly expensive 9V lithium with BMS built-in. Shipping devices with lithium battery might be a problem to some locations.
SOFTWARE UPDATES - For the first units this will need to be done by USB thumb drive, copy the update file, plug it into the COMBOX, load the config page and select USB UPDATE. The software code for this still needs to be done. Next step is to add code to update from the Midnite Server and leave the USB option for sites without Internet.
STILL to DO:
1) Add option to set the CLOCK without an active Internet connection.
2) Finish adding the Classic to the CANBUS so MNGP2 can control it.
3) Rework code modules for DIY3024, DIY3548, DIY5048.
4) Add module to access the NEW MNS AIO 10K Inverter.
5) Get user feedback for options.
6) Update and finish the manual...
Quote from: Wizbandit on March 02, 2024, 07:19:26 AMYes, it's been a while since I posted an update, I work part-time helping out in the tech support department, things are really busy with the new products... and old...
Okay, here is where we are at:
HARDWARE MODIFICATIONS - Adding a 9V battery, charging circuit and detect for power gone for safe shutdown to avoid LINUX file system corruptions. I updated my Rosie's yesterday and forgot it shuts off the power and BAM, crashed the COMBOX LINUX file system. I had to make a new Micro SD card and set it back up. I suspect only a small percent of our COMBOX owners will be able to do this and we would need to mail out a replacement Micro SD card every time. I have a prototype on my bench with a bread board working on it now. Maybe an option for user supplied 9V non-rechargeable battery, I'm using a slightly expensive 9V lithium with BMS built-in. Shipping devices with lithium battery might be a problem to some locations.
SOFTWARE UPDATES - For the first units this will need to be done by USB thumb drive, copy the update file, plug it into the COMBOX, load the config page and select USB UPDATE. The software code for this still needs to be done. Next step is to add code to update from the Midnite Server and leave the USB option for sites without Internet.
STILL to DO:
1) Add option to set the CLOCK without an active Internet connection.
2) Finish adding the Classic to the CANBUS so MNGP2 can control it.
3) Rework code modules for DIY3024, DIY3548, DIY5048.
4) Add module to access the NEW MNS AIO 10K Inverter.
5) Get user feedback for options.
6) Update and finish the manual...
Can you build string of MQTT or option for that into the output so we can integrate into our existing monitoring systems ?
Will the Canbus protocol ever be published like the Classic modbus has been ?
Thanks for your efforts - will look forward to trying out whatever comes out of it.
Larry
I did install a MQTT Broker or "server" as it is now called on my development COMBOX, it is running but I have not tested it. It claims to be a "low bandwidth" service but that does not mean it does not need a lot of processor to operate. As it just serves to distribute "published data" to "subscribers" with no data being stored on the actual server I would need to publish to it first. With over 400 different data points I don't want to publish every one as I suspect that would load down the system to a halt.
The only way I can see to accomplish this is to have a configuration page for each device, Rosie Inverter, Barcelona, Hawkes bay, Classic, KID, DIY3024, DIY3548, DIY5048, 10K MNAIO-ONE. Each page would allow the user to turn "on" MQTT and select using "check boxes" the data they would like published to the broker, select too many and the system crawls to a halt.
I still need to work on "safe shutdown" hardware, with the increase in support calls I have had little time to work on this issue. Once it is done I could start on building the configuration pages and testing. You would need to have some way to have your external monitor systems access the broker as I won't have time to work on outside devices.
The MNS CANBUS is complicated and not real easy to understand. Where as you read a 16 bit MODBUS register and get for example "Battery Voltage" our CANBUS is 64 bits and each of these packets can hold from 1 to 8 bytes of data. For example register 0x0A0 is the "battery register", it has 2 bytes for voltage, 2 bytes for current and 4 bytes for power (watts) stored in "big-endian" whereas MODBUS uses "little-endian". I know this won't mean much to many of you but the bytes need to be combined to get the one data value.
MODBUS data is requested per 16 bit register whereas CANBUS data is "streamed" and you need to monitor for the data you want which requires multiple tasks running concurrent in the background. That being said there are configuration registers that must be requested and they return up to 64 bits of data that needs to be unpacked and combined.
It took me over a year to become really good at this...FYI
Quote from: Wizbandit on March 06, 2024, 06:57:14 AMI did install a MQTT Broker or "server" as it is now called on my development COMBOX, it is running but I have not tested it. It claims to be a "low bandwidth" service but that does not mean it does not need a lot of processor to operate. As it just serves to distribute "published data" to "subscribers" with no data being stored on the actual server I would need to publish to it first. With over 400 different data points I don't want to publish every one as I suspect that would load down the system to a halt.
The only way I can see to accomplish this is to have a configuration page for each device, Rosie Inverter, Barcelona, Hawkes bay, Classic, KID, DIY3024, DIY3548, DIY5048, 10K MNAIO-ONE. Each page would allow the user to turn "on" MQTT and select using "check boxes" the data they would like published to the broker, select too many and the system crawls to a halt.
I still need to work on "safe shutdown" hardware, with the increase in support calls I have had little time to work on this issue. Once it is done I could start on building the configuration pages and testing. You would need to have some way to have your external monitor systems access the broker as I won't have time to work on outside devices.
The MNS CANBUS is complicated and not real easy to understand. Where as you read a 16 bit MODBUS register and get for example "Battery Voltage" our CANBUS is 64 bits and each of these packets can hold from 1 to 8 bytes of data. For example register 0x0A0 is the "battery register", it has 2 bytes for voltage, 2 bytes for current and 4 bytes for power (watts) stored in "big-endian" whereas MODBUS uses "little-endian". I know this won't mean much to many of you but the bytes need to be combined to get the one data value.
MODBUS data is requested per 16 bit register whereas CANBUS data is "streamed" and you need to monitor for the data you want which requires multiple tasks running concurrent in the background. That being said there are configuration registers that must be requested and they return up to 64 bits of data that needs to be unpacked and combined.
It took me over a year to become really good at this...FYI
I think there is a difference between publishing the data and having a broker ?
I am no expert. I use Grahams Classic MQTT software and pretty sure it does not publish ever data point available - just the ones most of us would want to use - voltage, current, soc, whizbang, state of charge, etc.
I have the broker running on my raspberry pi - so don't need one running in a combox.
Anyway thanks for including mqtt - it will make life a lot easier for anyone wanting to monitor data.
As far as Canbus - I gave up on trying to figure it out for the Hawkes Bay because my old brain isn't up to the task now.
Larry
I agree with Larry, having a broker in the combo box doesn't help us DIYers. We need to integrate data from various sources for display in grafana/influxdb or load/diversion control in node-red or homeassistant...
Also if the broker is in the "cloud", it allows us to access the data from anywhere on the internet...
I have a couple of projects in Github that convert serial data from Jakiper lithium batteries to MQTT and modbus data from the classic to MQTT, now we'll need to have a Canbus to MQTT converter...
It would be great if the Combo box dealt with all the complicated Canbus comms and included a simple MQTT publisher to forward the relevant data to a broker.
An MQTT publisher feature should not be a load on the CPU (I have light bulbs that publish MQTT).
Graham
In the simplest of terms that an elderly Tennessee Hillbilly can understand:
What is the issue the Combox is intended to resolve?
What is the issue that MQTT is intended to resolve?
I do appreciate y'alls patience.
Quote from: Barry Fields on May 23, 2024, 10:23:16 AMIn the simplest of terms that an elderly Tennessee Hillbilly can understand:
What is the issue the Combox is intended to resolve?
What is the issue that MQTT is intended to resolve?
I do appreciate y'alls patience.
The Combox is a communications product design that is still in progress but close to seeing some sold.
It is a plastic box with Orange Pi inside that has 4 CAN ports, Ethernet, USB, 2 RS-232 ports for Classic integration... It can be powered by Rosie, Barcelona, Hawkes Bay over CANBUS or 9V to 12V Wall Wart supply.
I was going to add a picture of it but it doesn't look like that is an option for this posting.
It has to be on some URL which I do not have without uploading to another web page it looks like
Quote from: boB on May 23, 2024, 12:49:32 PMIt is a plastic box with Orange Pi inside that has 4 CAN ports, Ethernet, USB, 2 RS-232 ports for Classic integration...
Could that function be performed by the STM32F030 in my proposed BBMT product?
What is MQTT for?
Quote from: Barry Fields on May 23, 2024, 01:38:10 PMQuote from: boB on May 23, 2024, 12:49:32 PMIt is a plastic box with Orange Pi inside that has 4 CAN ports, Ethernet, USB, 2 RS-232 ports for Classic integration...
Could that function be performed by the STM32F030 in my proposed BBMT product?
What is MQTT for?
MQTT is some kind of IoT communications protocol. That is all I know.
Google can tell you more but I am unfamiliar with it.
boB
Quote from: Barry Fields on May 23, 2024, 01:38:10 PMQuote from: boB on May 23, 2024, 12:49:32 PMIt is a plastic box with Orange Pi inside that has 4 CAN ports, Ethernet, USB, 2 RS-232 ports for Classic integration...
Could that function be performed by the STM32F030 in my proposed BBMT product?
What is MQTT for?
I would use a bit higher powered STM32 part than the STM32F030 myself but that part might work.
https://midniteftp.com/forum/index.php?action=dlattach;attach=10367;type=preview
Quote from: Barry Fields on May 23, 2024, 10:23:16 AMIn the simplest of terms that an elderly Tennessee Hillbilly can understand:
What is the issue the Combox is intended to resolve?
What is the issue that MQTT is intended to resolve?
I do appreciate y'alls patience.
Quote from: Barry Fields on May 23, 2024, 10:23:16 AMIn the simplest of terms that an elderly Tennessee Hillbilly can understand:
What is the issue the Combox is intended to resolve?
What is the issue that MQTT is intended to resolve?
I do appreciate y'alls patience.
This was software project that Graham created for the Classic. It is explained on page linked below. Basically the Classic had limitation of being able to only have one modbus link at a time. And that link had to be local or some kind of ip tunnel or whatever. The project linked made it so that something like a raspberry pi could connect to the Classic, and then publish the Classic data as MQTT . Those mqtt packets are easy to send out either locally via pi , or to external source. You don't need to open any ports on your router or do anything magic networking wise. Once the data is in mqtt form - as many clients as you want can get that data at the same time which got rid of the only one connection at a time limitation. Here is the link so you can see the graphic that Graham had made about it. https://github.com/ClassicDIY/ClassicMQTT
I use it via a raspberry pi with my classics and it is stable and never crashes.
https://github.com/ClassicDIY/ClassicMQTT
Larry
Quote from: ClassicCrazy on May 23, 2024, 03:47:39 PMThis was software project that Graham created for the Classic. It is explained on page linked below. Basically the Classic had limitation of being able to only have one modbus link at a time. And that link had to be local or some kind of ip tunnel or whatever. The project linked made it so that something like a raspberry pi could connect to the Classic, and then publish the Classic data as MQTT . Those mqtt packets are easy to send out either locally via pi , or to external source. You don't need to open any ports on your router or do anything magic networking wise. Once the data is in mqtt form - as many clients as you want can get that data at the same time which got rid of the only one connection at a time limitation. Here is the link so you can see the graphic that Graham had made about it. https://github.com/ClassicDIY/ClassicMQTT
I use it via a raspberry pi with my classics and it is stable and never crashes.
https://github.com/ClassicDIY/ClassicMQTT
Larry
Your post was really appreciated and kept me out of the bar for a couple of hours.
I am really trying to understand the interconnections. I have attached a crude diagram of what I think I understand.
How does MQTT get to the cloud? Ethernet to the router?
"Basically the Classic had limitation of being able to only have one modbus link at a time." Explain please.
Feel free to edit my diagram iffn ya like.
Quote from: Barry Fields on May 23, 2024, 10:23:16 AMIn the simplest of terms that an elderly Tennessee Hillbilly can understand:
What is the issue the Combox is intended to resolve?
The MNCOMBOX is a "data miner", it gathers data and allows the user to customize their "Dashboard" to display whatever they want or feel is important. All I do is gather the data, store it in a data base and the user selects what data that want to see using Grafana. The user can display the data many ways, as a dial, a graph, a bar code graph and many other "visualizations" too numerous to list.
It does not matter where the data is, MQQT Broker (server) somewhere, MODBUS, CANBUS Serial data, I can grab it and format it then write to a "Time Series Database", I use InfluxDB as Grafana interfaces with it well.
Here a screen shot of my dual Rosie Stack testing the new SELL to GRID code. I have colored the WATTS green when ever "selling" and red when "using" from the grid. My idea is have everything user customizable.
Quote from: Barry Fields on May 24, 2024, 12:17:10 AMYour post was really appreciated and kept me out of the bar for a couple of hours.
I am really trying to understand the interconnections. I have attached a crude diagram of what I think I understand.
How does MQTT get to the cloud? Ethernet to the router?
"Basically the Classic had limitation of being able to only have one modbus link at a time." Explain please.
Feel free to edit my diagram iffn ya like.
I can't explain to you exactly why the Classic can only connect to one IP modbus at a time - limitation of the hardware I suspect.
Basically the software Graham wrote sends modbus requests to the Classic, and then takes the data requested and converts it to MQTT which is a data that can be easily sent to what is called a broker . The broker can be living at your house on a raspberry pi ( that is how I do mine) or the mqtt data can be sent to a broker server out on the internet somewhere.
Anything that has the credentials ( password) can subscribe to the broker and request that mqtt data. And as it shows in the original diagram - my raspberry pi program that graphs the data can subscribe, a program running Classic Monitoring app can subscribe, or Home Assistant program could subscribe , etc and they can all subscribe at the same time and gather the data independently to do whatever with it.
Grahams program is requesting the data regularly via modbus so that it is always fresh and timestamped. So that is how it works in a nutshell.
Canbus is different than modbus in that no request for the data has to be made, the canbus is just sending the data all the time .
The difference is that what Jim is making with the combox is that it can send modbus requests to Classic for data, but it also has the canbus hardware to connect to newer Hawkes Bay , Rosie , Barcelona etc and that software will be able to interpret the canbus data stream into something us mere mortals ( or the influx program) can understand as voltage, current, charge state , etc.
Larry
Quote from: ClassicCrazy on May 24, 2024, 09:23:20 AMThe broker can be living at your house on a raspberry pi ( that is how I do mine) or the mqtt data can be sent to a broker server out on the internet somewhere.
Could that broker be on your local PC? What would that connection look like?
Quote from: ClassicCrazy on May 24, 2024, 09:23:20 AMI can't explain to you exactly why the Classic can only connect to one IP modbus at a time - limitation of the hardware I suspect.
Larry
I think I understand. If we had three Classics in follow me and I wanted to tell them all to turn off (example only):
I would have to call the first one with my modbus phone and say"shut off"and hang up.
I would then have to call the second one and hang up.
Ditto for the third.
Is there a way to do a conference call to save on modbus time?
Can a Modbus unit respond to two unique addresses? (for writes only)
IE 1st unit addresses 10 & 11
2nd unit 10 & 12
3rd unit 10 & 13
all would respond to address 10 (conference call)
each would respond to 11 or 12 or 13 (private line)
I again want to thank you all for your patience.
The Classic's MODBUS registers can be accessed two ways, by Serial MODBUS aka MODBUS RTU or by MODBUS TCP/IP. RTU is available from the FOllow-Me jacks which are just serial data jacks. Serial data devices generally are just two devices "talking" to each other.
MODBUS TCP/IP uses the Ethernet jack on each Classic which generally connects to a router with each Classic being assigned an IP address. The limit is only ONE TCP/IP connection at a time to a Classic. If a device is connected then another device will not be allowed to connect, this limitation is unique to our Classic and has to do with resources in the Networking Code. A device, such as the COMBOX connects by opening a TCP/IP channel and grabbing data, then closing the channel, also known as ports. Our LOCAL.APP Dashboard does this but it does not release the port until the software is closed down. SO if the LOCAL.APP is running the COMBOX gets "connection refused" and no data. Since I wrote the code in the COMBOX to open a port, get ONE or TWO registers then close the port, if I open the LOCAL.APP it jumps in between my data requests and LOCKS itself in so the COMBOX again gets refused a connection. It would be nice if the LOCAL.APP would open/close but it's not being updated anymore.
The Classic can actually talk to two things at once on the Ethernet jack.
But that second one is for My Midnite which is not another general purpose modbus over TCP/IP connection. We restricted the network this way to reduce traffic on the Classic processor that has other important things to do like run the MPPT itself. It's all resource restricted so as to not slow down the processor too much.
Also, the newer products with canbus can also be queried, not just sending out a data stream. We don't want to overload the canbus traffic with data that is more rarely accessed.
boB
example; three Classics in "follow me"
Quote from: Barry Fields on May 24, 2024, 11:26:47 AMCan a Modbus unit respond to two unique addresses? (for writes only)
IE 1st unit addresses 10 & 11
2nd unit 10 & 12
3rd unit 10 & 13
all would respond to address 10 (conference call)
each would respond to 11 or 12 or 13 (private line)
Reason I ask
My new charge regime would want to be able to force FLOAT or ABSORB for all three classics.
Quote from: Barry Fields on May 24, 2024, 03:36:03 PMexample; three Classics in "follow me"
Quote from: Barry Fields on May 24, 2024, 11:26:47 AMCan a Modbus unit respond to two unique addresses? (for writes only)
IE 1st unit addresses 10 & 11
2nd unit 10 & 12
3rd unit 10 & 13
all would respond to address 10 (conference call)
each would respond to 11 or 12 or 13 (private line)
Reason I ask
My new charge regime would want to be able to force FLOAT or ABSORB for all three classics.
If you have Follow-Me cables connected and enabled, you just have to tell ONE Classic go to Float or Bulk (Absorb) and the others will follow.
Otherwise, you can access each Classic over TCP/IP at the same time by using the 3 IP addresses. One per Classic. I mean, one computer could have all 3 Classics open on 3 IP connections at the same time. A computer can only do one thing of a time so they would communicate so many milliseconds apart from each other over their connections to your computer or R-Pi or whatever.
Quote from: Barry Fields on May 24, 2024, 11:26:47 AMQuote from: ClassicCrazy on May 24, 2024, 09:23:20 AMThe broker can be living at your house on a raspberry pi ( that is how I do mine) or the mqtt data can be sent to a broker server out on the internet somewhere.
Could that broker be on your local PC? What would that connection look like?
The mqtt broker I use is called Mosquitto and it runs on my raspberry pi , which is also running Telegraf, InfluxDB, and Grafana . The raspberry pi I am using only has a wifi connection to my router , the same router that has cat 5 cables that go to my two midnites . (I actually have three routers all configured as one network so doesn't matter which router the Classics plug in to. )
I should mention that Graham also has a project that an esp32 can make one of the serial ports on Classic into an IP port . I haven't tried that one but others have gotten it working.
These days there doesn't seem to be value running three Classics when you can run one Hawkes Bay instead ( that is if buying new).
Larry
For MQTT, in order to display a time related graph, is is necessary to have some history date stored somewhere.
Is that done in the BROKER? What kinda memory size is required?
Same question for MNGP & MNGP2?
Quote from: Barry Fields on May 25, 2024, 01:44:25 PMFor MQTT, in order to display a time related graph, is is necessary to have some history date stored somewhere.
Is that done in the BROKER? What kinda memory size is required?
Same question for MNGP & MNGP2?
The data is all stored by InfluxDB I believe. Then Grafana uses that to make graphs. You can set things up to purge old data but I haven't done anything other than defaults and it has been running fine on my raspberry pi 3B+ . The only thing I have done is replace the SD card with a newer one that is supposed to be able to do more read writes . I put in the new micro SD as a preventative maintenance. This pi runs the Mosquitto broker, Telegraf, InfluxDB , and Grafana in containers set up via IOTStack . Maybe that doesn't mean much to you, I can just say that the IotStack makes installing and updating anything very easy. Besides getting data from my 3 Classics , it is also gathering the mqtt data from various esp32 boards running Tasmota connected to various energy monitors, temp sensors, and my four batteries bms . The pi just sits on the edge of my desk with only power via micro usb plug. The Tasmota devices have their own web pages , but I made my own graphs in Grafana that display everything that I want to show. I connect to the Pi's IP address for the Grafana or other programs running on it.
So I guess to answer you question it is all stored and running on the Raspberry Pi sd card and I think I have either a 64 or 128 GB sd card in it. Once in awhile I do also shut it down and make backup copy of the SD card. I know there are ways to back it up while running but I only get to a minor level with the linux raspberry pi stuff - if it was easier to do I would do it that way.
There is a newer way to run everything on a new mini pc or used mini pc where you can run Proxmox which will allow you to run multiple operating systems like Linux, Windows, Home Assistant, etc.
I refer you to Andreas Spies videos on the details of how all this works.
https://youtu.be/xVq_5f0aFlw?si=5fBjYTVLSl0GdvmL
Larry
Yes, it's been a while since I posted an update, I work part-time helping out in the tech support department, things are really busy with the new products... and old... and HEATWAVE across the US...
Okay, here is where we are at:
HARDWARE MODIFICATIONS - Adding a 9V battery, charging circuit and detect for power gone for safe shutdown to avoid LINUX file system corruptions. I updated my Rosie's yesterday and forgot it shuts off the power and BAM, crashed the COMBOX LINUX file system. I had to make a new Micro SD card and set it back up. I suspect only a small percent of our COMBOX owners will be able to do this and we would need to mail out a replacement Micro SD card every time. I have a prototype on my bench with a bread board working on it now. The Wal-mart ONN 32GB cards wear out and even PATRIOT brand seem to also, a $25 industrial SD card is needed...
SOFTWARE UPDATES - For the first units this will need to be done by USB thumb drive, copy the update file, plug it into the COMBOX, load the config page and select USB UPDATE. The software code for this still needs to be done. Next step is to add code to update from the Midnite Server and leave the USB option for sites without Internet.
STILL to DO:
1) Add option to set the CLOCK without an active Internet connection
NOW THE BAD NEWS - Seems the little Orange Pi Zero is running hard to keep up with all the tasks, running way too hot for me, I have seen 90C on the CPU temperature data I just started logging to the database. There may be a limit on the number of devices it will comfortably support. I am testing 2 Rosies, 1 Barcelona, 1 Hawkes Bay and that seems to much. 3 Devices and the MNGP2 may be the limit. A CPU heat sink and small FAN is a must now. I have some small 5V 1" sq fans to test with.
NOW THE GOOD NEWS - I have ported most of the code over to run on a Raspberry Pi 3B+ and it seems to handle my devices. No, it will not fit in the MNCOMBOX case so I decided if I have to get a bigger case for mine I'll switch to a 4-Line x 20 chr Blue LCD display. Easier to see than the Tiny OLED display. I may make available the code for those who can setup and run a Raspberry Pi on their own. I don't have all the requirements and setup documented yet so... And, before Midnite can release this product there has to be a good support mechanism in place to provide needed help, which there isn't yet. I can only provide limited email & forum support, no phone support, which will not be acceptable by management I'm sure.
Newark Electronics has the RPi 3B+ in stock for just $35
Amazon has the USB CAN plug for $20
Yes the cheap micro SD cards just don't last too long - I had problems but once I got a decent Samsung card never had a problem again. Sandisk also makes some SD cards that can take the repeated writes.
I would be happy to help with this. But I think I would want to set it up on a pi4 or pi5 and get the extra processing power plus the ability to put it on to an nvme ssd that won't wear out like an sd card.
My main interest is just to get the data to mqtt so I can start monitoring.
My present Pi3B+ h as been running here on my desk for years without a hitch and is gathering data from 3 Classics, 4 48v lithium batteries bms data so that is 128 cells along with the voltage, current, etc from the batteries, and I have other sensors like energy monitors and temp sensors all being gathered by that pi 3B+.
Anyway happy to give it a try whenever - I can get another pi3b+ and that CAN adapter if I can't get the CAN adapter I already have to work.
Larry
Quote from: Wizbandit on June 23, 2024, 11:22:49 AMNOW THE BAD NEWS - Seems the little Orange Pi Zero is running hard to keep up with all the tasks, running way too hot for me, I have seen 90C on the CPU temperature data I just started logging to the database. There may be a limit on the number of devices it will comfortably support. I am testing 2 Rosies, 1 Barcelona, 1 Hawkes Bay and that seems to much. 3 Devices and the MNGP2 may be the limit. A CPU heat sink and small FAN is a must now. I have some small 5V 1" sq fans to test with.
NOW THE GOOD NEWS - I have ported most of the code over to run on a Raspberry Pi 3B+ and it seems to handle my devices. No, it will not fit in the MNCOMBOX case so I decided if I have to get a bigger case for mine I'll switch to a 4-Line x 20 chr Blue LCD display.
Would the commbox also be used for comms with b17s? Just wondering if each of the five modules would be considered a separate component like a Rosie, HB etc, or if it's rolled up in the chassis to present as one enclosure/frame with 5 subcomponents Otherwise may run out of resources on the commbox?
Quote from: Brucey on August 18, 2024, 07:20:13 PMWould the commbox also be used for comms with b17s? Just wondering if each of the five modules would be considered a separate component like a Rosie, HB etc, or if it's rolled up in the chassis to present as one enclosure/frame with 5 subcomponents Otherwise may run out of resources on the commbox?
Yes, probably :)
At this time, it certainly could and is compatible with what we are doing with Canbus.
The commbox has already verified it talks to the B17 and back and forth.
Hi, perhaps your sick of people asking, but is there any approx eta when the Combox might make it to market? I really enjoyed installing my last Rosie, and am looking forward to the next ones, however the lack of integration and especially online monitoring for the devices are a turn-off for remote users these days.
Thanks for your work! Looking forward to it.
Damien
Off Grid Salt Spring
Positive Power Systems
I'm going to say the Midnite COMBOX project is dead. There is no path forward for a sustaining engineer to work the project and deal with the needed hardware changes. There is no support mechanism plan in place, there would be no phone support which Midnite has always required. I worked on all the present Python code for all the Midnite products running on the COMBOX and with some limitations have most of the bugs worked out. I even added some code and built an engine to gather data from the MN-ONE AIO 10K inverter system which is pretty cool to look at. I even made a bridge to get the Classic on the CANBUS and controlled from a MNGP2 which was not easy but the development version works mostly and is pretty cool.
It looks like Management is turning over monitoring to Solar Assistant. They will be handling all the hardware, software and support issues. I'm not in favor of their EULA as it it pretty restrictive as most software developers have become with their specialized software. One thing I didn't like is if you want to change to say a bigger Raspberry Pi, you get to move your paid license ONE TIME, after that you need to buy the license again, pretty hinky. You need to ask them when they will be adding MN products to their software.
Here is the web site: https://solar-assistant.io/
As you will see they have found you need minimum requirements from a Raspberry Pi to work dependably. The little Orange Pi ZERO used in the MNCOMBOX was under-powered. The case was sealed and it ran hot without ventilation and a small 5V fan.
I will at some point finish porting all my code over to run on a $35 Raspberry Pi 3B+ and include instructions on how to setup and run your own if there is interest.
Quote from: Wizbandit on September 04, 2024, 03:44:11 PMI'm going to say the Midnite COMBOX project is dead. There is no path forward for a sustaining engineer to work the project and deal with the needed hardware changes. There is no support mechanism plan in place, there would be no phone support which Midnite has always required. I worked on all the present Python code for all the Midnite products running on the COMBOX and with some limitations have most of the bugs worked out. I even added some code and built an engine to gather data from the MN-ONE AIO 10K inverter system which is pretty cool to look at. I even made a bridge to get the Classic on the CANBUS and controlled from a MNGP2 which was not easy but the development version works mostly and is pretty cool.
It looks like Management is turning over monitoring to Solar Assistant. They will be handling all the hardware, software and support issues. I'm not in favor of their EULA as it it pretty restrictive as most software developers have become with their specialized software. One thing I didn't like is if you want to change to say a bigger Raspberry Pi, you get to move your paid license ONE TIME, after that you need to buy the license again, pretty hinky. You need to ask them when they will be adding MN products to their software.
Here is the web site: https://solar-assistant.io/
As you will see they have found you need minimum requirements from a Raspberry Pi to work dependably. The little Orange Pi ZERO used in the MNCOMBOX was under-powered. The case was sealed and it ran hot without ventilation and a small 5V fan.
I will at some point finish porting all my code over to run on a $35 Raspberry Pi 3B+ and include instructions on how to setup and run your own if there is interest.
Thanks for your efforts on this despite the ultimate ending. So looks like solar assistant would be around $56 for the license, provide own pi of appropriate type, and then a USB cable to connect to Rosie canbus?
Can you help on which one of these would work?
https://solar-assistant.io/shop
Or is Rosie support for Solar Assistant still a work in progress on their end?
Oops nevermind should have read better.
"You need to ask them when they will be adding MN products to their software."
Quote from: Wizbandit on September 04, 2024, 03:44:11 PMI will at some point finish porting all my code over to run on a $35 Raspberry Pi 3B+ and include instructions on how to setup and run your own if there is interest.
Hey James, I would be super interested in trying your code when you have time! (I would bet there are quit a few of us, running both Classic & HB/Barc/Rosie in the same system.). Can't thank you enough for your efforts and hard work on the COMBOX. It was once resurrected from the fire .... could happen again some day? :) Maybe its new name then will be the Phoenix ;)
Just downloaded and flashed a card w/solar-assistant to use w/my existing Pi4. Might as well get it connected to my Pytes batteries and have it ready when the Midnite Canbus libraries are uploaded.
Dave
Quote from: Wizbandit on September 04, 2024, 03:44:11 PMI'm going to say the Midnite COMBOX project is dead.
Saddens me to see efforts like yours come to an end.
Try to look forward to other opportunities.
Barry
Quote from: Wizbandit on September 04, 2024, 03:44:11 PMI will at some point finish porting all my code over to run on a $35 Raspberry Pi 3B+ and include instructions on how to setup and run your own if there is interest.
Yes I am also interested in anything that you release. The main thing I want is to just monitor my Hawkes Bay. Some of us can probably make something work from your efforts.
Thanks,
Larry
Quote from: Wizbandit on September 04, 2024, 03:44:11 PMI'm going to say the Midnite COMBOX project is dead. There is no path forward for a sustaining engineer to work the project and deal with the needed hardware changes. There is no support mechanism plan in place, there would be no phone support which Midnite has always required. I worked on all the present Python code for all the Midnite products running on the COMBOX and with some limitations have most of the bugs worked out. I even added some code and built an engine to gather data from the MN-ONE AIO 10K inverter system which is pretty cool to look at. I even made a bridge to get the Classic on the CANBUS and controlled from a MNGP2 which was not easy but the development version works mostly and is pretty cool.
It looks like Management is turning over monitoring to Solar Assistant. They will be handling all the hardware, software and support issues. I'm not in favor of their EULA as it it pretty restrictive as most software developers have become with their specialized software. One thing I didn't like is if you want to change to say a bigger Raspberry Pi, you get to move your paid license ONE TIME, after that you need to buy the license again, pretty hinky. You need to ask them when they will be adding MN products to their software.
Here is the web site: https://solar-assistant.io/
As you will see they have found you need minimum requirements from a Raspberry Pi to work dependably. The little Orange Pi ZERO used in the MNCOMBOX was under-powered. The case was sealed and it ran hot without ventilation and a small 5V fan.
I will at some point finish porting all my code over to run on a $35 Raspberry Pi 3B+ and include instructions on how to setup and run your own if there is interest.
Sure to hear of this. Your graphics from the MN Combox, have been quite stunning!
Thank you very much for all of your hard work on all of this.
Take care, Vic
Quote from: Vic on September 05, 2024, 10:29:29 PMSure to hear of this. Your graphics from the MN Combox, have been quite stunning!
Thank you very much for all of your hard work on all of this.
Take care, Vic
Right on ! He has done a GREAT job !
Wizbandit:
I am also very interested in anything you would publish about live monitoring. A Rpi with a Canbus usb dongle (I have a Jhoinrch with the lights, works with Savvycan, Cangaroo) can share the Canbus on the network with usbip. Just need the appropriate message info for MN products. Here's hoping. Will be using the same tools: Node-red, Grafana, and Influxdb.
R.
Well that sucks!
mike
Well, if someone can convince Midnite to build a batch of COMBOXes and sell them to FORUM users as bare hardware with no support I will provide the software for no charge. They do work but not the way Midnite wants. The idea was to have an account on MyMidite so you could get a way to connect without port forwarding like
MYSOLARSYSTEM.MYMIDNITE.COM and have your COMBOX reporting it's local IP so you could access it. This was never going to happen, the programmer for MyMidnite site is gone, the Local App programmer is gone, the hardware engineer that designed the Combox is gone, the software developer they hired to try and get it working is gone.
Solar Assistant will be okay, nothing great IMHO. I like my idea of user customization of graphs, gauges and dials. I'm not sure SA has that, I have not had time to play with it. I looks like they are using the paid version of Grafana so they have much more custom graphics on their dashboards.
Quote from: Wizbandit on September 06, 2024, 03:39:02 PMWell, if someone can convince Midnite to build a batch of COMBOXes and sell them to FORUM users as bare hardware with no support I will provide the software for no charge. They do work but not the way Midnite wants. The idea was to have an account on MyMidite so you could get a way to connect without port forwarding like
MYSOLARSYSTEM.MYMIDNITE.COM and have your COMBOX reporting it's local IP so you could access it. This was never going to happen, the programmer for MyMidnite site is gone, the Local App programmer is gone, the hardware engineer that designed the Combox is gone, the software developer they hired to try and get it working is gone.
Solar Assistant will be okay, nothing great IMHO. I like my idea of user customization of graphs, gauges and dials. I'm not sure SA has that, I have not had time to play with it. I looks like they are using the paid version of Grafana so they have much more custom graphics on their dashboards.
I think all that some of us want is just the Canbus code to get the basic stuff like we could get with the Classic. Like volts, amps, state of charge, soc , etc. For me , I can make and share with others the graphs to display all that in Grafana , others have the skills to get that ported over to do the same in Home Assistant .
I have never been able to fully evaluate what my Hawkes Bay is doing since I would have to watch it real time.
And I don't need to send the data or monitor it through a remote server somewhere. Just need it on my home network. Remote access to data can be accomplished if someone wants to do it with mqtt or using free Tailscale vpn which works on all platforms and is easily set up. I recently learned about Tailscale and am setting it up on my home computer and a raspberry pi 3 to go in out hamshack where there is only a limited public sort of internet . Tailscale creates a secure tunnel that works without doing anything like port forwarding , etc.
Raspberry Pi also has an official secure remote system now, though I haven't tried that yet since it needs 64bit pi which means I need to get a newer Raspberry Pi 4 or Pi 5 model which I may soon get.
I think the talents of those who own the newest Midnite products will develop what we need and be shared for free, much like what was done with other apps that users made for the Classic.
Monitoring is what is really needed right now.
Larry
ClassicCrazy:
Excellent summary. I would like the same. I don't know if I can figure all the connections out, but will try if the Can data is available. For example, with Node-Red on a RPI4, I have a GPS dongle with FTDI to USB dongle, and also BLE to gather temp data from RuuviTag sensors, and an SDR interface to get temp data from longer range AmbientWeather temp sensors. The GPS puts out a lot of stuff that can be pre-processed in Node-Red. NR doesn't have a great dashboard, but will do initially for the most important live data.
What are the pinouts for the Canbus on the MNGP2?
R.
Quote from: Raster on September 07, 2024, 12:27:32 AMClassicCrazy:
Excellent summary. I would like the same. I don't know if I can figure all the connections out, but will try if the Can data is available. For example, with Node-Red on a RPI4, I have a GPS dongle with FTDI to USB dongle, and also BLE to gather temp data from RuuviTag sensors, and an SDR interface to get temp data from longer range AmbientWeather temp sensors. The GPS puts out a lot of stuff that can be pre-processed in Node-Red. NR doesn't have a great dashboard, but will do initially for the most important live data.
What are the pinouts for the Canbus on the MNGP2?
R.
I was able to get the canbus data last winter - but don't remember the pinouts right now . Maybe I see if I can find it later. I sent you a personal message on forum here - look for it if you haven't seen it yet.
Larry
ClassicCrazy:
Received. Thanks much.
R.
I received this message from solar assistant.
Hi Mike,
Thanks for reaching out. We do not have any immediate plans to support Midnite solar products. If we do, we will show it here:https://solar-assistant.io/help/updates/changelog
Kind Regards,
Apparently, midnite products are even on their radar.
Too bad.
Mike
ClassicCrazy:
Still would like the pinouts for MN Can bus.
Also if anyone is interested (in trying to get all data live on the local net):
Had some success talking to the 6 EG4-LL batteries. There is a setting on the panel for Can bus support for Victron. It says to set the ID of the top battery to 64 which can't be done, so it is really 0. The panel key it says to press in the manual is wrong, it should be the Return key, not the Enter key. Set to Victron. I downloaded their Venus OS for a RPi4. The imager software is balenaEtcher.
For the Can dongle: pin 4 on the battery is CanHi, and pin 5 is CANLo. Gnd doesn't seem to be needed. The RS485 cable that is supplied with the batteries is using two wires also, pin 7 and pin 8. That works for the Windows app to look at all the batteries.
Venus OS supports the Can dongle I have. It has Node-Red installed already. It sees all 6 batteries and reports information. Not sure which battery it is using for info. It seems to stroke the bus every second. What is good is the console is available on the LAN. At least I can look at the batteries now, half of the battle.
R.
Quote from: qrper on September 08, 2024, 11:10:37 AMI received this message from solar assistant.
Hi Mike,
Thanks for reaching out. We do not have any immediate plans to support Midnite solar products. If we do, we will show it here:https://solar-assistant.io/help/updates/changelog
Kind Regards,
Apparently, midnite products are even on their radar.
Too bad.
Mike
I got a similar response, I'm guessing customer service guys aren't aware/privvy of what's going on in development, or they don't mention until it's officially released to avoid support headaches. I think it was mentioned it may be three weeks or so before we see anything.
Raster
Here is what I have for canbus connection using Inno-Maker usb2 can board
RJ45 on the Midnite canbus to an Inno-Maker usb-can-hat-rpi board that has a DB9 connector on it
RJ45 pin 5 solid blue to db9 pin 2 Can L
RJ45 pin 4 blue white to db9 pin 7 Can H
RJ45 pin 6 green white to db9 pin 3 ground
Plugged in to the MNGP2 canbus jack seems to get data using Busmaster program.
I don't understand canbus stuff
Larry
QuoteI got a similar response, I'm guessing customer service guys aren't aware/privy of what's going on in development, or they don't mention until it's officially released to avoid support headaches. I think it was mentioned it may be three weeks or so before we see anything.
I chatted with Ryan on the COMBOX and he is going to ask management if they will be willing to use up existing parts to build up and sell some bare COMBOX's to users as un-supported hardware. Then all you would need is to ask me for the code to play with. I have it talking to the new MNAIO-10K All-in-One inverter as well as the MNPowerFlo5 battery now. The MNCOMBOX has a working builtin power supply that takes 9-12VDC via 2.1mm coaxal power jack. I just received some 36-60V to 12V power supplies to test to see if I can avoid Linux file system damage by powering the COMBOX off the 48VDC battery. I would probably have all the raw parts shipped here, assemble and commission them before shipping. Not sure, still thinking about this. I have also hooked a 9V battery to a 2.1mm power plug and used it to keep the COMBOX running during a power-cycle of Rosies.
Quote from: Wizbandit on September 09, 2024, 03:59:38 PMQuoteI got a similar response, I'm guessing customer service guys aren't aware/privy of what's going on in development, or they don't mention until it's officially released to avoid support headaches. I think it was mentioned it may be three weeks or so before we see anything.
I chatted with Ryan on the COMBOX and he is going to ask management if they will be willing to use up existing parts to build up and sell some bare COMBOX's to users as un-supported hardware. Then all you would need is to ask me for the code to play with. I have it talking to the new MNAIO-10K All-in-One inverter as well as the MNPowerFlo5 battery now. The MNCOMBOX has a working builtin power supply that takes 9-12VDC via 2.1mm coaxal power jack. I just received some 36-60V to 12V power supplies to test to see if I can avoid Linux file system damage by powering the COMBOX off the 48VDC battery. I would probably have all the raw parts shipped here, assemble and commission them before shipping. Not sure, still thinking about this. I have also hooked a 9V battery to a 2.1mm power plug and used it to keep the COMBOX running during a power-cycle of Rosies.
Thanks, would definitely be interested in this officially unsupported option for my Rosie and hopefully soon a Hawkes bay 90A. I think it was mentioned these are a little underpowered for large/complex systems but I can't see myself going beyond the one Rosie and maybe three Hawkes bays so shouldn't be an issue there.
Larry:
Great info. I will look at the Inno site.
The pinouts for Can lines are the same as for the EG4-LL. That is good news. I got some ethernet breakout connectors, male and female, to help determining the correct pins. Can pins should have 2.5v to ground. I will try to use Savvycan or Cangaroo to look at the MNGP2. Your image and maybe some accomplice attacks will get results.
Forgot to add this on the EG4-LLs post:
Bit rate for the Can is 500k.
An ethernet cable, raspberry pi 4, power supply, Can dongle, custom Can cable, SD card, and Venus OS, gets you the EG4-LL battery data. Browser gets the display/modification, and SSH gets other control. Lots of documentation on Venus. No tech support, but it works, and is maintained. Also supports GPS and Ruuvitags out of the box.
R.
Quote from: Raster on September 10, 2024, 12:23:11 AMQuote from: Raster on September 10, 2024, 12:23:11 AMLarry:
Great info. I will look at the Inno site.
The pinouts for Can lines are the same as for the EG4-LL. That is good news. I got some ethernet breakout connectors, male and female, to help determining the correct pins. Can pins should have 2.5v to ground. I will try to use Savvycan or Cangaroo to look at the MNGP2. Your image and maybe some accomplice attacks will get results.
Forgot to add this on the EG4-LLs post:
Bit rate for the Can is 500k.
An ethernet cable, raspberry pi 4, power supply, Can dongle, custom Can cable, SD card, and Venus OS, gets you the EG4-LL battery data. Browser gets the display/modification, and SSH gets other control. Lots of documentation on Venus. No tech support, but it works, and is maintained. Also supports GPS and Ruuvitags out of the box.
R.
I used Savvycan last winter but I just can't get my brain to understand all the CAN data. My usual tactic of staying up very late to figure it out didn't work either !
Larry
Larry:
Node-red has Can nodes, even just read-only which I like. Packets come in as JSON, with all the fields. I am hoping that MN will publish a limited DBC for the Rosie, Barcelona, and MNGP2 with all the important fields that give status, and the scheme for ARB-IDs and Busids. Then the live project can produce a critical info dashboard, all done in NR. I would be very willing to work on that since I have no other options. One Rpi for the EG4 batteries, and one Rpi for MN. There would be a limited amount of programming, just data manipulation, and just live data for the initial foray.
R.
Quote from: Raster on September 10, 2024, 10:36:57 PMLarry:
Node-red has Can nodes, even just read-only which I like. Packets come in as JSON, with all the fields. I am hoping that MN will publish a limited DBC for the Rosie, Barcelona, and MNGP2 with all the important fields that give status, and the scheme for ARB-IDs and Busids. Then the live project can produce a critical info dashboard, all done in NR. I would be very willing to work on that since I have no other options. One Rpi for the EG4 batteries, and one Rpi for MN. There would be a limited amount of programming, just data manipulation, and just live data for the initial foray.
R.
I sent you a message with question on node red.
Larry
Larry:
Got the first message, but nothing more so far.
R.
ClassicCrazy:
Some progress. Took the Rpi4 with the Can dongle, plugged it into the MNGP2, and it lit up like a Christmas tree. Plenty of pretty packets.
I used the socketcan-out node and a debug node for Node-Red. The Can dongle has to be configured on the command line with sudo ip link commands before starting NR.
R.
Raster
take another look in your messages or send me one so i can send you my email
Larry
Quote from: Wizbandit on September 09, 2024, 03:59:38 PMQuoteI got a similar response, I'm guessing customer service guys aren't aware/privy of what's going on in development, or they don't mention until it's officially released to avoid support headaches. I think it was mentioned it may be three weeks or so before we see anything.
I chatted with Ryan on the COMBOX and he is going to ask management if they will be willing to use up existing parts to build up and sell some bare COMBOX's to users as un-supported hardware. Then all you would need is to ask me for the code to play with. I have it talking to the new MNAIO-10K All-in-One inverter as well as the MNPowerFlo5 battery now. The MNCOMBOX has a working builtin power supply that takes 9-12VDC via 2.1mm coaxal power jack. I just received some 36-60V to 12V power supplies to test to see if I can avoid Linux file system damage by powering the COMBOX off the 48VDC battery. I would probably have all the raw parts shipped here, assemble and commission them before shipping. Not sure, still thinking about this. I have also hooked a 9V battery to a 2.1mm power plug and used it to keep the COMBOX running during a power-cycle of Rosies.
Is there any progress on getting monitoring established for Rosie/HB/Barc??? I just checked Solar Assistant website and the Rosie/HB/Barc are not listed as compatible. Or ... yay/nay about building some unsupported ComBoxes? It's been over a month since the ComBox was killed and the subject has gone silent. Appreciate any updates :)
Dave
Quote from: aaapilot on October 07, 2024, 02:57:38 PMQuote from: Wizbandit on September 09, 2024, 03:59:38 PMQuoteI got a similar response, I'm guessing customer service guys aren't aware/privy of what's going on in development, or they don't mention until it's officially released to avoid support headaches. I think it was mentioned it may be three weeks or so before we see anything.
I chatted with Ryan on the COMBOX and he is going to ask management if they will be willing to use up existing parts to build up and sell some bare COMBOX's to users as un-supported hardware. Then all you would need is to ask me for the code to play with. I have it talking to the new MNAIO-10K All-in-One inverter as well as the MNPowerFlo5 battery now. The MNCOMBOX has a working builtin power supply that takes 9-12VDC via 2.1mm coaxal power jack. I just received some 36-60V to 12V power supplies to test to see if I can avoid Linux file system damage by powering the COMBOX off the 48VDC battery. I would probably have all the raw parts shipped here, assemble and commission them before shipping. Not sure, still thinking about this. I have also hooked a 9V battery to a 2.1mm power plug and used it to keep the COMBOX running during a power-cycle of Rosies.
Is there any progress on getting monitoring established for Rosie/HB/Barc??? I just checked Solar Assistant website and the Rosie/HB/Barc are not listed as compatible. Or ... yay/nay about building some unsupported ComBoxes? It's been over a month since the ComBox was killed and the subject has gone silent. Appreciate any updates :)
Dave
I'll bump my post to the top. FNG or Whizbandit, can you update the forum for monitoring Rosie/HB/Barc please. Thanks.
Dave
Dave,
Do you know how to run Node Red ?
There is some work being done to have that do some monitoring.
I haven't had time to play with it yet though because I am busy putting up some more PV before winter .
Larry
Hi Larry, sadly, no .... at least not yet. As the winter sets in and I have time, I may have to pick your brain to figure out something. I'm pretty disappointed that MN did not provide a way to remotely monitor their new Flagship equipment, now selling retail for well over a year, after promising early adopters that it was practically complete. Then it's completely abandoned. In this day and age, I can't conceive a reason monitoring wasn't built into the system from day one.
Dave
While waiting for solar assistant integration, I've just been using a Cerbo and VRM to monitor my Rosie load as "DC power". Got a second smartshunt to connect to my hawkes bay 90A to track production that way as well.
Quote from: aaapilot on October 22, 2024, 07:58:44 PMHi Larry, sadly, no .... at least not yet. As the winter sets in and I have time, I may have to pick your brain to figure out something. I'm pretty disappointed that MN did not provide a way to remotely monitor their new Flagship equipment, now selling retail for well over a year, after promising early adopters that it was practically complete. Then it's completely abandoned. In this day and age, I can't conceive a reason monitoring wasn't built into the system from day one.
Dave
I hear you and wonder about that also.
Larry
Quote from: ClassicCrazy on October 22, 2024, 07:01:03 PMDave,
Do you know how to run Node Red ?
There is some work being done to have that do some monitoring.
I haven't had time to play with it yet though because I am busy putting up some more PV before winter .
Larry
Hi Larry,
I know how to use Node Red. Would you be able to send me what you have? I just got my Midnite "The One" Inverter and I'm really interested in pairing it with Home Assistant.
Thanks,
Nathan
Quote from: Crisply8719 on December 12, 2024, 10:19:54 AMQuote from: ClassicCrazy on October 22, 2024, 07:01:03 PMDave,
Do you know how to run Node Red ?
There is some work being done to have that do some monitoring.
I haven't had time to play with it yet though because I am busy putting up some more PV before winter .
Larry
Hi Larry,
I know how to use Node Red. Would you be able to send me what you have? I just got my Midnite "The One" Inverter and I'm really interested in pairing it with Home Assistant.
Thanks,
Nathan
I suspect that The One inverter is going to be totally different comms than the Hawkes Bay , Barcelona, Rosie types. Maybe Ryan will weigh in on if it has the same comm specs. The other question is if Solar Assistant software which was just announced will support above mentioned, will also be supporting The One ?
I will see what I have for node red , though I haven't tried it yet with my Hawkes Bay.
Larry
Quote from: ClassicCrazy on October 22, 2024, 07:01:03 PMI suspect that The One inverter is going to be totally different comms than the Hawkes Bay , Barcelona, Rosie types. Maybe Ryan will weigh in on if it has the same comm specs. The other question is if Solar Assistant software which was just announced will support above mentioned, will also be supporting The One ?
I will see what I have for node red , though I haven't tried it yet with my Hawkes Bay.
Larry
MODBUS RS485
Quote from: Wizbandit on December 12, 2024, 12:38:03 PMQuote from: ClassicCrazy on October 22, 2024, 07:01:03 PMI suspect that The One inverter is going to be totally different comms than the Hawkes Bay , Barcelona, Rosie types. Maybe Ryan will weigh in on if it has the same comm specs. The other question is if Solar Assistant software which was just announced will support above mentioned, will also be supporting The One ?
I will see what I have for node red , though I haven't tried it yet with my Hawkes Bay.
Larry
MODBUS RS485
Wow, that looks like exactly what I'm wanting. Can I ask how you are getting the modbus data?
Quote from: Crisply8719 on December 14, 2024, 03:34:22 PMWow, that looks like exactly what I'm wanting. Can I ask how you are getting the modbus data?
The MNCOMBOX that uses an Orange Pi ZERO but that project has been shelved. I have ported most of the code to run on a Raspberry Pi 3B+. The little OrgPi struggles to run 2 Rosies, 2 Hbays, a Barcelona, BMS code and 4 MNGP2's. The Raspberry Pi has enough power but it won't fit in the COMBOX case.
I have 2 COMBOXS running, one in the Garage for the MNAIO10K, 1 Hbay90 and 4 Classics, one in the WOODSHOP for the others. The Classics use MODBUS over TCP, the AIO uses MODBUS over RS485. Since I had the code done for Classics it was easy to just change registers to get data from the MNAIO10K, took me 20 minutes of code work. My code allows you to get data from all COMBOXS on the network and display on a single GRAFANA dashboard. Really cool.
Quote from: Wizbandit on December 17, 2024, 06:21:01 AMQuote from: Crisply8719 on December 14, 2024, 03:34:22 PMWow, that looks like exactly what I'm wanting. Can I ask how you are getting the modbus data?
The MNCOMBOX that uses an Orange Pi ZERO but that project has been shelved. I have ported most of the code to run on a Raspberry Pi 3B+. The little OrgPi struggles to run 2 Rosies, 2 Hbays, a Barcelona, BMS code and 4 MNGP2's. The Raspberry Pi has enough power but it won't fit in the COMBOX case.
I have 2 COMBOXS running, one in the Garage for the MNAIO10K, 1 Hbay90 and 4 Classics, one in the WOODSHOP for the others. The Classics use MODBUS over TCP, the AIO uses MODBUS over RS485. Since I had the code done for Classics it was easy to just change registers to get data from the MNAIO10K, took me 20 minutes of code work. My code allows you to get data from all COMBOXS on the network and display on a single GRAFANA dashboard. Really cool.
Will your raspberry pi code ever be released ?
Larry