Skip to content
English - United States
Submit a Ticket Tickets
Submit a Ticket
  • There are no suggestions because the search field is empty.

Adding a New Intersection Ready to Migrate to Sepac 5.x

The new pre-5.x intersection will have the version pre-set to allow migrating or converting to 5.x

A new intersection created from scratch in TACTICS does not have a Sepac version and this is the default behavior. However, sometimes you may want to have an intersection that has a pre-5.x version that can be updated to 5.x NTCIP or ECOM, but you don't have a controller with the older Sepac version. The steps below will help you.

  1. Find a copy of the older 3.58 intersection file (e.g. "Main & First St.int").

  2. In TACTICS, add a new intersection and select Protocol ECOM. Set other settings as necessary and save:

    add_new_int1

  3. Open the new intersection's Database Menu, go to All Data, go to File | Import, select the 3.58 intersection file from step 1: 

    add_new_int2

    Ignore SQL warnings related to deadlock. Answer "No" to question about defaulting the ring sequence; wait until the import is finished and saved. 

  4. The new intersection should have the 3.58 version pre-populated once finished.


    add_new_int3
  5. The new intersection should be able to either convert to ECOM 5.x or migrated to NTCIP 5.x via the Migrate option:

          add_new_int4

Note: This is possible without a controller running an older Sepac version.