Se rendre au contenu

7/5/2025

7 mai 2025 par
CTech Metrology, Luc Wens
​

Proxy error handling



Error generated at Proxy level:

  • is caught in main loop
  • sends string telegram with code TCPGRAM_CODE_ERROR to engine
  • engine receives proxy telegram, identifies proxy device and rethrows the error, which will send an error to UI (should be existing code, check it out), this will trigger the error state
  • UI receives error and goes to error state as well and shows the error
  • user can correct the error and reset by starting a new configuration

To test this we will update the proxy test device which runs on a simulation file so that at the end of the file it generates an error, halfway it generates a warning.

Our goal is to:

  • At proxy level
    • See that the warning and error are logged
  • At engine level
    • See that warning and error are caught by engine
    • The causing proxy is correctly identified, and do note here that a device can have multiple proxies running, with just the serial of the device being different
    • The error/warning is correctly handled in the main catch block
    • See that the warning and error are logged
  • At UI level
    • See that the warning are correctly handled
    • See that the error is correctly handled
    • See that the warning and error are logged

​

6/5/2025