I can’t seem to get Scratch X working with my line-us. I have it connected to the local network and when I set up the program I do a connect to line-us.local and then instruction but nothing happens. If I try to go to line-us.local in my web browser it doesn’t work.
I believe I am using the latest firmware 2.0.4 as I updated it as the first thing I did. I also can not seem to find the ip address that the line-us is using to try to connect to that rather than the line-us.local.
Hi. Are you running on a mac or windows? On windows you may need to install bonjour print services. It could also potentially be a firewall issue so you could also try turning off firewall/AV software running on your PC.
You could also try re-starting your router to see if that helps.
To get you going quickly though if none of the above works log in to your router and find the IP address that way. It may show up in the list as ESP_XXXX - then use the IP address (e.g. something like 192.168.1.102) instead of line-us.local,
I have installed that print sever you suggested and unfortunately it doesn’t appear to have helped.
I have also tried disabling my bitdefender firewall and then tried to use Scratch X with no success.
I am fairly certain it is me doing something not quite right as the line-us works perfectly in the app. When programming in ScratchX do I need a connect to line-us.local (or IP which I have also tried) before giving it commands?
I have also tried inkspace and the LUS extension and am having trouble with that too could the issues be linked?
I can not see any settings in the bonjour print services program that would make anything better and the line-us is no listed as a shared printer.
If I try going to line-us.local it can not be found and if I go to the ip address of the line-us it takes me to a web page that says Welcome to Line-us and lists lots of technical details etc.
I believe everything it work but I am missing something.
Ok interesting in trying to get it working I followed the scratchX link from the “secret project Github page” and this page worked? When following the link from the line-us.com website it does not?
Also just one other question, now I have it working do you have any examples for ScratchX just to give a little push I am just trying to get my head round the co-ordinates system.
The examples we have aren’t very tidy at the moment, but should be enough to get you started. Durrell’s really the Scratch expert and his advice is to move the sprite (as in most if not all of the examples) and then use a block like this to send the sprite’s position to Line-us:
Of course you can just put your program on the stage if you prefer but definitely look at the sprite option if you haven’t before.
Because the Scratch stage is landscape shape the Line-us needs to be rotated for the drawing to match the screen:
I had problems with connecting via line-us.local but replacing that with the ip adress 1XX.xxx.x.xx:1337 worked to get connected.
The line-us will indicate connection as it would do with telnet ; running the newest firmware 3.0 (is there an updated command line summary pdf? )
But from here I can not get further - any chance to read the messages coming from the line-us? edit 3.3.2019 : in Chrome you can get messages in the console by pressing ctrl shift j.
The flow seems to stop somewhere - when I activate disconnect device can I immmediately reconnect
Could you share a project file (.sbx) one could load ? ah just saw the repository THX
I think the problem is that you’ve got the port number in the IP address. Try xxx.xxx.xxx.29 instead of xxx.xxx.xxx.29:1337. We run the Websockets server on the standard port - 1337 is just for the plain sockets interface used by the app.
That’s interesting - I’ll try to replicate the problem here - what were you seeing? Slowness or disconnects (or something else?). Good to hear that you got it working though.
After disabling the network cache all robots worked. It took a while to resolve the issue and it’s only a workaround. Our setup worked with less drawbots with the same repeater in another network.
That looks very odd - it’s having problems with Bonjour name resolution, but you mentioned that telnet worked, so name resolution must have been working at the OS level. If it happens again could you try another browser (e.g. firefox) before disabling the cache to try to establish whether it’s only affecting Chrome.
In general Bonjour can sometimes cause headaches - we put a lot of effort into the app to work around them but with Scratch running in the browser we don’t have the same level of control. Still, it’s important that it reliably connects in situations like yours so keep us up to date on how it goes.
One other question, what kind of WiFi hub are you using.
It’s really odd. I compared all the computers and browsers. Identical OS and browser version.
Firefox is not an option since we had to install historic Flash plugins on the students’ computers.
