Replies: 5 comments 15 replies
-
|
Hi! Thanks for your kind words. I'm currently running a small personal ESP32 project that successfully integrates isobus++. If you have the time to make a step-by-step guide on how to implement isobus-plus-plus with ESP on PlatformIO, that would be greatly appreciated! Regarding the issue you are facing, I also faced it a while back if I remember correctly. But I'm unsure how I fixed it back then. My current [env:debug]
platform = espressif32
board = esp32-s3-custom
framework = espidf
build_type = debug
upload_protocol = esptool
debug_tool = esp-builtin
board_build.embed_txtfiles = src/vtpooldata.iop
monitor_dtr = 0
monitor_speed = 115200
monitor_filters = esp32_exception_decoder
lib_deps = https://github.com/ad3154/Isobus-plus-plus.gitI'm using the C++14 is indeed a requirement for integrating this library. There should be an option somewhere in PlatformIO to enforce it. Let me know if you are able to fix it. Otherwise the logs of building and/or steps to reproduce would be useful to help you solve this problem. Thanks for your interest in the project! |
Beta Was this translation helpful? Give feedback.
-
|
Oh also, the "cStandard": "c17",
"cppStandard": "c++20",Note that it is an auto generated file, and should therefore only be used as indication: |
Beta Was this translation helpful? Give feedback.
-
|
My |
Beta Was this translation helpful? Give feedback.
-
|
I think |
Beta Was this translation helpful? Give feedback.
-
|
Hi @GwnDaan You embed the iop-file in the platformio config - how did you load it into the VirtualTerminal? |
Beta Was this translation helpful? Give feedback.
-
Hey! Coincidentally, I explained this a few days ago here: #229 (comment) |
Beta Was this translation helpful? Give feedback.
-
|
Hi! I added the folowing line in the MakeList.txt of the root folder: |
Beta Was this translation helpful? Give feedback.
-
|
Thanks a lot for you quick support, guys! Right now I was able to comile the project and honestly I don't know what I made wrong the last hours. The only thing I changed right now after creating a new project in PlatformIO with the ESP-IDF framework was adding the library, so my platformio.ini looks like: Maybe it's important to disable the Espressif IDF extension. I will try to understand this with a clean installation of VSCode and all the necessary extensions. |
Beta Was this translation helpful? Give feedback.
-
|
Hi guys, This is the terminal output: Thanks a lot for your work! |
Beta Was this translation helpful? Give feedback.
-
|
Update: This fix is now in |
Beta Was this translation helpful? Give feedback.
-
|
Hi! I was able to resolve the issue with the However I am still getting the second error: |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for reporting this. I was hoping this would be fixed earlier, but It seems like it's actually mad that we're trying to use An easy fix might be for us to add overloads of I will open an issue for this and get it fixed on our end ASAP |
Beta Was this translation helpful? Give feedback.
-
|
Created issue #322 |
Beta Was this translation helpful? Give feedback.
-
|
OK @Schine73 I believe we have fixed this in #323 so updating the library (which platform IO might do automatically?) should fix the compilation issue you and @joaooliveira82 were seeing. |
Beta Was this translation helpful? Give feedback.
-
|
Hello together, I'm not sure if my issue is on the right spot here. I also tried to get the library running with an ESP32 and the virtual terminal example. After some challenges that I faced (like there was no "create" function in the can_network_manager.hpp anymore (seems liks it's replaced by "create_internal_control_function", I was able to compile everything and flash it on the esp32. I now attached the esp32 to a CLAAS Communicator II. Unfortunately the object pool is not loading. On the serial monitor I get following output: ... it seems like address claiming is happening (?) but there is function sent by the terminal which doesn't work with the stack? I am kinda new to that ISOBUS area. Is there something which I miss/don't understand? Since it' working fine with my raspberry and the same VT. |
Beta Was this translation helpful? Give feedback.
-
|
Hi there, I'm happy to try to help you out here. TLDR: make sure you have fully applied step 8 of the ESP32 tutorial. Especially the increase of the default thread stack size. The long answer: since the partnered control function has been claimed by the VT server, I think you're CAN communication is working correctly. Though I've not seen any unsupported function being sent before, so that's new, though I doubt that's the only reason the ESP crashed. Looking at the backtrace that was dumped, it looks like it crashed on the following line: (assuming you were on the latest commit of the main branch here) The interesting part here is that Also, the "create" function for an internal control function is already using the new Lastly, you've found some some small formatting issue here with the logged unsupported function codes, I proposed a fix for it in #475 :). It would be appreciated if you can try to run the code again once the PR is merged to main and see which function-code the server tries to send. I'm curious to see what the VT wants hahah. I assume you also encounter this log messages when running the example on the raspberry pi? |
Beta Was this translation helpful? Give feedback.
-
|
Hey GwanDaan, thanks for your fast reply and your help!! I checked step 8 again and unfortunately didn't make it run in the first place (check beyond for new errors..). Few more information and tests from my side (as said before, I am at the start or working with C++ and those things). I writing down in the order in tried. Create function:
So I was replacing it by the code from the example folder in the stack with the lines: Frame Handler:
Using the example from the example main.cpp again. (create_internal_control_function already there. Adding preferred number 0x81) Attention: The lines from the tutorial in step 7 ... where not given in the example main.cpp, therefore the code wasn't working out of the box. The good news: I don't know what I did different now, but at least ESP32 is not rebooting anymore. That's the log now (I already adjusted the isobus_virtual_terminal_client.cpp lines to %hu and removed the additional debugging lines again for better overview): Do you have any idea about how to fix these errors? Thanks for your help in advance! |
Beta Was this translation helpful? Give feedback.
-
|
Hi @Ditzebecker, sorry for the delay. The The
I'd suggest to make sure you're wiring is correct and follows the canbus specifications |
Beta Was this translation helpful? Give feedback.
-
|
Hey @GwnDaan , now the delay is on my side .. harvest season started .. I additionally added following lines for the TWAI Timing and Driver setup: I got it by the ISOBUS Norm, hope I understood it the correct way. Best regards! |
Beta Was this translation helpful? Give feedback.
-
Hi guys,
I'm really enthusiastic about your work with the isobus-plus-plus project.
I got the project compiled in linux and windows and also got the examples working with the PCAN driver, finally seeing the CAN messages on the bus. :)
Now I tried to integrate the library to a ESP32 platform using PlatformIO, but struggeling. Do you have any hints how to get it working? I added the library to the lib_deps by using this in the platformio.ini:
lib_deps =
https://github.com/ad3154/Isobus-plus-plus.git
Now there are several errors, some of seem to be caused that C++14 is necessary?
Maybe a short tutourial would be nice, how to integrate it for "dummies". Let me know, if I should note it step by step so it could be published in the readthedocs-section.
Do you have any hints for me?
Thanks a lot for your great work!
Beta Was this translation helpful? Give feedback.
All reactions