RRB JE CBT 2 - Electronics common mistakes
RRB JE CBT 2 - Electronics · Understand the traps and how to avoid them.
Treating the transistor as a current-controlled device when computing bias, then applying β-based formulas to a circuit whose operating point is actually set by the base-emitter loop voltage; the candidate writes IC = βIB and stops, without checking whether the assumed active region is consistent with the resulting VCE.
Coaching material often presents IC = βIB as the definition of transistor action, so candidates memorise it as a universal law rather than a consequence of the forward-biased base-emitter junction. They also skip the region check because it feels like extra work, and they have often only practised circuits where the answer happens to be in the active region.
What to do instead
Adopt a fixed three-step routine for every bias problem: (1) assume active region, write the base loop KCL/KVL and solve for IB using VBE = 0.7 V; (2) compute IC = βIB and then VCE = VCC − IC(RC + RE); (3) test the assumption - if VCE < 0.2 V the device is saturated, so re-solve with VCE = 0.2 V and IC set by the collector loop alone. Practise at least five circuits where the first assumption fails, so the region check becomes automatic rather than optional.
Reading a truth table or Karnaugh map and writing the minimised expression with the wrong adjacency grouping - for example grouping two 1s that touch only at a corner of the K-map, or forgetting that the map wraps around at the edges, producing a simplified expression that is not logically equivalent to the original.
Candidates learn the K-map as a picture-matching exercise rather than as a Gray-code adjacency tool, so they group visually close cells instead of cells differing in exactly one variable. The wrap-around adjacency (left column with right column, top row with bottom row) is the part most often omitted from short revision notes.
What to do instead
Before grouping, label every row and column with its Gray-code value and verify that any two cells you group differ in exactly one bit. After deriving the expression, verify equivalence by substituting two or three input combinations back into both the original minterm list and the simplified expression. Also re-derive the same function algebraically with Boolean identities as a cross-check; a mismatch immediately exposes an illegal group.
Computing modulation index, bandwidth or power for AM and FM by mixing up the formulas - applying the FM Carson's rule bandwidth to an AM signal, or using the total AM power formula with the wrong sideband count - and then carrying the wrong number through the remaining parts of a multi-part question.
AM and FM are taught together in a single chapter, and the formulas look superficially similar (both involve a modulation index and a bandwidth). Candidates memorise a formula sheet without attaching each formula to the physical quantity it describes, so retrieval under time pressure picks the wrong row.
What to do instead
Build a two-column comparison table from memory each week: for AM list m = Vm/Vc, total power PT = Pc(1 + m²/2), bandwidth = 2fm; for FM list β = Δf/fm, Carson's bandwidth ≈ 2(Δf + fm), and note that FM carrier power is constant. Annotate each formula with the physical meaning of every symbol. When a question has multiple parts, write the given quantities and the target quantity first, then select the formula - never select the formula first.
Confusing the roles of the program counter, stack pointer, accumulator and general-purpose registers when tracing a short assembly routine, so the candidate predicts the wrong value in a register after a CALL/RET or PUSH/POP sequence.
Candidates memorise register names and bit widths but never trace an actual instruction sequence by hand. The stack's LIFO behaviour and the fact that CALL pushes the return address are stated in textbooks but rarely practised, so the candidate guesses rather than simulates.
What to do instead
Trace at least ten short routines on paper with a table of columns for PC, SP, A and the flagged registers, writing the new value in each column after every instruction. Include one routine with nested CALLs and one with PUSH/POP pairs around a subroutine. Once the hand trace is reliable, verify the same routines against a simulator or emulator so the mental model is corrected by observed behaviour.
Applying the wrong network theorem precondition - using superposition on a circuit containing a diode or other non-linear element, or applying Thevenin's theorem across a terminals pair while leaving a dependent source inside the 'dead' network in a way that removes its controlling variable.
Theorems are learned as procedures ('short voltage sources, open current sources') without the linearity condition that justifies them. Dependent sources are the hardest case because the standard 'kill the sources' step is not valid for them, and this exception is usually compressed into a single line in revision notes.
What to do instead
Before starting any theorem-based solution, write one line stating the precondition you are relying on: 'superposition requires linearity - no diodes, no dependent sources treated as independent'. For Thevenin/Norton with dependent sources, keep the dependent source alive and find Rth by applying a test source (1 V or 1 A) at the terminals and computing V/I, rather than by killing sources. Solve two circuits both ways - test-source method and source-killing method - to see exactly where the naive method breaks.
Reporting a measurement without accounting for loading and instrument error - quoting the meter reading as the true circuit value while a low-impedance voltmeter or a high-resistance ammeter has measurably perturbed the very quantity being measured.
Candidates treat instruments as ideal observers because introductory problems assume ideal meters. The habit persists into numerical questions where the meter resistance is given but ignored, and into error-analysis questions where the candidate reports the reading minus true value without computing relative or percentage error.
What to do instead
For every measurement question, first note the meter's internal resistance and the circuit impedance, then decide whether loading is negligible (voltmeter resistance at least 100 times the circuit resistance, ammeter resistance at most one-hundredth). If not negligible, recompute the reading with the meter in place. Always present error explicitly as absolute error, relative error and percentage error, and state the limiting error when component tolerances are given.
Mixing up the operating principle and typical application of power semiconductor devices - swapping thyristor and TRIAC behaviour, or describing a DIAC as a controlled rectifier - and then selecting the wrong device for a phase-control or chopper application.
The device family (SCR, TRIAC, DIAC, GTO, IGBT, MOSFET) is introduced rapidly and the symbols look similar. Candidates learn the symbol before the conduction mechanism, so they cannot distinguish unidirectional latching behaviour from bidirectional triggering, and application questions expose the gap.
What to do instead
Make a device card for each of SCR, TRIAC, DIAC, GTO, BJT, MOSFET and IGBT listing: number of junctions, trigger condition, turn-off method (natural commutation, gate turn-off, or none), direction of conduction, and two named applications. For each card, state in one sentence why the device suits those applications. Test yourself by naming the device from the application alone, not the other way round.
Answering number-system and data-representation questions by converting through decimal every time, which is slow and produces sign and overflow errors in two's-complement arithmetic - for example reporting a negative result as a large positive value because the sign bit was not interpreted.
Decimal is the comfortable intermediate, so candidates never build fluency in direct binary/hex/octal grouping. Two's-complement overflow and sign extension are procedural details that are memorised as rules without being practised on cases that actually overflow.
What to do instead
Learn the 4-bit grouping shortcut: hex to binary is a direct 4-bit expansion, octal a direct 3-bit expansion, with no decimal step. For two's complement, always state the bit width first, perform addition in that width, and check overflow by comparing the carry into and out of the sign bit - if they differ, overflow has occurred. Drill ten signed additions per session, deliberately including cases that overflow, and interpret every result by its sign bit before writing the decimal value.
Losing marks on General Intelligence and Reasoning by attempting every question in strict serial order, so a long multi-condition seating or ranking puzzle consumes the time budget and forces rushed guesses on the short coding-decoding and series items that were easily solvable.
Candidates treat the reasoning section as a test of persistence rather than of selection, and they have usually practised individual question types in isolation rather than under a whole-section time constraint. Multi-condition puzzles feel productive because progress is visible, which makes the sunk-cost trap easy to fall into.
What to do instead
Do two timed full-section mocks and record the time spent per question type. Adopt a two-pass strategy: first pass solves series, coding-decoding, analogies, blood relations and direction sense; second pass returns to puzzles, and any puzzle not broken open within about 90 seconds is abandoned. For puzzles, draw the constraint grid and fill certainties before attempting deductions from uncertain conditions.
In General Awareness and Current Affairs, relying on undated static facts and general reading, so the candidate cannot answer questions tied to a specific recent budget, appointment, award or scientific mission, and also misattributes static facts such as constitutional articles or scientific units.
Preparation for this section is often passive - reading news without recording it - and static awareness is revised from undated compilations. Without a dated log, recent items blur together and static facts are recalled with false confidence.
What to do instead
Maintain a dated one-line log: for each current item record the date, the organisation or person, and one distinguishing detail. Review it weekly with self-testing rather than rereading. For static awareness, group facts into small numbered sets (articles, units, discoveries, institutions) and test recall of the set, not the individual fact, so confusions between neighbouring items surface early.