Getting Started with Rifidi Emulator — Installation & First Steps

Troubleshooting Common Issues in Rifidi Emulator

1. Verify Java and Environment

• Check Java version: Rifidi Emulator requires a compatible Java runtime (typically Java 8 or 11). Run:
  java -version

  Ensure the major version matches the emulator’s requirements.

• Match ⁄₆₄-bit: Use a Java build that matches your OS and any native libraries (32-bit vs 64-bit).
• Environment variables: Confirm JAVA_HOME and PATH point to the intended Java installation.

2. Confirm Rifidi Build and Plugins

• Correct release: Use a stable Rifidi release compatible with your use case; avoid mixing plugins from different versions.
• Eclipse/OSGi plugin errors: Look for unresolved bundles in the OSGi console or Eclipse Error Log. Reinstall or update problematic plugins.

3. Check Logs for Errors

• Locate logs: Check Rifidi’s log files (or console output) for stack traces and error messages.
• Interpret stack traces: Identify the root cause (missing class, configuration error, or runtime exception) and search relevant messages online or in project issue trackers.

4. Network and Port Problems

• Port conflicts: If the emulator exposes services (sockets/HTTP), ensure required ports aren’t used by other processes. Use netstat/ss to inspect listening ports and kill/conflict processes.
• Firewall and permissions: Allow the emulator through local firewalls and grant required network permissions.

5. Reader and Tag Simulation Issues

• Reader profiles: Confirm reader adapters and profiles are loaded and assigned correctly in Rifidi’s UI or config files.
• Tag format and memory map: Verify tag data conforms to the reader profile (EPC length, memory banks). Incorrect formats can cause tags not to appear.
• Antenna settings: Ensure antenna IDs and power settings match expected configuration; simulated antenna mismatch can prevent reads.

6. Configuration File Problems

• Syntax and schema: Validate XML/JSON configuration files for typos, missing fields, or invalid values.
• File locations: Ensure Rifidi is reading the correct config files (check launch parameters and working directory).
• Permissions: Confirm the emulator process can read config and resource files.

7. Performance and Resource Constraints

• CPU/memory: Large simulations may require more heap. Increase JVM heap via:
  -Xms512m -Xmx2g

• Thread limits: Watch for thread exhaustion; tune OS limits and JVM thread settings if necessary.

8. Compatibility with External Systems

• Middleware interfaces: If integrating with external middleware, verify protocol versions (LLRP, custom TCP) match and message formats are correct.
• Time synchronization: Ensure clocks are aligned if time-dependent behavior is expected.

9. GUI Problems

• Eclipse workspace corruption: If the Rifidi UI (Eclipse-based) crashes or behaves oddly, start with a fresh workspace or clear the workspace metadata.
• Missing UI elements: Check for error logs indicating failed bundles; reinstall or re-enable UI plugins.

10. Reproducing and Isolating Issues

• Minimal reproduction: Reduce simulation complexity to the smallest setup that reproduces the problem (one reader, one tag).
• Binary search: Re-enable components incrementally to isolate the failing module.

11. Useful Commands and Tools

• java -version, jcmd/jmap/jstack for JVM diagnostics
• netstat/ss/lsof for port and file handles
• tail/less on log files; grep for error keywords
• OSGi console (if available) to list bundles and their states