Skip to main content
Associate III
June 20, 2024
Question

STEVAL-STWINBX1 datalogger board - add digital input for logging to SD card (to sync multiple DAQs)

  • June 20, 2024
  • 1 reply
  • 2986 views

I am using the STEVAL-STWINBX1 development board and have downloaded the FP-SNS-DATALOG2 software to the board.

Is it possible to add another channel, in this case a digital input that will be logged to the SD card ?

I need to synchronize the data logs from different DAQ systems including the STEVAL-STWINBX1

I was thinking if the STEVAL-STWINBX1 could log a GPS PPS (Pulse Per Second) digital signal, then I could manually (offline) sync its log with the logs from the other DAQ systems.

Or is there some other technique I can use to synchronize all these logs from different DAQ systems (e.g. IRIG, NTP, EtherCAT, PTP).

 

 

 

 

1 reply

SimonePradolini
Technical Moderator
June 26, 2024

Hello @johngj 

Natively DATALOG2 firmware has not this feature.

But you can modify the firmware and exploit the pin exposed by the CN1 connector on the STEVAL-STWINBX1. Here you can find the schematic for reference.

I suggest you to start modifying the code from the "mx" folder, where you can also find the .ioc project for CubeMX. There, you are free to change the GPIO setup.

 

Best regards

Simone

In order to give better visibility on the answered topics, please click on 'Accept as Solution' on the reply which solved your issue or answered your question.
johngjAuthor
Associate III
June 28, 2024

Thanks Simone, setting a pin to be a digital input is the easy part !

How would I go about logging that digital input to the SD card in stand alone mode ?

 

SimonePradolini
Technical Moderator
July 1, 2024

Hello @johngj 

Extending the log with external data is not automatically managed by FP-SNS-DATALOG2. I can suggest you a strategy to let you implement it.

FP-SNS-DATALOG2 provides firmware components called Tag Manager and Tags_Info_PnPL + App_model (see tags_info section). In this example, they are used to provide software tags, allowing labelling datasets. Those tags are then saved into the "acquisition_info.json" file in the acquisition folder.

I suggest you to implement the same schema: exploit the "TM...HSTag.." APIs from TagManager and extends Tags_Info_PnPL and App_model (tags_info section).

 

Feel free to come back for any further assistance.

Best regards

Simone

In order to give better visibility on the answered topics, please click on 'Accept as Solution' on the reply which solved your issue or answered your question.