alden

Forum Replies Created

Viewing 15 posts - 526 through 540 (of 702 total)
  • Author
    Posts
  • in reply to: Z Axis Broken? #3430
    alden
    Member

    Sorry to hear you are having problems. What are your settings? Try $$

    in reply to: TinyG on Duemilanove #3421
    alden
    Member

    I’m not in a position to test this for a week or so, but changing the feed rate, velocity max and travel per revolution ($1tr) should be reflected in the next $ display command (e.g. $x). At least, that’s the way it’s always worked for me. These commands (and all others) should be issued when no Gcode is running, so they take effect on the next Gcode command.

    The only command I’m aware of that needs to be effected immediately (i.e. before the next Gcode command is received) is the power mode (pm) because if the steppers are drawing power without movement you want to be able to stop that without waiting.  I don’t actually see this as a major issue, but it would be nice if it took effect immediately.

    Correct me if I’ve got this wrong or you have another opinion.

    Alden

    in reply to: How to bring out the reset button? #3413
    alden
    Member

    The best way is just to wire another switch across the existing switch terminals. This entails soldering a pair of wires to the surface mount leads. In a future revision I will probably make a 2 pin connector for this. Are you OK with the soldering or do you need further clarification or assistance?

    in reply to: Z axis moves in the wrong direction #3396
    alden
    Member

    Let me make sure I understand correctly. You moved the X motor to the Z axis board connector. You changed $2=43.74. You sent a “Z” command like G0Z10 to the board and the Z channel drove the X motor and X axis just fine. Do I have that right?

    Second, when you swapped the X and Z motors did you also run X commands with the Z axis motor and axis ($0 should have been set to 300)? Did that work OK too, or did the motor still behave erratically?

    Third, when you moved the motors back to their original configuration the Z axis was still having problems.

    It sounds like the Z connector or possibly the Z motor itself is bad, especially if it was unable to be driven from the X channel (if you did that second test). The board sounds like it’s fine.  If you have not done the Second test, can you do that as well to confirm?

    in reply to: GRBL shield – how to make it running? #3393
    alden
    Member

    Jan, the only way to set the maximum feed rate ($4) and seek rate($5) is to try various settings. Set these the same, and start low and go higher. $5 sets the velocity in a G0, $4 sets the maximum feed rate (F word) in G1, G2 and G3. In some cases people set the max feed rate to be lower than the seek rate, but I’d recommend keeping them the same for now to keep it simple.

    The acceleration value $8 will also affect the feed rate and seek rate. In some high-speed cases $9 may also need adjustment, but only if you are having problems with cornering.

    Please email us at synthetos at gmail.com for a shipping address

    • This reply was modified 12 years, 3 months ago by alden.
    in reply to: coolterm not sending all gcode #3389
    alden
    Member

    This is good news, but it’s also bad news – if the 2.2.17 driver is broken. How did you get 2.2.16? I had to hack the URL. Did you?

    I will want to test this before changing the config page. I have 2 laptops that I use, an the one I’m on right now has the 2.2.17 driver in my “sources” directory, and I have no way to test what is actually loaded as it appears that the USB listing in the system profiler doesn’t show a driver unless it’s activated – which I will not be able to do for the next week due to travel.

    In the mean time, happy cutting.

     

    UPDATE: I had to run home. Here’s what’s in my system profiler under FT232R USB UART:

    Product ID: 0x6001

    Vendor ID: 0x0403  (Future Technology Devices International Limited)

    Version: 6.00

    Serial Number: A5014Y93

    Speed: Up to 12 Mb/sec

    Manufacturer: FTDI

    Location ID: 0xfa122000 / 10

    Current Available (mA): 500

    Current Required (mA): 90

    No indication of driver revision other then “Version” that doesn’t seem to correlate to the driver rev. How did you determine your driver revision?

    • This reply was modified 12 years, 3 months ago by alden.
    in reply to: Z axis moves in the wrong direction #3387
    alden
    Member

    Victor,

    Thanks for registering at the forum. Your questions handled one-by-one:

    – Here is a link about setting the pots. They are one turn pots so *please do not turn them more than 270 degrees* or they will break. However, I doubt the pot settings are your problem, so I wouldn’t mess with them right now. Just set them in the middle of the range.

    https://www.synthetos.com/wiki/index.php?title=Using_the_grblShield#Setting_Motor_Current

    – I’d like to confirm that you (1) have the kit from Inventables and that (2) your grblShield has the Z axis mod. Does your board have the little wire to the switch like the one in the last picture on this page? (scroll all the way down)

    https://www.synthetos.com/wiki/index.php?title=Z_Axis_Mod_for_Shapeoko

    – If it does not let me know. Can you please post your grbl settings? Z should not be more than 1200 ($3=1200), and might possibly need to be set to less, depending on the friction in your system.

    – Check the Z axis motor plug. DOes this give good contact? If any 1 of the 4 wires does not contact or contacts intermittently then it could cause what you are seeing.

    – If you swap motors – i.e. put the Z motor on Y and the Y motor on Z – what happens? This may be hard to do given that the motors are in the machine – you may need to remove the Y belt and/or change the grbl settings. Does Z work OK and Y have problems, or the other way around?

    Please let me know how this goes.

    • This reply was modified 12 years, 3 months ago by alden.
    in reply to: coolterm not sending all gcode #3384
    alden
    Member

    Congrats. This sounds like a driver problem to me. THe XON/OFF is not being handled correctly. The host drivers might warrant some more attention.

    in reply to: coolterm not sending all gcode #3381
    alden
    Member

    Interesting machine. You have 25.4 thread per inch screws? Try turning off the status reports and see if that helps. 50 ms is very fast. I’m thinking of making something like 200ms the minimum.

    in reply to: coolterm not sending all gcode #3377
    alden
    Member

    I flashed a board with 338.11 and am ran it to completion, so it doesn’t look like that’s the problem, but can you please dump your TinyG settings with a $$ and post them?

    D4 is the RX and D3 is the TX. I think both are working or you wouldn’t have any echo at all. The symptom you describe sounds like the XOFF is being sent by TinyG to the host and the host honors it, but the subsequent XON is either never sent or is not honored. If you look at the echo in Coolterm the periods (.) in the text are the XON or XOFF characters.

    Separately, I don’t know why your Gcode has periods at the end of integer numbers, but this should not affect anything and indeed doesn’t give my setup any problem.

    • This reply was modified 12 years, 3 months ago by alden.
    in reply to: coolterm not sending all gcode #3373
    alden
    Member

    Feedhold is problematic with XON/XOFF, as you have to get it through the serial interface, which is blocked during XOFF. ALso, Coolterm is unpredictable as to when you can get a console charater into a file download. Feedhold is more something we need to work into tgFX.

    in reply to: coolterm not sending all gcode #3372
    alden
    Member

    Almost all the way through. SO the basics work. We should be looking for something in your setup. It;s also possible that it’s something in 338.11 that’s not in 338.12, but I’m not aware of any bug I fixed between the two of this type. I’ve been meaning to get 339.2 out of dev and tested and into master. This fixed a short arc problem. Do you have the ability to flash new firmware? (BTW – just finished).

    in reply to: coolterm not sending all gcode #3369
    alden
    Member

    Out of curiosity, what version of MacOS are you running? I’m on 10.7.4  I think you mentioned it also failed on a PC for you.

    in reply to: coolterm not sending all gcode #3368
    alden
    Member

    Seems to have gotten almost 1/2 of the way around. Currently processing line 746

    in reply to: coolterm not sending all gcode #3365
    alden
    Member

    I just ran Coolterm build 162 at the high feed rate. Ran through OK. So that’s not it. I will now try your really really really really slow feed rate, so don’t expect a post back for a while.

    Yes, I have run jobs that have taken a long time, but I don’t think an hour. Let’s also be sure it’s not the stepper driver chips going into thermal shutdown. It doesn’t sound like it, but let’s rule that out. At slow speeds the chips take maximum current (and deliver maximum torque)

Viewing 15 posts - 526 through 540 (of 702 total)