I'm also curious to understand why the pulse duration is much longer than 320-350 ns that you originally mentioned.
Since the pulses have undershoots because of the AC coupling and the baseline is moving quite significantly, I'd suggest trying the automatic baseline mode to improve the resolution. In automatic mode, the baseline level is defined as the minimum value just before the rising edge of the analyzed pulse.
I'd also suggest trying different values of the decimation factor. Maybe setting it to 8 or 16 could improve the resolution.
It's by design. The application only does the data acquisition. It doesn't have any data analysis functionality.There is also no energy calibration field nor temperature adjustment...
The data analysis should be done by specialized tools like InterSpec or analysis scripts written in Julia, Matlab, Python, etc.
The histogram in the FPGA configuration has a fixed number of 16384 bins. The re-binning to 1024 bins is done by the javascript code of the web interface.Bins are limited to either 1024 or 16656 samples. -- more typical is 2048 and 4096bins
There is nothing typical about 2048 and 4096 bins. Nowadays, many commercially available multi-channel analyzers have 8k or 16k bins:
https://www.amptek.com/products/multich ... l-analyzer
https://www.ortec-online.com/products/e ... lyzers-mca
http://www.caen-group.com/csite/CaenFly ... parent=228