Repetier-Firmware-4-Davinci VS prettier

I have a Davinci 1.0a with Repetier 0.92.10 installed via the tutorial from Luc (https://github.com/luc-github/Repetier-Firmware-4-Davinci). Everything appears to function properly but the hot end and bed won't heat up nor is voltage being sent to them. I've pulled the plugs to the power supply and tested everything, it seems normal. I've checked fuse R271 and have continuity through it. I have a 4gb ADATA microSD so storage shouldn't be an issue. Do I need to change something in the configuration file for Repetier or should everything just work? What are some other points on the mainboard to check to help narrow down the issue?

Github link

I've had an XYZ DaVinci 1.0A for a couple of years now, flashed with custom Repetier firmware and connected to OctoPi / OctoPrint. It worked fine, until a couple of month ago the USB connection started getting flaky and I needed to power-cycle the printer to get USB back. Now USB disappeared completely. The printer apparently still runs its firmware (it shows its menu on the LCD when turned on), but there's to USB connection to the Pi. Plugging the printer into a different computer shows no USB device / only USB errors in Linux dmesg. I've tried resetting the firmware via J37 which should put it into firmware upload mode (acting as an Arduino board), but still nothing. I used an oscilloscope to check and there's activity on the D+/D- lines, so the cable is good, but the printer mainboard isn't responding. I suspect the Atmel ATSAM3X8EA-AU that provides the USB to be broken (at least the USB part). I could change the chip, but am unsure if / how I can flash the blank chip with the new firmware (an Arduino bootloader?). If you have ideas what else I should check or clarify the firmware situation I'd be grateful! If you need mainboard images, tell me. I have no schematics though...

Ok, let's start with the beginning... Before you flashed Repetier did it print and function normally? Next did you get the correct version of .92 , I think there are 2 or 3 different boards that require different versions. If you check this out https://www.thingiverse.com/groups/xyz-davinci-10/forums/general/topic:823 and this https://github.com/luc-github/Repetier-Firmware-4-Davinci. It should help, follow the procedure on thingiverse and re-flash with the binary from the github. let me know if it works after that. My 1.0 took a couple of tries and I had to send the M503 and M500 commands from pronterface to get it to start.

In this post, I also use ESLint + Standard JS as my code formatting tools. Formatting JS/TS code by using ESLint is also subjective and opinionated, arguably most people would rather use Prettier instead, which provides more configurable options.

Let's be honest - setting up tools for a new project can be a frustrating process. Especially when you want to jump straight to coding part. This is often the case with ESLint and Prettier, two popular tools in the JavaScript ecosystem that can sometimes interfere with each other when it comes to code formatting. Fortunately, there's a simple solution to this process, and it's called eslint-plugin-prettier.

From my point of view, Prettier doesn't work well for styling with utility classes. For a discussion see Prettier#7863 or Prettier#5948.

Prettier: An opinionated code formatter that enforces a consistent code style.

Automating code checks with static code analysis allows us to enforce code styling effectively. By integrating tools into our workflow, we can identify errors at an early stage, while coding instead of blocking us at the end. For instance, flake8 checks Python code for style and errors, eslint performs similar checks for JavaScript, and prettier automatically formats code to maintain consistency.

So anyways, I wanted to hook up Emacs with Astro support. For now, I've just been roughing it out there and running Prettier by itself and turning off save on format and auto-complete. It's been scary.

If you're a developer, you're surely familiar with Prettier and ESLint. With over 8 years of existence, they have established themselves as references in the JavaScript ecosystem.

prettier is used to format you text

No formatting inconsistencies: The committed code should follow the organization's code formatting standards(prettier or pretty-quick).

Let’s walk through the steps for a one-time setup to configure husky pre-commit and pre-push hooks, ESLint with code styles conventions, prettier code formatter, and lint-staged. Husky automatically runs a script on each commit or push. This is useful for linting files to enforce code styles that keeps the entire code base following conventions.