Using an interrupt and LoRaWAN

Projects Programming
1

Hello Forum,

I am using an interrupt in my code to count the pulses from a flow meter. I am converting to a usable flow rate and then sending the information over The Things Network (TTN) using a LM-110H (LoRaWAN). When i comment out the interrupt i am able to send and see example data on TTN. When the interrupt is being used to calculate my pulse count my serial prints everything fine but when i plug in my LM-110H transmitter no data is received on the TTN.

My question: Can i use an interrupt and send data wirelessly? How is the interupt affecting my wireless signal out?

Thank you in advance,
The New Guy

2

Can you guess what our problem here might be?

Here's a hint: this is the programming section.

3

Where do you think this question best fits in?

4

Hello Forum,

I am using an interrupt in my code to count the pulses from a flow meter. I am converting to a usable flow rate and then sending the information over The Things Network (TTN) using a LM-110H (LoRaWAN). When i comment out the interrupt i am able to send and see example data on TTN. When the interrupt is being used to calculate my pulse count my serial prints everything fine but when i plug in my LM-110H transmitter no data is received on the TTN.

My question: Can i use an interrupt and send data wirelessly? How is the interupt affecting my wireless signal out?

Thank you in advance,
The New Guy

5

Where do you think this question best fits in?

A much better question to ask would be: what do I need to do to get help on the programming section of the forum?

Hint: see the "How to use this forum" post.

6

I know what my problem is now.
i start the interrupt() and hold it for one second this is how i am determining how many pulse per second there are.
then i use noInterrupts()....well this just shut off all my interrupts even the ones sending out bytes to the serial hardware....

Is there a way to just stop the interrupt on Pin 2 and allow other auto background interrupts to still do their thing?

interrupts();           // starts interupt
delay(1000);          //waits 1 sec
noInterrupts();           // ends interupt
7

I know what my problem is now.

Great.

This is just a snippet of my answer.
Hope that's OK with you.

8

TolpuddleSartre:
Great.

This is just a snippet of my answer.
Hope that's OK with you.

I wish i could take back that Karma i gave you :-\

9

I wish you wouldn't keep waffling and wasting time.

Maybe one of us will get our wish.

10

The problem could be in your code. Or in your wiring. Or both. Hard to say since we can't see either one.

Please read the "how to use this forum-please read" stickies.

11

The reason i wont upload all the code is that it contains private information including gateway keys and EUIs....i was hoping someone might have a quick solution to turn on and off interrupts per pin instead stopping all intterupts

12

Just mask the interrupt.
This answer implies information in the public domain, so I won't be expanding upon it.

13

Why not just disable the interrupt you're using?
Depending on what interrupt you're triggering on that pin, it could be either in one of the PCMSK registers (for PCINT), EIMSK (for INTn), TIMSK1 (if using input capture), and so on - that's assuming it's a 328p-based board, other microcontrollers will give different names for them.

14

I see from your cross post in Programming that you will not post code. Please do not cross post.

15

sweet thanks guys you have led me in the right direction i am now reviewing the data sheet for my Atmega 328P

16

jball:
my Atmega 328P

Can you see why we're frustrated?

Dribbling out (or not) information about your problem is a waste of time, not least yours, when you have to wait five minutes between posts.

You could have told us in your first post which processor you're using, what type of interrupt, what your code looked like (passwords etc are very easily masked/redacted).

Instead, we got waffle.

17

Threads merged.

18

jball:

interrupts();           // starts interupt

delay(1000);          //waits 1 sec
noInterrupts();          // ends interupt

Why start and stop interrupts at all. Let the interrupt continue all the time but just zero the count, wait a second and then read the count. You have the information you need now and it does not matter if the interrupt count continues or even overflows and wraps around because the next time you ready to take a reading the count is zeroed.