I've supposed it should be configured as controller but when I do that VeriStand send me an error during the deploy (I've attached the error file), so I'm only able to set my LocalHost as Controller.
This is expected with the 9188 because it is an ethernet chassis and not a controller. Basically, it is not capable of running a supported operating system that has the VeriStand Run-Time installed on it. Therefore you cannot remotely execute the VeriStand engine on it. You will need to continue running VeriStand locally on your PC that has the 9188 connected to it.
but I encountered some issues acquiring a bad signal when TTL frequency exceeds 180 Hz: I noticed that the System Time is updating of 1ms every acquisition (and it should be right), instead the Absolute Time is updating of 4/6ms; have I miss something in the configuration of my DAQ?
Can you elaborate on this point? What do you mean by "issues acquiring a bad signal"? Are you getting an error that says the signal is bad in some way?
I would also investigate some other System Channels during your testing:
https://www.ni.com/docs/en-US/bundle/veristand/page/system-channels.html
- HP Loop Duration: Make sure that this is not approaching your loop rate. If it is, then you may need to run your system more slowly.
- HP Count, LP count: Make sure that these aren't increasing. If they are, it means that your system is having performance problems and is unable to keep up with the rates you have specified.
- DAQ Error: Check to see if you are getting any values reported here. This would help you diagnose any possible errors with the DAQ driver which is managing your DIO communication.
Further information about the engine architecture can be found here.
NI VeriStand Engine Architecture
https://www.ni.com/docs/en-US/bundle/veristand/page/vs-engine.html
This is often a good document to reference when looking to understand the working parts of the engine and when you're trying to debug a performance issue.
Tim A.
