LOR DMX isn't true DMX ... they swapped a couple wires ... so I believe the Falcon F16v2 outputs the LOR version of DMX, which is nice because no special cable or converter is needed to swap
the two wires that LOR decided to swap (from true DMX wiring). You would not want to hook up a true DMX thing to this output. THe F16v2 or v3 would allow you to configure one serial output for the LOR DMX and 1-2 other for true DMX and 1 other for Pixelnet or Renard or DMX. Super flexible/configurable.
The LOR protocol is a special rs485 ... I believe ... nice and long range, pretty tolerant to adverse conditions ... but is very SLOW compared to DMX, so can lag with higher channel counts,
xlights used to cap at 96 LOR protocol channels (still does?), but no limit for DMX. The link below shows a nice history on these. LOR allows for a regular telephone cable to be used and I guess because of that, the LOR protocol runs very slow to allow for that late 90's tech.http://blog.holidaycoro.com/2013/03/dmx-lor-protocols-and-rs-485.html
The only thing you lose with going LOR DMX is the LOR hardware based shimmer effect, which can be replaced in DMX with other effects that are similar ... but
not exactly the same. To me, its the least compelling effect, and a weak reason to stay with the sluggish LOR protocol.
The first year I switched from using LOR protocol to LOR DMX (on same LOR controllers), WOW -- I never knew my show was lagging -- but it was ... around 300-400 channels at the time.
All I had to do was update my firmware on those boxes (can be done in the field) ... and they were DMX capable, just send them DMX on the same cable and it auto detects.
The LOR boxes use the unit number to determine the LOR DMX starting address ... kind of limiting, but you just set the unit accordingly, and its not in pure numeric order, it goes to some hex values around 9 or 10 ... its well documented by LOR.