mb-software/esphome-huawei-r4850

EspHome Component to control and read values from a huawei r4850huawei r4850 power supply via CAN bus.

Requirements

This component is currently tested and verified to work on a ESP32 using the Esphome esp32_can platform. So in addition to any ESP32 board of your choice you need a CAN tranceiver like the sn65hvd230. These are cheap and available from many sources and can be wired directly to the 3.3v GPIO and supply pins of the ESP32 board. In theory it should work also with the mcp2515 platform, but this is currently not tested and verified.

How to use

Please check the provided example esphome configuration: huawei_r4850.yaml

Post by Manu Abraham
From your post, it was difficult to understand your english, I am by
no means a german speaker, sorry about that.
From what you wrote: "prepared 48V output", I was under the belief you
were able to get a 48V output. With your latest post, I understood
incorrectly, what you tried to imply there.
If you want to talk to the vendor, the best that you could ask them to
provide the software to configure the power supply. Couldn't be any
simpler.
I doubt, even if anyone from the vendor were to be on the list,
providing a closed protocol of a product, would be the last thing
anyone would remotely try to do.
Why don't you get the actual necessary software from the vendor and
use it directly ? That would be the simplest to do. If really
necessary, you can snoop on the communication to get the basic command
infrastructure to work on some bare metal platform.
There is talk about secure CAN in the industry, so that vendors can
lock people out, or IOW keep their automobiles safer, another way you
look at it. A coin has two sides to it; not one.
That said, a PSU controller is unlikely to be a device with large
amounts of memory, given the cost of the PSU, it is unlikely that way
either. The lesser memory implies that the amount of parsing /
tokenizing would be just minimal. More tokens imply more storage of
words. Most likely, you could open the power supply, have a look at
what controller it uses and so on. If you are lucky, you could even
find that controller datasheet and get a fair understanding of what
happens under the hood inside that PSU. The next good thing would be
to know, what the PSU was really intended for. Then you could try to
gain info, how it is run in that context. Please note, that all this
takes time and and times, could be frustrating. I don't think, there's
an easy way out.
If I were you, I would've got the actual software/platform, snooped on
the bus, logged each command, to be later utilized into a dictionary
for RE. the comms. syntax. I think it would be a very interesting
project. If you've used Linux and Digital Video hardware, probably you
would've known. Most of the Linux DVB drivers were written that way.
The rev. engg'd stuff would be then compared with actual datasheets
(if available) and the quality of the driver improved eventually. ;-)
It's painful, but if you enjoy doing such things, very much an
enjoyable project. It will take you a long way. In the process, you
will be giving away knowledge to other people in the same way too.
Let us people on this list know, how you get along. Not that anyone
could help, due to lack of time, hardware and the list could go on ..
But you could be of help to someone who comes along later on another
day like this.
Cheers,
Manu

From your post, it was difficult to understand your english, I am byno means a german speaker, sorry about that.From what you wrote: "prepared 48V output", I was under the belief youwere able to get a 48V output. With your latest post, I understoodincorrectly, what you tried to imply there.If you want to talk to the vendor, the best that you could ask them toprovide the software to configure the power supply. Couldn't be anysimpler.I doubt, even if anyone from the vendor were to be on the list,providing a closed protocol of a product, would be the last thinganyone would remotely try to do.Why don't you get the actual necessary software from the vendor anduse it directly ? That would be the simplest to do. If reallynecessary, you can snoop on the communication to get the basic commandinfrastructure to work on some bare metal platform.There is talk about secure CAN in the industry, so that vendors canlock people out, or IOW keep their automobiles safer, another way youlook at it. A coin has two sides to it; not one.That said, a PSU controller is unlikely to be a device with largeamounts of memory, given the cost of the PSU, it is unlikely that wayeither. The lesser memory implies that the amount of parsing /tokenizing would be just minimal. More tokens imply more storage ofwords. Most likely, you could open the power supply, have a look atwhat controller it uses and so on. If you are lucky, you could evenfind that controller datasheet and get a fair understanding of whathappens under the hood inside that PSU. The next good thing would beto know, what the PSU was really intended for. Then you could try togain info, how it is run in that context. Please note, that all thistakes time and and times, could be frustrating. I don't think, there'san easy way out.If I were you, I would've got the actual software/platform, snooped onthe bus, logged each command, to be later utilized into a dictionaryfor RE. the comms. syntax. I think it would be a very interestingproject. If you've used Linux and Digital Video hardware, probably youwould've known. Most of the Linux DVB drivers were written that way.The rev. engg'd stuff would be then compared with actual datasheets(if available) and the quality of the driver improved eventually. ;-)It's painful, but if you enjoy doing such things, very much anenjoyable project. It will take you a long way. In the process, youwill be giving away knowledge to other people in the same way too.Let us people on this list know, how you get along. Not that anyonecould help, due to lack of time, hardware and the list could go on ..But you could be of help to someone who comes along later on anotherday like this.Cheers,Manu

EspHome Component to control and read values from a huawei r4850 power supply via CAN bus.

Requirements

This component is currently tested and verified to work on a ESP32 using the Esphome esp32_can platform. So in addition to any ESP32 board of your choice you need a CAN tranceiver like the sn65hvd230. These are cheap and available from many sources and can be wired directly to the 3.3v GPIO and supply pins of the ESP32 board. In theory it should work also with the mcp2515 platform, but this is currently not tested and verified.

If you are looking for more details, kindly visit vertiv telecom.

How to use

Please check the provided example esphome configuration: huawei_r4850.yaml

Post by Manu Abraham
From your post, it was difficult to understand your english, I am by
no means a german speaker, sorry about that.
From what you wrote: "prepared 48V output", I was under the belief you
were able to get a 48V output. With your latest post, I understood
incorrectly, what you tried to imply there.
If you want to talk to the vendor, the best that you could ask them to
provide the software to configure the power supply. Couldn't be any
simpler.
I doubt, even if anyone from the vendor were to be on the list,
providing a closed protocol of a product, would be the last thing
anyone would remotely try to do.
Why don't you get the actual necessary software from the vendor and
use it directly ? That would be the simplest to do. If really
necessary, you can snoop on the communication to get the basic command
infrastructure to work on some bare metal platform.
There is talk about secure CAN in the industry, so that vendors can
lock people out, or IOW keep their automobiles safer, another way you
look at it. A coin has two sides to it; not one.
That said, a PSU controller is unlikely to be a device with large
amounts of memory, given the cost of the PSU, it is unlikely that way
either. The lesser memory implies that the amount of parsing /
tokenizing would be just minimal. More tokens imply more storage of
words. Most likely, you could open the power supply, have a look at
what controller it uses and so on. If you are lucky, you could even
find that controller datasheet and get a fair understanding of what
happens under the hood inside that PSU. The next good thing would be
to know, what the PSU was really intended for. Then you could try to
gain info, how it is run in that context. Please note, that all this
takes time and and times, could be frustrating. I don't think, there's
an easy way out.
If I were you, I would've got the actual software/platform, snooped on
the bus, logged each command, to be later utilized into a dictionary
for RE. the comms. syntax. I think it would be a very interesting
project. If you've used Linux and Digital Video hardware, probably you
would've known. Most of the Linux DVB drivers were written that way.
The rev. engg'd stuff would be then compared with actual datasheets
(if available) and the quality of the driver improved eventually. ;-)
It's painful, but if you enjoy doing such things, very much an
enjoyable project. It will take you a long way. In the process, you
will be giving away knowledge to other people in the same way too.
Let us people on this list know, how you get along. Not that anyone
could help, due to lack of time, hardware and the list could go on ..
But you could be of help to someone who comes along later on another
day like this.
Cheers,
Manu

From your post, it was difficult to understand your english, I am byno means a german speaker, sorry about that.From what you wrote: "prepared 48V output", I was under the belief youwere able to get a 48V output. With your latest post, I understoodincorrectly, what you tried to imply there.If you want to talk to the vendor, the best that you could ask them toprovide the software to configure the power supply. Couldn't be anysimpler.I doubt, even if anyone from the vendor were to be on the list,providing a closed protocol of a product, would be the last thinganyone would remotely try to do.Why don't you get the actual necessary software from the vendor anduse it directly ? That would be the simplest to do. If reallynecessary, you can snoop on the communication to get the basic commandinfrastructure to work on some bare metal platform.There is talk about secure CAN in the industry, so that vendors canlock people out, or IOW keep their automobiles safer, another way youlook at it. A coin has two sides to it; not one.That said, a PSU controller is unlikely to be a device with largeamounts of memory, given the cost of the PSU, it is unlikely that wayeither. The lesser memory implies that the amount of parsing /tokenizing would be just minimal. More tokens imply more storage ofwords. Most likely, you could open the power supply, have a look atwhat controller it uses and so on. If you are lucky, you could evenfind that controller datasheet and get a fair understanding of whathappens under the hood inside that PSU. The next good thing would beto know, what the PSU was really intended for. Then you could try togain info, how it is run in that context. Please note, that all thistakes time and and times, could be frustrating. I don't think, there'san easy way out.If I were you, I would've got the actual software/platform, snooped onthe bus, logged each command, to be later utilized into a dictionaryfor RE. the comms. syntax. I think it would be a very interestingproject. If you've used Linux and Digital Video hardware, probably youwould've known. Most of the Linux DVB drivers were written that way.The rev. engg'd stuff would be then compared with actual datasheets(if available) and the quality of the driver improved eventually. ;-)It's painful, but if you enjoy doing such things, very much anenjoyable project. It will take you a long way. In the process, youwill be giving away knowledge to other people in the same way too.Let us people on this list know, how you get along. Not that anyonecould help, due to lack of time, hardware and the list could go on ..But you could be of help to someone who comes along later on anotherday like this.Cheers,Manu

Want more information on outdoor delta rectifier cabinet? Feel free to contact us.