l0:0:wait:/etc/init.d/rc 0l1:1:wait:/etc/init.d/rc 1l2:2:wait:/etc/init.d/rc 2l3:3:wait:/etc/init.d/rc 3l4:4:wait:/etc/init.d/rc 4l5:5:wait:/etc/init.d/rc 5l6:6:wait:/etc/init.d/rc 6# Normally not reached, but fallthrough in case of emergency.z6:6:respawn:/sbin/suloginS1:12345:respawn:/bin/start_getty 115200 ttyS1# /sbin/getty invocations for the runlevels.## The "id" field MUST be the same as the last# characters of the device (after "tty").## Format:# <id>:<runlevels>:<action>:<process>#

# 1:12345:respawn:/sbin/getty 38400 tty1

The last line is the one I add the "#".

I went to /etc/, /sbin/, /dev/ or root folder to use command "telinit q" command, I don't get any feedback, maybe it's normal, then I reboot.

At this point, I still can't see anything Node-RED.

So via PuTTY I called the "cat /dev/tty1" to see if I get a result after pressing a key, nothing.

So, I went through all the "tty" I can see in /dev/ folder via WinSCP.

Here are the commands I tried:

cat /dev/tty1

...

cat /dev/tty63

cat /dev/ttyGS0

cat /dev/ttyS0

cat /dev/ttyS1

cat /dev/ttyS2

cat /dev/ttyS3

Still nothing, I am not use to giving up easily.

Did you do something to connect USB host port to TTY1?

I feel like I am really close, but there is a little something missing.

Currently, I use a USB keyboard to be on the same level as you. At this point, I still can't see anything Node-RED.

So via PuTTY I called the "cat /dev/tty1" to see if I get a result after pressing a key, nothing.

As long as the "cat" command is active in Node-Red, you can't access the tty1 from any other command, so you have to stop the flow.

Make sure that no other process is using /dev/tty1 using this command:

ps auxww | grep tty1

Normally you would use "fuser" for this purpose, but I think this is not part of the IoT2000 image.

The next step is to look, which console has the input focus. On my machine this is tty1, on a normal PC this is a text console on the VGA card. On the IoT2000 it still exists but without VGA/HDMI output you will never see it. Normally you would use "fgconsole" but this is also not part of the IoT2000 image. With the tool "chvt" and using <ALT>-<1> to <8> you could switch the focus between tty1..tty8 (maybe even more), so avoid to press this key combination.

Here the output how it looks like when cat is already running in the Node-Red flow:

l0:0:wait:/etc/init.d/rc 0l1:1:wait:/etc/init.d/rc 1l2:2:wait:/etc/init.d/rc 2l3:3:wait:/etc/init.d/rc 3l4:4:wait:/etc/init.d/rc 4l5:5:wait:/etc/init.d/rc 5l6:6:wait:/etc/init.d/rc 6# Normally not reached, but fallthrough in case of emergency.z6:6:respawn:/sbin/suloginS1:12345:respawn:/bin/start_getty 115200 ttyS1# /sbin/getty invocations for the runlevels.## The "id" field MUST be the same as the last# characters of the device (after "tty").## Format:# <id>:<runlevels>:<action>:<process>#

# 1:12345:respawn:/sbin/getty 38400 tty1

Use "reboot" command to restart IOT2040

Right click on PuTTY header and select "Restart session" when you can ping IOT via command prompt.

Open Node-RED via your web browser using the IP address you configured on point 2.2 and add :1880 at the end of it, like that http://192.168.0.202:1800

Wait until "SD" led as stop blinking which is a sign the boot is finish.

Click on the button with 3 lines at the top right of web page, select "Import" and "Clipboard"