light-controller | A Simple http proxy for controlling the spotlights at work | Proxy library

The type of the DataBroker constructor parameter for HelloProvider in the blueprint XML (org.opendaylight.controller.md.sal.binding.api.DataBroker) doesn't match the code (org.opendaylight.mdsal.binding.api.DataBroker).

Please see UM0290 in which we find:

Each Alternate setting string descriptor must follow this memory mapping else the PC Host Software would be able to decode the right mapping for the selected device:

• @: To detect that this is a special mapping descriptor (to avoid decoding standard descriptor)
• /: for separator between zones
• Maximum 8 digits per address starting by “0x”
• /: for separator between zones
• Maximum of 2 digits for the number of sectors
• * : For separator between number of sectors and sector size
• Maximum 3 digits for sector size between 0 and 999
• 1 digit for the sector size multiplier. Valid entries are: B (byte), K (Kilo), M (Mega)
• 1 digit for the sector type as follows:
  • a (0x41): Readable
  • b (0x42): Erasable
  • c (0x43): Readable and Erasable
  • d (0x44): Writeable
  • e (0x45): Readable and Writeable
  • f (0x46): Erasable and Writeable
  • g (0x47): Readable, Erasable and Writeable

So your string really does mean that the internal flash is 64 sectors of 2 KB, and that they are "readable, erasable and writable" (i.e. flash). Are you sure about your expectations of the device's flash layout?

The archetype artifacts had expired from our repository (which is a side-effect of our unfortunate reliance on snapshot artifacts). We’ve update the archetypes and pushed them to the repository again; they are available here and usable with

The API doc explorer feature is called odl-mdsal-apidocs, not mdsal-apidocs.

The dlux and dluxapps feature repos aren't included by the archetype - it's just a starting point - you can add whatever other feature you want. That said, the dlux and dluxapps projects are no longer actively maintained and thus were archived a few months ago. However you can still download and get them to build yourself. If you're interested in rebooting them upstream, contributions are always welcome.

You have to take a look at the allowed characters for Java class names. - is not allowed. Take a look here: https://docs.oracle.com/javase/specs/jls/se7/html/jls-3.html#jls-3.8

I have found a solution in the OpenDaylight forum.

Please remove -DarchtypeCatlog=http://nexus.opendaylight.org/content/repositories/opendaylight.release/archetype-catalog.xml

and execute following command.

mvn archetype:generate -DarchetypeGroupId=org.opendaylight.controller -DarchetypeArtifactId=opendaylight-startup-archetype -DarchetypeRepository=http://nexus.opendaylight.org/content/repositories/opendaylight.release -DarchetypeVersion=1.4.0

The lobodol and YMFC systems work without using the time constant, because the code is written in such a manner that the Arduino would not do anything other then the control.

As such the time difference between calculations of P, I and D error would remain the same.

There is no difference in how you would tune these systems to how you would tune any other PID system.

While this system works, this also means that the final tuned PID values would only be used with these systems and not to any other.

The other systems which are using the time difference in their calculations. This means that the tuned PID values could be used(More reliably as compared to lobodol and YMFC) with other systems as well.

In the YMFC implementation

Just to clarify for anyone else, the org.opendaylight.qos is not an Opendaylight.org project but just the name you gave when using the archetype.

The broken features build seems to be because the released (old) archetypeVersion=1.3.0-Carbon seems to be broken. Have you considered just using the latest one?

Make sure that you have the ODL settings.xml, and then just: