rastan350 Posted November 2, 2018 Share Posted November 2, 2018 Hello, Just got LEDWiz setup with a Launch button and 2 beacons. If I test the ports with LEDBlinky everything works and lights up as expected. I have added the LEDWiz ID#1 to DOF Config tool and set the port assignments, downloaded the config files and replaced. I get nothing in the DOF tester tool or on any table. I also have a SainSmart, Teensy and Pinscape. I am not sure what else to try at this point. I am sure I a missing something stupid. Any help would be very appreciated as always. From what I can tell from the log it is detecting the LEDWiz at ID#1. Log is attached. log.txt Link to comment Share on other sites More sharing options...
Content Provider arngrim Posted November 4, 2018 Content Provider Share Posted November 4, 2018 @TerryRed, not sure if the issue that i see on rastan350 logs is the root cause of his problem, but there is a problem in your master of the universe dof config, can you have a look it, i don't see what's wrong on the config myself 2018.11.02 13:14:52.795 Warning: Cant parse the part PURPLE of the ledcontrol table config setting E422 L Purple L11 AT80 AH20 F50 BLINK BPW10 ASDR 2018.11.02 13:14:52.796 EXCEPTION: Could not parse setting E422 L Purple L11 AT80 AH20 F50 BLINK BPW10 ASDR in column data E406 SWhite AH30 AL0 AT0 AW9 SHPCircle3 500 L0... 2018.11.02 13:14:52.800 Warning: Previous exceptions occured in the line motu,E110 LPurple 50 AH100 ADU AS300 2018.11.02 13:14:52.927 EXCEPTION: Could not parse setting L in column data L. Link to comment Share on other sites More sharing options...
Content Provider TerryRed Posted November 5, 2018 Content Provider Share Posted November 5, 2018 Yah, I checked my files here...and I get no errors at all with the LedControFileTester. I don't have that extra L like he does with all the L PURPLE instances. Link to comment Share on other sites More sharing options...
Content Provider TerryRed Posted January 14, 2019 Content Provider Share Posted January 14, 2019 On 11/4/2018 at 5:47 AM, arngrim said: @TerryRed, not sure if the issue that i see on rastan350 logs is the root cause of his problem, but there is a problem in your master of the universe dof config, can you have a look it, i don't see what's wrong on the config myself 2018.11.02 13:14:52.795 Warning: Cant parse the part PURPLE of the ledcontrol table config setting E422 L Purple L11 AT80 AH20 F50 BLINK BPW10 ASDR 2018.11.02 13:14:52.796 EXCEPTION: Could not parse setting E422 L Purple L11 AT80 AH20 F50 BLINK BPW10 ASDR in column data E406 SWhite AH30 AL0 AT0 AW9 SHPCircle3 500 L0... 2018.11.02 13:14:52.800 Warning: Previous exceptions occured in the line motu,E110 LPurple 50 AH100 ADU AS300 2018.11.02 13:14:52.927 EXCEPTION: Could not parse setting L in column data L. To follow up on this....it turned out to be an extra space! Damn those extra spaces! They will show up as L in the LedControFileTester. SpaceTime had a space in one of the MX toys as well, so I fixed them both. Link to comment Share on other sites More sharing options...
Content Provider arngrim Posted January 14, 2019 Content Provider Share Posted January 14, 2019 thanks Terry for finding it, fixes have been approved Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.