Tridium LonWorks import can't do special charachters?

[MaxBurn]

We have had some trouble with some BMS systems not liking our LonWorks points but no real specific complaints until today. So we have a tech on site that gave us feedback that Tridium can't do special charachters in point names, things like <>% space etc do NOT work. For some reason underscore _ does work fine.

It also appears that there is NO provision to manually enter a point when this automatic point import fails so of course they want us to change all of our point names.

All this true? Anyone have a list of forbidden charachters?

[crab master]

TAC Vista doesn't like it either. Underscores are fine, it doesn't like space although from memory one can manually enter in an _. I don't have a list, but another thing it doesn't like are slashes as it tends to think with the \ to go down another level, nor does it like -. The best advice I could come across is "use nothing but alpha-numeric characters and (_) underscores"

Hopefully someone can get you a Tridum/LON specific list.

[digo]

Anyone have a list of forbidden charachters?

Take a look in docUser.pdf (About component naming)
Only alphanumeric (A-Z, a-z, 0-9) and underscore (_) characters are used.

[MaxBurn]

Take a look in docUser.pdf (About component naming)
Only alphanumeric (A-Z, a-z, 0-9) and underscore (_) characters are used.

Is this what you are talking about? http://www.setempco.com/docUser.pdf

We don't have anything to do with Tridium, we OEM WEBctrl. WEBctrl doesn't appear to have trouble with the names we are using. The program we used to test with from echelon called nodeutil doesn't see a problem with the point names that we can see. There are plenty of vendors that haven't had this trouble getting points from us. Is there guidelines from Echelon for point names I'm not aware of? Any particular reason why these Tridium / TAC Vista do not support these characters?

[crab master]

http://www.echelon.com/support/docum...mers_Guide.pdf

http://buildingskb.schneider-electri...w.php?AID=8062

http://buildingskb.schneider-electri....php?AID=11189

http://buildingskb.schneider-electri...w.php?AID=4051

http://buildingskb.schneider-electri...w.php?AID=6517

From what I gather from the above links there are Neuron standards in the xif file that don't have to be followed, however if they aren't followed some software will throw errors.

[MaxBurn]

Thanks, thats the info I need to get the committee to change their ways.