Agustinus

For some endeavors, the distance between two points, such as starting from zero experience and ending up with a completed working design running on hardware, is usually not a straight line. Everyone learns differently and at a different pace. Be prepared for the unexpected and you'll be fine. Mere mortals like me have learned that starting off simple and adding complexity as I gain experience generally works out to be the quicker route to success. But that's what seems to work best for me, most of the time....

[edit] It's always tempting to ask yourself "can X platform be used to accomplish Y goals?" instead of "is there sufficient evidence that I can use X platform to complete Y goals within my budget and time constraints?" What you don't know can hurt you. When evaluating suitability for a particular platform it helps to see what the platform vendor demos for their products offer, and what version of the tools were used to implement them. I tend to be cautious because I know that facts out of context, and advertising promises rarely hold up when I'm doing actual real-world project development. Bord capabilities and board functionality are not the same. There are a lot of "ifs" and "exceptions" lurking in the details that the advertising doesn't cover. Again, I'm me doing "me projects". Your mileage, or download speed, or whatever may vary...

Hi @Agustinus,
@asmi and @zygot are correct in that we will need some more details about the types of sensors that you have before any effective answer can be provided. Are these sensors all communicating simultaneously at 96 kHz? Individually addressed like different nodes on an I2C daisy chain that collect data at 96 kHz? Something else entirely?
It would also be very helpful to know the number of individual data inputs and outputs each sensors needs as I would hazard a guess that each sensor is not a one-wire device so you would need much more than 128 spare I/O pins which most of the Digilent and MCC boards (including the Arty A7 100T) do not have available.
Thanks,
JColvin
 
@zzzhhh I am not sure why you brought up the book reference on creating a digital oscilloscope or the Getting Started with Microblaze Servers tutorial, as neither of those things seem to be relevant to the topic at hand of integrating over 100 sensors into a system. I would ask in the interest of clarity and helping the original poster to only address the question at hand. I spoke with @artvvb a bit earlier today and learned that they are still looking into your question on the topic here: https://forum.digilent.com/topic/25583-to-digilent-employees-is-there-any-chance-to-update-the-tutorial-arty-getting-started-with-microblaze-servers/; currently they believe the issue might be due to same changes in DDR clocking, but they are still debugging the issue alongside the myriad of other tasks that they have on their plate as a Digilent employee, though they hope to find a solution in a reasonable time frame.
 

Well tell us then, how do you know that Arty-100 is going to be "more than enough" without knowing answers to the questions I listed. And, while you're at it, maybe you can enlighten us how that stupid tutorial which you failed to make work is relevant to this topic.

Could you be more specific? What kind(s) of sensors are you talking about? It's hard to provide a good answer without enough information.
In general Digilent FPGA boards are designed to support their PMOD ecosystem, and are IO pin deficient. They do sell a couple of boards with 1 FMC connector but finding an off-the-shelf mezzanine card that supports 128 undefined sensors is going to be a problem. Even if you can list all of the exact sensors by part number an answer is not likely to be a simple one.
Usually, for low Fs, multiple channel ADC applications, analog inputs to the sampler(s) are time mutiplexed. Are you prepared to do some digital and analog design and prototype construction?

Except Digilent staffs, some people do not reply in order to answer a question. They only come here to show off. Even after finishing the reply, they still do not know what the question is. Their reply can do nothing but confuse the asker by complicating simple things, with a mild threat. I hope the asker can be smart enough to identify such a people.

Before you select a board, you've got to figure out four things:
1. Data source - How are you going to do the capture? Is it going to be a crap ton of ADCs, or some fast multichannel ADCs, or maybe something else?
2. Data input - Whatever you settle on in (1), how this data is going to be fed into FPGA? SPI, I2S, or some custom bus? This will help you determine which and how many pins will you require from FPGA, which can disqualify a lot of FPGA boards because they won't have suitable connectivity.
3. Data processing - Once the question if bringing data into FPGA is resolved, what exactly are you going to do with that data inside FPGA? That has a major implications on a FPGA family and density that you require.
4. Data output - And finally, once you've done all the processing inside FPGA, what are going to be your outputs? This again can disqualify some boards because they lack the output method of your choice.
 
Or, and number 0 - don't ever listen to anyone saying "board X is going to be more than enough" without knowing answers to above four questions, because it will very likely end up with wasted money and frustration.

I think a low-end Arty A7-100T is more than enough. A book "Architecting High-Performance Embedded Systems: Design and build high-performance real-time digital systems based on FPGAs and custom circuits" written by Jim Ledin uses this board to implement a digital oscilloscope sampled at 100 MHz with 14 bits of resolution. Digilent is offering 15% discount right now.
Note however that the step-by-step tutorial of baseline Vivado project (the same as this Digilent tutorial) in this book does not work under current version of Xilinx Vivado/Vitis software (2022.2.2). I still don't know how to use the Ethernet of this board, and you can get no technical support in this regard from Digilent or Xilinx.
If you somehow get through this tutorial, I would greatly appreciate it if you can share with us how you make it.