SAMA5D4 Platform » VAS Product Release 2.0

Discussed Today

1. What is the turn-around time for acquisition 22Ksps (acq. 120ms- transfer 6ms-1sec) - LAN / Switch

2. Acq. duration - what is the max. memory size ( 100MB ) / Ping-Pong (linker, attribute) or circular buffer (head and tail)

3. Sync. rpm - configuration through USB or GUI ? (polar plot, phase analysis) GPIO Triggerring of DMA (Dynamic in GUI), add in first packet

4. Sync. in / out
   5.Timed Acquisition

5. Persistancy ? => NVM storage

6. RTS/CTS - Backpressure (scanning ) application controlling the data transfer

7. Assembly for 10 units - projection for next 3 months (Vinay will share exact ...)

8. AI PCB of Gateway - PLCIO => (Tracker not)

9. One SAM and two boards daisy chain (DMA config) or two SAM boards or one board with two SPI => Block diagram

10. Plan for SAM/replacement (anticipated requirement is 20-30, adani 6, BSH, Motherson, Plantiqx)

11. Internal processing - RMS/FFT

Follow-up : 18/03/2026

@Mohan Kashyap :

As discussed, please proceed with 3386, 3391, 3381

Discussion with Jiban

1. peak and peak-peak
   user selectable Calculation window, display like RMS
2. use channel name in all legends
3. add marker points, save in the same datastes under [Marker], reload for later analysis. add Marker view tab
4. temperature
   discuss with Mohan and decide protocol. this will not be interleaved with vibration data streaming
   do the protocol processing
   for GUI rendering, do some study. preferred to display along with vibration plots
   temp. will stored separately of along with vib. raw data and temp channel
5. Alert
   a. Set thresholds
   b. storage of threasholds in a table as like raw data
   c. thresholds will be displayed along with incoming data
   d. threasholds will be separate for each plot
   e. provide a Alert view tab

BSH Plan added
CRS prepared - review requested

Project review and internal demo (Mohan, Jiban, Venumadhav, Thomas)

Crashed once -identify the reason and resolve

Acq. Count - add label, infinite acq => 0

Acq. Duration - to be in ms, update in GUI

Acq. Duration - to be in second

Trigger - rising edge to start acq. and falling edge to stop acq. 

Pulse count - to be implemented

Acq. Count no to be displayed in the status bar

UDP connection live checking to be implemented

performance check with LAN - to do with two devices

S time missing with long trigger - FFT to data ploting

A time - arrival time definition

Configuration is onetime until a new configuration is sent

Pulse trigger - does not require acq. count

Define the LED status (4 LEDs) in a table

Power on or / bootup on all LEDs
power status - implemented
UDP live
data posting ok/failed
acq. failed
trigger status
Connection live to be tested.

Connection should restore after a reconnection

USB Connection should be asynchronous, does not require a command from VAS software - discus with Greeshma

Acq. interval and duration - not functioning as per the value and unit

Peakdetection

Threshold - add delete option

colour option for different channel

Threshold - shouldnot be tabbed => Channel no. to be  in the table

1. Face Plate Design.
2. Panel Assembly.
3. mDAQ3(V1.1) PCB Testing.

1. Create new Threshold setting UI
2. Modify new Device View UI
3. Save Temperature data in file
4. Test and correct app's connection indicator/status