Following Bob's post, noticed that I had forgotten to trim my previous post= s .. Got a bit more interested to dig deeper into it. The PSU is additionally used here as well: goo.gl/hGL4Nc goo.gl/RP8HRT Scrolling down, It states the following additionally: 2. Technology support For all the EPON and terminal units, Ethernet switch, and other products, HUANET promises: Technology support for life: Free call and E-mail technology supports for each sold network products for life. Software upgrade for life: Provide upgrade software in the form of E-mail or CD for clients and clients can download it in customer service web The CAN bus is connected to a interface module which interfaces between Ethernet ports and the CAN bus. The Ethernet port seems to be accessed a web UI to control/monitor the PSU https://support.huawei.com/enterprise/en/doc/EDOC1100003664 You need to register with their support site. If nothing works, you can buy that and ask them to support it with their Web UI. ;-) Hopefully, if everything goes well. Just the cost of 2 PSU's. After that, you can fiddle around to your heart's content. Hope that helps. Cheers, Manu On Thu, Nov 15, 2018 at 11:24 PM Manu Abraham wrot= e: > > Actually, a quick search yielded me the following, which is where that > PSU is used: > https://fccid.io/ANATEL/03368-13-03257/Manual/E55D6368-99CD-4125-9693-256= F6FCC50A1/PDF > > Which states: > > Networked monitoring TP482000B-L20B1 > supports remote operations and software upgrades over a Web UI > > Searching again, led me to the vendor support web site. So, they have > some sort of support for it. > Only thing is, you need to ask them the Right Thing, the Right Way, at > the Right Time. > > e.huawei.com/ae/account/login > or > goo.gl/utqHnq > > So, definitely, you need to create an account with them and eventually > talk to them. > Let us know of your success on the topic. > > Hope it helps. > > Cheers, > Manu > > On Thu, Nov 15, 2018 at 10:23 PM Manu Abraham wr= ote: > > > > 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 --=20 http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist .