Hi,
I try to scan ibeacons through a script under Raspbian and send the result to pd but I have some problems...
Actually I think it's not a pd problem since I can send data using socket with a simple script like test_socket_to_pd-OK.sh

I can scan the ibeacon using ibeacon_scan_OK.sh but as soon as I put the two scripts together like ibeacon_scan_to_pd_socket_NOTOK.sh , I have many problems and nothing is received in pd...

If you have any idea why it dosen't work I would be very happy to hear about it since my Linux experience is still very new...

Thanks

yes, good idea @whale-av! ... after making it unix compatible (looks like you use windows), and make it even easier getting rid of the do_scan function (starting from the simple working ibeacon_scan_OK.sh script), I receive something in pd! but it's a blank character and an repeating "EOF on socket 14" but it's almost working.

I also only send the UUID at first to make it easier...

noob_attempt2.sh

@60htz Maybe the EOF can be fixed by adding the semi-colon....... as Pd expects that......

         echo "$UUID;" | pdsend ${pdport} ${pdhost} 

although the "while read line do" is a loop, so I would expect a repeating message (you had a repeating error before).

And maybe it even needs the curly brackets to get the value of the variable UUID....... whilst still sending the semi-colon..... but excluding it from the variable name???

         echo "${UUID};" | pdsend ${pdport} ${pdhost} 

Clutching at straws, but my noob rating is total.
Yes, I am using windows, so bash is weird stuff for me.

After more reading I wonder if

pdsend ${pdport} ${pdhost} <<< "$UUID;"

might work as it should bypass stdin and stdout....... which I am having trouble with....... and which might give "empty" values with echo?
....and maybe give UUID a value in the line above to check whether Ibeacon gave it an empty string...?

    UUID="test"
         echo "$UUID;" | pdsend ${pdport} ${pdhost} 

David.

Thanks a lot @whale-av, adding a simple semi-colon makes the value understandable in pd!

pdsend ${pdport} ${pdhost} <<< "$UUID;"

is also working, but I still have "EOF on socket 14" after every message in pd

@60htz It's great that you are having some success..... but this problem is making my head spin!
I understand that the data is sent into the pipe, and as there is no more data echo sends an EOF.
I don't know whether pdsend then closes, and has to restart for every pass of the "while" loop.
And of course the EOF will be sent after every message, before the loop goes around again.

Sleeping on it might help.... but it is "going over my head"........ https://stackoverflow.com/questions/8410439/how-to-avoid-echo-closing-fifo-named-pipes-funny-behavior-of-unix-fifos

AhHa!..... the answer might be here....https://stackoverflow.com/questions/15617418/pipe-to-executable-without-exiting-eof-in-bash
So maybe......

$ { echo "$UUID;"; cat; } | pdsend ${pdport} ${pdhost} 

Although I don't yet know what the initial $ means, or if it is necessary......!
Is it spawning a sub-process....... in which case that is what is required I think.
But a sub-process that sits and listens.... just taking in messages and sending them on.....
I think that is what you had with your first attempt....... but incorrectly implemented.

Can you live with it (the EOF messages) filtering them out with a [route EOF]........?
David.

@whale-av no, the cat function doesn't help here...

./noob_attempt5.sh: ligne 37: erreur de syntaxe près du symbole inattendu « } »
./noob_attempt5.sh: ligne 37: `         {echo "$UUID;"; cat;} | pdsend ${pdport} ${pdhost} '

I still have "EOF on socket 14" : the [netreceive 9999] object speak straight in the console so no way to filter it... sometimes the message change to socket 22... sometimes pd can' be closed and I need to kill it... so something might be wrong somewhere I guess!

then it changed to socket 22.
Also sometime I have port already in use (98)

On the pd side also It seems that I can't execute the working command with [shell]... it does nothing. Maybe the "while read line" is not friendly with shell?

@60htz Probably the last try for me....... or maybe not..... we will see.
I have messed about a bit in windows, and read a lot more about the differences with Linux.
I am loath to mess about with my RPI as it runs my whole house...... ! Time to buy a spare maybe.

Just a spippet.......line32-36 of the bash script....

          if [[ $2 == "-b" ]]; then
        echo "$UUID $MAJOR $MINOR $POWER" \ ; | pdsend 9999
          else
            echo "UUID: $UUID MAJOR: $MAJOR MINOR: $MINOR POWER: $POWER" \ ; | pdsend 9999
          fi

and here the whole..... but saved in windows........ sorry.... noob_attempt_no2.sh

In windows it doesn't matter if it is.......

" \ ; |
or
"\; |
((it must have the space before the pipe, but the others between " \ ; make no difference))

Then a question....... looking at your patch.... how does the bash script find the "pdsend" executable?
I would expect you might need to copy it into the same path as your script, or the same path as your patch.

I have to have a copy of pdsend in the folder where the script is running (root for you?).
And then, if it doesn't work........ permissions?
David.

@whale-av this solution still doesn't work...

./noob_attempt3.sh: ligne 37: erreur de syntaxe près du symbole inattendu « | »
./noob_attempt3.sh: ligne 37: `         echo "$UUID $RSSI" \ ; | pdsend ${pdport} ${pdhost} '

About the pdsend question, in linux the file is in /usr/bin/pdsend and it's a common place known by the system.

@60htz You can do it in 2 steps:

• first send the value to a file using > (ex: echo "hello" > sendtopd.txt)
• then use sed to add a ";" and pipe it to pdsend (ex: sed 's/$/;/' sendtopd.txt | pdsend 12345)

Cheers~