Posts made by jevs

For anyone finding this and looking for an answer, this is a part failure in my case. Mine started working again today, but then went out again. Intermittent.

@t3p3tony Unfortunately it is older than that. The printer has low usage, but I have had it longer. I only use it once or so every few months.

@t3p3tonym/

@mfs12 No. I updated everything after it failed to see if it would help. It did not. I just turned it on one day and it looked like that.

Mine is doing the exact same thing. Out of the blue after booting up yesterday it looked like this. I updated my duet, erased and reflashed the paneldue and it looks the same. No loose connections to be found. Tapping around on everything changes nothing, so not an intermittent connection.

There was never any solution for this, so I assume I have to just buy a new one?

Yeah. A little more in depth info on the M540 section of the instruction set could be beneficial, but it all makes sense to me now.

Adding that entering "M540" by itself will report the MAC address would be great since it does work. This can be used to test that you are getting what you intended without going on the network and trying to find out if it is there, especially in a scenario where you do not have any control or access to the network controls.

You also cannot just randomly change digits. I put in "II" as the last two. Those are I's as in "eye"
This did not change the last digits to ":II". It actually messed up the whole MAC addess.

So, what I did was go to a random MAC address generator. Set the prefix to "be" like what the duet has in the default and then generated a made up MAC address.

For example if I generate a random MAC address specifying "be" as the prefix and the generator gives me be:dd:e0:d3:31:62, i would then enter this line in the config.g:

M540 P0xbe:0xdd:0xe0:0xd3:0x31:0x62

Once it saves the config.g and reboots, you can run "M540" from the G code command line and it will report the MAC as be:dd:e0:d3:31:62

So, as of now we have a static IP on the system assigned and the MAC address is showing up normal and just as I set it.

Success......finally. The documentation certainly needs some clarification on this one in my opinion.

M540 does return a MAC address.

I commented out the M540 MAC address line in the config.g
However, now, how would I tell what unique MAC address it assigned? How can I retrieve it?

@bot said in MAC Address issues:

Even better, simply remove the gcode to set the MAC address, as the ethernet version of the Duet 2 will generate a unique MAC address based on the MCU serial number, in the absence of a user-set MAC address.

I will experiment and try this. This seems like a good way if it works.

"Also, there's no reason that BE:EF:DE:AD:FE:EE would be an invalid MAC address, but they may have objections to using a human-chosen MAC."

The confusion is the extra characters because P0xBE:0xEF:0xDE:0xAD:0xFE:0xEE does not equal BE:EF:DE:AD:FE:EE to the average person, unless you know to decode it that way. It does not state this in the documentation in a clear way. Most people may not know that. I had a feeling it was something like this, but no way to read and verify that I found so far.... I never gave MAC addresses a second thought until today, so I would not have known that.

The documentation is not totally clear on this, but now it makes more sense after this conversation.

From the manual:
M540: Set MAC address
Parameters

Pnnn The MAC address
Examples

M540 P0xBE:0xEF:0xDE:0xAD:0xFE:0xED
M540 PDE:AD:BE:EF:CA:FE
Sets the http://en.wikipedia.org/wiki/MAC_address of the printer. This should be done before any other network commands. The MAC address is six one-byte hexadecimal numbers separated by colons. The 0x prefix is optional.

All devices running on the same network shall all have different MAC addresses. For your printers, changing the last digit is sufficient.

Note on the Duet 2 Wifi the MAC address is unique and set on the Wifi Module so this command has no effect. The default MAC address on a Duet 2 Ethernet is generated from the unique processor ID so there is normally no need to change it.

So if I want to enter my own MAC address of lets say 3B:C5:14:FA:21:8C for example. I believe I would enter:

M540 P0x3B:0xC5:0x14:0xFA:0x21:0x8C
or
M540 P3B:C5:14:FA:21:8C

Would these end up the same MAC address of 3B:C5:14:FA:21:8C ?

I need a real MAC address to set up a static IP on the ethernet board. I had to get rid of the Wi-Fi version because nothing would allow it to properly move a file at a reasonable speed and without crashing.
I have the ethernet version working now, but I want to give it a static IP.
However, the MAC address is in a format I cannot use: P0xBE:0xEF:0xDE:0xAD:0xFE:0xEE
I know this is just some generic filler, but the IT guys can't work with this. It does not seem to be a supported format or values.

Can I just make up a MAC address and enter it in the config in a more conventional format like MM:MM:MM:SS:SS:SS ? Like using a generator to randomly create something like 3B:C5:14:FA:21:8C ?

I am not sure what format I should use or enter, I am just researching this as of today, but I need to get this locked down.

I have done some more troubleshooting and there seems to be an issue with it's communication to the WIFI system we are using here at work with the printer.
I set my phone to a WIFI hotspot and connected to that fine and moved files over at a proper speed (500-600 KiB/s).
The speed on the regular Wifi bottoms out at about 10 KiB/s, so there is something going on with that communication. The IT guy is looking into it further.
From the router side so far it is reporting that everything looks good from what they checked so far, but there is some thing amiss.

I cannot seem to solve communications issues.
It has always been very slow to move a file to the printer and if the file is very big it times out.
It has also dropped part of the file and then I don't notice until the print stops with the nozzle burning into the print. When I look I realizes not all the layers are showing.

M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.02(RTOS) running on Duet WiFi 1.02 or later + DueX5
Board ID: 08DGM-9T6BU-FG3SN-6JKD6-3S86L-KAZRF
Used output buffers: 3 of 20 (20 max)
=== RTOS ===
Static ram: 25524
Dynamic ram: 98560 of which 0 recycled
Exception stack ram used: 488
Never used ram: 6500
Tasks: NETWORK(ready,544) HEAT(blocked,1232) MAIN(running,3812) IDLE(ready,200)
Owned mutexes:
=== Platform ===
Last reset 02:21:04 ago, cause: power up
Last software reset at 2019-02-07 14:53, reason: User, spinning module GCodes, available RAM 6388 bytes (slot 1)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
Error status: 16
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 351.3ms, max retries 0
MCU temperature: min 45.0, current 45.7, max 46.2
Supply voltage: min 24.1, current 24.2, max 24.4, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: standstill, SG min/max not available
Driver 1: standstill, SG min/max not available
Driver 2: standstill, SG min/max not available
Driver 3: standstill, SG min/max not available
Driver 4: standstill, SG min/max not available
Driver 5: standstill, SG min/max not available
Driver 6: standstill, SG min/max not available
Driver 7: standstill, SG min/max not available
Driver 8: standstill, SG min/max not available
Driver 9: standstill, SG min/max not available
Date/time: 2019-02-12 12:23:12
Cache data hit count 4294967295
Slowest loop: 75.10ms; fastest: 0.08ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0
=== Move ===
Hiccups: 0, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm: 240, MaxWait: 0ms, Underruns: 0, 0
Scheduled moves: 23, completed moves: 23
Bed compensation in use: none
Bed probe heights: 0.000 0.000 0.000 0.000 0.000
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
Heater 1 is on, I-accum = 0.5
=== GCodes ===
Segments left: 0
Stack records: 1 allocated, 0 in use
Movement lock held by null
http is idle in state(s) 0
telnet is idle in state(s) 0
file is idle in state(s) 0
serial is idle in state(s) 0
aux is idle in state(s) 0
daemon is idle in state(s) 0
queue is idle in state(s) 0
autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 353.21ms; fastest: 0.00ms
Responder states: HTTP(1) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 1 of 8

• WiFi -
  Network state is running
  WiFi module is connected to access point
  Failed messages: pending 0, notready 0, noresp 1
  WiFi firmware version 1.22
  WiFi MAC address 84:f3:eb:82:db:11
  WiFi Vcc 3.40, reset reason Turned on by main processor
  WiFi flash size 4194304, free heap 29000
  WiFi IP address 10.106.10.17
  WiFi signal strength -57dBm, reconnections 0, sleep mode modem
  Socket states: 2 0 0 0 0 0 0 0