T
treez
Guest
Hello,
Our remote software engineer recently wrote some code for our new DALI dimmable lamp.
It’s just a simple dimmable lamp, however, due to the use of the DALI protocol, the code is enormous. When I loaded his code, and then turned the lamp on at full power, the lamp lit for several minutes and then for no reason, just turned off and stayed off. This should not have happened.
Every time it turned off, I kept recycling the power to bring it back on again, but it kept turning off, again, randomly after a few minutes or so. :sad:
Anyway, we told the software engineer what was happening and he said that his code was fine, and that the turning off must be due to our “noisy” hardware crashing his good software. :bsdetector:
Anyway, I then wrote some very very simple code for the lamp, -code that simply turned the lamp on at full power and leaves it on. With my simple code running, the lamp correctly stayed running at full power and did not turn off. :clap:
I also wrote several other similar simple programs, each one to demonstrate that all of our lamp hardware was working fine…..for example, I wrote one code which simply did PWM dimming at 50%, to prove that that would correctly dim the lamp…and it did. :clap:
We then replied back to the software engineer and informed him that our own simple code was running fine on the lamp…no errant turning off and no problems. We informed him that if our hardware was “noisy” and thereby crashing his software, then why was the “noisy” hardware not crashing our own simple software(?).
-Anyway, he replied that our simple software test programs were much shorter than his own software…and he told us that short software programs are less susceptible to noise corruption. Is this true? :???:
The microcontroller is PIC16F18856.
Our remote software engineer recently wrote some code for our new DALI dimmable lamp.
It’s just a simple dimmable lamp, however, due to the use of the DALI protocol, the code is enormous. When I loaded his code, and then turned the lamp on at full power, the lamp lit for several minutes and then for no reason, just turned off and stayed off. This should not have happened.
Every time it turned off, I kept recycling the power to bring it back on again, but it kept turning off, again, randomly after a few minutes or so. :sad:
Anyway, we told the software engineer what was happening and he said that his code was fine, and that the turning off must be due to our “noisy” hardware crashing his good software. :bsdetector:
Anyway, I then wrote some very very simple code for the lamp, -code that simply turned the lamp on at full power and leaves it on. With my simple code running, the lamp correctly stayed running at full power and did not turn off. :clap:
I also wrote several other similar simple programs, each one to demonstrate that all of our lamp hardware was working fine…..for example, I wrote one code which simply did PWM dimming at 50%, to prove that that would correctly dim the lamp…and it did. :clap:
We then replied back to the software engineer and informed him that our own simple code was running fine on the lamp…no errant turning off and no problems. We informed him that if our hardware was “noisy” and thereby crashing his software, then why was the “noisy” hardware not crashing our own simple software(?).
-Anyway, he replied that our simple software test programs were much shorter than his own software…and he told us that short software programs are less susceptible to noise corruption. Is this true? :???:
The microcontroller is PIC16F18856.