Chain Startup Sequence Documentation

DUELink
1

The following text is from the Internal Engine section of the documentation. It discusses the startup sequence using a terminal program.

The first thing you do is hit enter. This is required by the module on power up so it can detect the correct Interface. This will result with >prompt. It is possible that a module is running an internal script with an infinite loop and it does not respond to commands. In this case, pressing the escape key will terminate the running internal script.

To be safe, just hit escape then enter! You will for sure see > prompt coming back. The device is now ready to accept commands in Immediate Mode.

My question is about the last paragraph. With scripts running on the chain, I have found that sending escape and then enter, on startup, does not work for me. Reversing the sequence, enter before escape, does work.

Am I confused again or again confused?

2

Hi Mike, did you hit escape on console or TeraTerm?

I don’t think hitting escape on console is supported for now.

And it does only work on selected device, default is device 1.

3

I noticed the issue on a Mac terminal program and a library I am developing for another language.

It shows up when attaching to a just booted chain with a script running on device 3.

I needed to verify on a windows machine.

4

Enter (empty command) is needed to set the interface. Escape terminates a running program.

So, if a module powered up and is running a program, it will need a valid command (enter is an empty command) to know what interface needs to be selected. After that, you can send escape to terminate a running program.

Does this help? Are you seeing something else?

5

Oh I see it now, the docs needs to be corrected.

1 Like