SHAPER_CLIBRATE using a Beacon Rev H
I am having an issue when I run the "SHAPER_CALIBRATE" command while using the Beacon Rev H. probe. The calibration process begins, but after a few minutes, the printer reboots. The printer was originally set up with an adxl345 accelerometer, but it was removed when I removed a pinda probe and added a Beacon Rev H probe. I updated the printer.cfg to remove references to the adxl345 and to add the following sections:
Beacon (everything is already installed, just connect it and run BEACON_CALIBRATE)
[include RatOS/z-probe/beacon.cfg]
resonance testing configuration
[resonance_tester]
accel_chip: beacon
probe_points:
100,100,20 # 200mm printer
150,150,20 # 300mm printer
200,200,20 # 400mm printer
250,250,20 # 500mm printer
The bed leveling and mesh routines work perfectly, only the "SHAPER_CALIBRATE" has the problem.
I tried using "SHAPER_CLIBRATE CHIP=beacon" but this did not fix the issue. It appears as if the system is still expecting data from the adxl345 because when I run the "ACCELEROMETER_QUERY" command i receive the following 10:28 AM Invalid adxl345 id (got ff vs e5). 10:28 AM Invalid adxl345 id (got ff vs e5). This is generally indicative of connection problems (e.g. faulty wiring) or a faulty adxl345 chip. If I use the "ACCELEROMETER_QUERY CHIP=beacon" command I received the following "accelerometer values (x, y, z): 76.589155, 382.945777, 9726.822748" I can also successfully run the "TEST_RESONANCES AXIS=X CHIP=beacon" command. To summarize, I believe the accelerometer is working but RATOS believes it should be using the adxl345 instead of the beacon probe for acceleration values. Any help is very much appreciated. Doug Sanqunetti
I tried using "SHAPER_CLIBRATE CHIP=beacon" but this did not fix the issue. It appears as if the system is still expecting data from the adxl345 because when I run the "ACCELEROMETER_QUERY" command i receive the following 10:28 AM Invalid adxl345 id (got ff vs e5). 10:28 AM Invalid adxl345 id (got ff vs e5). This is generally indicative of connection problems (e.g. faulty wiring) or a faulty adxl345 chip. If I use the "ACCELEROMETER_QUERY CHIP=beacon" command I received the following "accelerometer values (x, y, z): 76.589155, 382.945777, 9726.822748" I can also successfully run the "TEST_RESONANCES AXIS=X CHIP=beacon" command. To summarize, I believe the accelerometer is working but RATOS believes it should be using the adxl345 instead of the beacon probe for acceleration values. Any help is very much appreciated. Doug Sanqunetti
0 Replies