Have a mockup of a full machine sensor CAN-FD network in the home shop for testing. A bit of a mess but it all works.
Four boards, 3 3dof acceleration sensor data collectors and 1 network host.
The current job is to make these processes (data collection and data storage) as reliable as possible.
Zoom mode on the bottom half of the screen.
Blue for CAN packets (4 types) on the bus, Yellow for serial data packets (4 types) to the Ethernet. Serial bandwidth is a bottleneck but easily manageable with only a few sensors..
We all love CAN because it's easy to put the data in a buffer and then receive that buffer on the other-side without a lot of software a manage the physical bus.
The UART stream is trickier without hardware flow control but here we let the host CAN receiver be our flow-control with it's FIFO buffers that work with little cpu intervention. For the UART we only need a simple bounce-buffer and a DMA/wait trigger for the next serial packet to the TCP server.
Incoming data logging from the database Java client reading Ethernet data from the CAN host and sending that to another database server. If you run a Linux firewall (lots of spamming connections) and a database on the same server you need to make sure you don't DoS your own network with too many continuous connections that can happen of you create and drop a DB connection with every packet.
https://cs7networks.co.uk/2016/11/20/ipv6-conntrack-and-munin/
https://support.huaweicloud.com/intl/en-us/trouble-ecs/ecs_trouble_0324.html
32 message FIFOs
Each FIFO can have up to 32 messages for a total of 512 messages
FIFO can be a transmit message FIFO or a receive message FIFO
https://ww1.microchip.com/downloads...twork_with_Flexible_Data_rate_DS60001549A.pdf
That's plenty of headroom for 1/2 dozen sensors running asynchronously.
Four boards, 3 3dof acceleration sensor data collectors and 1 network host.
The current job is to make these processes (data collection and data storage) as reliable as possible.
Blue for CAN packets (4 types) on the bus, Yellow for serial data packets (4 types) to the Ethernet. Serial bandwidth is a bottleneck but easily manageable with only a few sensors..
We all love CAN because it's easy to put the data in a buffer and then receive that buffer on the other-side without a lot of software a manage the physical bus.
The UART stream is trickier without hardware flow control but here we let the host CAN receiver be our flow-control with it's FIFO buffers that work with little cpu intervention. For the UART we only need a simple bounce-buffer and a DMA/wait trigger for the next serial packet to the TCP server.
https://cs7networks.co.uk/2016/11/20/ipv6-conntrack-and-munin/
https://support.huaweicloud.com/intl/en-us/trouble-ecs/ecs_trouble_0324.html
32 message FIFOs
Each FIFO can have up to 32 messages for a total of 512 messages
FIFO can be a transmit message FIFO or a receive message FIFO
https://ww1.microchip.com/downloads...twork_with_Flexible_Data_rate_DS60001549A.pdf
That's plenty of headroom for 1/2 dozen sensors running asynchronously.