Photon pwm alocation

kazemzahedi · September 12, 2022, 8:33pm

Hi Everyone,
I am using the following pin allocations for my Photon project
int PWM1 = TX; // pwm out for chanel 1 pin 3
int PWM2 = WKP; // pwm out for chanel 2 pin 5
int PWM3 = A5; // pwm out for chanel 3 pin 7
int PWM4 = A4; // pwm out for chanel 4 pin 8
int Button = D5; // interrupt button
int FULBR1 = D1; // pin 14 Digital out
int FULBR2 = D7; // pin 20, Digital out
int FULBR3 = A6; // pin 6,Digital out
int FULBR4 = RX; // pin 4,Digital out

// RELAY CHANNELS
int CH1 = D2; //digital out for relays 1 pin 15 D6
int CH2 = D3; //digital out for relays 2 pin 16 D4
int CH3 = D4; //digital out for relays 3 pin 17 D3
int CH4 = D6; //digital out for relays 4 pin 19 D2

int CH1IN = A0; //Digital in for PWM1 for short ckt checking pin 12
int CH2IN = A1; //Digital in for PWM2 for short ckt checking pin 11
int CH3IN = A2; //Digital in for PWM3 for short ckt checking pin 10
int CH4IN = A3; //Digital in for PWM4 for short ckt checking pin 9
Is there a conflict between PWM1 to 4 pin allocations?
I am using a web App to control the PWMs. I have built a few boards for this project. On some boards, PWM2 is not always responding and on other boards, PWM4 is not always responding
Would somebody please help? Thanks in advance

kazemzahedi · September 12, 2022, 8:36pm

PS: I have no problems controlling relays 1 to 4

gusgonnet · September 12, 2022, 10:30pm

Hi, it might be that you are getting impacted by this:

On the Photon, P1 and Electron, this function works on pins D0, D1, D2, D3, A4, A5, WKP, RX and TX with a caveat: PWM timer peripheral is duplicated on two pins (A5/D2) and (A4/D3) for 7 total independent PWM outputs. For example: PWM may be used on A5 while D2 is used as a GPIO, or D2 as a PWM while A5 is used as an analog input. However A5 and D2 cannot be used as independently controlled PWM outputs at the same time.

source here and screenshot here:

Note: I read the above very very quick, please verify if it is the case

kazemzahedi · September 13, 2022, 9:01pm

Thanks Gus, I am using Photon with header which is the same as P0,
The board was working fine in year 2020. Is it possible that API has changed since then.

gusgonnet · September 13, 2022, 9:16pm

Sorry, I wouldn’t know.
If you changed the Device OS, perhaps. But if it stayed the same then I would look elsewhere.

gusgonnet · September 13, 2022, 9:17pm

Also, if you posted the code maybe someone in the community could spot an issue.

kazemzahedi · September 13, 2022, 10:22pm

Sure Gus here is the code
Hops, It is an 1100-line file, I can not copy past the whole file
How else can I send it
Regards Kazem

gusgonnet · September 13, 2022, 10:46pm

if you are using the particle web Build interface, you can share your project and post the link IF NOTHING in that firmware should remain SECRET

kazemzahedi · September 13, 2022, 11:08pm

Sorry I can not share the hole file.
If I can find a way to send a cutdown version of it I will
Thanks again Gus

kazemzahedi · September 15, 2022, 5:52pm

Hello Gus,
I found the problem with PWM4 connected to A4,
I have a hardware interrupt activated by overloaded on any PWM outputs. When I removed the code within the interrupt routine the PWM4 started to work fine. I do not understand the relationship between the 2. Would you explain it to me, please?

void SHORT(){
   detachInterrupt(Button); // disable short ckt interrupt
   if (digitalRead(CH1IN) == LOW) {
       FLshort1 =1; 
        digitalWrite(PWM1, LOW); digitalWrite(FULBR1, LOW);
    }
        if (digitalRead(CH2IN) == LOW){
        FLshort2 =1; 
        digitalWrite(PWM2, LOW); digitalWrite(FULBR2, LOW);
    } 
        if (digitalRead(CH3IN) == LOW) {
       FLshort3 =1;
        digitalWrite(PWM3, LOW); digitalWrite(FULBR3, LOW);
    }
        if (digitalRead(CH4IN) == LOW) {
        FLshort4 =1;
        digitalWrite(PWM4, LOW); digitalWrite(FULBR4, LOW);
    }

    attachInterrupt(Button, SHORT, FALLING, 11);  
}

If I remove the code within void short(), PWM4 work fine??
I need to have this function. What is the way around it
Thanks in advance

gusgonnet · September 15, 2022, 9:12pm

I do not know. What are you trying to achieve with that function?

kazemzahedi · September 16, 2022, 2:13am

It is for detecting which PWM is overloaded then it will shut it off and set a flag
another timer will enable all PWM’s. every 8 seconds If there is still an overload on it or any other PWM it will shut it off and set the corresponding flag so it can not be turned on for 8 seconds.
The shorted PWM has to be turned off in the interrupt routine as fast as possible to protect the output transistors I hope I have answered your question. Regards Kazem

gusgonnet · September 16, 2022, 2:27am

when you say that (above), could it be that this function deactivated PWM4?
Could it be that CH4IN is detected LOW sometimes?

rickkas7 · September 16, 2022, 1:55pm

I’m not sure if this is your problem, but you should not detach the interrupt and reattach it in the ISR.

The attachInterrupt() call is not ISR-safe as it allocates memory using new. I’m kind of surprised it didn’t cause a SOS panic. Actually, detachInterrupt() isn’t either because it calls delete.

kazemzahedi · September 18, 2022, 6:55am

Thank you, gentlemen. Short ISR is called only under short circuit conditions. rickkas7 I implemented your idea, but it did not help. I even commented //attachInterrupt(Button, SHORT, FALLING,11); in the setup loop When a short circuit takes place a hardware interrupt will call short ISR and relevant PWM will be turned off within that ISR. Relevant CH1IN to 4 will remain active until the corresponding PWM is turned off within the short ISR. If short circuit ISR is not called in under normal conditions why is it making PWM4 not respond? I have doubts about my PWM allocations being TX, WKP, A5, and A4. Are you sure that this allocation is OK?

rickkas7 · September 18, 2022, 9:15am

This is the source of truth for timer assignments from the Device OS source.

github.com

particle-iot/device-os/blob/develop-2.x/hal/src/photon/pinmap_hal.c#L58


      
          * adc_channel (ADC_Channel_xx or NONE. Note we don't define the peripheral because our chip only has one)
          * dac_channel (DAC_Channel_xx or NONE)
          * timer_peripheral (TIM1 - TIM5, or NONE)
          * timer_ch (1-3, or NONE)
          * pin_mode (NONE by default, can be set to OUTPUT, INPUT, or other types)
          * timer_ccr (0 by default, store the CCR value for TIM interrupt use)
          * user_property (0 by default, user variable storage)
          */
          
          
/* COMMON TO PHOTON, P1 and ELECTRON */
          /* D0            - 00 */ { GPIOB, GPIO_Pin_7, GPIO_PinSource7, NONE, NONE, TIM4, TIM_Channel_2, PIN_MODE_NONE, 0, 0 },
          /* D1            - 01 */ { GPIOB, GPIO_Pin_6, GPIO_PinSource6, NONE, NONE, TIM4, TIM_Channel_1, PIN_MODE_NONE, 0, 0 },
          /* D2            - 02 */ { GPIOB, GPIO_Pin_5, GPIO_PinSource5, NONE, NONE, TIM3, TIM_Channel_2, PIN_MODE_NONE, 0, 0 },
          /* D3            - 03 */ { GPIOB, GPIO_Pin_4, GPIO_PinSource4, NONE, NONE, TIM3, TIM_Channel_1, PIN_MODE_NONE, 0, 0 },
          /* D4            - 04 */ { GPIOB, GPIO_Pin_3, GPIO_PinSource3, NONE, NONE, NULL, NONE, PIN_MODE_NONE, 0, 0 },
          /* D5            - 05 */ { GPIOA, GPIO_Pin_15, GPIO_PinSource15, NONE, NONE, NULL, NONE, PIN_MODE_NONE, 0, 0 },
          /* D6            - 06 */ { GPIOA, GPIO_Pin_14, GPIO_PinSource14, NONE, NONE, NULL, NONE, PIN_MODE_NONE, 0, 0 },
          /* D7            - 07 */ { GPIOA, GPIO_Pin_13, GPIO_PinSource13, NONE, NONE, NULL, NONE, PIN_MODE_NONE, 0, 0 },
          /* NOT USED      - 08 */ { NULL, NONE, NONE, NONE, NONE, NULL, NONE, NONE, NONE, NONE },
          /* NOT USED      - 09 */ { NULL, NONE, NONE, NONE, NONE, NULL, NONE, NONE, NONE, NONE },
          /* A0            - 10 */ { GPIOC, GPIO_Pin_5, GPIO_PinSource5, ADC_Channel_15, NONE, NULL, NONE, PIN_MODE_NONE, 0, 0 },

Timers on the same timer number (TIM1, TIM3, etc.) must share the same frequency, but can have different duty cycles. If two pins share the same timer and channel, only one can be used for PWM.

TX - TIM1, TIM_Channel_2
WKP - TIM1, TIM_Channel_3
A5 - TIM3, TIM_Channel_1
A4 - TIM3, TIM_Channel_2

That looks safe, and it matches the documentation.

kazemzahedi · September 18, 2022, 9:44am

Thank you, Sir. Now I am starting to look elsewhere.
I moved the short circuit checking to the main loop. I still had the same problem, then it turned out that reading CH4IN connected to PWM4 is the source of the problem, but I do not know why.
once I found out I will let you know if you like me to
Thanks again

kazemzahedi · October 6, 2022, 5:37am

My problem was circuit miswiring.
Problem is solved now. Thanks a lot to all of you beautiful guys
Best regards.
Kazem

system · November 5, 2022, 3:38pm

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.

Topic		Replies	Views
Using Photon RGB-led pins (aka 27-29?) for PWM Troubleshooting	6	3793	March 25, 2016
PWM Rgb LED on the Photon Troubleshooting	24	9005	December 23, 2016
Is the PWM value independent foreach pin? Hardware	5	654	November 22, 2019
What is the PWM pin in the spark core and photon? General	1	4715	September 8, 2015
PWM on Photon same as Core? Hardware	4	4908	May 21, 2015

Photon pwm alocation

Related topics