Duet3D Logo Duet3D
    • Tags
    • Documentation
    • Order
    • Register
    • Login
    1. Home
    2. Behrouz-AKT
    • Profile
    • Following 0
    • Followers 0
    • Topics 11
    • Posts 27
    • Best 0
    • Controversial 0
    • Groups 0

    Behrouz-AKT

    @Behrouz-AKT

    0
    Reputation
    5
    Profile views
    27
    Posts
    0
    Followers
    0
    Following
    Joined Last Online

    Behrouz-AKT Unfollow Follow

    Latest posts made by Behrouz-AKT

    • Unable to build on MAC M series

      Hi

      I am trying to build RRF 3.4-dev on a MAC M1.

      I have managed to build CANlib, CoreN2G, FreeRTOS and RRFLibraries with no issues but when it comes to RepRapFirmware it seems to have issues - attaching partial console log below

      
      Building file: ../src/Libraries/Fatfs/ff.c
      Invoking: Cross GCC Compiler
      arm-none-eabi-gcc -std=gnu99 -D__SAME70Q20B__ -DRTOS -DDUET3_MB6HC -DUSE_CAN0 -Dnoexcept= -I"/Users/minibp/Reprap3 original/CoreN2G-3.4-dev" -I"/Users/minibp/Reprap3 original/CoreN2G-3.4-dev/src" -I"/Users/minibp/Reprap3 original/CoreN2G-3.4-dev/src/SAM4S_4E_E70" -I"/Users/minibp/Reprap3 original/CoreN2G-3.4-dev/src/SAM4S_4E_E70/asf" -I"/Users/minibp/Reprap3 original/CoreN2G-3.4-dev/src/SAM4S_4E_E70/asf/sam/drivers" -I"/Users/minibp/Reprap3 original/CoreN2G-3.4-dev/src/SAM4S_4E_E70/asf/sam/utils" -I"/Users/minibp/Reprap3 original/CoreN2G-3.4-dev/src/SAM4S_4E_E70/asf/common/utils" -I"/Users/minibp/Reprap3 original/CoreN2G-3.4-dev/src/SAM4S_4E_E70/asf/sam/utils/preprocessor" -I"/Users/minibp/Reprap3 original/CoreN2G-3.4-dev/src/SAM4S_4E_E70/asf/sam/utils/header_files" -I"/Users/minibp/Reprap3 original/CoreN2G-3.4-dev/src/SAM4S_4E_E70/asf/sam/utils/cmsis/same70/include" -I"/Users/minibp/Reprap3 original/CoreN2G-3.4-dev/src/arm/CMSIS/5.4.0/CMSIS/Core/Include" -I"/Users/minibp/Reprap3 original/CoreN2G-3.4-dev/src/SAM4S_4E_E70/SAME70" -I"/Users/minibp/Reprap3 original/RepRapFirmware-3.4-dev/src/Networking/LwipEthernet/Lwip" -I"/Users/minibp/Reprap3 original/RepRapFirmware-3.4-dev/src/Networking/LwipEthernet/Lwip/src/include" -I"/Users/minibp/Reprap3 original/RRFLibraries-3.4-dev/src" -O2 -Wall -c -mcpu=cortex-m7 -mthumb -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=ff.s" -MMD -MP -MF"src/Libraries/Fatfs/ff.d" -MT"src/Libraries/Fatfs/ff.o" -o "src/Libraries/Fatfs/ff.o" "../src/Libraries/Fatfs/ff.c"
      ../src/Networking/ESP8266WiFi/WiFiInterface.cpp: In member function 'virtual void WiFiInterface::Spin()':
      ../src/Networking/ESP8266WiFi/WiFiInterface.cpp:676:25: error: 'MinimumStatusResponseLength' was not declared in this scope
        676 |      if (rc >= (int32_t)MinimumStatusResponseLength)
            |                         ^~~~~~~~~~~~~~~~~~~~~~~~~~~
      ../src/Networking/ESP8266WiFi/WiFiInterface.cpp: In member function 'virtual void WiFiInterface::Diagnostics(MessageType)':
      ../src/Networking/ESP8266WiFi/WiFiInterface.cpp:936:91: error: 'MinimumStatusResponseLength' was not declared in this scope
        936 |   if (SendCommand(NetworkCommand::networkGetStatus, 0, 0, nullptr, 0, status) >= (int32_t)MinimumStatusResponseLength)
            |                                                                                           ^~~~~~~~~~~~~~~~~~~~~~~~~~~
      ../src/Networking/ESP8266WiFi/WiFiInterface.cpp: In member function 'void WiFiInterface::StartWiFi()':
      ../src/Networking/ESP8266WiFi/WiFiInterface.cpp:2045:27: error: 'WiFiBaudRate_ESP32' was not declared in this scope; did you mean 'WiFiBaudRate'?
       2045 |  SERIAL_WIFI_DEVICE.begin(WiFiBaudRate_ESP32);    // initialise the UART, to receive debug info
            |                           ^~~~~~~~~~~~~~~~~~
            |                           WiFiBaudRate
      Finished building: ../src/Movement/RawMove.cpp
      Finished building: ../src/Movement/MoveSegment.cpp
       
       
      Building file: ../src/Libraries/Fatfs/ffunicode.c
      make[1]: *** [src/Networking/ESP8266WiFi/WiFiInterface.o] Error 1
      Building file: ../src/InputMonitors/InputMonitor.cpp
      Invoking: Cross GCC Compiler
      make[1]: *** Waiting for unfinished jobs....
      arm-none-eabi-gcc -std=gnu99 -D__SAME70Q20B__ -DRTOS -DDUET3_MB6HC -DUSE_CAN0 -Dnoexcept= -I"/Users/minibp/Reprap3 original/CoreN2G-3.4-dev" -I"/Users/minibp/Reprap3 original/CoreN2G-3.4-dev/src" -I"/Users/minibp/Reprap3 original/CoreN2G-3.4-dev/src/SAM4S_4E_E70" -I"/Users/minibp/Reprap3 original/CoreN2G-3.4-dev/src/SAM4S_4E_E70/asf" -I"/Users/minibp/Reprap3 original/CoreN2G-3.4-dev/src/SAM4S_4E_E70/asf/sam/drivers" -I"/Users/minibp/Reprap3 original/CoreN2G-3.4-dev/src/SAM4S_4E_E70/asf/sam/utils" -I"/Users/minibp/Reprap3 original/CoreN2G-3.4-dev/src/SAM4S_4E_E70/asf/common/utils" -I"/Users/minibp/Reprap3 original/CoreN2G-3.4-dev/src/SAM4S_4E_E70/asf/sam/utils/preprocessor" -I"/Users/minibp/Reprap3 original/CoreN2G-3.4-dev/src/SAM4S_4E_E70/asf/sam/utils/header_files" -I"/Users/minibp/Reprap3 original/CoreN2G-3.4-dev/src/SAM4S_4E_E70/asf/sam/utils/cmsis/same70/include" -I"/Users/minibp/Reprap3 original/CoreN2G-3.4-dev/src/arm/CMSIS/5.4.0/CMSIS/Core/Include" -I"/Users/minibp/Reprap3 original/CoreN2G-3.4-dev/src/SAM4S_4E_E70/SAME70" -I"/Users/minibp/Reprap3 original/RepRapFirmware-3.4-dev/src/Networking/LwipEthernet/Lwip" -I"/Users/minibp/Reprap3 original/RepRapFirmware-3.4-dev/src/Networking/LwipEthernet/Lwip/src/include" -I"/Users/minibp/Reprap3 original/RRFLibraries-3.4-dev/src" -O2 -Wall -c -mcpu=cortex-m7 -mthumb -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=ffunicode.s" -MMD -MP -MF"src/Libraries/Fatfs/ffunicode.d" -MT"src/Libraries/Fatfs/ffunicode.o" -o "src/Libraries/Fatfs/ffunicode.o" "../src/Libraries/Fatfs/ffunicode.c"
      Invoking: Cross G++ Compiler
      arm-none-eabi-g++ -std=gnu++17 -D__SAME70Q20B__ -DRTOS -DDUET3_MB6HC -D_XOPEN_SOURCE -DUSE_CAN0 -I"/Users/minibp/Reprap3 original/CoreN2G-3.4-dev" -I"/Users/minibp/Reprap3 original/CoreN2G-3.4-dev/src" -I"/Users/minibp/Reprap3 original/CoreN2G-3.4-dev/src/SAM4S_4E_E70" -I"/Users/minibp/Reprap3 original/CoreN2G-3.4-dev/src/SAM4S_4E_E70/asf/common/utils" -I"/Users/minibp/Reprap3 original/CoreN2G-3.4-dev/src/SAM4S_4E_E70/asf/sam/utils/cmsis/same70/include" -I"/Users/minibp/Reprap3 original/CoreN2G-3.4-dev/src/arm/CMSIS/5.4.0/CMSIS/Core/Include" -I"/Users/minibp/Reprap3 original/CoreN2G-3.4-dev/src/SAM4S_4E_E70/SAME70" -I"/Users/minibp/Reprap3 original/CoreN2G-3.4-dev/src/SAM4S_4E_E70/asf" -I"/Users/minibp/Reprap3 original/CoreN2G-3.4-dev/src/SAM4S_4E_E70/asf/sam/utils" -I"/Users/minibp/Reprap3 original/CoreN2G-3.4-dev/src/SAM4S_4E_E70/asf/sam/utils/preprocessor" -I"/Users/minibp/Reprap3 original/CoreN2G-3.4-dev/src/SAM4S_4E_E70/asf/sam/utils/header_files" -I"/Users/minibp/Reprap3 original/CoreN2G-3.4-dev/src/SAM4S_4E_E70/asf/sam/drivers" -I"/Users/minibp/Reprap3 original/RepRapFirmware-3.4-dev/src" -I"/Users/minibp/Reprap3 original/RepRapFirmware-3.4-dev/src/Hardware/SAME70" -I"/Users/minibp/Reprap3 original/RepRapFirmware-3.4-dev/src/Networking" -I"/Users/minibp/Reprap3 original/RepRapFirmware-3.4-dev/src/Networking/LwipEthernet/Lwip" -I"/Users/minibp/Reprap3 original/RepRapFirmware-3.4-dev/src/Networking/LwipEthernet/Lwip/src/include" -I"/Users/minibp/Reprap3 original/DuetWiFiSocketServer-master/src/include" -I"/Users/minibp/Reprap3 original/FreeRTOS-3.4-dev/src/include" -I"/Users/minibp/Reprap3 original/FreeRTOS-3.4-dev/src/portable/GCC/ARM_CM7/r0p1" -I"/Users/minibp/Reprap3 original/RRFLibraries-3.4-dev/src" -I"/Users/minibp/Reprap3 original/CANlib-3.4-dev/src" -O2 -Wall -c -mcpu=cortex-m7 -mthumb -mfpu=fpv5-d16 -mfp16-format=ieee -mfloat-abi=hard -ffunction-sections -fdata-sections -fno-threadsafe-statics -fno-rtti -fexceptions -nostdlib -Wundef -Wdouble-promotion -Werror=return-type -Wsuggest-override -fsingle-precision-constant "-Wa,-ahl=InputMonitor.s" -fstack-usage -MMD -MP -MF"src/InputMonitors/InputMonitor.d" -MT"src/InputMonitors/InputMonitor.o" -o "src/InputMonitors/InputMonitor.o" "../src/InputMonitors/InputMonitor.cpp"
      Finished building: ../src/Movement/ExtruderShaper.cpp
       
      Finished building: ../src/Movement/StepTimer.cpp
       
      Finished building: ../src/Movement/DriveMovement.cpp
       
      Finished building: ../src/Libraries/sd_mmc/sd_mmc.cpp
       
      Finished building: ../src/Libraries/sd_mmc/sd_mmc_spi.cpp
       
      Finished building: ../src/Libraries/Fatfs/ffunicode.c
       
      Finished building: ../src/Libraries/Fatfs/fattime_rtc.cpp
      Finished building: ../src/Libraries/Fatfs/diskio.cpp
       
      Finished building: ../src/Movement/AxisShaper.cpp
       
       
      Finished building: ../src/Movement/DDARing.cpp
       
      Finished building: ../src/Movement/Move.cpp
       
      Finished building: ../src/InputMonitors/InputMonitor.cpp
       
      Finished building: ../src/Movement/DDA.cpp
       
      Finished building: ../src/Libraries/Fatfs/ff.c
       
      make: *** [all] Error 2
      "make -j15 all" terminated with exit code 2. Build might be incomplete.
      
      20:14:41 Build Failed. 6 errors, 0 warnings. (took 1s.268ms)
      

      Thanks for your help

      posted in Firmware developers
      Behrouz-AKTundefined
      Behrouz-AKT
    • RE: can I echo a string ?

      @moth4017 Not sure I understand . In essence pin 1.io2.in in an input from optical sensor and (digital signal). When the sensor is triggered then trigger2.g file gets called. The problem is that this only works once. Are you saying that I should not be processing in the trigger file? is the trigger2.g not a macro ?

      posted in General Discussion
      Behrouz-AKTundefined
      Behrouz-AKT
    • RE: Parameter passing from within a macro

      @fcwilt I am observing the same thing - a string for some odd reason does not work but it should - actually i am trying to do something similar.

      posted in General Discussion
      Behrouz-AKTundefined
      Behrouz-AKT
    • RE: can I echo a string ?

      @moth4017 That what I thought at first. However, I have never seen echo work - The WiFi is right next to the machine, router and the PC. eg they are all withing 1 meter of each other.

      Also does not explain why the trigger only works once. I must be missing something

      posted in General Discussion
      Behrouz-AKTundefined
      Behrouz-AKT
    • can I echo a string ?

      I am using version 3.4.6 on Mini5+ board

      I tried to echo a string but it doe not seem to work for me. However I have seen examples of its use in sample code in the online documentation. I am trying to debug the my code

      ;trigger2.g
      echo "trigger2"         ;should echo to console
      G1 V -10 F1000          ; move Middle drive 10 mm
      M581 P2 S1 T2 R0	; Set trigger2.g again
      

      I am trying to see if the file gets triggered , I know G1 gets executed but only once and it will not work the second time. I have to reset the machine either by uploading a new trigger file or config file.

      other information that might be useful is the config

      ;back sensor 1.io0.in
      M950 J1 C"!1.io0.in"  	; conveyor back sensor 
      M581 P1 S1 T1 R0		; calls trigger1.g
      ; front sensor 1.io2.in 
      M950 J2 C"!1.io2.in"  	; conveyor front sensor 
      M581 P2 S1 T2 R0		;trigger2.g
      

      any help is appreciated

      posted in General Discussion
      Behrouz-AKTundefined
      Behrouz-AKT
    • RE: Reference to Dozuki.com - does not exist

      @fcwilt Thanks, but not what i was looking for - most probably because i was not clear in my description. Let me try again. in some online documentation i come across references to an old site that is no longer supported. typically these are G- code examples mainly in the comment section eg

      https://duet3d.dozuki.com/Wiki/Gcode#Section_M574_RepRapFirmware_Num_3

      but if you click this it does not exist. I tried variations on this such as
      https://duet3d.com/User_manual/Reference/Gcode#Section_M574_RepRapFirmware_Num_3

      but does not work. typically i do a search on the G code.

      I am wondering if there a substitute for certain keywords in the original link that will take me to the correct reference?

      posted in Documentation
      Behrouz-AKTundefined
      Behrouz-AKT
    • Reference to Dozuki.com - does not exist

      I keep coming across duet3d.dozuki.com/wiki/... in documentation - Is there a quick substitute that i can use for duet3d.dozuki.com/wiki ?

      posted in Documentation
      Behrouz-AKTundefined
      Behrouz-AKT
    • RE: Is there a limit of 10 axis labels ?

      @dc42 Thank you. I will have to spend some time with the code, this is very helpful.

      posted in Using Duet Controllers
      Behrouz-AKTundefined
      Behrouz-AKT
    • RE: Is there a limit of 10 axis labels ?

      @dc42 Thanks for your help. I only need 11 axis at the moment.

      ON the CAN side and ignoring the axis issues if I add one additional CAN board ( with motor control ) then that will use an additional 4bytes and If I add 50 boards then that an extra 200bytes. Is that correct?

      posted in Using Duet Controllers
      Behrouz-AKTundefined
      Behrouz-AKT
    • RE: Is there a limit of 10 axis labels ?

      @gloomyandy Fantastic, thank you . I see the limits and will start experimenting. With CAN-FD. I am planning on sending a simple command as it will be a custom board. I t will receive the command of the CAN bus, process the command and ack back to main. I could have over 50 of these little boards. They will never be accessed at the same time.

      Are you saying that it must keep track of each even if they are doing nothing? Is there a specific file that a expansion board gets instantiated?

      posted in Using Duet Controllers
      Behrouz-AKTundefined
      Behrouz-AKT