DOF Log File

[CapnUSA]

Hi All,

 

I have been recovering from surgery, which gave me plenty of time to clean up my pincab files. While reading into things, I came across the DirectOutput.log. It has several errors, but I'm unsure if I should be concerned with them. Here's one for example:

 

2025.01.25 13:05:05.506    Error: Failed: CS18
2025.01.25 13:05:05.506    Warning: Cant parse the trigger part CS18 of the ledcontrol table config setting  CS18 White BLINK M200 FU50 FD100 L23 AT75 AH10.
2025.01.25 13:05:05.507    EXCEPTION: Could not parse setting  CS18 White BLINK M200 FU50 FD100 L23 AT75 AH10 in column data S18 CCyan 40 L23 AT65 AH10 ASS400 ASDU/S18 CCyan 40 L23 AT85 AH10 ASS400 ASDD/ CS18 White BLINK M200 FU50 FD100 L23 AT75 AH10/ CW29 Red AT70 AH30 ADD AS300/ CW28 Green AT70 AH30 ADD AS300/ CW33 Yellow AT70 AH30 ADD AS300/ CW23 Royal_blue L0 ADU AS250 BLINK 800 BPW9 AL0 AW100 AT85 AH15/ CW23 Forest_green L1 ADD AS250 BLINK 800 BPW9 W400 AL0 AW100 AT85 AH15/ CW23 Royal_blue INVERT 100 1 W10 L2 AS200 ASDU/ CW23 Forest_green INVERT 300 1 W50 FD250 L3 AS200 ASDU.
2025.01.25 13:05:05.507    EXCEPTION: Thread: 
2025.01.25 13:05:05.507    EXCEPTION: Message: Exception --> Cant parse the part CS18 of the ledcontrol table config setting  CS18 White BLINK M200 FU50 FD100 L23 AT75 AH10.
2025.01.25 13:05:05.508    EXCEPTION: Stack trace:    at DirectOutput.LedControl.Loader.TableConfigSetting.ParseSettingData(String SettingData)
2025.01.25 13:05:05.508    EXCEPTION: Stack trace:    at DirectOutput.LedControl.Loader.TableConfigColumn.ParseColumnData(String ColumnData, Boolean ThrowExceptions)
2025.01.25 13:05:05.508    EXCEPTION: Target site: Void ParseSettingData(System.String)

 

I have attached the entire log file for examination.

 

Thanks,

 CapnUSA

DirectOutput.log

[CapnUSA]

Hi All,

 

I was able to resolve the issue by editing the files created by the DOF Config Tool. I'm not sure if the problem existed in the old version of the Tool, but the new tool is randomly inserting the letter C throughout the controller files. In my case these files are named directoutputconfig30.ini and directoutputconfig51.ini. Both files contained random letter C throughout. I'm not sure if the tool is adding them, or if the collected data is corrupt. Most of my toys worked properly, but my DirectOutput.log file was flooded with errors. After manually removing the random characters, the errors stopped, and my log file is now clean.

 

I would be interested in knowing if others are finding the same errors in their DirectOutpout.log file and they just weren't aware it was happening. The errors won't prevent DOF from working; however, there are many triggers being bypassed because of the errors.

 

Thanks,

 

CapnUSA