Continue to Site

Welcome to EDAboard.com

Welcome to our site! EDAboard.com is an international Electronics Discussion Forum focused on EDA software, circuits, schematics, books, theory, papers, asic, pld, 8051, DSP, Network, RF, Analog Design, PCB, Service Manuals... and a whole lot more! To participate you need to register. Registration is free. Click here to register now.

MCU Selection Help--Urgnet Requirement

Status
Not open for further replies.

Qasim1991

Newbie level 6
Joined
Jun 21, 2017
Messages
14
Helped
0
Reputation
0
Reaction score
0
Trophy points
1
Activity points
136
Hi All,

I hope everything is going well.

I have a very simple application--basically I need 3 temperature and 2 humidity inputs, and need to control 2 relays based on the input values (Need 9 such systems). Also, I need to communicate the temperature and humidity data, as well as the status of the relays (on/off) to a Master controller, from where that data should be visible via a Dashboard or some sort of GUI.

Which MCUs will be suitable for this project? Which communication protocol should be used? Simply the CAN protocol? Or Modbus TCP? Or some other?

I have never actually worked on a professional level with a MCU, so really need some advice.


The block diagram may help as well..
 

Attachments

  • with MCU.PNG
    with MCU.PNG
    33.8 KB · Views: 137

I have created a similar project a long time ago.
I used an Atmega168.
I used I2C Bus for to communicate with DHT22 sensors (Humidity and temp).
Also had an LCD for displaying information and other chips such as a DS1307 clock etc....

You will need tools to do this project. Atmel Studio, AVRDude software, a chip programmer, also a simulator software such as Proteus is helpful but not required.
 
Thanks Pete. How about the TI MCUs? Got any experience with them? Also, which communication protocol did you use?

- - - Updated - - -

I am very inclined towards using Modbus as the communication protocol..
 

Hi,

Without more specificatiin I see no reason why a TI mcu should not work.

Interface.
Did you try find out how to specify an interface?
You surely would use different busses for "3 ICs on the same PCB" than for "3 devices some kilometers apart".
Or for a couple of bytes per second or megabytes per second.
Peer-to-peer like shown in your picture, or true bus with multiple members.
Single ended, differential,
Hardware effort
Software effort
Power requirements
Cable requirements
...and so on...

Klaus
 
As from what I have understood Klaus from your question Klaus, I intend to use temperature and humidity sensors with I2C interface, so that the distance is not an issue. Secondly for the communication between different systems and the Host CPU, I am inclined towards Modbus TCP as the communication protocol. This answers the cable requirements for sensors, and the cable requirement for communication will be satisfied with the ethernet cables for Modbus TCP.
I am happy to provide 240vac or 5/12/24vdc as the power. The sensors will be power from the MCU as well, so I am not too worried about the power.

Have I answered your question? Do you have any feedback/recommendations over this?

- - - Updated - - -

https://www.ti.com/store/ti/en/p/product/?p=HDC1010YPAR or
https://www.ti.com/store/ti/en/p/product/?p=HDC1080DMBR

These are the temperature sensors I have in mind. Both can communicate via i2c.


https://www.ti.com/store/ti/en/p/product/?p=MSP432E401YTPDTR

Planning this to use as my HOST/Master controller--the reason being it has MAC PHY.


Now I need to find a MCU which has i2c and ethernet both, so that it can sense and communicate too.

- - - Updated - - -

https://www.ti.com/product/msp432e401y
I guess this unit can do this all.
 

Status
Not open for further replies.

Similar threads

Part and Inventory Search

Welcome to EDABoard.com

Sponsor

Back
Top