getting error 'Serial' was not declared in this scope











up vote
1
down vote

favorite
1












I am adding Dust Sensor to my particle photon project at home,



I got this GitHub project that I want to test before implementing a final code.



I am not an expert in cpp, I wanted to modularise the dust sensor codebase to separate library so I created new dustSensor.cpp file and kept the code linked above.



but I keep getting error:



'Serial' was not declared in this scope



'Serial1' was not declared in this scope



'DEBUG' was not declared in this scope



'DEC' was not declared in this scope dustSensor.cpp:13:57:



I do have Serial.begin(57600) called in setup() function but still get the above error










share|improve this question


















  • 1




    add #include <Arduno.h> to cpp
    – Juraj
    Nov 15 at 13:48










  • you can find it with opened your Particle Project in the Desktop IDE and click on the Browse and Manage Libraries buttons and find the library you need. that's automatically include your libraries. see this docs.
    – abu-ahmed al-khatiri
    Nov 15 at 14:02

















up vote
1
down vote

favorite
1












I am adding Dust Sensor to my particle photon project at home,



I got this GitHub project that I want to test before implementing a final code.



I am not an expert in cpp, I wanted to modularise the dust sensor codebase to separate library so I created new dustSensor.cpp file and kept the code linked above.



but I keep getting error:



'Serial' was not declared in this scope



'Serial1' was not declared in this scope



'DEBUG' was not declared in this scope



'DEC' was not declared in this scope dustSensor.cpp:13:57:



I do have Serial.begin(57600) called in setup() function but still get the above error










share|improve this question


















  • 1




    add #include <Arduno.h> to cpp
    – Juraj
    Nov 15 at 13:48










  • you can find it with opened your Particle Project in the Desktop IDE and click on the Browse and Manage Libraries buttons and find the library you need. that's automatically include your libraries. see this docs.
    – abu-ahmed al-khatiri
    Nov 15 at 14:02















up vote
1
down vote

favorite
1









up vote
1
down vote

favorite
1






1





I am adding Dust Sensor to my particle photon project at home,



I got this GitHub project that I want to test before implementing a final code.



I am not an expert in cpp, I wanted to modularise the dust sensor codebase to separate library so I created new dustSensor.cpp file and kept the code linked above.



but I keep getting error:



'Serial' was not declared in this scope



'Serial1' was not declared in this scope



'DEBUG' was not declared in this scope



'DEC' was not declared in this scope dustSensor.cpp:13:57:



I do have Serial.begin(57600) called in setup() function but still get the above error










share|improve this question













I am adding Dust Sensor to my particle photon project at home,



I got this GitHub project that I want to test before implementing a final code.



I am not an expert in cpp, I wanted to modularise the dust sensor codebase to separate library so I created new dustSensor.cpp file and kept the code linked above.



but I keep getting error:



'Serial' was not declared in this scope



'Serial1' was not declared in this scope



'DEBUG' was not declared in this scope



'DEC' was not declared in this scope dustSensor.cpp:13:57:



I do have Serial.begin(57600) called in setup() function but still get the above error







serial programming softwareserial serial-data cpp






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 15 at 13:22









Ciasto piekarz

2741421




2741421








  • 1




    add #include <Arduno.h> to cpp
    – Juraj
    Nov 15 at 13:48










  • you can find it with opened your Particle Project in the Desktop IDE and click on the Browse and Manage Libraries buttons and find the library you need. that's automatically include your libraries. see this docs.
    – abu-ahmed al-khatiri
    Nov 15 at 14:02
















  • 1




    add #include <Arduno.h> to cpp
    – Juraj
    Nov 15 at 13:48










  • you can find it with opened your Particle Project in the Desktop IDE and click on the Browse and Manage Libraries buttons and find the library you need. that's automatically include your libraries. see this docs.
    – abu-ahmed al-khatiri
    Nov 15 at 14:02










1




1




add #include <Arduno.h> to cpp
– Juraj
Nov 15 at 13:48




add #include <Arduno.h> to cpp
– Juraj
Nov 15 at 13:48












you can find it with opened your Particle Project in the Desktop IDE and click on the Browse and Manage Libraries buttons and find the library you need. that's automatically include your libraries. see this docs.
– abu-ahmed al-khatiri
Nov 15 at 14:02






you can find it with opened your Particle Project in the Desktop IDE and click on the Browse and Manage Libraries buttons and find the library you need. that's automatically include your libraries. see this docs.
– abu-ahmed al-khatiri
Nov 15 at 14:02












1 Answer
1






active

oldest

votes

















up vote
4
down vote













I learned that I needed to include Arduino.h header file



apart from that I learned .ino files and .cpp files is that the .ino files transparently include particle.h for you.



The other difference is that .ino files generate forward declarations for you. This is necessary when you’ve implemented a function later in the file than when you’ve first used it. For example, if you pass the function to something like Particle.subscribe in setup() but you’ve implemented it farther down the file.






share|improve this answer

















  • 2




    The technical name for that is a "forward reference". Historical note: the necessity to declare the function before a forward reference originated because early C compilers were written to read your source code only once, rather than once to find function and variable definitions and again to generate code once the components of it were known. Such a compiler was easier to write and ran faster (which was a bigger concern at the time than it is today).
    – JRobert
    Nov 15 at 15:44











Your Answer






StackExchange.ifUsing("editor", function () {
return StackExchange.using("schematics", function () {
StackExchange.schematics.init();
});
}, "cicuitlab");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "540"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2farduino.stackexchange.com%2fquestions%2f57875%2fgetting-error-serial-was-not-declared-in-this-scope%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes








up vote
4
down vote













I learned that I needed to include Arduino.h header file



apart from that I learned .ino files and .cpp files is that the .ino files transparently include particle.h for you.



The other difference is that .ino files generate forward declarations for you. This is necessary when you’ve implemented a function later in the file than when you’ve first used it. For example, if you pass the function to something like Particle.subscribe in setup() but you’ve implemented it farther down the file.






share|improve this answer

















  • 2




    The technical name for that is a "forward reference". Historical note: the necessity to declare the function before a forward reference originated because early C compilers were written to read your source code only once, rather than once to find function and variable definitions and again to generate code once the components of it were known. Such a compiler was easier to write and ran faster (which was a bigger concern at the time than it is today).
    – JRobert
    Nov 15 at 15:44















up vote
4
down vote













I learned that I needed to include Arduino.h header file



apart from that I learned .ino files and .cpp files is that the .ino files transparently include particle.h for you.



The other difference is that .ino files generate forward declarations for you. This is necessary when you’ve implemented a function later in the file than when you’ve first used it. For example, if you pass the function to something like Particle.subscribe in setup() but you’ve implemented it farther down the file.






share|improve this answer

















  • 2




    The technical name for that is a "forward reference". Historical note: the necessity to declare the function before a forward reference originated because early C compilers were written to read your source code only once, rather than once to find function and variable definitions and again to generate code once the components of it were known. Such a compiler was easier to write and ran faster (which was a bigger concern at the time than it is today).
    – JRobert
    Nov 15 at 15:44













up vote
4
down vote










up vote
4
down vote









I learned that I needed to include Arduino.h header file



apart from that I learned .ino files and .cpp files is that the .ino files transparently include particle.h for you.



The other difference is that .ino files generate forward declarations for you. This is necessary when you’ve implemented a function later in the file than when you’ve first used it. For example, if you pass the function to something like Particle.subscribe in setup() but you’ve implemented it farther down the file.






share|improve this answer












I learned that I needed to include Arduino.h header file



apart from that I learned .ino files and .cpp files is that the .ino files transparently include particle.h for you.



The other difference is that .ino files generate forward declarations for you. This is necessary when you’ve implemented a function later in the file than when you’ve first used it. For example, if you pass the function to something like Particle.subscribe in setup() but you’ve implemented it farther down the file.







share|improve this answer












share|improve this answer



share|improve this answer










answered Nov 15 at 14:43









Ciasto piekarz

2741421




2741421








  • 2




    The technical name for that is a "forward reference". Historical note: the necessity to declare the function before a forward reference originated because early C compilers were written to read your source code only once, rather than once to find function and variable definitions and again to generate code once the components of it were known. Such a compiler was easier to write and ran faster (which was a bigger concern at the time than it is today).
    – JRobert
    Nov 15 at 15:44














  • 2




    The technical name for that is a "forward reference". Historical note: the necessity to declare the function before a forward reference originated because early C compilers were written to read your source code only once, rather than once to find function and variable definitions and again to generate code once the components of it were known. Such a compiler was easier to write and ran faster (which was a bigger concern at the time than it is today).
    – JRobert
    Nov 15 at 15:44








2




2




The technical name for that is a "forward reference". Historical note: the necessity to declare the function before a forward reference originated because early C compilers were written to read your source code only once, rather than once to find function and variable definitions and again to generate code once the components of it were known. Such a compiler was easier to write and ran faster (which was a bigger concern at the time than it is today).
– JRobert
Nov 15 at 15:44




The technical name for that is a "forward reference". Historical note: the necessity to declare the function before a forward reference originated because early C compilers were written to read your source code only once, rather than once to find function and variable definitions and again to generate code once the components of it were known. Such a compiler was easier to write and ran faster (which was a bigger concern at the time than it is today).
– JRobert
Nov 15 at 15:44


















draft saved

draft discarded




















































Thanks for contributing an answer to Arduino Stack Exchange!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.





Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


Please pay close attention to the following guidance:


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2farduino.stackexchange.com%2fquestions%2f57875%2fgetting-error-serial-was-not-declared-in-this-scope%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

How to change which sound is reproduced for terminal bell?

Title Spacing in Bjornstrup Chapter, Removing Chapter Number From Contents

Can I use Tabulator js library in my java Spring + Thymeleaf project?