Glitchyness with TCP Request

#1

This flow worked fine in the past v0.18.x but is mis-behaving now in v0.19.1

Press 1st time without Scratch running - get 1st error msg - all as expected

Start up Scratch with RSC enabled
press 2nd time - all fine

press 3rd time - get that 2nd error message

it may be an issue with my machine so it'd be nice if someone could test it out on a machine with Scratch 1.4 on it.. Just need to enable remote sensor connections by right clicking on bottom block in sensing category

[{"id":"75339fa9.b338f","type":"inject","z":"60eeba5b.7c29b4","name":"","topic":"","payload":"","payloadType":"date","repeat":"","crontab":"","once":false,"onceDelay":0.1,"x":880,"y":40,"wires":[["3e4e8867.432a28"]]},{"id":"3e4e8867.432a28","type":"change","z":"60eeba5b.7c29b4","name":"set payload to string:broadcast \"TestFromNR\"","rules":[{"t":"set","p":"payload","pt":"msg","to":"broadcast \"TestFromNR\"","tot":"str"}],"action":"","property":"","from":"","to":"","reg":false,"x":990,"y":100,"wires":[["c9604942.0310d8"]]},{"id":"c9604942.0310d8","type":"function","z":"60eeba5b.7c29b4","name":"String to Buffer conversion","func":"var msglength = msg.payload.length;\nvar msgbuff = new Buffer(msg.payload, \"utf-8\")\nvar outbuff = new Buffer(4 + msglength);\nmsgbuff.copy(outbuff,4);\noutbuff[3] = msglength;\nmsg.payload = outbuff;\nreturn msg;","outputs":1,"noerr":0,"x":940,"y":180,"wires":[["83d17bb5.156968","3591a767.4fc0a8"]]},{"id":"83d17bb5.156968","type":"tcp request","z":"60eeba5b.7c29b4","server":"127.0.0.1","port":"42001","out":"sit","splitc":" ","name":"","x":920,"y":240,"wires":[["78ed4e75.7fc6a"]]},{"id":"3591a767.4fc0a8","type":"debug","z":"60eeba5b.7c29b4","name":"SENT","active":true,"tosidebar":true,"console":false,"tostatus":false,"complete":"payload","x":1210,"y":180,"wires":[]},{"id":"78ed4e75.7fc6a","type":"debug","z":"60eeba5b.7c29b4","name":"RECEIVED","active":true,"tosidebar":true,"console":false,"tostatus":false,"complete":"true","x":1190,"y":240,"wires":[]}]

1 Like

#2

JFI I noticed that 0.19.3 had been published a couple of days ago so I upgraded my WIn10 machine and the bug has gone :slight_smile:

0 Likes