QuoteMKSA Set the TFT for Marlin emul, serial stays 115200 Issued serial debug command via Pronterface, commands (home, set heat ...) sent from pronterface are indeed echoed back but when issued from the TFT, one, two char are echoed back. Funny but when pressing home a few time on the TFT, I can see a G, 8 , 2 , one char per command but erratic order. Looks like G28 is really sent ????? I triby sdavi - Firmware - experimental, borrowed, and future
QuoteMKSA Hi, TFT is not yet working. Just tried different speed, (in config.g) not the Marlin emulation mode. BTW, can these commands be issued on the Pronterface console or are they handled just at startup time ? Too bad I don't have anything to analyze the traffic on these TX RX ! An other issue is that Pronterface works OK but Repetier acts strangely. I can connect, get status, set hoteby sdavi - Firmware - experimental, borrowed, and future
QuoteMKSA Will the fixed MKSBASE ver be released soon here ? PS: If the combo MKS SBASE TFT32 works with RRF, it could boost it. Not top notch hardware but dirt cheap and could be an incentive to go for something better later. Smoothieware is OK but not that much activity and new releases are said not to be able to run on MKS due to clock speed differences. Yep, updated and uploaded to githubby sdavi - Firmware - experimental, borrowed, and future
QuoteMKSA Hi, I put M575 P1 B115200 S0 in config.g (speed as In smoothiefirmawre no checksum), doesn't work With P0 I can't connect via the USB anymore, so P0 is indeed for USB Looking at the MKS schematic, the TFT is connected to TXD0, RXD0 (pin 98 P0[2], 99 P0[3]) I hooked up my FTDI board to the UART today, and funnily enough there was a issue with the UART code in the lib i was using, lookby sdavi - Firmware - experimental, borrowed, and future
QuoteMKSA -Yes, I noticed. I was asking if it was planned. It is quite convenient as one can modify the config, macros, load print job easily from the PC. Not everyone wants to use the Ethernet and is it currently OK for this board ? - Indeed, the TFT32 is just that, a bit clumsy but comes handy as it allows to prepare, monitor, start jobs standalone. Has a regular SD card easier to handle thanby sdavi - Firmware - experimental, borrowed, and future
QuoteMKSA OK, it works. As I use USB, not the network (no WIFI on the MKS), will the SD card be able to be accessed from the PC/USB (saw in the first post it isn't currently possible))? I want to copy from PC to the SD via USB then initiate the print from it. I don't like to print from my PC via USB. I also have the MKS TFT32, is it supported ? Would be nice, the SD card slot in it is for theby sdavi - Firmware - experimental, borrowed, and future
Hopefully I've tracked down that odd SDCard issue. Uploaded new binaries - this update sends an extra 8 SPI clock cycles before sending the commands to the card and all my cards are now working.by sdavi - Firmware - experimental, borrowed, and future
Quotedc42 Most discussion about RepRapFirmware takes place on the Duet3D forum, . There is a subsection for RRF on non-Duet controllers there. I'll leave it up to @sdavi to decide whether he wants to use that, or continue here, or request a forum for RRF here - perhaps with your support. I'm happy to use both forums.by sdavi - Firmware - experimental, borrowed, and future
QuoteMKSA Hi, Wanted to play with RRF on a MKS SBASE 1.3. No network and I use Pronterface via USB to talk to the board/printer. Last week, I installed the "firmware-SMOOTHIEBOARD", managed to bring the machine to live (motor, endstop, heater ...). Now, I just replaced it by your latest: firmware-MKSBASE and nada, yes, the firmware changed to .cur, I can connect via Pronterface but when tryingby sdavi - Firmware - experimental, borrowed, and future
QuoteMarco67 Ops, missing this step, added, thanks! I've no reply on the web gui screen of the G-CODE console if i send M503, is normal? But i can see all the M503 output with USB. Yep that's normal due to the memory constraints we have on the LPC for Networking. config.g and config-override.g are viewable (and even editable, as are the other sys files) in DWC Settings->System Editor so you dby sdavi - Firmware - experimental, borrowed, and future
QuoteMarco67 Now the LAN version work fine on MKS Sbase V1.3! But i can't write the settings on MicroSD with M500. Good to hear the networking issue has been resolved. I just tested M500 and is working for me. To use M500, you first need to have M501 at the end of config.g. Can you check you have that and it's not commented out?by sdavi - Firmware - experimental, borrowed, and future
Updated to upstream RRF v2.02RC5. Binaries updated in their usual location. LPC Changes: - Increased the memory for the networking related tasks to see if that fixes some of the networking issues some are having. - Increased the delay needed for RRD Full Graphic LCD to avoid some corruption on the screen. The upstream version of RC5 has some updates to the LCD code. I was having a play arounby sdavi - Firmware - experimental, borrowed, and future
Quotechrishamm The error in DWC is caused by the missing 'fanRPM' property in the sensors field of the status response. I just prepared another build that checks if this field is present and omits it if it is not. Please check if that resolves your problem. In the latest version i was sending fanRPM set to zero as a workaround but i'll probably remove that in next version now that DWC can handleby sdavi - Firmware - experimental, borrowed, and future
The LCD (ST7920) is also now compiled in by default in the Non-Networking builds only - there is not enough memory to include it with the networking builds at this stage. The only modification I made to it was to drop the SPI freq down to 1MHz (cause it was showing garbage on with my RepRapDiscount Graphic LCD when running at 2MHz) and to select the 2nd SSP port on the LPC. I have only brieflby sdavi - Firmware - experimental, borrowed, and future
New experimental binaries (updated to latest upstream RRF Version 2.02RC4) available for download. As usual, download the binary for your board and copy to / on the internal SDCard and reboot the board. Ensure everything is working correctly after updating before attempting a print. For those using the Networking version, also update DuetWebControl to version 1.22.5. LPC port changes: * heap5by sdavi - Firmware - experimental, borrowed, and future
QuoteMarco67 Yes, is not a related cache problem, but i think because this board install a different LAN chip. See the image, it's a "Microchip LAN8720A". Smoothieboard has the PHY 8720A chip as well. Since it's sending the html files off the sdcard to the browser, would assume that's probably not the issue. I've just about finished updating to RRF v2.02RC4. That should also work with the latesby sdavi - Firmware - experimental, borrowed, and future
QuoteMarco67 With the old web interface i've no error but it doesn't connect to the board (always disconnected), i can't modify anything. Have you tried your code with this board? Have you tried cleaning out the browser cache etc in case its cached some of the previous versions files? No I don't have a MKS SBase, but it works on my smoothieboard.by sdavi - Firmware - experimental, borrowed, and future
QuoteMarco67 Thanks! Now i've a javascript error, see the image. The "MKS SBase V1.3" board is powered from USB and connected to the LAN, no other connection to the board, without main power. Try the older version v1.21.1 of DuetWebControl. Seems there has been some changes which hasn't been included in this port yet.by sdavi - Firmware - experimental, borrowed, and future
QuoteMarco67 @sdavi i tried the latest bin on MKS SBase V1.3 (Smoothieware board with LPC1768), but the web server doesn't work weel, the page is loaded very badly and is not paginated. Monitoring the serial output when i try to acces the web server and i've a lot of error: 18:49:26.173 : Error: Can't open 0:/www/js/jquery.flot.navigate.min.js.gz to read, error code 4 18:49:26.173 : Error: Can'by sdavi - Firmware - experimental, borrowed, and future
QuotecharlieRC Ok, so here’s the sandwich plan... I have a bottom mounting plate of 1/8th aluminum that rides on v-slot rails and wheels. The 1/4” aluminum plate will be mounted to the mounting plate with a semi fixed point in the left rear and a spring loaded leveling point in the right rear. I will have a spring loaded pitch adjusting point in the middle of the front. The heating elementby sdavi - Extruded Aluminum Frames
QuoteDreamscape74 Hi sdavi, Thank you for the effort on porting. Appreciate it much. Got a question if you can help answering. I am using smoothieboard on my printers but I have external drivers. Any pointers on how I can make that work with this port? I am sorry I do not know / never used RRP. Hope you can help. Thank you. If the external drivers only connect to the 4pin breakout headers (iby sdavi - Firmware - experimental, borrowed, and future
Quotedigi2life OK, I'm trying to update my ReArm and getting this error: M997 S0 Error: M997: Invalid module number '0' I downloaded firmware-REARM-NETWORK.bin from and renamed it to Duet2WifiCombined.bin... and then RepRapFirmware.bin. DWC recognizes the latter as firmware and tries to update but gives the above error. I made sure I have iap4e.bin in the /sys directory as well. Am I doingby sdavi - Firmware - experimental, borrowed, and future
QuoteAlexY @sdavi I tried a relatively high-speed print and it looks like the printer is stuttering in some areas causing layer shifting. Not sure what the cause is; perhaps slow SD reads or something with memory usage? Unfortunately I won't have access to my printer for a while so I'll be unable to test. SD access is faster in V2 code. The original SDCard library I use was running SPI at 2.5MHzby sdavi - Firmware - experimental, borrowed, and future
QuoteAlexY Works now, thanks. Repetier-Host sends M111 S6 on connection, which caused the problem. Is there a way to disable debugging to eliminate the need for manually setting M111 each time, or alternatively preventing Repetier-Host from sending M111 S6 on connection start? I don't use Repetier Host so I don't really know. Now I know that some programs turn it on I'll look into it. You coulby sdavi - Firmware - experimental, borrowed, and future
QuoteAlexY M119 works correctly for all endstops. The error I got was the following: 22:39:32.817 : Last software reset time unknown, reason: Assertion failed, spinning module GCodes, available RAM 1108 bytes (slot 0) 22:39:32.818 : Software reset code 0x0093 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00428811 BFAR 0xe000ed38 SP 0x10007cdc Task 0xa5a5a5a5 22:39:32.818 : Stack: 10007b80 00000001 0001by sdavi - Firmware - experimental, borrowed, and future
QuoteAlexY Looks like this version is having issues with homing - when I home x or y it resets the board, though z is fine. Do you know what could be causing the issue? The previous version worked with the same gcode configuration. I just loaded up the AZSMZ binary onto my smoothieboard (fortunately the motor and endstops match up to the smoothieboard) and it had no issues with homing X or Y.by sdavi - Firmware - experimental, borrowed, and future
Very experimental RepRapFirmware v2.01 RTOS port now available. Source code for CoreLPC V2 (along with PreBuilt Binaries, FreeRTOS, FreeRTOS+TCP and build scripts) and RepRapFirmware v2 Pre-built binaries are also available for various boards. As with the previous version there are two versions: Networking and No-Networking. *IMPORTANT* those using the special pins i.e. for Servos etc theby sdavi - Firmware - experimental, borrowed, and future
Thanks David, will look into that. I'm still getting into the FreeRTOS stuff, any recommendations for the priorities of new tasks? I'm using FreeRTOS+TCP for the networking, which has 2 additional tasks - one for IP and one for EMAC. Currently, I moved Heat up a priority level and have them both running at the same priority at the old heat priority. So far it runs quite well on my CNC machine (by sdavi - Firmware - experimental, borrowed, and future
QuoteAlexY I'm having a weird issue with fan PWM. The fan only turns on at 50% and runs at full speed from 50-100%. Looks like it's not trying to PWM at all. However, when the fan turns off, the fan LED slowly fades out instead of abruptly turning off. The hotend seems to PWM just fine, so I'm not really sure what could be causing the issue. It seems RRF expects the fan to be on a Hardware PWM,by sdavi - Firmware - experimental, borrowed, and future
QuoteAlexY Here is the LPC folder. Networking should be disabled in the makefile, but I'll double check. I noticed that some of the pins in the special pin map overlap with some of the used pins. Could this cause the issue? I had a quick look over the config and changed a few things (see attached) based on the smoothie config i found online for the board. The enable pin for X i think should be Pby sdavi - Firmware - experimental, borrowed, and future