i am helping a friend with this new vertex, as he seems to have quite some issue with the usage of the printer.
a lot of strange noises on the z even wen auto home or using the z axis buttons in manual control
this printer has never printed yet as we never got past this issue…
after careful analyses i noticed that there is an issue in the Amax settings in the eeprom.
on start/restart they have the strange value of Amax z: 47872 Amax e:34320 also an ureadable value for Z steps/mm
upon restore Failsafe the values are Amax z: 100 Amax e:10000 which seem the correct settings…
as the manual indicates you should do after the firmware update a restore failsafe and then store memory…
we did that and we did that about 100 times by now but on every restart it comes back with the same strange values as indicated above…
it looks like the new settings are not stored in the eeprom for some reason.
we initially installed firmware v1.4 for 1 head as this was the latest one…
then we downlgraded to firmware v1.1 to make sure it was not a firmware issue…
behaviour is on both firmware versions the same, i tried to search the forum but i could find a solution for this, anyone experienced this or Velleman, what should be the issue here and how can we solve it?
btw, i already have my vertex for more than half a year and never had a bad experience with it and this seems just very strange in this case. could this be a bad arduino board?
If the threaded rod isn’t perfectly straight it’s vibrating a lot when moving the axis. That’s why a lot of us have installed a Z-axis stabilizer like this one.
On the other hand if the threaded rod is inserted too far in the flex coupler the coupling will be rigid, amplifying the vibrations (see here)
it’s not that kind of noise that is the problem, is more a sort of noise of skipping…
if we do the restore failsave on every startup, it is not doing that because it loads the correct settings… think is even if you store it to memory that everytime the printer is powered on the settings are gone and we need to do the restore failsave again…
so something is wrong with the eeprom or with writing the values to the eeprom at store memory.
by the way even on editing the eeprom settings via repetier host the settings are gone after restart/reset/power-up
Sorry for your inconvenience, those values you mention are indeed not correct. But the Amax Z: 100 etc… are correct.
Am I correct that you can get the correct values by using the restore failsafe option, but they return to the wrong values after restart?
This is caused by a bad eeprom setting (which should be correct from the factory so my apalogies) normally you can fix this by first choosing the RESTORE FAILSAFE option and directly after that the STORE MEMORY option. This will save the failsafe values (which are hardcoded) into the eeprom and would normally fix your problem.
If this however does not fix your problem you have a board/controller with a bad eeprom memory and this will be replaced. You can do this by opening a ticket here: support.velleman.eu
(mention this thread in your ticket)
thanks for your message, this is exactly the case…
loading the restore failsave and immediately store memory is not solving the issues…
we will create a ticket for this.
I encore exactly the same problem as peterjoris with skipping noise when the vetrex go to the home position.
It seems that if the x and y stop detector didn’t work well although the connection are ok. If fact after arrived at the course end, the motor try to continue farther during 6 seconds and then go to the next step and print normally (with enough precision).
As explain by the peterjoris explained it seems to come from the EEPROM parameter (even selecting RESTORE FAILSAFE before each printing job). I work with the firmware 1.4 with one nuzzle.
Is a solution or an update to solve the problem now ?