Skip to content

Sega New Net City

The last candy cab in the City line (2005): an evolution of the Net City, designed JVS / network from the start, with a standard JVS panel and PSU and a chassis ready for 31 kHz (Naomi 2, Lindbergh-era).

Identification

Field Value
Manufacturer Sega
Year 2005
Type Candy cab (last of the City line)
Screen 29″ tri-sync CRT (15/24/31 kHz)
I/O JVS (standard JVS panel) + network wiring
PCB format JAMMA + JVS

Technical notes

  • The most modern City: built around the JVS standard (standard JVS panel and PSU), with factory LAN wiring like the Net City.
  • Tri-sync: accepts 15/24/31 kHz → classic PCBs and 31 kHz systems (Naomi / Naomi 2).
  • Flat multiscan monitor (Toshiba) 29″ 15/24/31 kHz, rotatable: Sega moved to the flat tube as curved tubes were being phased out.
  • Network: supports non-Sega PCBs and connects to the VF.NET network (Virtua Fighter 4).
  • Distinguished from the Net City by artwork details and full standardisation around JVS.
  • Power: Sega candy brick → candy cab PSU.

⚡ Connector & power

Aspect Value
PCB connector JAMMA + JVS (standard JVS panel + PSU)
Network factory LAN wiring (networked games)
Monitor sync tri-sync 15/24/31 kHz (29″ CRT)
Power 100 V AC (Japan), Sega candy brick
Consumption ≈ CRT candy cab (~140 W order of magnitude) — see the service manual

(Sources: Arcade Otaku.)

Common faults

Symptom Likely cause Lead
Unstable image (CRT) tri-sync chassis, recap Adjustments + recap (Nanao MS9)
Dead controls JVS I/O / harness JVS diagnosis
No power candy brick Check voltages at JVS/JAMMA

Repair

Identical to the other tri-sync candy cabs: recap + adjustments of the 29″ chassis (see Nanao MS9), Sega candy power.

Manuals (archived)

(Source: Arcade Otaku Wiki — scans by BlinG, archived locally for preservation.)

Photos / assets

(To add: New Net City, JVS panel, tri-sync chassis.)

Repair & maintenance

Modernise (video, PSU, JVS, upscaler, PC/FPGA) → Modernising a cabinet. CRT monitor (discharge HV!) → CRT safety + Nanao MS8 / MS9 chassis · Sega candy PSU → PSU repair · recap → Recap.

Sources & attribution

Review & corrections

How this space is used

Spotted a wrong value, an outdated procedure, a chip reference that does not match your board? Say so here, with what you observed (model, board revision, serial number, measurement). Every report is cross-checked against a source before anything changes — an unverifiable correction is published as “reported by …, not cross-checked” rather than silently applied.

Reading is open to everyone; posting requires signing in with Discord. Reports from the wiki's declared reviewers are handled first; anyone else's are read too, but go through a human before anything is changed.