I do see a difference. In procedure hal(), PWM2 is addressed on lines 141, 144 and 147. Then, on line 153 or 158 the procedure command_send_kamer() is called, which addresses PWM1. It must be command_send_hal() at that point. Greets,Kiste
Am Dienstag, 5. April 2022, 18:41:35 MESZ hat Rob CJ <[email protected]> Folgendes geschrieben: Hi Hans, I agree with Kiste. You should keep the PWM running and switch the PWM output to input to output a '1' or '0'. But the issue with pwm2 remains a mistery. I will try it this weekend and use the test program to compare pwm1 and pwm2 since I did not see any difference in the code and at least I know if I would have the same problem. Kind regards, Rob Van: 'Oliver Seitz' via jallib <[email protected]> Verzonden: dinsdag 5 april 2022 18:09 Aan: [email protected] <[email protected]> Onderwerp: Re: [jallib] PWM2. In procedure kamer (bit in x) is a call to command_send_kamer(HEAT_hal[teller]). And also in procedure hal (bit in x) is a call to command_send_kamer(HEAT_hal[teller]). The second should surely call command_send_hal(HEAT_hal[teller]). As long as the wrong PWM is addressed, no fine-tuning helps. Greets,Kiste Am Dienstag, 5. April 2022, 16:13:19 MESZ hat hans <[email protected]> Folgendes geschrieben: Hello Kyle, Done but same result. PWM1 works and PWM2 not. Now tested on 16FHow can i combine 19 bytes in one big word Op dinsdag 5 april 2022 om 13:30:54 UTC+2 schreef Kiste: Hi hans, now as I know what it is for, I can give some hints ;-) I've done remote signals a lot, and I did it this way: - I keep the PWM running all the time, at 50% duty.- I switch the LED on and off by setting the port pin to input/output (Works if the LED is directly connected or via bipolar transistor, not via FET) If you're changing the duty cycle to switch the LED on or off, there can be a significant delay before the action takes effect. Switching the pin to input or output works instantaneous. In the "procedure hal()" you're calling "command_send_kamer()", which is probably wrong? You've got procedures for sending a bit, a byte and a full command. That is good for readability, but not so good for signal quality. You send a burst of 450µs, and the following pause codes the bit. If you're at the end of a byte, the bit procedure is ended, then the byte procedure is ended, then the loop in the command procedure is forwarding one step, the byte procedure is called, then the bit procedure is called, and just then there's the next burst. That's quite some time passing, which can make a "0" look like a "1". Better collect all the bits in a single variable, and send all 152 bits in one loop in one procedure. And even if not, this is using time in bad places: teller = 0 for 19 loop if x == high then command_send_kamer(HEAT_kamer[teller]) else command_send_kamer(HALT_kamer[teller]) end if teller = teller + 1 end loop This would be better: if x == high then for 19 using teller loop command_send_kamer(HEAT_kamer[teller]) end loopelse for 19 using teller loop command_send_kamer(HALT_kamer[teller]) end loopend if That way there's no "if" between the bytes. Greets,Kiste Am Dienstag, 5. April 2022, 11:47:50 MESZ hat hans <[email protected]> Folgendes geschrieben: Everything has its limits. We have tried to make a remote control for his two DAIKIN ACs. With PWM1, the case responds just fine with PMW2 not responding. The IR LEDs are controlled with an npn. (swapped) . We also tried the 16F877a, same result. On an AUDICITY we compared the IR results on a TSOP , the IR leds (swapped!)… Both look the same. The frequencies of the PMW varied from 35 to 40. No effect. So that's the end of the story for us and then just fiddling with one PWM, which we then switch via hardware. Unless ……. Any of you have a different idea. Attached program and picture Op maandag 4 april 2022 om 13:52:34 UTC+2 schreef hans: Thank s Kiste. oops, I've now replaced all on/off's with set_dutycycle_percent(..) the program that I use works fine with PWM1 but not with PWM2. So there must be a difference. Where should I look now? Op maandag 4 april 2022 om 12:04:31 UTC+2 schreef Kiste: Sorry, no. PWM2_off() does not set the LED off, it switches off the PWM module and passes control of the output pin back to the simple digital output. The digital output can be randomly set to "on", you did not set it to "off". If you want to keep PWM running and switch off the LED, use pwm2_set_dutycycle_percent(0) pwm2_on() and pwm2_off() is not switching the *output* to on or off, it starts or stops the PWM module. If you want to set LED brightness, you don't want to ever stop the module. It's like waiting at the traffic lights: You're setting the car speed to zero (=duty_cycle(0)), but you don't switch off the engine (=pwm_off()). If the street's going downhill, a switched off engine will not surely prevent the car from moving. You need to use the right means for the purpose of stopping the car. Greets,Kiste Am Montag, 4. April 2022, 11:43:01 MESZ hat hans <[email protected]> Folgendes geschrieben: Hi Kiste,PWM2_off() sets the led ON and PMW2_on () sets the lightoff.. regards Hans Op maandag 4 april 2022 om 09:21:03 UTC+2 schreef Kiste: Hi hans, this is what the program should do if the LED is connected to RC1 and GND (with resistor): The LED will slowly light up from off to 99% within one second,then it will fade from 99% to 1% within another second. The LED stays at 1% for half a second PWM is disabled, so the LED will reflect the port pin, which is undefined by default, for half a second Then, PWM is reactivated and the LED will resume at 1% for 5 seconds, before starting over again. That is not what you're seeing? Greets,Kiste Am Sonntag, 3. April 2022, 16:10:38 MESZ hat hans <[email protected]> Folgendes geschrieben: A question from a friend. Attached is a test program for the use of the second PWM port C1. The results are opposite to the assignment. On is off and off is on. See the end of the file, the LED would go on for a long time but then it is just off -- You received this message because you are subscribed to the Google Groups "jallib" group. To unsubscribe from this group and stop receiving emails from it, send an email [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jallib/0fc3bf61-ee5b-435f-a883-fbe7e1f9188fn%40googlegroups.com. -- You received this message because you are subscribed to the Google Groups "jallib" group. To unsubscribe from this group and stop receiving emails from it, send an email [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jallib/977fd495-4f9e-40f7-b9eb-caa72e361cd4n%40googlegroups.com. -- You received this message because you are subscribed to the Google Groups "jallib" group. To unsubscribe from this group and stop receiving emails from it, send an email [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jallib/a5691502-ada9-4089-8666-3a0399756e44n%40googlegroups.com. -- You received this message because you are subscribed to the Google Groups "jallib" group. To unsubscribe from this group and stop receiving emails from it, send an email [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jallib/c3f11c7f-47d8-4eaf-bf6d-34bd4761f886n%40googlegroups.com. -- You received this message because you are subscribed to the Google Groups "jallib" group. To unsubscribe from this group and stop receiving emails from it, send an email [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jallib/1759365406.1110179.1649174971737%40mail.yahoo.com. -- You received this message because you are subscribed to the Google Groups "jallib" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jallib/DB6P195MB01835B837FCC857AF0C008ACE6E49%40DB6P195MB0183.EURP195.PROD.OUTLOOK.COM. -- You received this message because you are subscribed to the Google Groups "jallib" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jallib/2123250335.929292.1649177954746%40mail.yahoo.com.
