FreeEMS communications stress testing
Re: freeems communications stress testing
Feedback (yes, already) :
1) Remove or obfuscate your email to reduce spam!
2) You shouldn't have/don't need to have the gpl header in the readme file, you can just tell them for information purposes what the license used is.
3) You should include the text version of the license and/or link to the gnu.org site with that on it.
4) GREAT to see doxygen from the start! :-)
5) There isn't much more to comment on! But it's great to see a git repo properly setup already. I'll clone it now, please setup the irc hook to announce in #freeems-dev, just use the channel, irc.freenode.net the port and check the activate box at the bottom and it should work.
Keep up the good work :-)
Fred.
1) Remove or obfuscate your email to reduce spam!
2) You shouldn't have/don't need to have the gpl header in the readme file, you can just tell them for information purposes what the license used is.
3) You should include the text version of the license and/or link to the gnu.org site with that on it.
4) GREAT to see doxygen from the start! :-)
5) There isn't much more to comment on! But it's great to see a git repo properly setup already. I'll clone it now, please setup the irc hook to announce in #freeems-dev, just use the channel, irc.freenode.net the port and check the activate box at the bottom and it should work.
Keep up the good work :-)
Fred.
DIYEFI.org - where Open Source means Open Source, and Free means Freedom
FreeEMS.org - the open source engine management system
FreeEMS dev diary and its comments thread and my turbo truck!
n00bs, do NOT PM or email tech questions! Use the forum!
The ever growing list of FreeEMS success stories!
FreeEMS.org - the open source engine management system
FreeEMS dev diary and its comments thread and my turbo truck!
n00bs, do NOT PM or email tech questions! Use the forum!
The ever growing list of FreeEMS success stories!
Re: freeems communications stress testing
Error on macports macosx :
Code: Select all
freeair:freeems-cst fred$ make
Scanning dependencies of target cst
[ 50%] Building CXX object src/CMakeFiles/cst.dir/main.cpp.o
cc1plus: warnings being treated as errors
In file included from /opt/local/include/boost/lambda/lambda.hpp:23,
from /Users/fred/Desktop/workspaces/home/freeems-cst/src/main.cpp:26:
/opt/local/include/boost/lambda/detail/operator_return_type_traits.hpp:494: warning: use of old-style cast
/opt/local/include/boost/lambda/detail/operator_return_type_traits.hpp:494: warning: use of old-style cast
make[2]: *** [src/CMakeFiles/cst.dir/main.cpp.o] Error 1
make[1]: *** [src/CMakeFiles/cst.dir/all] Error 2
make: *** [all] Error 2
DIYEFI.org - where Open Source means Open Source, and Free means Freedom
FreeEMS.org - the open source engine management system
FreeEMS dev diary and its comments thread and my turbo truck!
n00bs, do NOT PM or email tech questions! Use the forum!
The ever growing list of FreeEMS success stories!
FreeEMS.org - the open source engine management system
FreeEMS dev diary and its comments thread and my turbo truck!
n00bs, do NOT PM or email tech questions! Use the forum!
The ever growing list of FreeEMS success stories!
Re: freeems communications stress testing
No problem! Thanks for the app, looking forward to those bug reports! :-)
DIYEFI.org - where Open Source means Open Source, and Free means Freedom
FreeEMS.org - the open source engine management system
FreeEMS dev diary and its comments thread and my turbo truck!
n00bs, do NOT PM or email tech questions! Use the forum!
The ever growing list of FreeEMS success stories!
FreeEMS.org - the open source engine management system
FreeEMS dev diary and its comments thread and my turbo truck!
n00bs, do NOT PM or email tech questions! Use the forum!
The ever growing list of FreeEMS success stories!
Re: freeems communications stress testing
Can I get the packet checksum calculation method added to FreeEMS-SerialProtocolCoreSpecification.odt ? I want to avoid peeking into anyone else's implementation.
To get started, is it just a simple rolling sum ?
To get started, is it just a simple rolling sum ?
Re: freeems communications stress testing
At the moment it is just "byte + byte + byte + byte + byte = one byte checksum" how would you like that written in the document. I thought it already was, but you want it more specific/explicit (and for good reason) so can you suggest how you would write it?
Fred.
Fred.
DIYEFI.org - where Open Source means Open Source, and Free means Freedom
FreeEMS.org - the open source engine management system
FreeEMS dev diary and its comments thread and my turbo truck!
n00bs, do NOT PM or email tech questions! Use the forum!
The ever growing list of FreeEMS success stories!
FreeEMS.org - the open source engine management system
FreeEMS dev diary and its comments thread and my turbo truck!
n00bs, do NOT PM or email tech questions! Use the forum!
The ever growing list of FreeEMS success stories!
Re: freeems communications stress testing
So I'm new to cpp and I'm already in love:
is actually caught at compile time! templates are the sh!t.
where the following was actually intended .. so the deref in the coming iterator actually matches the qualifier on the declaration
took me forever to figure out that there was a ::const_iterator, thanks http://cplusplus.com/reference/stl/vector/
checkin will follow shortly and I'll need comments from the cpp experts out there.
Code: Select all
/**
* @public
* @brief encode a flattened packet
* @param[in] p reference to flattened packet
* @retval vector<uint8_t> packet encoded in accordance with the freeems
* core protocol spec. caller is responsible for
* destruction when use is complete.
*/
std::vector<uint8_t> *
feEncoder::encode( std::vector<uint8_t> const &p )
{
std::vector<uint8_t> *const v = new std::vector<uint8_t>();
v->reserve( 1024 * 4 ); /**< reserve initial worst case capacity */
std::vector<uint8_t>::iterator pkt_iter = p.begin();
......
}
where the following was actually intended .. so the deref in the coming iterator actually matches the qualifier on the declaration
Code: Select all
/**
* @public
* @brief encode a flattened packet
* @param[in] p reference to flattened packet
* @retval vector<uint8_t> packet encoded in accordance with the freeems
* core protocol spec. caller is responsible for
* destruction when use is complete.
*/
std::vector<uint8_t> *
feEncoder::encode( std::vector<uint8_t> [color=#FF0000]const[/color] &p )
{
std::vector<uint8_t> *const v = new std::vector<uint8_t>();
v->reserve( 1024 * 4 ); /**< reserve initial worst case capacity */
std::vector<uint8_t>::[color=#FF0000]const_iterator[/color] pkt_iter = p.begin();
......
}
checkin will follow shortly and I'll need comments from the cpp experts out there.
Re: freeems communications stress testing
https://github.com/EssEss/freeems-cst/c ... ...cac6424
my last test is failing for some reason .. although its looks like its encoded correctly. anyways ...
I'd like an experienced cpp dev to look over my encode function (starting small) and I'll start moving things to a library and build off of it.
edit -> fixed -> https://github.com/EssEss/freeems-cst/c ... 5583c61e22
my last test is failing for some reason .. although its looks like its encoded correctly. anyways ...
I'd like an experienced cpp dev to look over my encode function (starting small) and I'll start moving things to a library and build off of it.
edit -> fixed -> https://github.com/EssEss/freeems-cst/c ... 5583c61e22
Re: freeems communications stress testing
Great to see progress on this! I did some payload id fixes this evening, I'm trying to beat you to finding issues with it :-) Testing is essential, and my hand testing tonight proves that, yet again! :-) Looking forward to your 15 page report on how shit my work is.
DIYEFI.org - where Open Source means Open Source, and Free means Freedom
FreeEMS.org - the open source engine management system
FreeEMS dev diary and its comments thread and my turbo truck!
n00bs, do NOT PM or email tech questions! Use the forum!
The ever growing list of FreeEMS success stories!
FreeEMS.org - the open source engine management system
FreeEMS dev diary and its comments thread and my turbo truck!
n00bs, do NOT PM or email tech questions! Use the forum!
The ever growing list of FreeEMS success stories!
- nitrousnrg
- LQFP144 - On Top Of The Game
- Posts: 468
- Joined: Tue Jun 24, 2008 5:31 pm
Re: freeems communications stress testing
EssEss, I'm looking forward for you code, I'd really like to have someone else's code in charge of communications for ecumanager :-)
What I did in Debian was just
# aptitude install libboost1.42-dev
Others could also do:
# aptitude install libboost1.42-dev cmake g++
I already had those packages.
Anyway, I can't build it:
After
cd <build_dir>
cmake <path_to_src>
make
I get the following error:
My cmake version is 2.8.2,
boostversion: 1.42
I took a look at the makefiles and cmakefiles, but can't find references to the inc/ directory. I don't know cmake, so I could be going in a totally wrong direction.
Cheers
What I did in Debian was just
# aptitude install libboost1.42-dev
Others could also do:
# aptitude install libboost1.42-dev cmake g++
I already had those packages.
Anyway, I can't build it:
After
cd <build_dir>
cmake <path_to_src>
make
I get the following error:
Code: Select all
marcos@nitrousPresario:~/electronica/programas/freeems-cst$ make
Scanning dependencies of target cst
[ 33%] Building CXX object CMakeFiles/cst.dir/main.cpp.o
/home/marcos/electronica/programas/freeems-cst/EssEss-freeems-cst-ab4066a/src/main.cpp:26:18: error: main.h: No such file or directory
make[2]: *** [CMakeFiles/cst.dir/main.cpp.o] Error 1
make[1]: *** [CMakeFiles/cst.dir/all] Error 2
make: *** [all] Error 2
marcos@nitrousPresario:~
boostversion: 1.42
I took a look at the makefiles and cmakefiles, but can't find references to the inc/ directory. I don't know cmake, so I could be going in a totally wrong direction.
Cheers
Marcos