i got my accelerometer installed using a usb3 cable, i was able to get it working even over 3meters!! i generated the csv files but right now i am stuck at figuring out how to make use of the data. how do i know which frequency to use in M953 Fnn? do i actually need to print something to tune even with the accelerometer? i was under the impression that printing and measure ringing and calculating Hz wS only needed if you dont have an accelerometer to generate the csv files.
thanks for the suggesting in 2. I will impliment a square move instead of a linear move. I assume this would also be useful to avoid majority of the half printed workpiece by moving around its perimeter.
I don't have a call to lock and unlock because I am using magnets.
@Danal said in Setting tool offset using USB microscope:
@tekstyle said in Setting tool offset using USB microscope:
(not connected to the duet2. not sure how i would do it).
You can't. Don't connect it. It is really a stand-alone PI, just happens to be built with the Duet image as a start.
i followed this tutorial to set up duetpi on raspberry pi 3. took out the card and put it into the raspberry pi. powered it up, all i get is an endless list of EXT4-fs error lines after line. been doing this for the past 2 hours. not sure if I did something wrong?
Followed the Duet "etch" tutorial? And edited wpasupplicant.conf? And did NOT format when windows complained about the card after etching?
That last bit is the most important. The card is partitioned, with a windows readable "boot" partition and a much larger Linux partition. Windows tries to assign a drive letter to that Linux partition, balks, and asks to format it. Which you must always decline,
EXT4-fs is the file system that windows doesn't like, and asks to format. That certainly seems to relate to those error messages.
Yup. I followed the tutorial on duet exactly. Only thing was inside the boot partition, it already contained a wpasupplicant.conf file. I Openned itnin notepad and editted it with my ssid and PW. Pulled the card out and popped it in to the rpi. Then powered it up. Will try again tonight
@tekstyle said in Setting tool offset using USB microscope:
@Danal said in Setting tool offset using USB microscope:
@tekstyle said in Setting tool offset using USB microscope:
(not connected to the duet2. not sure how i would do it).
You can't. Don't connect it. It is really a stand-alone PI, just happens to be built with the Duet image as a start.
i followed this tutorial to set up duetpi on raspberry pi 3. took out the card and put it into the raspberry pi. powered it up, all i get is an endless list of EXT4-fs error lines after line. been doing this for the past 2 hours. not sure if I did something wrong?
Followed the Duet "etch" tutorial? And edited wpasupplicant.conf? And did NOT format when windows complained about the card after etching?
That last bit is the most important. The card is partitioned, with a windows readable "boot" partition and a much larger Linux partition. Windows tries to assign a drive letter to that Linux partition, balks, and asks to format it. Which you must always decline,
EXT4-fs is the file system that windows doesn't like, and asks to format. That certainly seems to relate to those error messages.
Yup. I followed the tutorial on duet exactly. Only thing was inside the boot partition, it already contained a wpasupplicant.conf file. I Openned itnin notepad and editted it with my ssid and PW. Pulled the card out and popped it in to the rpi. Then powered it up. Will try again tonight
you won't believe this. I used my other laptop running windows 8, win32diskimager to load the duetpi image. and that worked. i have no idea why using balena etcher on win 10 doesn't work.
I was wondering if it would be possible to integrate one of these 3 pin tilt sensor to an endstop input on the duet2wifi. I am having issues with my magnetic rods falling down in the middle of a print and I need some way for the printer to do an emergency stop the moment it senses the smart effector tilting.
h##ps://www.ebay.com/itm/Tilt-Sensor-Module-Vibration-Detection-Sensor-Module-for-STM32-AVR-Brand-New/251649528768?epid=1039147961&hash=item3a977b13c0:g:~TQAAOSwfcVUGqaT
got it. and thank you for all your guys help
i was looking at that too and wonder whats going on as well. it doesnt seem to be related but ill have to look into it. i have physical drive 5 on the duex5 assigned as the extruder for tool 0 right now.
as for the tool change motor direction, it was a bad connection on the DIR wire. i swapped it out for a new one and all is fine.
thank you phaedrux!
@fcwilt when no sensors are blocked, the e1 status will change. i need the change to happen when any 1 of 3 sensors becomes unblocked.
this is for a delta arm parallel sensor setup. hence the reason for 3 sensors. i need it to pause print when any one of the sensors trip (block to unblocked)
I got the IC hooked up, and everything is working GREAT! thank you! This is actually a triple 3input OR gate. I just inverted the 1 and 0 in duet firmware.
what is the best practice for eventlogging? one thing I find annoying is when a print fails after 8 hours and you want to know why, scrolling through 8 hours of stuff is pretty time consuming. Would be nice if I can have multiple eventlog files that start and stop right before a major event of some kind, hence why I am wondering what you all do when logging stuff.
got it thank you. also, if using an arduino. do you know which INO sketch is appropriate? I only know of the one from BLV MGN.
do you still need an arduino? or can I just connect the signal wire on the strip to pin 5 of CONN_LCD which happens to be EN-10 pin of stepper 10 driver using a 74HCT08 and then use M150 command to control? can i still use pin 5 if I have a stepper driver connected to stepper 11 (pins 4,6,8,10).
@thebaseddoge
Can you Share the source of the sketch you used for your arduino?
@phaedrux oh ok. i'll wait for that in the meantime. Thank you.
@phaedrux i have the accelerometer plugin. i was able to visual the graph for all 3 axis. i just dont know what to look for as the link provided isnt clear on how to interpret the data to figure out which hz to use. or i am just not understanding the content.
i got my accelerometer installed using a usb3 cable, i was able to get it working even over 3meters!! i generated the csv files but right now i am stuck at figuring out how to make use of the data. how do i know which frequency to use in M953 Fnn? do i actually need to print something to tune even with the accelerometer? i was under the impression that printing and measure ringing and calculating Hz wS only needed if you dont have an accelerometer to generate the csv files.
is there any reason to use VIN instead of the 3V pin on the LIs3DH module?
@diamondback how would u use a USB cable? it only has 4 wires but we need 7 for the adafruit accelerometer