Forum Replies Created
-
AuthorPosts
-
cmcgrath5035
ModeratorIf you want to give avrdude another go, try this file:
I sort of though avrdude was a Win32 application that of course would run on Win64.
I am not really a Windows guy, so not sure how o tell, except try and fail.Later comment – don’t bother with this – the library file .dll is bad as well, read further down in thread
-
This reply was modified 10 years, 4 months ago by
cmcgrath5035.
cmcgrath5035
ModeratorAh so, that must be Win64 version of avrdude.
Hmmmmcmcgrath5035
ModeratorI sort of doubt it.
CMD window avrdude (32 bit) should work, have that?You can also try this:
1. Download this archive:2. Unzip it into a clean folder
3. browse to that folder in cmd window.
4 Read ReadMe.txt-
This reply was modified 10 years, 4 months ago by
cmcgrath5035.
cmcgrath5035
ModeratorBrrr. You should be thermally good under those conditions.
Some folks have reported strange side effects to making parameter changes, such as changing X velocity, then X will only move in one direction when jogged, moves same direction irrespective of arrow push. Then it starts to behave normally again.
Obviously, can’t be doing a hard reset after changes during a freehold, etc.
Keep an eye open and report, thanks.
cmcgrath5035
ModeratorAre you using the configuretinyG widget to make your parameter changes?
Don’t. Use the serial port Command window.
Are you in mm mode or inch mode?
I suggest only changing parameters while in mm mode until we figure this oput.You can run $$ in the CP Comand line widget, then highlight the buffer and copy, then paste.
Helps to clear the window first.If a reset button on tinyG does not reboot it (after 10 second wait, your flash image is corrupted.
I’m not sure that the SPJS FW upgrade will work if tinyG is stuck in bootloader.
Try this:You are not alone, several other threads with same garbled CP then death issue.
Root cause still eludes the devscmcgrath5035
ModeratorHere is another useful wiki reference:
In this reference you will see explicitly that $sl=1 is necessary for soft limits to be in effect.
Also note the settings for Z axis[ztn] z travel minimum -95.000 mm
[ztm] z travel maximum 0.000 mmBy procedural design, when the Zmax switch is operated during a homing cycle, that position is set to Z=0 for G53 coordinate system, and G54 will also be 0 as you have no G54 offset.
So $Ztm needs to be set to 0.00 and Ztn needs to be a negative number for soft limits to workIn the $$dump you first posted, you had
[zsn] z switch min “1 [0=off,1=homing,2=limit,3=limit+homing]”
[zsx] z switch max “0 [0=off,1=homing,2=limit,3=limit+homing]”I see that you have corrected that in the latest two $$ dumps.
I believe that if you correct the $ztn and $ztm values and set $sl=1,, then rehome, you should find that soft limits will work. Do note that Z movement must be to positions <0.
What I envision from your parameters is a XYYrZ machine with GT3 belts and an 8mm leadscrew for Z, perhaps an Ox or ShapeOko2 or Xcarve.
I appears to me that you may have entered your parameters in inch mode, which makes comparison to the recommended (or start-up parameters) somewhat difficult. What I am referring to is, for example, $zvm=787, rather than $zvm=800, a typical recommended value. I also note that you X and Y velocity settings are rather low (5000 or in your case 5080) compared to typically recommended value of 16000.
I also question why your $xjm = 25, vs. a typical recommended starting value of 5000. In fact all your jerk settings seem low.Is there a particular setup guide you are following?
I am a bit concerned about the bogus value of $atn, which should be -1.0 deg.
You are not using the A axis, so it might be benign, but sometimes crazy values like this are an indicator of corrupted parameter store in EEPROM.What tool did you use to set parameters?
Finally – I was able to read your latest two parameter dumps, but as bitmaps (rather than the text format you posted first time) they are difficult to manipulate. For example, I will often ‘diff’ your parameter set against a typical or recommended set (I work in Linux space), letting the machine, rather than my eyes, spot potential issues.
-
This reply was modified 10 years, 4 months ago by
cmcgrath5035.
cmcgrath5035
ModeratorWierd.
There is a thermal shutdown ckt inside the driver device, so that is therefor a possibility but your comment would seem to imply doubtful.
It might be interesting to try to reproduce, to best of your recollection.
Try running the job in air (no need to waste material), freehold the job for the same amount of time (more or less) with motors energised same (or perhaps a bit longer) duration, then see if it resumesOK.Do you have a fan blowing on tinyG?
(Carefully) finger test the x driver device at end of the freehold-energize cycle.Are you running at a high current level setting (on pot)?
cmcgrath5035
ModeratorHmmm, your parameter dump is a bit hard to decipher, I forgot to request you put tinyG into mm mode first so that parameters are shown in mm.
In this dump, $sl=0 and hard limits are turned off.
I’ll assume you changed at some point.A couple more fundamental questions I skipped earlier:
What OS are you running (It may affect proplem resolution suggestions){Winxx,MacOS, Linux}?
How do you communicate/send commands to tinyG? {CoolTerm, Chilipeppr, other}?I suggest you review, carefully, this wiki item
You have your Z axis set up wrong, if in fact you are homing your Z axis.
The tinyG implementation of Homing homes to Zmax, not Z min. And Zmax is set to zero, so for your set up, $ztn=-2.953in and $ztm=0, if you choose to Home Z axis.The following would be helpful in proceeding:
1. Reset your tinyG
2. Make sure it is in mm mode
3. Provide a $$dump, call it “after_reset”
4. Run your homing cycle
5. Retest a move that you violate Soft limits, if you do enable them.
6. Provide another $$dump (again, mm mode) all it “after_home”cmcgrath5035
Moderatorcmcgrath5035
Moderatorprariehome – On my step 11. – did you observe an extended period of LED flashing, 20-25 seconds or so, before the verification failure?
That 25-30 seconds of flashing indicates the hex download and flashing porocess is actually happening.Can I assume you hit the tinyG reset button? (step 9.)
cmcgrath5035
Moderatorprariehome – please try this procedure. I just ran it, it works but my tinyGV8 was in OK state before it ran, so not same as yours.
Please READ CAREFULLY – I had to tweak the process for it to run
((I am assuming you are running 64 bit windows of some sort and know how to manipulate files and folders))
[[If you are a MACOS user, there is a different zip for you. Follow this step by step as best you can (I don’t do MAC, can’t really help)]]
1. Make sure SPJS is NOT running (reboot if necessary, check with Task Manager)
2. Disconnect, then reconnect tinyG from USB port
3. Download this file, MAKE SURE YOU GET VERSION 0.6.14. Unzip the downloaded zip into a clean working directory, I’ll call it C:\users\ph\folder
5.Using file manager, navigate to folder
C:\users\ph\folder\tinyG-updater-Windows64_0.6.1
6. In that folder you should see 3 subfolders and 20 files, one of which is TinyG-Updater.exe
7. Right click on TinyG-Updater.exe, choose Run as Administrator. Acknowledge to Windows that you are an intelligent human being and know what you are doing(I seriously dislike Windows, but I digress)
8. The Window “/Synthetos TinyG Updater” should open
9. Under 1.), choose to install version 440.20 .
If you tinyG is connected, 2.) should display the COMport
10. BEFORE you click GO! — I find that the “Attempt automatic reset” does not reset tinyG, it may or may not for you. I recommend you hit the reset button on tinyG, then move you finger to the mouse and click Go!
11. Observe the LEDs on tinyG – the “Boot Loader flash” should stop, then you should observe 20-30 seconds on multiple LED flashing activity.
12. The procedure should complete with a Green verification success message.
13. If success, please report
14. If you still get verification fail again, please repeat steps 9-13 a second timeIf you don’t succeed, please try to report the messaging and the step where you receive said message.
cmcgrath5035
ModeratorHmmm, good question.
Can you capture a $$ parameter dump for analysis?
Can you describe how this happened:
I had a G54 zero set wrong and
Messing with zero set likely would reset “homed” status…..
cmcgrath5035
ModeratorI would try the updated SPJS 1.86.
Overall, 1.86 is much more cpu efficient and targeted some issues with ‘stalling’, but not necessarily as you describe; more often the issue was with very long Gcode runs (hours long)..I would suggest you gather a before and after benchmark as to CPU utilization for the serial-port-json-server application. Method depends on OS.
cmcgrath5035
ModeratorI’ll lookup the cncccookbook item, thanks. Microstepping is implemented by the driver, incrementally offsetting the rise and fall edges of the A and B drive windings.
A read of a device data sheet, such as for TI 8825, shows the small offset specifications.cmcgrath5035
Moderator
BTW do you know of a version\change log so that I can tell ahead of time if for instance 83.08 will have the proper features ahead of time?
I don’t believe there is one. You can infer from some of the check-in comments on GitHub, but in general I would say that a Master build is intended to implement tinyG2 as described in the Wiki.
You can also get some info by monitoring the chatter atWith G2, stick with the Master builds unless you are looking for specific leading edge features..
EDGE builds tend to be really edgy sometimes.Pul is pulse or Step pul+ gets directly connected to 5V and the minus is set up in a low side n channel switch using the bs170. 3 step pins and 3 direction pins.Pul is pulse or Step pul+ gets directly connected to 5V and the minus is set up in a low side n channel switch using the bs170. 3 step pins and 3 direction pins.
So your verbal schematic for PUL is:
PUL+ to +5V
PUL- to Drain of BS170 MOSFET
DUE Step Port to Gate of BS170 MOSFET
Gnd to Source of BS170 MOSFETThat is a simple inverting switch, which is what you need.
It is what I thought you were describing but one version did not read that way.Microstepping = OK, understand your 0011 setting.
I wonder how useful(accuracy and torque) their microstepping >64 actually is. -
This reply was modified 10 years, 4 months ago by
-
AuthorPosts