This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Tool/software: TI C/C++ Compiler
I have to work on MSP430F425. My code in the TI TIDC299 software.
I tried to calibrate the meter but the texas instruments 430 calibrated mass
Turn on red. So there is a communication error. I used a simple terminal to test communication uart which is configured in tidc449 I find that the communication is established correctly and there are messages that I received. I did not understand where the problem is. I think there is a communication between the graphical interface of TI GUI and the code tidc499 which allows to test the communication because there is no problem on the hardware side. I need help to know the instruction in the communication part which is dided to test the communication. Always the graphical interface turning red.emeter-communication.c
We are glad that we were able to resolve this issue, and will now proceed to close this thread.
If you have further questions related to this thread, you may click "Ask a related question" below. The newly created question will be automatically linked to this question.
In reply to arfaoui aymen:
Arfaoui, Are you configuring the COM port on your PC properly? You have to check Device Manager in Windows to find out which COM port the RS232-to-USB adapter is using. Then, you have to update the COM port number in the 'calibration-config.xml' file in "tidc299.zip" -> "emeter-software" -> "emeter-software" -> "GUI" folder. Also, I'm assuming that you're using one of our EVMs or a custom hardware that has the UART interface implemented properly. Regards, James MSP Customer Applications
In reply to James Evans:
thank you James for reply, Yes i have configure com 6 and also i change the port in the xml file of GUI and i am sure the hardware communication is well established. Because I have tested its functionality by a simple terminal I think the problem software side for this I am looking for it is the responsible function has established the beginning of communication.
If you are using a simple terminal program, you'll need to send commands to the i20xx device using the dlt645 protocol. I've found that the Serial Port Utility terminal software allows multi-byte packets required for this protocol to be generated. The GUI uses this protocol with the default communication code to pass data back and forth. Since you're using a simple terminal program, you're probably sending data byte-by-byte, which may not work correctly with the state machine in the code for the various commands. Perhaps you could use a logic analyzer to monitor what's being send over the UART interface as well.
Although you are sure that your hardware is working, it may be good to try the original code on our EVM as a comparison. If you're already using an EVM, then this wouldn't apply.
MSP Customer Applications
I think I can do an interface using MATLAB which allows to read and write data on the counter to calibrate the values to avoid the standard screen format for the old interface is possible !!! I change my configuration uart for a simple communication of sending and receiving the problem is what possible to interfere MATLAB with MSP430F425 !! Is what a good idea !! Because I think the TIDC299 code uses an IEC1107 communication protole and the interface uses dlt645.
Unfortunately, I don't have much experience with using MATLAB to interface with hardware, but I found some links that may be helpful (see below). Also, if you interested in keeping the DLT645 protocol as-is on the MSP430F425 and just want to use MATLAB to read the results, calibrate the device, etc., I would encourage you to post a question about how to do this in MATLAB's Community and Support website.
If you would like to change the DLT645 protocol, this can be done but would involve extensive work. I don't have any specific references on how to do this, but if you have a specific UART-based protocol that you're required to use, you can modify the code to create the appropriate data packet (frame start notification, address, control bits, data, checksum, etc.) according to the specifications for that protocol. For example, you can read about the structure of the DLT645 protocol in Appendix A in the MSP430AFE253 Test Report for China State Grid Specification app note.
Hopefully this helps.
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with respect to these materials. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.