Hi,
We're planning to establish communication between 2 C2000 controllers ie TMS320F28377S and TMS320F2812 for paralleling 2 power systems.
Which communication Protocol do you recommend. Is there any app note on this or similar subject?
Aish
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.
Hi,
We're planning to establish communication between 2 C2000 controllers ie TMS320F28377S and TMS320F2812 for paralleling 2 power systems.
Which communication Protocol do you recommend. Is there any app note on this or similar subject?
Aish
Hi Aish,
Aish Ahuja said:Is there any app note on this or similar subject?
Nope, there's no App note on this topic.
Aish Ahuja said:Which communication Protocol do you recommend.
This depends on the developer and the intensity of the application. Previously RS-232/485 where very widely used and now a days Ethernet or MODBUS are preferred. Implementing the later would be a challenge but very much possible (search the forum for the same). As for RS232/485 would be comparatively easier. You can use the SCI peripheral for the implementation.
If I'm not wrong this parallel connection would be external right? If internal then you can explore I2C and SPI too.
Regards,
Gautam
Gautam Iyer said:Previously RS-232/485 where very widely used and now a days Ethernet or MODBUS are preferred. Implementing the later would be a challenge but very much possible (search the forum for the same). As for RS232/485 would be comparatively easier.
Sorry Gautam but this is wrong.
1) RS-232 and RS-485 standards simply define physical (electrical) level of communication and Modbus, in contrary, is application layer protocol, thus they are on completely different OSI levels. You can implement Modbus on RS-232 or RS-485 or on TCP/IP, it's completely up to you. RS-232 or RS-485 as is don't give you anything. You will have to either implement custom protocol or use any available protocol (such as Modbus RTU, or Modbus ASCII).
2) Implementing Modbus (RTU for instance) is not harder than implementing custom protocol, if you really need a reliable communication and you are planning to send different type of data packets. In fact normally it will save you a lot of time, because standard protocols are robust and effective. Of course, if you just need to send some flags then Modbus (or similar protocol) would be an overkill.
Aish Ahuj,
You need to consider lengths. RS-232 shouldn't go for more than a couple of meters, in contrary, RS-485 with proper cable can go up to 1200m. RS-485 with Modbus is a good choice for master-slave reliabile communication especially in harsh conditions. As for SPI it's also dedicated for short distances and also is unbalanced, hence less immune to noise.
Hi Andrei,
I agree with your statements and I'm very well aware of the same. My statements were made in general wrt the industrial usage.
As the query was related to paralleling of power systems I enlisted the best suited protocols with libraries available for C2000 mcus. I've personally paralleled inverters with RS-485 MODBUS (for high power) and SPI (for low power).
Thank you for your detailed insight! Very valuable :)
Regards,
Gautam