- Will there exist (and be handled) a situation where multiple devices try to communicate at the same time? Not an incoming/outgoing collision, but multiple objects trying to transmit at the same time? I'm not sure if this will be an issue in the GridLAB-D framework or not (may be an implementation issue).-Ftuffner 21:12, 27 May 2010 (UTC)
- Will any specified, underlying model be used for collision and simultaneous signaling? i.e., will it determine this with something like one of the ALOHA-based models or a more advanced CSMA algorithm? Or is this well beyond the scope of expected capabilities? -Ftuffner 21:12, 27 May 2010 (UTC)
- Does the communications module need to incorporate any signal degradation effects? Things like noise, general bit-error-rate (BER) calculations, or the like? -Ftuffner 21:14, 27 May 2010 (UTC)
Link/port modeling concept
Take a look at V3_applications_concepts#Modeling_Concepts. It seems the link "duplex" isn't the right way to approach the requirement. The idea of a port simply expresses the path a data item can take and when the transmission is triggered. There are three ways a transmission can be triggered:
- Regular time interval (e.g., heartbeat) that is regulated by a "frequency" parameter;
- Whenever the data changes; and
- When commanded (e.g., a counter is incremented or a flag is set).