Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is it really could open the pipe using krl_fopen in KSS8.3.22 ? #1

Open
davidrobot opened this issue Jan 29, 2018 · 4 comments
Open

Comments

@davidrobot
Copy link

davidrobot commented Jan 29, 2018

Hi

SWRITE (FILENAME[], STAT, OFFSET, "%s", "\\\\.\\pipe\\kukanet")
CWRITE($FCT_CALL, STAT, MODE, "krl_fopen", FILENAME[], "a", HANDLE)

when run the CWRITE step, it will return

{STATE_T: 
RET1 #CMD_ABORT,
**MSG_NO -16,**
MSG_TYPE "D",
HITS 0,
LENGTH 0
}

the code -16:
-16 At least one function parameter string contains invalid characters, e.g. \ * ? " < > : , = ; ] [ ) ( } {, for paths, etc.

@dddomodossola
Copy link
Owner

Hello @davidrobot , sure you can open a pipe, but the pipe have to be already opened by the other side. However the communication library doesn't work, I hadn't the time to do enough tests.

@davidrobot
Copy link
Author

davidrobot commented Jan 31, 2018

Hi.
I am sure the pipe is opened, I tested the pipe with Putty , the pipe works.
I think the problem is that it said the krl_fopen() can not open the path includes "\", but the pipe path includes ones.

@dddomodossola
Copy link
Owner

I was able to connect (open) the pipe from both sides, but unable to exchange data. Unfortunately I lost the corrected code because I have no access to the test robot I used. However I can remember there was something wrong in the code. Some tips to try:

  1. Increase the FILENAME size;
  2. Fill FILENAME with zeros before writing the filename content;
  3. Found some code elsewhere in my PC, try something like this "SWRITE (FILENAME[], STAT, OFFSET, "%s", "/kukanet/kukanet")";
  4. Found also a test to mount a network pipe "CWRITE($FCT_CALL, Stat, Mode, "krl_mount", "/kukanet","//192.168.2.106/pipe", "Everyone", "001F16DC43536C6D4E77DA00A00D6BE079")";

I hope you will be able to solve the problem! Would you like to work on this repo? I can share administrative priviledges with you.

@mgadaleta87
Copy link

Hello,
any update here?
I created a pipe on the Windows side of a KUKA KRC4 but I didn't find a way for connecting to it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants