Communication and Setup

Go To Last Post
11 posts / 0 new
Author
Message
#1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Good day all

I need some recommendations on how and with what to do the following project.

I want to start building a system that will start relative small but that will be expanded as the need arises.

Master controller that consist of a HMI (preferably touchscreen), Some type of wireless access (2.4GHz, bluetooth, must not be line off sight dependent), GSM (at a way later stage), Battery management (monitors battery levels, maybe even the charging part, but this can be a third party device as well).

Then I will need communication to 5 other sets of systems which will consist each of smaller uC, ADC, Temp, pressure, etc. (this list will expand in the future, haven't completely decided what and where yet). So lets say I will have 5 slave systems that each consists of various other units if I can call it that. I thought about SPI...daisy chained to minimize the amount of CS lines. I know that with daisy chain I will need to write through all the devices if I want to address the last device. Speed will not be critical, rather a less complex system with not so much routing involved (this also determines the amount of I/O lines needed on the uC). If possible, a controller with 5 SPI channels? Any recommendations? Also on the communication, any recommendations other than SPI? Communication will be bidirectional.

I have the AVR ISPMKII programmer, so I would like if I could stick to the compatible AVRs for the AVR ISPMkII.

Thank you,

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:
any recommendations other than SPI?
I2C or TWI?

John Samperi

Ampertronics Pty. Ltd.

https://www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Ipad and arduino. Job done. Next question.....

Ah yes, use rs485 to communicate.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

js wrote:
Quote:
any recommendations other than SPI?
I2C or TWI?

I'm not familiar with I2C or TWI. What advantages will these two types of communication protocols have op SPI?

Regards,

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

No individual CE or CS lines
Bus topology with device addressing in the protocol

Though as Kartman already suggested, RS485 is probably better again.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Thank you all, I'll have a look at the suggestions and take it from there.

Thank you,

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Wouldn't a critical factor in selecting the bus be the distance between the units?

JC

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

JC wrote

Quote:
Wouldn't a critical factor in selecting the bus be the distance between the units?
And don't forget to include the speed of the interface in your decision.
Ron.

 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Need to know how far you slave devices will be from the master and each other. And what speed to you want to go? As others have suggested, RS-485 sounds best.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

The distance will be up to max 500m which RS-485 is capable to do if I'm not mistaken. Speed is not a factor, stability and distance is more important.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hi mtlost,

I sent you a PM about this.

______
Rob

Scattered showers my arse -- Noah, 2348BC.
Rob Gray, old fart, nature photographer, embedded hardware/software designer, and serial motorhome builder, www.robgray.com