Open
Conversation
Updated the project file for Visual Studio 2013
Introducing Basic Parameter, Diagnostic, and Macro Variable Read. Importantly, the functions are tested, however, they are not complete to handle every case of return type across byte, word and double word values.
Updated so that program names are also displayed in the case for FS30i and also updated cnc_statinfo() -> cnc_statinfo2()
…nux can be redistributed freely"
errors:
string_buffer.cpp: In member function ‘void StringBuffer::timestamp()’:
string_buffer.cpp:116:64: warning: format ‘%d’ expects argument of type ‘int’, but argument 3 has type ‘__suseconds_t {aka long int}’ [-Wformat=]
sprintf(mTimestamp + strlen(mTimestamp), ".%06dZ", tv.tv_usec);
^
logger.cpp: In member function ‘const char* Logger::timestamp(char*)’:
logger.cpp:79:58: warning: format ‘%d’ expects argument of type ‘int’, but argument 3 has type ‘__suseconds_t {aka long int}’ [-Wformat=]
sprintf(aBuffer + strlen(aBuffer), ".%06dZ", tv.tv_usec);
^
…lisware.com/wordpress/mtconnect-fanuc-adapter-on-ubuntu-linux/ Fix compile warnings about improper format specifiers (%ld for long int instead of %d) e.g. fanuc_adapter.cpp: In member function ‘void FanucAdapter::configMacrosAndPMC(const char*)’: fanuc_adapter.cpp:233:63: warning: format ‘%d’ expects argument of type ‘int’, but argument 3 has type ‘long int’ [-Wformat=] printf("Adding sample macro '%s' at location %d\n", name, v);
…nIni_07 folder for easy *nix builds
… to change case of header from FOCAS CD
…rs from gLogger calls. gLogger adds it's own newline, so log file was filling up with blank lines between log entries
…style command line switches and a short help message.
…start the adapter This allows multiple adapters to run side by side on the same machine and each can write to their own log files.
remove unnecesary newline characters
|
@mmxe may connect to focas/focas2's enabled controller? |
Author
|
Yes, I use it in my shop with FANUC 0i-MD and 0i-MF controllers (FOCAS2) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hi,
Can you review, test, and pull my linux-compat branch onto a new linux-compat branch in your repo?
I only have Fanuc machines so its only tested against FANUC, and the cmake files are FANUC specific as well.