Signal errors

busheyheath · by **busheyheath** on Sat, 27th Jun 2009, 22:52

Dear friends,

I am currently working on a project in which I am using LU signs, and I am getting more and more errors like this:

Signal is expected to have between 1 and 2 arguments at line 381, column 1 in file C:\Program Files\Open BVE\Railway\Route\Northern_Heights_1\NH_1.2a.csv
Signal is expected to have between 1 and 2 arguments at line 382, column 1 in file C:\Program Files\Open BVE\Railway\Route\Northern_Heights_1\NH_1.2a.csv
Signal is expected to have between 1 and 2 arguments at line 383, column 1 in file C:\Program Files\Open BVE\Railway\Route\Northern_Heights_1\NH_1.2a.csv
Signal is expected to have between 1 and 2 arguments at line 384, column 1 in file C:\Program Files\Open BVE\Railway\Route\Northern_Heights_1\NH_1.2a.csv
Signal is expected to have between 1 and 2 arguments at line 385, column 1 in file C:\Program Files\Open BVE\Railway\Route\Northern_Heights_1\NH_1.2a.csv
Signal is expected to have between 1 and 2 arguments at line 387, column 1 in file C:\Program Files\Open BVE\Railway\Route\Northern_Heights_1\NH_1.2a.csv
Signal is expected to have between 1 and 2 arguments at line 388, column 1 in file C:\Program Files\Open BVE\Railway\Route\Northern_Heights_1\NH_1.2a.csv
Signal is expected to have between 1 and 2 arguments at line 389, column 1 in file C:\Program Files\Open BVE\Railway\Route\Northern_Heights_1\NH_1.2a.csv
Signal is expected to have between 1 and 2 arguments at line 390, column 1 in file C:\Program Files\Open BVE\Railway\Route\Northern_Heights_1\NH_1.2a.csv
Signal is expected to have between 1 and 2 arguments at line 391, column 1 in file C:\Program Files\Open BVE\Railway\Route\Northern_Heights_1\NH_1.2a.csv
Signal is expected to have between 1 and 2 arguments at line 392, column 1 in file C:\Program Files\Open BVE\Railway\Route\Northern_Heights_1\NH_1.2a.csv
Signal is expected to have between 1 and 2 arguments at line 393, column 1 in file C:\Program Files\Open BVE\Railway\Route\Northern_Heights_1\NH_1.2a.csv

All these commands seem to refer to signals of the LU Northern Line (latest version). I get simular warnings when I try to drive those lines, but without much problems. Still, I would like to know where these warnings come from. Anybody any ideas?

velaro · by **velaro** on Sat, 27th Jun 2009, 23:18

Could you post lines 381-393 of this route file?

busheyheath · by **busheyheath** on Sun, 28th Jun 2009, 09:51

;Signals deep level
Signal(1).Load Northern_Heights_1\\LuSigs\TSCv2\tun_home; Northern_Heights_1\\LuSigs\TSCv2\glowhome ;;home (line 384)
Signal(2).Load Northern_Heights_1\LuSigs\TSCv2\tun_repeat; Northern_Heights_1\LuSigs\TSCv2\glowrepeat ;;repeater
Signal(3).Load Northern_Heights_1\LuSigs\TSCv2\tun_combi; Northern_Heights_1\LuSigs\TSCv2\glowcombi ;;combi
Signal(4).Load Northern_Heights_1\LuSigs\TSCv2\tun_leftfeather; Northern_Heights_1\LuSigs\TSCv2\glowhome ;;feather l
Signal(5).Load Northern_Heights_1\LuSigs\TSCv2\tun_rightfeather; Northern_Heights_1\LuSigs\TSCv2\glowhome ;;feather r
;Signals Surface
Signal(6).Load Northern_Heights_1\LuSigs\TSCv2\surface_home; Northern_Heights_1\LuSigs\TSCv2\glowhome ;;home
Signal(7).Load Northern_Heights_1\LuSigs\TSCv2\surface_rep; Northern_Heights_1\LuSigs\TSCv2\glowrepeat ;;high level repeater
Signal(8).Load Northern_Heights_1\LuSigs\TSCv2\surface_combi; Northern_Heights_1\LuSigs\TSCv2\glowcombi ;;combi
Signal(9).Load Northern_Heights_1\LuSigs\TSCv2\surface_leftfeather; Northern_Heights_1\LuSigs\TSCv2\glowhome ;;feather l
Signal(10).Load Northern_Heights_1\LuSigs\TSCv2\surface_rightfeather; Northern_Heights_1\LuSigs\TSCv2\glowhome ;;feather r
Signal(13).Load Northern_Heights_1\LuSigs\TSCv2\fog_repeat; Northern_Heights_1\LuSigs\TSCv2\glowrepeat ;;fog rep
Signal(14).Load Northern_Heights_1\LuSigs\TSCv2\surface_rightfeatherhb; Northern_Heights_1\LuSigs\TSCv2\glowhome ;;feather rhb

When starting Northern Line latest version I get exactly the same warnings... the line runs ok, though.

velaro · by **velaro** on Sun, 28th Jun 2009, 10:57

I think the parser does not like the 'double commenting' in each line (; text ;; more text). Leave the first semi-colon in each line but remove the two others.

Two more things:
- there is a double backslash in the path for the first signal
- the Northern Line does not generate any error messages on my system (most recent version of the route, openBVE 1.0.7.2)

busheyheath · by **busheyheath** on Sun, 28th Jun 2009, 15:51

velaro wrote:I think the parser does not like the 'double commenting' in each line (; text ;; more text). Leave the first semi-colon in each line but remove the two others.

Two more things:
- there is a double backslash in the path for the first signal
- the Northern Line does not generate any error messages on my system (most recent version of the route, openBVE 1.0.7.2)

Thank you, I will try it, line per line ( I have a backup :lol:

). The double backslash does not seem to be the problem, but I will remove one of them, just in case. And maybe my continental machine generates these warnings....

busheyheath · by **busheyheath** on Sun, 28th Jun 2009, 17:44

Sorry, but your advice didn't help. I even changed my country settings to UK standards ( dots to commas and vice versa), but the problem is not solved. I have founs out that the signal files are .X-files written in ANSI coding, and I will get more problems when I change the ANSI coding to UTF-8.

velaro · by **velaro** on Sun, 28th Jun 2009, 18:59

Strange. When I start with an error-free route file and add semi-colons in the same way as in your route file, I get the same error messages as you do, but perhaps that's a coincidence.

Emmanuel Vallois · by **Emmanuel Vallois** on Mon, 29th Jun 2009, 09:14

This is well explained in The CSV route documentation. Each command is separated from others by commas (,) and comments do not escape to this rule. As written in the post above, the comments are considered the fourth argument of the Signal.Load command, since the semi-colon (;) is the argument separator.
To have them being treated as comments, you should insert a comma to indicate you start an other "command", followed by a semicolon to indicate this is a comment "command".
Your sample code corrrected:

;Signals deep level
Signal(1).Load Northern_Heights_1\\LuSigs\TSCv2\tun_home; Northern_Heights_1\\LuSigs\TSCv2\glowhome,;home (line 384)
Signal(2).Load Northern_Heights_1\LuSigs\TSCv2\tun_repeat; Northern_Heights_1\LuSigs\TSCv2\glowrepeat,;repeater
Signal(3).Load Northern_Heights_1\LuSigs\TSCv2\tun_combi; Northern_Heights_1\LuSigs\TSCv2\glowcombi,;combi
Signal(4).Load Northern_Heights_1\LuSigs\TSCv2\tun_leftfeather; Northern_Heights_1\LuSigs\TSCv2\glowhome,;feather l
Signal(5).Load Northern_Heights_1\LuSigs\TSCv2\tun_rightfeather; Northern_Heights_1\LuSigs\TSCv2\glowhome,;feather r
;Signals Surface
Signal(6).Load Northern_Heights_1\LuSigs\TSCv2\surface_home; Northern_Heights_1\LuSigs\TSCv2\glowhome,;home
Signal(7).Load Northern_Heights_1\LuSigs\TSCv2\surface_rep; Northern_Heights_1\LuSigs\TSCv2\glowrepeat,;high level repeater
Signal(8).Load Northern_Heights_1\LuSigs\TSCv2\surface_combi; Northern_Heights_1\LuSigs\TSCv2\glowcombi,;combi
Signal(9).Load Northern_Heights_1\LuSigs\TSCv2\surface_leftfeather; Northern_Heights_1\LuSigs\TSCv2\glowhome,;feather l
Signal(10).Load Northern_Heights_1\LuSigs\TSCv2\surface_rightfeather; Northern_Heights_1\LuSigs\TSCv2\glowhom,;feather r
Signal(13).Load Northern_Heights_1\LuSigs\TSCv2\fog_repeat; Northern_Heights_1\LuSigs\TSCv2\glowrepeat,;fog rep
Signal(14).Load Northern_Heights_1\LuSigs\TSCv2\surface_rightfeatherhb; Northern_Heights_1\LuSigs\TSCv2\glowhome,;feather rhb

Note: albeit not necessary, a few spaces between the comma and the semicolon would improve readability.

busheyheath · by **busheyheath** on Mon, 29th Jun 2009, 17:08

Thanks! This did the trick. Somehow the first commas changed into semicolons in my downloads of the NL V4, and I got the same warnings because I copied these files :oops:

Saves 12 warnings.....

Signal errors

Signal errors

Re: Signal errors

Re: Signal errors

Re: Signal errors

Re: Signal errors

Re: Signal errors

Re: Signal errors

Re: Signal errors

Re: Signal errors

Who is online