-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Doubt about compilation #3
Comments
Hi, Both Step 1:
This creates a folder Step 2: #define CODE_VERSION_EXI 1
#define CODE_VERSION_SAMPLE 2
#define CODE_VERSION CODE_VERSION_SAMPLE The last line ( Step 3:
Change directory Step 4:
From within the
I hope this info helps you to get started. |
Hi, Thank you so much for your reply. I could execute the application. I think that in the code of the function charging1() is mixed the code of the charger and the vehicle. I think that if I want to communicate with the EV I need to comment the code related to the EV. Is this correct? Thanks in advance. |
Hi, I think you can keep function The actual communication with the EV was done using an INSYS Powerline GP. Some background info: #2 (comment) |
Hi, I noticed a few commits in the original repository on SourceForge, so I updated the repository and it is up-to-date with the original SVN version (https://sourceforge.net/p/openv2g/code/HEAD/tree/trunk/) now. |
Hi, In first place thank you so much for the reply. Now, I have achieved to see the slac messages, but I am not sure how to see the messages of the V2G protocol. I am using a board with a qca7000, so the messages are sended via CP. I want to see in a first place the messages that occurss in the appHandshake() but I am not sure how to see the messages in the terminal. In the first phase I execute the code related to the slac communication and after I execute the code related to OpenV2G. Could you indicate me how can I debug the messages of the communication? Thanks in advance. |
Hi, The easiest way to see the messages is probably by adding some struct appHandEXIDocument handshake; /* what you send */
struct appHandEXIDocument handshakeResp; /* what you receive */ If you want to view the raw data directly perhaps it is an option to send the data to the QCA7000 UART port too. You can attach a UART to USB converter to that port and monitor the data using software like |
Hi, Thank you for the reply. I have a doubt about how the library knows about which interface I have connected to the qca7000? Do I need configurate in any place of the code the interface? How is done the communication? Thanks in advance. |
Hi, Looking at the QCA7000 software (qca/qca7000) you can choose the QCA7000 software version you want to use:
|
Hi, Thank you for the reply. I know about the interface to communicate with the qca7000. I communicate my MPU via SPI. I have used the open-plc-utils library and works, but I have doubts about the OpenV2G library, which interface use this library to transmit? For example, I have the interface eth1 created by the driver of qca7000 and I want to use this interface to transmit and receive the messages of V2G, which do I need to configure? Thanks in advance. |
Hello, The library does not use an interface, it just feeds the message to itself and returns a response. For actually transmitting the data you have to write the code that transmits the data to the QCA7000. If you communicate with the QCA7000 using SPI you have to write that part of the code. In |
Hi,
I have seen that you have cloned the OpenV2G repository and you have worked with this repository. I have seen that in the folder src/test there is a file named main_example.c that execute a code that call the functions developed. I am not sure if there is a Makefile to compile all or I need to do this Makefile to compile. Could you indicate me this?
Thanks in advance.
The text was updated successfully, but these errors were encountered: