Placed Reuse Blocks do not retain their original internal component footprint positioning & the block itself cannot be snapped to grid.

I'm using Reuse Blocks (with no Net Ports) to represent entire pcb boards. Why? I'm creating a panel with more than one board design, and if I duplicate schematic content for multiple boards, all component names and trace labels need to be unique on the panel's pcb layout canvas. By using a Reuse Block, this duplication issue is avoided, and it should allow me to edit the block pcb layout in the future without disrupting the existing panel's block alignments with an 'Update Place and Route with Reuse Template' operation.

The PROCESS: I create a 'Panel' project, then place 3 or 4 blocks on a schematic. From the pcb canvas I next attempt to align these 'pcb board' blocks into a single row. This row is a collection of DIFFERENT blocks (some repeated, some unique), all of similiar height.  I next use "Tools/Panelize..." to copy this row multiple times to create a panel. I have learned that the block (to be successfully placed) must not contain any external dimensional lines, or other objects beyond its board outline boundary. The placement algorithm uses the maximum vertical and horizontal dimensions of the block as a 'bounding box' when placing, keeping other placed components clear.

The PROBLEM I am encountering: Snapping of the block to the grid does not work properly.

The best I can do is a 'chatGPT' suggested solution:  FIRST, turn Grid Snap OFF, next add a TINY VIA to the upper-left corner of the block's board outline (it needs to be smaller than the width of the board outline line, otherwise 'bounding box' issues occur), next click on this via FIRST during initial block placement on the pcb, then WITH SHIFT KEY HELD DOWN  move the mouse from lower-right to upper-left to select all remaining items of the block to be placed, then ZOOM IN and position the via at its target coordinates using a SINGLE mouse click. You can then repeat these single clicks until you finally have the via as close as possible to its intended position. After positioning all blocks, using layer/filter settings to select only these tiny vias for deletion (prior to Tools/Panelize... step.) This process works, but it is painfully slow.

IN GENERAL, a placed block's component positions can CHANGE at placement !!! They can not be 'locked' at block design. Reuse Blocks would attain their full potential if 1) a placed block could be snapped to the grid, and 2) the components within the block do not have their positions altered at placement.

ARE THERE CURRENT SOLUTIONS TO THESE ISSUES ? 

ARE SOFTWARE UPDATES PLANNED TO ADDRESS THESE ISSUES ? 

Thanks for your help !

#PCB#
Circuit Design
BUG REPORT: Common words flagged by filter system

Previously I have had issues with the oshwlab's Image filtering system, it was related to Mini RC Tank project a few months back. But this is ridiculously absurd

 

CRA(K

While I was writing a description for a new project, I was greeted with this warning when I clicked Save to Draft

For context, here's what I wrote.

 

JOINT

Just below that word. There is "joint", which also has a bad meaning. Thankfully that is not filtered yet.

Nowadays, a lot of simple words are getting new bad meanings. If you keep adding these to the list, then it will be very hard to write descriptons and articles in oshwlab.

 

List:

This list doesn't contain words like B0MB or MISS1LES but only the common words. I will add them here as I find new censored words

  1. [FIXED as of SEP 2025] CRACK
  2. [FIXED as of SEP 2025] BLOOD - why? I found this out while making a BL00D oxygen sensor board
  3. TRASH [NOV 2025] - discovered this while publishing this card
#Others#
Others
Problem by simulating simple opamp amplifier

Hi all,

have some problems to get proper results of attached amplifier circuitry, checked with an simple substitute of an opamp (high gain voltage controlled voltage source) and even with a "real" opamp:

https://u.easyeda.com/join?type=project&key=06e75f0b553f376f86aa1ac5c746f1cb&inviter=5ea5d08ee80b493ea28ae803c3e75c2f

AC analysis might work more or less, but with uncorrect axis dimensions of magnitude & phase. Transient simulation gives always input voltage level on mostly nodes of the circuit. Checking with "real" opamp model (i.e. LM358) ... same situation. What I make wrong ?

BR Thomek  

#Simulation#
Circuit Design