In NCAPI v1, input data for inferences had to be 16 bit floating point data type.
In NCAPI v2, input data for inferences can be 16 bit or 32 bit floating point data type. The default data type is FP32. The data type is set for each Fifo using Fifo.set_option() with FifoDataType.
Note: If the input FifoDataType is configured to FP32, the API will convert the data to the FP16 data type automatically when performing inferences. If the output FifoDataType is configured to 32FP, the API will convert the output back to the FP32 data type._
OK , it tells me NCAPI V2 would convert FP32 to FP16 to use , it means NCAPI v2 could deal with 32 bit data,the same as a computer,
it means there shouldn't have any overflow in the stick
I wonder whether mvNCCheck tool can deal with 32 bit, or maybe mvNCCheck only support 16 bit which leads an overflow