Simple Network – Will it Work?

Status
Not open for further replies.
F

For The Popcorn

Well-Known Member
Most Helpful Member
I have a need to monitor several sensor nodes, all within a couple meters, with small polled data readings (a few bytes) at low sample rates.

Rather than implementing something like an RS-485 network, I think this simple network will work. Each sensor node will have a PIC18F micro. Each sensor node UART Tx line would be paralleled via tri-state buffers, and connected to the host Rx. The host Tx line would be connected in parallel with all the sensor node Rx lines.

The host would send a message "node 1 send data". Node 1 would enable its tri-state buffer, communicate as needed, and disable its buffer. Other nodes would respond when queried. No data is sent by a node until requested, so no data sync problems. The nodes only see data send by the host, so no need to strain through a large stream of data looking for commands, nor the possibility of misinterpreting data streams as a command. 9600 baud is fine for this app.

Any problems with this idea?

 
Sort by date Sort by votes
Cheap wireless network ?

ESP-MESH with ESP32 and ESP8266: Getting Started | Random Nerd Tutorials

Build a mesh network with ESP-MESH protocol using the ESP32 and ESP8266 NodeMCU boards. ESP-MESH allows multiple devices (nodes) to communicate with each other.
randomnerdtutorials.com

ESP-NOW: Receive Data from Multiple ESP8266 Boards (many-to-one) | Random Nerd Tutorials

Setup an ESP8266 NodeMCU board to receive data from multiple ESP8266 boards via ESP-NOW communication protocol (many-to-one configuration) with Arduino IDE.
randomnerdtutorials.com


Regards, Dana.
 
Upvote 0 Downvote
For The Popcorn said:
Any problems with this idea?
Click to expand...
No.

There will be lotsa opinions about part selection, environment mitigation, power and ground management, programming techniques, completely different approaches, more complex methods, more expensive methods , , , , , . . . But -

The *idea* of a software controlled, polled data acquisition system with distributed node multiplexing is sound, and has been around for decades.

ak
 
Last edited:
Upvote 0 Downvote
I vaguely remember that enableing the receiver automatically enabled the transmitter so tristating may not work. It was a long time ago so a little vague. Think I only wanted to receive and use the transmit pin for something else. Of course the chips are much more flexible now so you can probably switch the transmit pin to nowhere using PPS.

Mike.
 
Upvote 0 Downvote
Pommie said:
I vaguely remember that enableing the receiver automatically enabled the transmitter so tristating may not work.
Click to expand...

It may be possible to accomplish this in the PIC, but I'm going to use a separate tri-state buffer.

Actually, thanks to Tony Stewart 's comment, I'll use a quad buffer to get some degree of ESD protection and add a /RESET line from host to each node's /MCLR pin so I can reset all the nodes if they become unresponsive.
 
Upvote 0 Downvote
A common similar but simpler method is just to "Diode /OR" all the TX pins - any device sending data will pull the host RX line low. One Schottky diode per node and a pull-up resistor.

However:
With the complexity you have in the drawing - extra driver IC & transmit control - you are already up to the complexity of RS422 or RS485, other than the link wires?
Using one of those standards gives you far better ESD protection and tolerance for wiring voltage drops and ground offsets.

If you are going to add ICs, I'd go with ones made for the job?

(And you can then use the same node design for remote ones in the future).
 
Upvote 0 Downvote
From experience, word of advice ... implement some kind of CRC with your data packets. My particular favorite is MODBUS <-- just for the CRC implementation, not necessarily the protocol
 
Upvote 0 Downvote
An even simpler system would be PICAXE from Dontronics (Don McKenzie) - NOT the later PICAXE which was a PIC containing a BASIC interpreter, but Don's original one.

You simply daisy chained the serial ports together, and sent packets of data, with each packet having an address, and each PIC having it's own unique address. So the first PIC received the data, checked the address, and if wasn't the correct address passed it on the next PIC - which did the same. Once a PIC found it's own address, it processes the command, and doesn't pass it on.

To send a reply it simply sends a command with the address of the host controller.

An obvious issue is if the chain is broken, but that applies to any system really.

Just another variation on a theme - but it was used successfully for all kinds of control systems - and Don sold a PICAXE board specifically for the purpose.

Unfortunately Dontronics has closed now.
 
Upvote 0 Downvote
Some thoughts...

Depending on the environment, at 9600 baud (~100us/bit) you could probably get away with a simple open-drain bus for the slave outputs. Most modern 18F's have an open-drain IO pin mode, and let you invert the TX data if you're using an external OD mosfet instead. Put a stiff pullup on the master side.

Using 9-bit uart mode allows you to "address" each device.

Be careful with adding a RESET line to the MCLR pins... that can make things more susceptible to noise on that line.

You can use a serial BREAK condition to reset them, or running your "RESET" into a slave INTR pin is a little more flexible... you may not really want the slave to reset right at that moment (writing to eeprom, I2C transactions, etc) and you can software filter it for noise, etc.

It's not as "100% foolproof" as having a hardware /MCLR reset, but it doesn't have the other issues associated with it.
 
Upvote 0 Downvote
You only have thousands of choices for ;

- error & fault detection/ protection/ correction/ testability/ calibration, hot-swap pluggability, capacity, gofundme-interest, expandability and cost

Reinvent the wheel or just make a simpler version of existing ones.

OSI model - Wikiwand

The Open Systems Interconnection (OSI) model is a reference model from the International Organization for Standardization (ISO) that "provides a common basis fo...
www.wikiwand.com

LAPB - Wikiwand

Link Access Procedure, Balanced (LAPB) implements the data link layer as defined in the X.25 protocol suite. LAPB is a bit-oriented protocol derived from HDLC t...
www.wikiwand.com
 
Last edited:
Upvote 0 Downvote
All of which is fairly irrelevant for his very low requirements, a couple of metres at low speed is no big deal.
 
Upvote 0 Downvote
For The Popcorn said:
Exactly. Short cables, low baud rate and data rate, a handful of nodes for a non-critical monitoring system.
Click to expand...
I'm all for your technique - always let the host request data, and the slaves never initiate contact on their own at all - no collision problems then

In my case I did it wirelessly though, using HC-12 serial modules (so gives a really good range, and a simple RS232 type interface), and individually addressed slave modules.
 
Upvote 0 Downvote
Status
Not open for further replies.

Similar threads

G
Will this circuit work?
2 3
Replies
44
Views
9K
audioguru
How does this generator work ?
2 3
Replies
42
Views
5K
Externet
M
  • Question
Understanding a simple electronic device
Replies
2
Views
336
camerart
J
  • Question
How does this fan control circuit from a PTC Ceramic heater work?
Replies
4
Views
579
JettTDi
J
  • Question
The very simple circuit that the boost converter voltage from 1.5 to 12 does not work in the Proteus software...why????
Replies
12
Views
4K
electronium
Menu
Log in
Register
Cookies are required to use this site. You must accept them to continue using the site. Learn more…