block:block-embededfb-en
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
block:block-embededfb-en [2019/01/13 17:01] – [Simulating the sensors] rjversluis | block:block-embededfb-en [2024/01/25 14:45] (current) – rjversluis | ||
---|---|---|---|
Line 2: | Line 2: | ||
[[: | [[: | ||
[[: | [[: | ||
- | * [[: | + | * [[: |
+ | |||
+ | \\ | ||
+ | |< >| | ||
+ | | Not recommended for novice users, and [[: | ||
\\ | \\ | ||
Line 12: | Line 16: | ||
A block with embedded sensors saves space in the track plan, and can speed up creating a new track plan.\\ | A block with embedded sensors saves space in the track plan, and can speed up creating a new track plan.\\ | ||
After dropping this type of block the following actions will be automatically handled by the server: | After dropping this type of block the following actions will be automatically handled by the server: | ||
- | - Generate two new invisible sensor objects with IDs fitting to the block: //" | + | - Generate two new invisible sensor objects with IDs fitting to the block: //" |
- Generate the four route events for both sides of the block; **Enter** and **In**. | - Generate the four route events for both sides of the block; **Enter** and **In**. | ||
Setting the sensor addresses must be done manually.\\ | Setting the sensor addresses must be done manually.\\ | ||
+ | |||
+ | See also: **[[# | ||
+ | |||
+ | For a convertion of a **Block with separate sensors** into a **Block with embedded sensors** \\ | ||
+ | see: __**[[: | ||
\\ | \\ | ||
Line 23: | Line 32: | ||
\\ | \\ | ||
=====Simulating the sensors===== | =====Simulating the sensors===== | ||
- | The sensors can be simulated with the **Left Mouse** button and both the **Shift** and **Alt** key pressed.\\ | + | The sensors can be simulated |
- | The sensor which will be activated depends of the mouse position in the block symbol.\\ | + | The sensor which will be activated depends of the mouse position in the respective quarter of the Block symbol.\\ |
+ | |||
+ | ===== Changing IDs ===== | ||
+ | |< >| | ||
+ | |:!: **Whether | ||
+ | ==== Created directly as a "Block with embedded sensors" | ||
+ | >These sensors are marked in the __**[[: | ||
+ | |||
+ | As described above, get embedded sensors which are did direct created the ID of the block plus the identifier of the block side. This relation between the IDs is a **necessary requirement** for the function. Therefore, changes to the IDs of the block **and** | ||
+ | // | ||
+ | //Before:// Block = " | ||
+ | // | ||
+ | |||
+ | These direct embedded sensors can __not__ | ||
+ | |||
+ | ==== Converted "Block with separate sensors" | ||
+ | >These sensors are marked in the __**[[: | ||
+ | |||
+ | First was a block with separate sensors created and later converted | ||
+ | |< >| | ||
+ | | :!: **The IDs of converted sensors must NOT be changed, \\ because the relation " | ||
+ | The ID of the converted block does not have this restriction and __may be changed at will__. \\ | ||
+ | |||
+ | If wished, these converted sensors can with the ' | ||
+ | |||
+ |
block/block-embededfb-en.1547395312.txt.gz · Last modified: 2019/01/13 17:01 by rjversluis