How to tell encounter to create vias with minimum number of row as 2.

setNanoRouteMode -drouteUseViaOfCut 2
setNanoRouteMode -drouteUseMultiCutViaEffort high
setNanoRouteMode -droutePostRouteSwapVia true
setNanoRouteMode -drouteStartIteration 20
setNanoRouteMode -drouteEndIteration default
detailRoute

 Thanks for the reply Yemelya. Does this swap single cut via with multicut on all vias? How to specify to swap single cut vias with multicut vias between Metal top and Metal 5 only ?

 I think you're talking about two different things here. The original question is about sroute and via arrays in the pwr/gnd bus. Yemelya's reply is how to swap single-cut vias for double-cut vias in regular signal routing. Diablo, if you could post a picture of your situation, that would help.

Hi Kari, 

I have attached the picture  for single row via generated by encounter sroute. DRC run is showing error that the minimum number of row for this via is 2. The interesting thing is if i move the wire shown in the picture, the correct via with multiple row is generated. I wonder why it's not doing that when it ran sroute. 

Regards. 

 Hmm, that is interesting! If you pull back the horizontal wire (the via will go away), then pull it back over the vertical wire, is the correct via array generated? Also, if you delete the via using the Edit Power Via form, then re-add it using the same form, is the correct via created? If you get the correct via by all of these methods, then it sounds like a bug in Sroute and you should file a Service Request.

Kari ,

Yes, I get the correct via by all of these methods. I have already file a service request as well. Thanks. 

 Could you please let me know the number of the service request? I would like to follow it and see the solution.

Thanks!

- Kari

Kari, 

Regards, 

 Thanks!

Can you upload your tech LEF to the service request? The .tf file is not used in Encounter, but the non-sroute methods where you are getting the correct vias are getting the info from somewhere, and that should be the tech LEF. So we need to see the tech LEF and then figure out why SRoute is not following it. (I can't seem to post directly to the service request - I guess they work a bit differently than CCRs.)

We use the Open Access database instead of LEF flow. I reference the tech file in encounter using set rda_Input(ui_oa_reflib) "". The .tf file was generated by dumping the tech library from OA database. That's where the encounter is getting the via information from.