OP6228 red LED always ON troubleshooting

Question:

The red LED of the OP6228 card is always ON. What can I do?

Answer:

The OP6228 red LED has a specific behavior and does not react exactly like other TestDrive OP6000 cards. Here is a description of the behavior and a troubleshooting procedure to ensure the OP6228 works fine.

Behavior:

The OP6228 red LED is ON at all times except once the model is loaded and when the model is executing. This behavior is different from other TestDrive cards where the red LED is ON only when a fault occurs. This means that to confirm there is indeed a problem on the OP6228, the model must be loaded (or executing) and the red LED must still be ON at that time.

Troubleshooting:

To perform troubleshooting steps, it is recommended to have only the Base Module (BM) and the OP6228 inserted in the TestDrive chassis. Note that the OP6228 is compatible only in the last slot of the TestDrive chassis (that is the righternmost slot).

Outside of standard faults similar to other TestDrive cards, specific conditions can lead to a red LED being ON at load/execution on the OP6228. The first thing to know is that the OP6228 is a reprogrammable FPGA card so it can run various applications based on the bitstream used. The two main applications delivered by Opal-RT are the "Current Sensor" and the "Resolver". It is important to have compatibility between the following items:

Bitstream application must match real-time model application: If the bitstream is a "current sensor" bitstream for example, the real-time Simulink model must also be a "current sensor" TestDrive model. Else, the red LED will always be ON. To verify this point, the safest method is to edit the real-time Simulink model in Matlab. Browse to the subsystem td/SM_Controller/Subsystem Modules. Scroll down. The last subsystem should either be named "Resolver Module" or "Current Sensor Module"

Hardware configuration must match the bitstream application: Depending on the application used, the right I/O mezzanines must be used in the right I/O slots of the OP6228. If the bitstream is a "current sensor" bitstream, both section A and B on the OP6228 card must be OP5340 (16ch A/D). Below is the expected hardware configuration for both applications.

Current sensor

Section A : A/D (Analog Input, 16ch), OP5340

Section B: A/D (Analog Input, 16ch), OP5340

Resolver

Section A : A/D (Analog Input, 16ch), OP5340

Section B: D/A (Analog Output, 16ch), OP5330

Any other configuration (either using other type of I/Os or if a section is empty) will result in the red fault LED being ON at all time.

An easy way to know your hardware configuration is to run the TestDrive model and look at the Current Sensor or the Resolver GUI panel. Indications on the top right of the interface will detail "Mezz A" and "Mezz B" as long as a "Hardware Status". Mezz A represents Section A while Mezz B represents Section B. The Hardware Status LED will be green only if the hardware configuration matches the bitstream configuration.

If you end up with a bitstream alone which you do not know if it's the current sensor or the resolver application, three options are available:

Forget about your bitstream and use the attached packs (models+bitstreams) which are the latest official current sensor and resolver packs
Run a current sensor model and a resolver model (with the right hardware configuration for both) with your lonely bitstream, one after the other. See which one returns an error at load/execution
Ask Opal-RT's Technical Support Department

You can get more details on both applications in the "TestDrive Modules User Guide" found on our website at http://www.opal-rt.com/products-manual-download

TD_Resolver_diff_24V_842_264_v2.zip - Resolver Pack
OP6000_24V_CS_12ch_842_264_v2.zip - Current Sensor Pack