During all this the LCD got even worse and I could not make out much of the display at all. I contacted the Vivedino support asking for the default firmware files and uploaded them. When I tried to operate the printer it moved in the wrong directions and I guess most of the settings regarding that was wrong, the homing pushed the hotend down in the bed etc. Then the LCD was not showing the pixels correctly and it kind of flickered but I was still able to make out what it said. I downloaded U8glib V1.17 and uploaded to the printer. I then downloaded arduino IDE, downloaded Marlin 2.0.0 and used the example files for my printer. I looked at some videos on youtube and did some reading on the Marlin firmware page. I have never updated any of my 3D printers before but it seemed simple enough, Or at least so I thought. I want to share my experience and at the same time ask for your thoughts. Used all three last night during the 6 hour leveling session. I also have three different BLtouch's two V2.1 and one V3.0 if that helps. I am tempted to rewire the entire BLtouch system and downgrade back to 1.9. Sorry for the rant but I am just puzzled, could it be a wiring issue, anyone having issues with this? After work I will downgrade back to 1.9 and report back. I would have to turn the printer off and back on to get it to act somewhat predictable again. Also sometimes the values would run away, as in although changing nothing and running G29 the values would double every time. I just dont remember it taking this long to solve. I was thinking about dropping the z axis feed rate and probing each point over 3 times. Anyone have any ideas what I could change. I spent over 6 hours yesterday trying to develop some correlation between the values it was producing with no luck. I like to do multiple rounds of bed leveling and slowly teak the bed so all nine values are within 0.1mm and I could do this before but now it just feels like a lost cause. This is rendering the BLtocuh system useless and I cant even lay down a first layer. When I get home from work I can post some examples but not changing anything and preforming G29 I would get 1mm or more differences. Now I know the BLtouch is not the most accurate piece of equipment but after doing multiple rounds the values seem almost random. Interfacing with pronterface I was carrying out an automatic bed leveling cycle and checking out the values it was producing. The other day I upgraded to the new marlin firmware (using an MKS Gen 1.4). Static_assert(digitalPinToPCICR(Z_MIN_PIN) != NULL, "Z_MIN_PIN is not interrupt-capable") Sketch\endstop_interrupts.h:162:21: note: in expansion of macro 'digitalPinToPCICR' Pins_arduino.h:117:66: error: reinterpret_cast from integer to pointer In file included from C:\Program Files (x86)\Arduino\hardware\arduino\avr\cores\arduino/Arduino.h:257:0, Static_assert(digitalPinToPCICR(X_MIN_PIN) != NULL, "X_MIN_PIN is not interrupt-capable") Sketch\endstop_interrupts.h: In function 'void setup_endstop_interrupts()':Įndstop_interrupts.h:121:7: error: non-constant condition for static assertion In file included from sketch\endstops.cpp:35:0: I can build the firmware OK with Arduino 1.8.5 but with Arduino 1.8.10 I get the following:Īrduino: 1.8.10 (Windows 10), Board: "Anet V1.0" Sensorpercent = map(sensorValue, 0, 1023, 0, 101) //Map value 0-1023 to 0-130%Ĭhar key = keypad.I have an ANET A6 and am trying to build the Marlin 1.1.9 firmware. Keypad.addEventListener(keypadEvent) // Add an event listener for this keypad Int neusensorValue = 0 // value output to the PWM (analog out) Int sensorValue = 0 // value read from the pot Keypad keypad = Keypad( makeKeymap(keys), rowPins, colPins, ROWS, COLS ) LiquidCrystal_I2C lcd(0x27,20,2) // set the LCD address to 0x27 for a 16 chars and 2 line displayīyte rowPins = //connect to the column pinouts of the keypad My arduino code(Ps Im not a programmer.)… In the marlin setup of have enable both ports.
My arduino code only sends data after an event, so I not sure why its happening… When the pendant is not connected it works fine. It works perfectly when I use it for setting up jobs, but when I use octoprint it is causing issues, the job stops and says too many errors, or somelike that… I’m not at the work shop…įurthermore, I set up out the job with the pendant, place it in its holder and start the job with octoprint that is running on a raspberry pi 4.
I run it on a lowrider with a ramps board connected to the serial 1 port pins on the ramps Zmax and Zmin, I have created myself a pendent using a encoder handwheel, Lcd, poti for feed rate, menbrane switch matrix and an arduino Nano.