Logical Node For Disconnector
Logical Node For Disconnector 3
Hi Klau,I think we are not on the same page. Let me clarify that he issue happens on transition(roaming) from parent Velop node to child Velop node, and testing laptop client is always connected by wireless, the wired backhaul only for two Velop nodes, so diagram is:Internet Route GW (wired connect to) Velop Parent Node (wired connect to) Velop Child Node, and the client laptop is wirelessly connected to parent node at first (No wired connection between client and Velop Node), when the client move close to child node, the wireless connection will be interrupted. It鈥檚 very odd that this issue is not happen on transition from Child to Parent Node.Please note that this issue is not happens on all client devices, but it happens on Windows 10 OS (With latest update) on 100% percentage from my testing, no matter what kind of WIFI adapter installed.
This tissue has following: blueCreated: 14 May 2012Links:Page: 28Clause: 7Paragraph: first dot point re ICD fileCategory: No impact on this partIssue: the reference to name can be confused with.name of Logical Nodes and the text describing substation TEMPLATE can be clarifiedProposal: Modified clause as follows:'Data exchange from the IED configurator to the system configurator (corresponding to items 170H b) and 171H c) of 172H 5.1). This file describes the functional and engineering capabilities of an IED type. It shall contain exactly one IED section for the IED type whose capabilities are described. The ‘name’ attribute of the “IED” element in the IED section shall be TEMPLATE. The file shall contain the needed data type templates inclusive of the logical node type definitions. The file may contain a substation section as a template, where the substation name shall be TEMPLATE, which defines the binding of logical node instances to primary equipment indicates a predefined functionality.
Logical Node For Disconnector And Spring
Any substation, in which this IED shall be used, must match an appropriate substation topology part (example: a CSWI LN bound to an equipment of type CBR is only allowed to control a circuit breaker; a CILO bound to a line disconnector implements the interlocking logic for a line disconnector). There might be an optional Communication section defining possible default addresses of the IED.'
DiscussionCreatedStatusBallot untilEditor09 Jul 12blueNot accepted. At this section of part 6 no SCL syntax elements have been introduced, and therefore neither an 'IED' element nor its 'name' attribute are known. However, the basic concept to have an IED description with name TEMPLATE indicating that this description is not related to a physical IED instance should be clear.30 May 12red2012-06-30.