Posts made by wuem

@dc42
Thank you. Now it finally worked...

@dc42 I checked the settings and they are the same as you show in your settings:

But what I realised is that I don't have a LibTinyusb/src/tinyusb/src folder (only LibTinyusb/src/tinyusb):

Could this be the problem?

@dc42
Ok. That helped. Now I am moving forward. Compiling for Duet2 now works. When I want to complie for Duet3_MB6HC with the required board configurations, I get for the CoreN2G the following errors:

So, there seems something else missing. How to fix this?

@dc42
Thank you. That helped somehow. My problem is, that in the workspace, the folder is called WiFiSocketServerRTOS, but in the compiler settings, it is called DuetWiFiSocketServerRTOS. This must have been the reason that it was not able to find it. So, now I added WiFiSocketServerRTOS to the paths. And then this error was solved.

I then downloaded everything again from GitHub and now, this problem didn't appear any longer (the path has the right name).

But now, I get the next errors (which I also had before):

../WiFiSocketServerRTOS-main/src/esp8266/HSPI.cpp:23:10: fatal error: esp_attr.h: No such file or directory
23 | #include "esp_attr.h"
| ^~~~~~~~~~~~
compilation terminated.
make[1]: *** [WiFiSocketServerRTOS-main/src/esp8266/HSPI.o] Error 1
make[1]: *** Waiting for unfinished jobs....
Building file: ../WiFiSocketServerRTOS-main/src/esp8266/gpio.c
Invoking: Cross GCC Compiler
arm-none-eabi-gcc -std=gnu99 -D__SAME70Q20B__ -DRTOS -DDUET3_MB6HC -DMQTTC_PAL_FILE="Networking/MQTT/mqtt_pal.h" -Dnoexcept= -I"/Users/zhaw/Documents/Studienarbeiten/PA_BA/BA25/BA_FS_25_wuem_185_HighSpeed/Firmware/Build/RepRapFirmware-3.6-dev/LibTinyusb-master" -I"/Users/zhaw/Documents/Studienarbeiten/PA_BA/BA25/BA_FS_25_wuem_185_HighSpeed/Firmware/Build/RepRapFirmware-3.6-dev/CoreN2G-3.6-dev" -I"/Users/zhaw/Documents/Studienarbeiten/PA_BA/BA25/BA_FS_25_wuem_185_HighSpeed/Firmware/Build/RepRapFirmware-3.6-dev/FreeRTOS-3.5-dev" -I"/Users/zhaw/Documents/Studienarbeiten/PA_BA/BA25/BA_FS_25_wuem_185_HighSpeed/Firmware/Build/RepRapFirmware-3.6-dev/CoreN2G-3.6-dev/src" -I"/Users/zhaw/Documents/Studienarbeiten/PA_BA/BA25/BA_FS_25_wuem_185_HighSpeed/Firmware/Build/RepRapFirmware-3.6-dev/CoreN2G-3.6-dev/src/SAM4S_4E_E70" -I"/Users/zhaw/Documents/Studienarbeiten/PA_BA/BA25/BA_FS_25_wuem_185_HighSpeed/Firmware/Build/RepRapFirmware-3.6-dev/CoreN2G-3.6-dev/src/SAM4S_4E_E70/asf" -I"/Users/zhaw/Documents/Studienarbeiten/PA_BA/BA25/BA_FS_25_wuem_185_HighSpeed/Firmware/Build/RepRapFirmware-3.6-dev/CoreN2G-3.6-dev/src/SAM4S_4E_E70/asf/sam/drivers" -I"/Users/zhaw/Documents/Studienarbeiten/PA_BA/BA25/BA_FS_25_wuem_185_HighSpeed/Firmware/Build/RepRapFirmware-3.6-dev/CoreN2G-3.6-dev/src/SAM4S_4E_E70/asf/sam/utils" -I"/Users/zhaw/Documents/Studienarbeiten/PA_BA/BA25/BA_FS_25_wuem_185_HighSpeed/Firmware/Build/RepRapFirmware-3.6-dev/CoreN2G-3.6-dev/src/SAM4S_4E_E70/asf/common/utils" -I"/Users/zhaw/Documents/Studienarbeiten/PA_BA/BA25/BA_FS_25_wuem_185_HighSpeed/Firmware/Build/RepRapFirmware-3.6-dev/CoreN2G-3.6-dev/src/SAM4S_4E_E70/asf/sam/utils/preprocessor" -I"/Users/zhaw/Documents/Studienarbeiten/PA_BA/BA25/BA_FS_25_wuem_185_HighSpeed/Firmware/Build/RepRapFirmware-3.6-dev/CoreN2G-3.6-dev/src/SAM4S_4E_E70/asf/sam/utils/header_files" -I"/Users/zhaw/Documents/Studienarbeiten/PA_BA/BA25/BA_FS_25_wuem_185_HighSpeed/Firmware/Build/RepRapFirmware-3.6-dev/CoreN2G-3.6-dev/src/SAM4S_4E_E70/asf/sam/utils/cmsis/same70/include" -I"/Users/zhaw/Documents/Studienarbeiten/PA_BA/BA25/BA_FS_25_wuem_185_HighSpeed/Firmware/Build/RepRapFirmware-3.6-dev/CoreN2G-3.6-dev/src/arm/CMSIS/5.4.0/CMSIS/Core/Include" -I"/Users/zhaw/Documents/Studienarbeiten/PA_BA/BA25/BA_FS_25_wuem_185_HighSpeed/Firmware/Build/RepRapFirmware-3.6-dev/CoreN2G-3.6-dev/src/SAM4S_4E_E70/SAME70" -I"/Users/zhaw/Documents/Studienarbeiten/PA_BA/BA25/BA_FS_25_wuem_185_HighSpeed/Firmware/Build/RepRapFirmware-3.6-dev/src" -I"/Users/zhaw/Documents/Studienarbeiten/PA_BA/BA25/BA_FS_25_wuem_185_HighSpeed/Firmware/Build/RepRapFirmware-3.6-dev/src/Networking/LwipEthernet/Lwip" -I"/Users/zhaw/Documents/Studienarbeiten/PA_BA/BA25/BA_FS_25_wuem_185_HighSpeed/Firmware/Build/RepRapFirmware-3.6-dev/src/Networking/LwipEthernet/Lwip/src/include" -I"/Users/zhaw/Documents/Studienarbeiten/PA_BA/BA25/BA_FS_25_wuem_185_HighSpeed/Firmware/Build/RepRapFirmware-3.6-dev/src/Networking/MQTT/MQTT_C/include" -I"/Users/zhaw/Documents/Studienarbeiten/PA_BA/BA25/BA_FS_25_wuem_185_HighSpeed/Firmware/Build/RepRapFirmware-3.6-dev/RRFLibraries-3.5-dev/src" -O2 -Wall -c -mcpu=cortex-m7 -mthumb -fno-math-errno -mfpu=fpv5-d16 -mfloat-abi=hard -mfp16-format=ieee -mno-unaligned-access -ffunction-sections -fdata-sections -nostdlib -Wundef -Wdouble-promotion -Werror=return-type -Werror=implicit -fsingle-precision-constant "-Wa,-ahl=gpio.s" -MMD -MP -MF"WiFiSocketServerRTOS-main/src/esp8266/gpio.d" -MT"WiFiSocketServerRTOS-main/src/esp8266/gpio.o" -o "WiFiSocketServerRTOS-main/src/esp8266/gpio.o" "../WiFiSocketServerRTOS-main/src/esp8266/gpio.c"
Finished building: ../src/CAN/CanMotion.cpp

../WiFiSocketServerRTOS-main/src/esp8266/gpio.c:3:10: fatal error: driver/gpio.h: No such file or directory
3 | #include "driver/gpio.h"
| ^~~~~~~~~~~~~~~
compilation terminated.
make[1]: *** [WiFiSocketServerRTOS-main/src/esp8266/gpio.o] Error 1

And here I don't find the path to add... So what to do?

@chrishamm
Thank you.

I just double checked MessageFormats.h is existing in WiFiSocketServerRTOS/src/include in the project on Eclipse. My problem is, that when compiling, it seems as if it can not be found.

Where could be my problem?

@chrishamm
Ok. I downloaded everything again and updated LibTinyusb. Now I get the following errors:

In file included from ../src/Networking/ESP8266WiFi/WiFiSocket.cpp:15:
../src/Networking/ESP8266WiFi/WiFiInterface.h:17:10: fatal error: MessageFormats.h: No such file or directory
17 | #include <MessageFormats.h>
| ^~~~~~~~~~~~~~~~~~
compilation terminated.
make[1]: *** [src/Networking/ESP8266WiFi/WiFiSocket.o] Error 1
make[1]: *** Waiting for unfinished jobs....
Building file: ../src/Networking/Network.cpp
In file included from ../src/Networking/ESP8266WiFi/WiFiInterface.cpp:8:
../src/Networking/ESP8266WiFi/WiFiInterface.h:17:10: fatal error: MessageFormats.h: No such file or directory
17 | #include <MessageFormats.h>
| ^~~~~~~~~~~~~~~~~~
compilation terminated.
Finished building: ../src/Networking/LwipEthernet/Lwip/src/apps/mdns/mdns.c
Invoking: Cross G++ Compiler
arm-none-eabi-g++ -std=gnu++17 -D__SAME70Q20B__ -DRTOS -DDUET3_MB6HC -DMQTTC_PAL_FILE="Networking/MQTT/mqtt_pal.h" -D_XOPEN_SOURCE -I"/Users/zhaw/Documents/Studienarbeiten/PA_BA/BA25/BA_FS_25_wuem_185_HighSpeed/Firmware/Build/RepRapFirmware/LibTinyusb" -I"/Users/zhaw/Documents/Studienarbeiten/PA_BA/BA25/BA_FS_25_wuem_185_HighSpeed/Firmware/Build/RepRapFirmware/CoreN2G" -I"/Users/zhaw/Documents/Studienarbeiten/PA_BA/BA25/BA_FS_25_wuem_185_HighSpeed/Firmware/Build/RepRapFirmware/FreeRTOS" -I"/Users/zhaw/Documents/Studienarbeiten/PA_BA/BA25/BA_FS_25_wuem_185_HighSpeed/Firmware/Build/RepRapFirmware/CoreN2G/src" -I"/Users/zhaw/Documents/Studienarbeiten/PA_BA/BA25/BA_FS_25_wuem_185_HighSpeed/Firmware/Build/RepRapFirmware/CoreN2G/src/SAM4S_4E_E70" -I"/Users/zhaw/Documents/Studienarbeiten/PA_BA/BA25/BA_FS_25_wuem_185_HighSpeed/Firmware/Build/RepRapFirmware/CoreN2G/src/SAM4S_4E_E70/asf/common/utils" -I"/Users/zhaw/Documents/Studienarbeiten/PA_BA/BA25/BA_FS_25_wuem_185_HighSpeed/Firmware/Build/RepRapFirmware/CoreN2G/src/SAM4S_4E_E70/asf/sam/utils/cmsis/same70/include" -I"/Users/zhaw/Documents/Studienarbeiten/PA_BA/BA25/BA_FS_25_wuem_185_HighSpeed/Firmware/Build/RepRapFirmware/CoreN2G/src/arm/CMSIS/5.4.0/CMSIS/Core/Include" -I"/Users/zhaw/Documents/Studienarbeiten/PA_BA/BA25/BA_FS_25_wuem_185_HighSpeed/Firmware/Build/RepRapFirmware/CoreN2G/src/SAM4S_4E_E70/SAME70" -I"/Users/zhaw/Documents/Studienarbeiten/PA_BA/BA25/BA_FS_25_wuem_185_HighSpeed/Firmware/Build/RepRapFirmware/CoreN2G/src/SAM4S_4E_E70/asf" -I"/Users/zhaw/Documents/Studienarbeiten/PA_BA/BA25/BA_FS_25_wuem_185_HighSpeed/Firmware/Build/RepRapFirmware/CoreN2G/src/SAM4S_4E_E70/asf/sam/utils" -I"/Users/zhaw/Documents/Studienarbeiten/PA_BA/BA25/BA_FS_25_wuem_185_HighSpeed/Firmware/Build/RepRapFirmware/CoreN2G/src/SAM4S_4E_E70/asf/sam/utils/preprocessor" -I"/Users/zhaw/Documents/Studienarbeiten/PA_BA/BA25/BA_FS_25_wuem_185_HighSpeed/Firmware/Build/RepRapFirmware/CoreN2G/src/SAM4S_4E_E70/asf/sam/utils/header_files" -I"/Users/zhaw/Documents/Studienarbeiten/PA_BA/BA25/BA_FS_25_wuem_185_HighSpeed/Firmware/Build/RepRapFirmware/CoreN2G/src/SAM4S_4E_E70/asf/sam/drivers" -I"/Users/zhaw/Documents/Studienarbeiten/PA_BA/BA25/BA_FS_25_wuem_185_HighSpeed/Firmware/Build/RepRapFirmware/src" -I"/Users/zhaw/Documents/Studienarbeiten/PA_BA/BA25/BA_FS_25_wuem_185_HighSpeed/Firmware/Build/RepRapFirmware/src/Hardware/SAME70" -I"/Users/zhaw/Documents/Studienarbeiten/PA_BA/BA25/BA_FS_25_wuem_185_HighSpeed/Firmware/Build/RepRapFirmware/src/Networking" -I"/Users/zhaw/Documents/Studienarbeiten/PA_BA/BA25/BA_FS_25_wuem_185_HighSpeed/Firmware/Build/RepRapFirmware/src/Networking/LwipEthernet/Lwip" -I"/Users/zhaw/Documents/Studienarbeiten/PA_BA/BA25/BA_FS_25_wuem_185_HighSpeed/Firmware/Build/RepRapFirmware/src/Networking/LwipEthernet/Lwip/src/include" -I"/Users/zhaw/Documents/Studienarbeiten/PA_BA/BA25/BA_FS_25_wuem_185_HighSpeed/Firmware/Build/RepRapFirmware/src/Networking/MQTT/MQTT_C/include" -I"/Users/zhaw/Documents/Studienarbeiten/PA_BA/BA25/BA_FS_25_wuem_185_HighSpeed/Firmware/Build/RepRapFirmware/FreeRTOS/src/include" -I"/Users/zhaw/Documents/Studienarbeiten/PA_BA/BA25/BA_FS_25_wuem_185_HighSpeed/Firmware/Build/RepRapFirmware/FreeRTOS/src/portable/GCC/ARM_CM7/r0p1" -I"/Users/zhaw/Documents/Studienarbeiten/PA_BA/BA25/BA_FS_25_wuem_185_HighSpeed/Firmware/Build/RepRapFirmware/RRFLibraries/src" -I"/Users/zhaw/Documents/Studienarbeiten/PA_BA/BA25/BA_FS_25_wuem_185_HighSpeed/Firmware/Build/RepRapFirmware/CANlib/src" -O2 -Wall -c -mcpu=cortex-m7 -mthumb -fno-math-errno -mfpu=fpv5-d16 -mfloat-abi=hard -mfp16-format=ieee -mno-unaligned-access -ffunction-sections -fdata-sections -fno-threadsafe-statics -fno-rtti -fexceptions -nostdlib -Wundef -Wdouble-promotion -Werror=return-type -Wsuggest-override -fsingle-precision-constant "-Wa,-ahl=Network.s" -fstack-usage -MMD -MP -MF"src/Networking/Network.d" -MT"src/Networking/Network.o" -o "src/Networking/Network.o" "../src/Networking/Network.cpp"

make[1]: *** [src/Networking/ESP8266WiFi/WiFiInterface.o] Error 1
In file included from ../src/Networking/ESP8266WiFi/WifiFirmwareUploader.cpp:12:
../src/Networking/ESP8266WiFi/WiFiInterface.h:17:10: fatal error: MessageFormats.h: No such file or directory
17 | #include <MessageFormats.h>
| ^~~~~~~~~~~~~~~~~~
compilation terminated.
make[1]: *** [src/Networking/ESP8266WiFi/WifiFirmwareUploader.o] Error 1
In file included from ../src/Networking/Network.cpp:34:
../src/Networking/ESP8266WiFi/WiFiInterface.h:17:10: fatal error: MessageFormats.h: No such file or directory
17 | #include <MessageFormats.h>
| ^~~~~~~~~~~~~~~~~~
compilation terminated.
make[1]: *** [src/Networking/Network.o] Error 1
Finished building: ../src/Networking/LwipEthernet/LwipSocket.cpp

Finished building: ../src/Networking/LwipEthernet/LwipEthernetInterface.cpp

Finished building: ../src/Networking/FtpResponder.cpp

Finished building: ../src/Networking/HttpResponder.cpp

make: *** [all] Error 2
"make -j9 all" terminated with exit code 2. Build might be incomplete.

16:28:26 Build Failed. 10 errors, 0 warnings. (took 4s.214ms)

Any idea on what to try next?

@chrishamm
Thank you for your reply. I had the wrong version of CoreN2G (3.5 instead of 3.6). Now I can compile if I choose Duet2, but when I choose Duet_MB6HC, I again get errors:

• Description Resource Path Location Type
  fatal error: driver/gpio.h: No such file or directory gpio.c /RepRapFirmware/WiFiSocketServerRTOS-main/src/esp8266 line 3 C/C++ Problem
• Description Resource Path Location Type
  fatal error: esp_attr.h: No such file or directory HSPI.cpp /RepRapFirmware/WiFiSocketServerRTOS-main/src/esp8266 line 23 C/C++ Problem
• Description Resource Path Location Type
  fatal error: tusb.h: No such file or directory SerialCDC_tusb.cpp /CoreN2G/src line 21 C/C++ Problem
• Description Resource Path Location Type
  fatal error: tusb.h: No such file or directory TinyUsbInterface.cpp /CoreN2G/src line 28 C/C++ Problem

Where could now be the problem?

Thank you

Hello
I tried to compile 3.6 with Eclipse on my Mac and followed all the instructions. I was able to build all required projects without errors. But when I tried to build RepRapFirmware I get multiple errors like:

• Description Resource Path Location Type
  'isAlnum' was not declared in this scope; did you mean 'isalnum'? Variable.cpp /RepRapFirmware/src/ObjectModel line 40 C/C++ Problem
• Description Resource Path Location Type
  'AdcBits' is not a member of 'AnalogIn'; did you mean 'LegacyAnalogIn::AdcBits'? Platform.cpp /RepRapFirmware/src/Platform line 127 C/C++ Problem
• Description Resource Path Location Type
  Function 'isAlnum' could not be resolved Variable.cpp /RepRapFirmware/src/ObjectModel line 40 Semantic Error

Could anybody give me a hint what could be wrong? I am not experienced in building firmware and therefore a little helpless.

Thank you

Michael

Thank you for your answer. What kinematics do have continuous rotation axis? How can I choose it? Maybe I can make a work around, since the gcode is not generated by a slicer, but by a script code, which I made myself.

Yes, if there is no other solution, this may be what I will do. And maybe I can reset the position with G92 if it gets too high. But no limit would still be better...

I did already try it as an extruder axis. But there are two big disadvantage:

• there is no possibility for a homing on an extrusion axis (as far as I know). And we need homing to know in which position the axis is.
• only relative movement is allowed, which is not the best for the application.

Thank you for your ideas. I have testet them both. Unfortunately both do not work. With both I can only move from 0 - 200 then it stops. I assume, that 200 is the default limit.
Any other ideas?

Hi
I have defined a u-axis (M584 X0 Y1 Z2 U4 E3) which works perfect. The problem now is, that I need "infinite" rotation on this axis. This means I don't want to have an upper limit. Even I define only limits with M208 for x, y and z, the u-axis still stops at 250. I also don't want to disable the limits with M564.
Is there any possibility to use an axis without a limit and have a limit for the other axis?

Thank you.

And something else: is "a software reset" the same as a restart? Or do I have to do something special for a software reset?

Thank you for your quick answer. Unfortunately I think, that the Duet restarts itself. When you look at the logfile it says:

2019-07-08 12:55:22 Started printing file TopfOverhangTest_0.5mm_schnell_nowand.gcode
power up + 00:00:00 Event logging started
power up + 00:00:01 Error: M557: bad grid definition: X range too small
power up + 00:00:02 Network running, IP address = 169.254.97.197

Does "power up" not mean, that it restarts?

Anyway. I will try to catch the next shutdown and look, if M122 will help.

Regards. Michael

Hello

Since one week we have a problem with our Duet 2 Ethernet, that we did not notice before.

Our prints suddenly stop, the bed moves down and the connected PC tells me on the website, that the connection is lost. The behavior of the Duet looks the same, as if I press "emergency stop". As I said, the stop always occurred at random places. The only thing, that seems to be reproducable is, that it only happens, if a pc is connected. When there is no PC connected, it prints to the end.

Also the log file does not really help:
Logfile of print, that stopped:
2019-07-08 12:55:22 Started printing file TopfOverhangTest_0.5mm_schnell_nowand.gcode
power up + 00:00:00 Event logging started
power up + 00:00:01 Error: M557: bad grid definition: X range too small
power up + 00:00:02 Network running, IP address = 169.254.97.197
power up + 00:18:20 HTTP client 169.254.196.202 login succeeded
2019-07-08 13:52:52 Date and time set at power up + 00:18:20

Logfile of successful print:
2019-07-09 10:56:41 Started printing file TopfOverhangTest_119_steil.gcode
2019-07-09 12:17:34 Finished printing file TopfOverhangTest_119_steil.gcode, print time was 1h 21m

Since there is no entry in the logfile, I assume, that there is a system crash.

Any help available?

Thank you. Michael