Langstone V3 Update

[g4eml]

Langstone V3 now also supports the new Raspberry Pi V2 display.

The installation process remains the same. The new display is automatically detected.

Note that if you are replacing the display on an existing system you will need to create a new SD card and do a clean install. The operating system doesn't seem to like the display being changed on an already configured system.

I can also confirm that although Langstone V3 was developed and tested on a Raspberry Pi 5 it does appear to run OK on the older Raspberry Pi 4.

Colin G4EML

[Pa3fbx]

Finally i got around to try Langstone V3. Installation was simple but getting it to work was a bit more hardware.

I've got v2 working for 5 years so i was thinking V3 was simple..
But The RPI5 would not accept my V1 Display flatcable..
Last week i finally decided to invest in a v2 Display with the right flatcable.
But a V2 Display would fit in a V1 display case.. So a bigger 3D print job and 40 hours later i can make a decent setup.

I found that de display stays dark (black) until the langstone was booted.
This could be something about not having a display while creating a SD card.

Now the V3 version finds a pluto+ on my network and it seems to work.
Only i have multiple pluto's on my network and i want to move to a different IP.

On v2 the ./set_pluto was simple but those commands do not work anymore on V3??

Or did i miss something and should i restart a fresh install with the new display 2 installed??

Should all V2 commands still work on V3 or is Trixie changing the controlls..

best regards
Benno

[g4eml]

Hi Benno,

The first run of the OS after building the SD card seems to make some changes depending on which Screen is fitted. I haven't worked out exactly what it changes but a system built with a V1 screen won't work correctly if the screen is then changed to a V2. So I would always recommend doing a fresh SD card build with the correct screen attached.

The Set_Pluto command should still work. All it does is change one line in the run script. You can also change that line by manual editing if necessary.

Just edit the run file and change the line that reads

export PLUTO_IP=pluto.local

Colin G4EML

[Pa3fbx]

To be 100% sure i made a fresh install
followed the guidlines to the letter.
But still same issue.

It finds a pluto_local on my network (x.x.1.16)
But i want it to use x.x.1.17

So if i do cd to Langstone i find the set_pluto..
i do a sudo ./set_pluto i get...
Langstone Pluto Device Selection
--------------------------------
Please enter the Pluto IP address. (e.g. pluto.local or 192.168.2.1)

: not found: 7: echo
192.168.1.17
: bad variable named: PLUTO_IP
: not found: 9:
: No such file or directorytone/run
: No such file or directorytone/stop
: not found: 12:
: not found: 13: echo
Langstone has been updated to use
: not found: 15: echo
: not found: 16: echo
: not found: 17:
: not found: 18:
: not found: 19:
-bash: Langstone: command not found
-bash: --------------------------------: command not found
-bash: syntax error near unexpected token `('
-bash: 192.168.1.17: command not found
-bash: Langstone: command not found

this is what worked for me.
sudo sed -i "s/export PLUTO_IP=.*/export PLUTO_IP=x.x.1.17/" $HOME/Langstone/run
sudo sed -i "s/PLUTO_IP=.*/PLUTO_IP=x.x.1.17/" $HOME/Langstone/stop
./stop
./run



benno

[g4eml]

You should not need sudo to run set_pluto, but it also shouldn't cause any problem.

I don't have access to my test system at the moment, maybe over the weekend.

As mentioned before you can always just use the nano editor directly on the run script and change the PLUTO_IP setting.

Colin.