Heldwhat Christmas wrote:Is there a reason you are testing these on a bread board? I haven't looked at the code for a while but I don't remember it really using PWM in the traditional sense. If I remember right, each LED gets turned on sequentially but the tail ones just get turned on for a shorter period of time. With the charlieplexing and the speed of these (primarily on the tail) I wouldn't be completely surprised if the higher impedance of the breadboard was the problem but Phil is the real expert here.
A breadboard is all that I have now. I never ordered any of the printed boards and I'm out of proto boards for the time being.
Heldwhat Christmas wrote:Not sure why the random option would have any effect. Honestly I don't think mine behave that differently with each of the random settings. Did you compile all 3 of the hex files yourself so we can rule out a compile problem?
For whatever reason, when I change the number of LED's where it says in the code:
movlw d'56'
movwf fall_count ;######## Set number of LEDs attached to controller ie. 3 segments = 21
incf fall_count, 1 ;Was easier than explaining add 1 to LED count.
Nothing happens. If I leave it at '56' then it runs with a single LED tail. If I slow it way down (setting the speed to 100) then I can see the 1 LED tail dimming (albeit at a different speed than the head LED), but I have so far been unable to get 4 LED's going at the same time.
Side note: It also runs solid without pausing. As soon as the last light finishes, it starts over. This may be the intent, I don't know.
Keith R wrote:
I commented the line "bcf d3, 6 and uncommented the two lines below and changed the movlw d'2' to d'9' or d'10' and it wouldn't compile. Am I missing something here?
I tried this real quick. I got a compile error because it was trying to compile the comment because there was an apostrophe instead of a semicolon in front of the comment. Just replace the ' with ;
So should be... movwf d3 ;####### a number between the quotes to set speed you like higher num = slower fall
airsouth wrote:
For whatever reason, when I change the number of LED's where it says in the code:movlw d'56' movwf fall_count ;######## Set number of LEDs attached to controller ie. 3 segments = 21 incf fall_count, 1 ;Was easier than explaining add 1 to LED count.Nothing happens. If I leave it at '56' then it runs with a single LED tail.
You have to change the 56 on both lines (it should be a couple lines above that one.
Are you trying to do something customer with the code?
Can you confirm what version of the code you are using? The one I have has the following comment:
; Sep-26-2011 : Fixed bug that caused fall to not start at top if you selected LED's less than 56..
Heldwhat Christmas wrote:Is there a reason you are testing these on a bread board? I haven't looked at the code for a while but I don't remember it really using PWM in the traditional sense. If I remember right, each LED gets turned on sequentially but the tail ones just get turned on for a shorter period of time. With the charlieplexing and the speed of these (primarily on the tail) I wouldn't be completely surprised if the higher impedance of the breadboard was the problem but Phil is the real expert here.Not sure why the random option would have any effect. Honestly I don't think mine behave that differently with each of the random settings. Did you compile all 3 of the hex files yourself so we can rule out a compile problem?
I didn't write that code, nor have I worked with it, so I don't consider myself the expert here.
Heldwhat Christmas wrote:I tried this real quick. I got a compile error because it was trying to compile the comment because there was an apostrophe instead of a semicolon in front of the comment. Just replace the ' with ;
So should be... movwf d3 ;####### a number between the quotes to set speed you like higher num = slower fall
Good catch....Didn't see that before.
