Re: meta-everest
Anton Wöllert
Hi Alberto, the problem you're seeing here is probably a missing java runtime. Type 'which java' for diagnosis or install the openjdk on your target system. Anton Am Mo., 16. Jan. 2023 um 10:01 Uhr schrieb Alberto Merciai <alb3rt0.m3rciai@...>:
|
||
|
||
meta-everest
Alberto Merciai
Hello, I'm trying to bitbake meta-everest c4158593c1a632958e2202c382cbd49f6b85f7a4 build works fine but If I try to run the manager I get this error? have you got the same issue? Any tips? /usr/bin/manager --conf /etc/everest/config-sil-dc.yaml 2022-04-28 17:49:18.030240 [INFO] manager :: 8< 8< 8< ------------------------------------------------------------------------------ 8< 8< 8< 2022-04-28 17:49:18.030583 [INFO] manager :: EVerest manager starting using /etc/everest/config-sil-dc.yaml 2022-04-28 17:49:19.084846 [INFO] everest_ctrl :: everest controller process started ... 2022-04-28 17:49:19.091323 [INFO] everest_ctrl :: Launching controller service on port 8849 2022-04-28 17:49:27.219253 [INFO] energy_manager: :: Module energy_manager initialized. 2022-04-28 17:49:27.377287 [INFO] auth:Auth :: Module auth initialized. 2022-04-28 17:49:27.547812 [INFO] grid_connection :: Module grid_connection_point initialized. 2022-04-28 17:49:27.567745 [INFO] api:API :: Module api initialized. 2022-04-28 17:49:28.693221 [INFO] evse_manager:Ev :: Module evse_manager initialized. 2022-04-28 17:49:32.111858 [INFO] token_validator :: Module token_validator initialized. 2022-04-28 17:49:32.124049 [INFO] imd:JsIMDSimula :: Module imd initialized. 2022-04-28 17:49:32.236021 [INFO] yeti_driver:JsY :: Module yeti_driver initialized. 2022-04-28 17:49:32.274439 [INFO] token_provider: :: Module token_provider initialized. 2022-04-28 17:49:32.284874 [INFO] powersupply_dc: :: Module powersupply_dc initialized. 2022-04-28 17:49:32.356947 [INFO] car_simulator:J :: Module car_simulator initialized. 2022-04-28 17:49:32.421857 [INFO] iso15118_car:Js :: Module iso15118_car initialized. 2022-04-28 17:49:32.471295 [INFO] slac:JsSlacSimu :: Module slac initialized. 2022-04-28 17:49:39.211908 [INFO] iso15118_charge :: Initializing framework for module iso15118_charger:PyJosev... 2022-04-28 17:49:39.250251 [INFO] iso15118_charge :: Initializing module iso15118_charger:PyJosev... 2022-04-28 17:49:39.511907 [INFO] iso15118_charge :: Module iso15118_charger initialized. 2022-04-28 17:49:39.544715 [INFO] manager :: >>> All modules are initialized. EVerest up and running <<< terminate called after throwing an instance of 'pybind11::error_already_set' what(): FileNotFoundError: [Errno 2] No such file or directory: 'java' At: /usr/lib/python3.10/subprocess.py(1845): _execute_child /usr/lib/python3.10/subprocess.py(1005): __init__ /usr/lib/python3.10/site-packages/py4j/java_gateway.py(331): launch_gateway /usr/lib/python3.10/site-packages/py4j/java_gateway.py(2162): launch_gateway /usr/libexec/everest/modules/PyJosev/../../3rd_party/josev/iso15118/shared/exificient_exi_codec.py(22): __init__ /usr/libexec/everest/modules/PyJosev/module.py(31): main 2022-04-28 17:49:39.841179 [CRIT] manager int boot(const boost::program_options::variables_map&) :: Module iso15118_charger (pid: 1053) exited with status: 6. Terminating all modules. 2022-04-28 17:49:39.841868 [INFO] manager :: SIGTERM of child: api (pid: 1044) succeeded. 2022-04-28 17:49:39.842118 [INFO] manager :: SIGTERM of child: auth (pid: 1045) succeeded. 2022-04-28 17:49:39.842296 [INFO] manager :: SIGTERM of child: car_simulator (pid: 1046) succeeded. 2022-04-28 17:49:39.842482 [INFO] manager :: SIGTERM of child: energy_manager (pid: 1047) succeeded. 2022-04-28 17:49:39.842726 [INFO] manager :: SIGTERM of child: evse_manager (pid: 1048) succeeded. 2022-04-28 17:49:39.842995 [INFO] manager :: SIGTERM of child: grid_connection_point (pid: 1050) succeeded. 2022-04-28 17:49:39.843159 [INFO] manager :: SIGTERM of child: imd (pid: 1051) succeeded. 2022-04-28 17:49:39.843301 [INFO] manager :: SIGTERM of child: iso15118_car (pid: 1052) succeeded. 2022-04-28 17:49:39.843453 [INFO] manager :: SIGTERM of child: powersupply_dc (pid: 1054) succeeded. 2022-04-28 17:49:39.845784 [INFO] manager :: SIGTERM of child: slac (pid: 1055) succeeded. 2022-04-28 17:49:39.846481 [INFO] manager :: SIGTERM of child: token_provider (pid: 1056) succeeded. 2022-04-28 17:49:39.847427 [INFO] manager :: SIGTERM of child: token_validator (pid: 1058) succeeded. 2022-04-28 17:49:39.848435 [INFO] manager :: SIGTERM of child: yeti_driver (pid: 1063) succeeded. 2022-04-28 17:49:39.848645 [CRIT] manager int boot(const boost::program_options::variables_map&) :: Exiting manager. Thanks, A
|
||
|
||
Upcoming Events
#cal-summary
Group Notification <noreply@...>
EVerest Discussion Upcoming EventsEVerest Weekly Tech SyncWhen: Organizer: marco.moeller@... marco.moeller@... Details: EVerest Weekly Tech SyncWhen: Organizer: marco.moeller@... marco.moeller@... Details: EVerest TSC Technical Steering CommitteeWhen: Organizer: marco.moeller@... marco.moeller@... Details: EVerest Weekly Tech SyncWhen: Organizer: marco.moeller@... marco.moeller@... Details: EVerest Weekly Tech SyncWhen: Organizer: marco.moeller@... marco.moeller@... Details:
|
||
|
||
Re: Admin Panel
Marco Möller
Now you are part of the list. Welcome! Marco Möller <marco.moeller@...> schrieb am Mi., 11. Jan. 2023, 22:26:
|
||
|
||
Re: Admin Panel
Marco Möller
Would be great if you subscribe to the EVerest email list since otherwise I have to approve every of your messages manually. Also the replies might never reach you like the one from Anton I forwarded. Just go here: Cheers
I am sorry to bother as well with the question of what server instance should I select or input? That may be my problem but I don't know how to solve it yet. By running the server instance in loopback is when the connection is lost and it does not let me save the config file. Thanks beforehand, if I have any advance I’ll share it.
|
||
|
||
Re: Admin Panel
Luis Castro
I am sorry to bother as well with the question of what server instance should I select or input? That may be my problem but I don't know how to solve it yet. By running the server instance in loopback is when the connection is lost and it does not let me save the config file. Thanks beforehand, if I have any advance I’ll share it.
|
||
|
||
Re: Admin Panel
Anton Wöllert
Hi, that's hard to diagnose from here. In the screenshot I can see that you're serving the admin-panel app via `npm run serve`. This shouldn't be necessary with a recent version of everest-framework. Usually, the reconnection screen appears, if everest itself is not running anymore. May it be that everest stops or crashes after a minute or something? Am Mi., 11. Jan. 2023 um 21:58 Uhr schrieb <lscastrochapa2000@...>:
Hi thank you so much, I was able to access the EVerest admin panel with your help. Actually it appears to work well even with the config design but only for a minute before it loses connection to EVerest backend.
|
||
|
||
Re: Admin Panel
Luis Castro
Hi thank you so much, I was able to access the EVerest admin panel with your help. Actually it appears to work well even with the config design but only for a minute before it loses connection to EVerest backend.
Is there something that I could possibly done wrong or is it just the server?
|
||
|
||
Re: Admin Panel
Anton Wöllert
Hi Luis, it depends on how you start the admin-panel, if you check out the everest-admin-panel via git as "standalone", you typically do an `npm install`, and then a `npm run serve`, which should give you something like: - Local: http://localhost:8080/ - Network: unavailable The port here (8080) might vary, depending on your system. But usually, if you run a recent everest installation, the admin-panel gets already started on the default port 8849 So try 8849 and everything should be fine. Best, Anton Am Mo., 9. Jan. 2023 um 08:53 Uhr schrieb Luis Castro <lscastrochapa2000@...>:
Hello,
|
||
|
||
Admin Panel
Luis Castro <lscastrochapa2000@...>
Hello,
I have been assigned as a project (for the entry to a masters) the use of this platform and I have been studying its great use and its features. I apologize because I am no expert with this environment and I just wanted to ask how do I access the admin panel. I already installed it via npm and went to the standard web port 80 which I suppose is localhost:1880(sent me to the nodered interface) and also tried localhost:80(didn’t work). I hope I can get help because in the introduction video I saw how easy it could be to be use the blocks to create a config file. Thanks beforehand and have a nice day.
|
||
|
||
Upcoming Events
#cal-summary
Group Notification <noreply@...>
EVerest Discussion Upcoming EventsEVerest Weekly Tech SyncWhen: Organizer: marco.moeller@... marco.moeller@... Details: EVerest Weekly Tech SyncWhen: Organizer: marco.moeller@... marco.moeller@... Details: EVerest Weekly Tech SyncWhen: Organizer: marco.moeller@... marco.moeller@... Details: EVerest TSC Technical Steering CommitteeWhen: Organizer: marco.moeller@... marco.moeller@... Details: EVerest Weekly Tech SyncWhen: Organizer: marco.moeller@... marco.moeller@... Details: EVerest Weekly Tech SyncWhen: Organizer: marco.moeller@... marco.moeller@... Details:
|
||
|
||
Re: UI and full python module info
Group Moderator
Hi Alberto,
regarding UI application: Yes, exactly the one for getting visual feedback when doing simulation with NodeRed. For a python example, I can point you to this one: https://github.com/EVerest/everest-core/tree/main/modules/PyJosev As far as I know, this is our first and only Python implementation. You can find the manifest file and module code files in that repo directory. (If I forgot anything to mention here, somebody will add to that in a follow-up mail.) Documentation for python integration will follow. Best regards, Manuel.
|
||
|
||
UI and full python module info
Alberto Merciai
Hello and happy new year! Is there any documentation or example of full python module? The UI application you mention is the one obtained using node red framework or there is also another example? Thanks a lot, Alberto
|
||
|
||
EVerest’s 2022 - and 2023
Group Moderator
Welcome everyone - let's step right into 2023! Let’s have a short glance in the rearview mirror to see the EVerest achievements of 2022 (with a few teasers for 2023). What could we create?
Be part of our journey by visiting our weekly tech meetups (virtual room links regularly posted on this mailing list). There you will get insights about our current development work. Also stay tuned on our YouTube channel at https://www.youtube.com/@lfe_everest. Thanks for being part and looking forward to a great EVerest future. Electric-powered greets, Manuel. Community Supporter
|
||
|
||
Re: edm --update issue
Alberto Merciai
Yes, thanks was a typo : )
On Mon, 2 Jan 2023, 14:09 Anton Wöllert via lists.lfenergy.org, <anton.woellert=pionix.de@...> wrote:
|
||
|
||
Re: edm --update issue
Anton Wöllert
Did you solved this issue already? It looks like a typo: iso151118 should be iso15118. Am Fr., 23. Dez. 2022 um 12:30 Uhr schrieb Alberto Merciai <alb3rt0.m3rciai@...>:
|
||
|
||
Upcoming Events
#cal-summary
Group Notification <noreply@...>
EVerest Discussion Upcoming EventsEVerest Weekly Tech SyncWhen: Organizer: marco.moeller@... marco.moeller@... Details: EVerest Weekly Tech SyncWhen: Organizer: marco.moeller@... marco.moeller@... Details: EVerest Weekly Tech SyncWhen: Organizer: marco.moeller@... marco.moeller@... Details: EVerest Weekly Tech SyncWhen: Organizer: marco.moeller@... marco.moeller@... Details: EVerest TSC Technical Steering CommitteeWhen: Organizer: marco.moeller@... marco.moeller@... Details: EVerest Weekly Tech SyncWhen: Organizer: marco.moeller@... marco.moeller@... Details: EVerest Weekly Tech SyncWhen: Organizer: marco.moeller@... marco.moeller@... Details:
|
||
|
||
Re: EVSEMaximumCurrentLimit DIN70121
Alberto Merciai
On Thu, 29 Dec 2022, 11:31 Cornelius Claussen via lists.lfenergy.org, <cornelius.claussen=pionix.de@...> wrote:
|
||
|
||
Re: MQTT available topic list
Cornelius Claussen
No, there isn't. But in general you should not access any of the topics directly outside of everest framework, that may confuse the internal logic and the topics are also not considered stable and may change any time. If you want to access some vars or execute commands you should write an everest module with proper requirements etc. If you want to have an non everest process communicate with everest over mqtt use the API module, it exposes a simplified API that is more stable. Best Cornelius Alberto Merciai <alb3rt0.m3rciai@...> schrieb am Do., 29. Dez. 2022, 14:52:
|
||
|
||
MQTT available topic list
Alberto Merciai
Is there a way to retrieve all MQTT topics available given a config file?
|
||
|