Skip to content
English
Submit Support Ticket Go to Customer Portal Sign in
  • There are no suggestions because the search field is empty.

Common controller errors and mitigation

List of common issues when using a Q.station or Q.monixx controller and how to resolve them

Errors List

Network scan cannot find the controller 

If you cannot find your controller with a network scan, we recommend starting with the following troubleshooting steps:

  1. Is the controller ON? (just checking 😜)
  2. Is the controller connected correctly to the PC via Ethernet? An Ethernet crossover cable is not needed. Replace the cable when in doubt.
  3. Is the green LED ON (not blinking)? If the LEDs are blinking: what sequence? Check the Q.series XL Manual for more details about the LED error codes.
  4. Make sure that the PC's LAN adapter has IPv6 enabled.
  5. Open GI.monitor from the GI.service user interface in the system tray and click Search, check if the controller shows up in the IPv6 Multicast tab. 
  6. What is the IP setting of your LAN adapter? If the connection to the controller is 1:1, the PC needs a static IP address (the factory default IP address of the controller is 192.168.1.18).
  7. Is there any firewall installed and running on the PC? If yes, deactivate it. Also, deactivate any antivirus software that may interfere. See also ports and libraries required for running GI.bench.
  8. Is it possible to ping the controller's IP address?
  9. Contact Gantner Instruments support with the following information:
    • Type of controller
    • Controller firmware version
    • Results from the above-mentioned troubleshooting steps

Base communication time error

Base communication time error

The error that the base communication time needs to be lower than 90% means that the amount of  one or more of the following needs to be modified:

  1. lower the amount of data on the UART (fewer modules or variables)
  2. lower the sample rate of the variables on the UART
  3. Increase the baud rate of UART, if possible

Q.monixx UART baud rate error with value

Issue: When adding an additional Q.bloxx module to the Q.monixx, you receive an "Error with value - no possible settings available" message.

Cause: This error is caused by an incorrect baud rate setting for the UART. The baud rate of 115200 bps (115k2) is not supported by the Q.bloxx modules.

Solution: Change the UART baud rate to 230400 bps (230k4).

Modbus TCPIP needs word aligned data

When the Modbus TCPIP protocol is activated on the dataport, the GI.bench Design Rule Check will show warnings about data formats needing to be word aligned.

This error message refers to a variable using a data format which is not in multiples of 16 bit (1 Register). In this case a Boolean (1 Bit). Those data formats cannot be transferred via modbus.

Boolean, Set8, SINT8, USINT8

Variable Error/Device EUART0 Instable Error

This error message cause be caused by various issues, please check the following:

  1. Bus Termination
    The last physical module of a UART needs to have the bus termination activated.
    To activate it, the last two DIP switches inside the module need to be in the down position (Q.series X) or the last two DIP switches on the socket (Q.series classic) need to be in the ON position.
  2. Module address
    All modules in a UART should have unique address. Ideally the first module starts at address 1 and module address should increment by 1 so there are no gaps.
  3. Module configuration
    Check the cockpit in GI.bench for errors or in test.commander go to File > Read Online Slaves info from Controller. Try writing a configuration. If ICP100 is available try directly sending a module configuration with that software.
  4. Module firmware
    Check that none of the modules show a firmware version that says "valid" and that all modules have the latest version installed.