Newb initial Maestro network setup via terminal

[splicer]

I am the proud owner of a new Duet 2 Maestro and am excited to get started. Unfortunately, I'm having trouble getting the "getting started" started.

I connect to the board well enough over USB using SerialTools on a Mac, and I get the following message:

RepRapFirmware for Duet 2 Maestro is up and running.

But instead of seeing "OK" when I issue an M command I see nothing at all until I try to type another command. After the first keystroke I receive a series of "Bad command" messages which look like the board is feeding its own output back to itself rather than displaying them to me:

M115
Bad command: d command: re/releases/
ok
Bad command: ok
ok
Bad command: mmand: 552s://github.com/dc42/RepRvad command: ok
ok
Bad command: ok
ok
Bad command: and: qttps://github.com/dc42/RepRapFirmware/rad command: 1ad command: A
ok
Bad command: ok
ok
Bad command: epRapFirmware/r
ok
Bad command: d command: rmware/releases/
ok
Bad command: ok
ok
Bad command: 
ok
Bad command: ok
ok
Bad command: vad command: ok
ok
Bad command: ok
ok
Bad command: mmand: ok
ok
Bad command: ok
ok
 

It looks as though I've botched something fundamental but I've been trying different settings in the terminal and have been unsuccessful in getting it to respond as described in the Getting Connected guide.

The next thing that I will try is setting up a dummy local network to connect to DWC without first reconfiguring any settings. But that seems like Doing It Wrong because it's not what the instructions say. When getting something started for the first time I like to try it the way I'm supposed to. I can try non-standard stuff later.

Any suggestions appreciated!

[A Former User]

@splicer said in Newb initial Maestro network setup via terminal:

It looks as though I've botched something fundamental but I've been trying different settings in the terminal and have been unsuccessful in getting it to respond as described in the Getting Connected guide.

I think that might be the result of lines that are not comments in your config.g file?

Try sending a few blank lines to clear out any buffered stuff and then send M552 S1 to enable networking?

[splicer]

Thank you!

If there are uncommented junk lines in my config.g file then I ought to pull the card, open it on another computer, and edit it? I would have done that except the config.g file on the card says explicitly not to edit or use it.

If I hit enter five times to send five blank lines I get a string of "bad command" messages as above. Typing "M552" and then a space similarly sends me a string of "bad command" messages without giving me a chance to hit enter and send it. It looks to me as though any five keystrokes sent results in string of "bad command" messages. I can get the whole string in if I paste it rather than type it as instructed here: https://duet3d.dozuki.com/Guide/1.)+Getting+Connected+to+your+Duet/7

… but there again, after pasting, it takes four keystrokes (be they Enter or Space or what have you) to get the string of "bad command" messages.

Although they do have different messages. Example:

M552 Bad command: mand: 552s://github.com/dc42/ReM
ok
Bad command: d command: d command: ok
ok
Bad command: ok
ok
Bad command: ok
ok
Bad command: c42/RepRapFirmware/releases/
ok
Bad command: ok5
ok
Bad command: d command: 1
ok
Bad command: ok
ok
Bad command: s/
ok
Bad command: ok
ok
Bad command: ok 552: Bad IP address
ok
Bad command: ok
ok
Bad command: ok
ok
Bad command: eases/
ok
Bad command: ok
ok
Bad command: 5
ok
Bad command: d command: re/releases/
ok
Bad command: ok
ok
Bad command: mmand: 552s://github.com/dc42/RepR2
ok
Bad command: d command: ok
ok
Bad command: ok
ok
Bad command: and: qttps://github.com/dc42/RepRapFirmware/r 
ok
Bad command: d command: 1ad command: A
ok
Bad command: ok
ok
 

The result of M552 S0 pasted (plus hitting enter four times) follows:

M552 S0
 
 
 
 
Bad command: epRapFirmware/r
ok
Bad command: d command: rmware/releases/
ok
Bad command: ok
ok
Bad command: 
ok
Bad command: ok
ok
Bad command: d command: ok
ok
Bad command: ok
ok
Bad command: mmand: ok
ok
Bad command: ok
ok
Bad command: r Duet 2 Maestro FIRMWARE_VERSIO
ok
Bad command: d command: ok
ok
Bad command: ok
ok
Bad command: releases/
ok
Bad command: ok
ok
Bad command: mand: 552s://github.com/dc42/Re
ok
Bad command: d command: d command: ok
ok
Bad command: ok
ok
Bad command: ok
ok
Bad command: c42/RepRapFirmware/releases/
ok
Bad command: ok
ok
Bad command: d command: 1
ok
Bad command: ok
ok
Bad command: s/
ok
Bad command: ok
ok
Bad command: ok 552: Bad IP address
ok
Bad command: ok
ok
Bad command: ok
ok
Bad command: eases/
ok
Bad command: ok
ok
 

[A Former User]

I can't say for sure where the extra stuff comes from, but it'll be the config.g on the SD card or from the serial port somehow.

I guess the easy test is to remove the SD card and try the usb serial terminal then.

@splicer said in Newb initial Maestro network setup via terminal:

… but there again, after pasting, it takes four keystrokes (be they Enter or Space or what have you) to get the string of "bad command" messages.

you'll need to send new lines (enter) until you no longer get a bad command to ensure whichever buffer contains the bad commands is cleared.

[A Former User]

@splicer said in Newb initial Maestro network setup via terminal:

the config.g file on the card says explicitly not to edit or use it.

looks a bit like https://github.com/T3P3/Duet/blob/master/Duet2/SD Card Contents/sys/config.g ?

the link at the bottom is a good starting point to make a suitable config

; M117 Use https://configurator.reprapfirmware.org/ to set up your printer config

[droftarts]

@splicer have you tried using the method in the documentation, ie using the Mac terminal? ie

Mac OSX Users: Open Applications > Utilities > Terminal .
Run ls /dev/tty.* Copy the result that has USB in the name. For example; /dev/tty.usbmodem1411
Run screen /dev/tty.usbmodem1411 115200. Replace "usbmodem1411" with the result you received. You should see a blank screen. Hit enter and you should see OK returned. You are connected successfully.

I’ve never had much success with Mac serial terminal software, but it may just be the settings. Old versions of Pronterface do work, but depends on which version of MacOS you’re on as to whether it will run.

See if you get the same response using the documented method.

Ian

[splicer]

I may have discovered the problem. I found another computer to plug in to the card with, and it responds to commands just as described everywhere. So my guess is I have a bad FTDI driver on the other machine. It would explain the gobbledygook.

I'm proceeding with cautious optimism. I also discovered I have one bad network port on my hub. Better to discover this now than get further into the process and wonder why everything still isn't working!

Edited the config.g with network config and I'm now in through the DWC!

I have a lot to learn here, but that's easier to do when everything looks like the docs say they should!

[splicer]

@droftarts said in Newb initial Maestro network setup via terminal:

See if you get the same response using the documented method.

Thanks, I should have mentioned that first. I did use screen first and had the described behavior. I switched to SerialTools in an attempt to try to get to the bottom of it.

I'll look at that computer and see what I did to mess it up. As I said just a moment ago, I may have a bad (or at least incompatible) FTDI driver on that machine left over from programming Sumobots. In the meantime, I have web access so serial access is less important.

Thank you so much!

[Phaedrux]

PronterFace on the Mac works as a suitable terminal app for the Duet. Though it hasn't been updated in a long time and I don't think it will work with Catalina.