http://rdm.openlighting.org/incoming/model_data

It doesn't show the progress message or an error.

See previous report by Petr:
https://groups.google.com/forum/#!topic/open-lighting/H4NY7hDuG1U

So i will use rdm_model_collector and will publish via http://rdm.openlighting.org/incoming/model_data , although i am not sure if it works, i am getting:

TypeError: c is null jquery.min.js:3:16491
TypeError: dialog.dialog is not a function

In FIrefox and

jquery.min.js:3 Uncaught TypeError: Cannot read property 'opener' of null
model_data:175 Uncaught TypeError: dialog.dialog is not a function

in Chromium

Label items aren't currently being validated as it doesn't seem to work, I think possibly because it's an int and a string in the same array.

http://rdm.openlighting.org/download?pids=manufacturers

Check if rdm-app and OLA can handle extended characters (or fix if not) and start allowing them through in tools/make_manufacturer_data.sh

89bd652

It causes lots of knock ons if they're linked to other data like responders.

Check but I assume the manufacturer update process did this, if so maybe just report a warning and allow a manual deletion in the extremely rare case where it's actually required.

E.g.
5734388809596928
becomes
5631596510052352

Once the new code is live, we need to set these back to processed=false and re-run them:
5632842922983424

Should re-run others when slot info can be handled too...

When sensor description is supported, re-run:
6202727348568064

Skip as suspected manually generated:
5652104307802112
5658617961250816
5659080240660480
5669793197719552
5733560778489856
5746609660887040

So the new responders aren't listed in the by manufacturer view.
http://rdm.openlighting.org/model/manufacturer

use the OLP jscs presets defined here

Eletronic -> Electronic
Manufacturer:
(0x00B9, "Guangzhou Baiyun District Sanjie Eletronic Stage Lighting Audio Equipment Factory"),

Revert commits:
00ee599
0dcaeb5

I'm not quite sure how this happened and maybe it's just a "feature" of the dev app server, but we really shouldn't end up with duplicate manufacturer ID entries in the database!

See OpenLightingProject/ola#1837

https://docs.travis-ci.com/user/deployment/google-app-engine/

Because I'm lazy and rubbish at actually updating the live website version when I should...

Doesn't include e.g. 0x8383 @nightrune 's ID.
https://github.com/OpenLightingProject/rdm-app/blob/master/data/manufacturer_data.py

In Chrome:

Uncaught TypeError: Cannot read property 'opener' of null jquery.min.js:3Ca jquery.min.js:3n.cssHooks.(anonymous function).set jquery.min.js:3n.extend.style jquery.min.js:3(anonymous function) jquery.min.js:4K jquery.min.js:2n.fn.(anonymous function) jquery.min.js:4(anonymous function) jquery-ui.min.js:5(anonymous function) jquery-ui.min.js:5
GET http://rdm.openlighting.org/libs/bootstrap/css/bootstrap.min.css.map 404 (Not Found) 

And indeed it's missing:
http://rdm.openlighting.org/libs/bootstrap/css/bootstrap.min.css.map

The minified version is there fine though:
http://rdm.openlighting.org/libs/bootstrap/css/bootstrap.min.css

replace the python template engine with static html pages in combination with angularjs and json api's for faster loading times and less stress on the server, also the ability to make a html based app for mobile platforms. also a directory restructuring wouldn't hurt.

See:
OpenLightingProject/open-fixture-library#287 (comment)

To link to part of https://open-fixture-library.herokuapp.com/ and they'll look it up based on the RDM IDs we pass in.

Comments / Suggestions from #10

• I'd removed the "RDM Manufacturer Library" in the top left, since there isn't really a 'Home' page for this site.
• In the manufacturer list, it would be good to be able to filter by id. Right now I always just Control-F to lookup the manufacturer id
• Also on the manufacturer list, it may be worth breaking out the decimal and hex values into separate columns.
• On the About page, the heading are rather compacted. I think a bit more whitespace would make it easier to read.
• On the device page, some more whitespace around the devices would be good, see screenshot. The other pages (Splitters, Software etc.) have a good amount of spacing.
• At least on my machine, whenever there is a select list followed by a button, the two are joined, eg http://rdm.bewaar.me/model/manufacturer?manufacturer=8482 . See attached screenshot
  
• On the devices search by .... pages, can you make the table fill the entire width of the screen.
  

From [email protected] on February 16, 2013 11:24:25

We should track this property of a responder. The count is less interesting since it often varies with the hardware profile.

Original issue: http://code.google.com/p/open-lighting/issues/detail?id=223

http://raw.githubusercontent.com/OpenLightingProject/logos/master/web fitted/OLA-Logo-Fitted-48px%402x.png

I 13:04:41.031 fetching http://raw.githubusercontent.com/OpenLightingProject/logos/master/web fitted/OLA-Logo-Fitted-48px%402x.png
I 13:04:41.068 image fetch failed. http://raw.githubusercontent.com/OpenLightingProject/logos/master/web fitted/OLA-Logo-Fitted-48px%402x.png -> 404

Compared to:
13:04:40.652
fetching http://raw.githubusercontent.com/OpenLightingProject/logos/master/web%20fitted/OLA-Logo-Fitted-48px%402x.png

When running the server locally using dev_appserver.py, saving fetched images fails (see traceback).

As it seems, Blobstore uses the deprecated Files API. Also, Blobstore is listed in the Superseded Storage Solutions and its support page suggests using Google Cloud Storage instead.

E.g.
http://rdm.openlighting.org/model/display?manufacturer=8482&model=38

https://travis-ci.org/OpenLightingProject/rdm-app/jobs/289552564

Example: http://rdm.bewaar.me/model/display?manufacturer=31344&model=1

• Can you reduce the width of the "Software Version:" drop down so it doesn't span the entire page
• In the Supports Recording & Supports Min/Max, can you use the tick icon rather than 'true / false' . I think false can just be left blank, rather than using a cross.

To catch issues like:

I guess this file is not preprocessed since it's in the static folder? Then you should use /* … */ for comments, CSS doesn't support //.

Originally posted by @FloEdelmann in #265 (comment)

Hey, I've just downloaded ELC Lighting's Fixture Library in which I accidentally found a file containing many manufacturers with their PIDs. The PID values are different than in rdm.openlighting.org, but the names are the same.

Don't know if this is a help, but I saw it and wanted to share it with you.

ManufacturerSpecificPIDs.xml.txt

Hi all,

any chance to push the queue of collector data in rdm.openlighting.org/admin?

cheers!

As sourced in:
OpenLightingProject/ola#240

See also this:
#197

These are the blockers, I've filed a separate bug with the nice-to-haves.

Parameters Page

• Some PIDs are showing up as not having GET or SET. Compare http://rdm.openlighting.org/pid/id?id=0x8000 vs http://rdm.bewaar.me/pid/id?id=0x8000 . Actually it looks like the SET column is using the data from the GET column.

Controllers

• Searching by manufacturer results in an error. For example if I click 'Controllers', then click 'Search' I get http://rdm.bewaar.me/controller/browse?manufacturer=16708 which is a 500. The same URL loads on the main site so this may be a data issue?
• Clicking on a picture of a controller doesn't do anything.

Software / Ethernet Nodes / Splitters

• Same 2 bugs as Controllers

The JSON and Proto API (e.g. http://rdm.openlighting.org/api/json/1/manufacturers) both return Content-Type: text/plain in their headers. However, common REST APIs (like this) use Content-Type: application/json.

A nice advantage in Firefox is that Content-Type: application/json urls are automatically JSON parsed and prettyprinted (with foldable arrays/objects).

E.g.
0xcc, 0x02, 0x18, 0x7a, 0x70, 0x00, 0x00, 0x00, 0x00, 0x7a, 0x70, 0x12,
0x34, 0x56, 0x78, 0x00, 0x00, 0x00, 0x00, 0x00, 0x10, 0x00, 0x02, 0x00,
0x03, 0xe0

https://saucelabs.com/open-sauce

For now will need a sed or something.

Ideally get it fixed upstream either in the data or to populate both fields, or fail back from one to the other.

These are non-blocking, I've filed another issue with the blocking bugs

Tools Page

• Can you add a bit of vertical space between the headings and the input fields
• Can you put the result in a frame, possibly with a grey background and rounded corners. See attached mock up.
  

About Page

• Same comment here, add some vertical whitespace around the titles

Controllers

• The responsive design causes some funny layouts, since we still fetch 16 objects per page. See attached.
  . This can probably wait until we move to an AJAX based page.

Devices

• It would be good to unify the Browse page with the Search by ... , like the other categories.

Manufacturers

• I'd split the Manufacturer ID into two columns, one for decimal and one for hex.

Currently e.g. eldoLED is at the bottom, it should be with the E's. This is down to how GAE Datastore works, so we'd need to fix it in our Python, what's the performance hit?

Likewise the device by manufacturer etc drop downs.

The admin homepage reports:
n Responders in the moderation queue

But when you click into it, it tells you there are no responders left to moderate.

This is because of:

Showing a more obvious error would be good at least, or ideally skipping onto the next fixture.

• Robe - #100 (comment)
  • ROBE_PT_FEED
  • ROBE_PT_MODE
  • ROBE_MIC_SENS
  • ROBE_THEATRE_MODE
  • ROBE_C_CAL_MODE
  • ROBE_C_MIX_MODE
  • ROBE_UV_MIXING
  • ROBE_WHITE_POINT_8K
  • ROBE_OUTPUT_MODE
  • ROBE_OUTPUT_UNIFORMITY
  • ROBE_OUTPUT_CONSISTENCY
  • ROBE_CRI_SELECTION
  • ROBE_TH_EF_SIM
  • ROBE_DL_COMPATIBLE_MODE
  • ROBE_DISPLAY_INTENSITY
  • ROBE_TOUCHSCREEN_LOCK
  • ROBE_TEMPERATURE_UNIT
  • ROBE_FAN_MODE
  • ROBE_CMY_CONTROL
  • ROBE_DIMMER_CURVE
  • ROBE_BLACKOUT_DMC
  • ROBE_BLACKOUT_PTM
  • ROBE_BLACKOUT_GWM
  • ROBE_BLACKOUT_COLM
  • ROBE_BLACKOUT_TIM
  • ROBE_EXTEND_SC_FUNC
  • ROBE_STAND_ALONE
• Soundlight - http://www.soundlight.de/techtips/dmx512/slh_rdm_commands.htm
  • All
• MDG - http://www.mdgfog.com/c/mdg/file_db/document.file_en/M3e-User-Guide-Rev-Ac.pdf and http://www.mdgfog.com/c/mdg/file_db/document.file_en/theONE-User-Guide-Rev-Ae.pdf
  • {'default_value': 0, 'prefix': 0, 'min_value': 0, 'description': 'GENERATOR STATE', 'data_type': 2, 'max_value': 0, 'command_class': 1, 'pid': 32770, 'unit': 0}
  • {'default_value': 0, 'prefix': 0, 'min_value': 0, 'description': 'SAVER (0=30S/1=2MN/2=OFF)', 'data_type': 3, 'max_value': 2, 'command_class': 3, 'pid': 32772, 'unit': 0}
  • {'default_value': 0, 'prefix': 0, 'min_value': 0, 'description': 'AUTO/LOCAL/DMX (0..2)', 'data_type': 3, 'max_value': 3, 'command_class': 3, 'pid': 32773, 'unit': 0}
• SGM - bartvanstiphout/ola@349f3fd#diff-6a3d17b00514ff8e00435a361b373398R6303
  • All
  • {'default_value': 1, 'prefix': 0, 'min_value': 0, 'description': 'Enable Gamma Correction', 'data_type': 1, 'max_value': 1, 'command_class': 3, 'pid': 34339, 'unit': 0}
  • {'default_value': 0, 'prefix': 0, 'min_value': 0, 'description': 'Invert Pixel Order', 'data_type': 1, 'max_value': 1, 'command_class': 3, 'pid': 34345, 'unit': 0}
  • {'default_value': 0, 'prefix': 0, 'min_value': 0, 'description': 'Dim Mode 0=Standard 1=Max Power', 'data_type': 3, 'max_value': 1, 'command_class': 3, 'pid': 34344, 'unit': 0}
  • {'default_value': 0, 'prefix': 0, 'min_value': 0, 'description': 'Serial Nr.', 'data_type': 2, 'max_value': 0, 'command_class': 1, 'pid': 32864, 'unit': 0}
• Creative Lighting And Sound Systems e.g. http://www.creativelighting.com.au/images/documents/SLAMMO%20V4-P%206ch%20User%20Manual.pdf
  • Device Curve
• Artistic Licence
  • DALI PIDs
• ARRI - https://www.arri.com/?eID=registration&file_uid=19468
  • All

Wouldn't it be nice to follow the upcoming RDM Schema for the manufacturer specific PIDs?https://github.com/ssilverman/rdm-schema

Or are there still things missing to map/port to this json format?

Add labels to slot_label_id for SLOT_INFO
http://rdm.openlighting.org/pid/display?manufacturer=0&pid=288

The following would be useful:

EUID calculator:

Enter a UID and it shows you the matching EUID

EUID Decoder

Paste in a hex dump and see the UID and if the checksum matches.

PID Lookup:

A table listing all of the PIDs, what document they are in, and with a filter search function to search by name or PID number

Packet Decoder:

Pasts in a hex-dump, and it will separate out the fields and tell you if the checksum is valid.

As discussed in IRC.