psyko

Forum Replies Created

Viewing 6 posts - 31 through 36 (of 36 total)
  • Author
    Posts
  • in reply to: Mysterious Serial communication in custom software #4571
    psyko
    Member

    Ok, problem solved !
    This was definitely me handling the Xon/Xoff flag incorrectly…
    It seems to be solved now ๐Ÿ™‚

    in reply to: Mysterious Serial communication in custom software #4569
    psyko
    Member

    I tried again, and it doesn’t seem to be linked to the Xon/Xoff. Even when sending one command every second, I have the issue…

    Even worst, it jumped from line 49 to line 74….

    {"r":{"gc":"N49G1F300.0Z-2.0","n":49,"f":[1,0,103,5670]}}
    {"sr":{"line":25,"posy":18.998,"posz":3.000,"vel":21.88}}
    {"sr":{"posy":18.996,"vel":22.12}}
    {"sr":{"posy":18.974,"vel":33.36}}
    {"sr":{"posy":18.935,"vel":60.67}}
    {"sr":{"posy":18.865,"vel":104.03}}
    {"sr":{"posy":18.752,"vel":163.46}}
    {"sr":{"posy":18.603,"vel":230.67}}
    {"sr":{"posy":18.370,"vel":320.46}}
    {"sr":{"posy":18.062,"vel":407.19}}
    {"sr":{"posy":17.690,"vel":477.86}}
    {"sr":{"posy":17.265,"vel":532.46}}
    {"sr":{"posy":16.803,"vel":571.01}}
    {"sr":{"posy":16.365,"vel":591.97}}
    {"sr":{"posy":15.867,"vel":600.00}}
    {"sr":{"posy":15.368,"vel":600.00}}
    {"sr":{"posy":14.868}}
    {"sr":{"posy":14.369}}
    {"sr":{"posy":13.870}}
    {"sr":{"posy":13.420}}
    {"sr":{"posy":12.921}}
    {"sr":{"posy":12.422}}
    {"sr":{"posy":11.923}}
    {"sr":{"posy":11.423}}
    {"sr":{"posy":10.924}}
    {"sr":{"posy":10.475}}
    {"sr":{"posy":9.975}}
    {"sr":{"posy":9.476}}
    {"sr":{"posy":8.977}}
    {"sr":{"posy":8.477}}
    {"sr":{"posy":7.978}}
    {"sr":{"posy":7.529}}
    {"sr":{"posy":7.029}}
    {"sr":{"posy":6.530}}
    {"sr":{"posy":6.031}}
    {"sr":{"posy":5.531}}
    {"sr":{"posy":5.032}}
    {"sr":{"posy":4.583}}
    {"sr":{"posy":4.083}}
    {"sr":{"posy":3.584}}
    {"sr":{"posy":3.085}}
    {"sr":{"posy":2.587,"vel":591.97}}
    {"sr":{"posy":2.104,"vel":567.88}}
    {"sr":{"posy":1.692,"vel":532.46}}
    {"sr":{"posy":1.272,"vel":477.86}}
    {"sr":{"posy":0.905,"vel":407.19}}
    {"sr":{"posy":0.605,"vel":320.46}}
    {"sr":{"posy":0.380,"vel":230.67}}
    {"sr":{"posy":0.223,"vel":156.79}}
    {"sr":{"posy":0.128,"vel":104.03}}
    {"sr":{"posy":0.062,"vel":60.67}}
    {"sr":{"posy":0.025,"vel":33.36}}
    {"sr":{"posy":0.004,"vel":22.12}}
    {"r":{"gc":"N74G1Y0.0","n":74,"f":[1,0,19,2165]}}
    • This reply was modified 11 years, 2 months ago by psyko.
    in reply to: Synthetos board does not respond #4413
    psyko
    Member

    Riley,

    Thanks but for some reasons, the link you provide don’t work. I mean, when I do “Register as” in firefox, the MIME type of the file change. It was recognized as a binary raw by AVR Dude (and the size of the file was around 900ko). I had to download the full repository as a zip file to have the correct MIME type. It was then recognized as an Intel Hex and worked perfectly. I moved to the edge version of the Firmware.

    Regarding the process for a non responsive board, I think I told you everything. The only thing I did to fix was to reinstall the firmware (the exact same master version) and it worked like a charm. I even managed to get my motor to move. I still have to set the correct values in the setting.

    I’m running a custom Shapeoko :
    http://www.shapeoko.com/forum/viewtopic.php?f=30&t=1608
    And the enclosure is
    http://www.shapeoko.com/forum/viewtopic.php?f=30&t=1922

    I won’t be able to post pictures, since I’m away from my workshop for at least 2 weeks now.

    Thanks for the help.
    I can’t wait to test my TinyG board. I was using Grbl (without issues) before and switch for the 4th motor support and the configurable microstepping that’s lacking on Grbl.

    I’ll keep you in touch

    in reply to: Synthetos board does not respond #4411
    psyko
    Member

    Ok got it to work.

    Reinstalling firmware (with same version did the job).

    Previous error was that while downloading, Windows changed the format of the file from Intel Hex to Binary Raw.

    Is it possible to only download the latest firmware at the correct format, without cloning the git repo ?

    Thanks

    in reply to: Synthetos board does not respond #4410
    psyko
    Member

    Hello, thanks for the answer.

    At my first connection, following this wiki page https://github.com/synthetos/TinyG/wiki/Connecting-TinyG
    I received the expected response (an Json {“r”:…} response enveloppe) but I don’t remember the content.

    Then I unplugged the power and assembled it into my enclosure.
    After that, I tried the exact same steps (coolterm, 115.200 bauds… so on), and I do not have any JSON answer. The serial port is listed, and I manage to connect to it, but the board remain silent.
    I even tried with tgfx which is stuck at :


    [+]Connected to COM5 Serial Port Successfully.

    Getting TinyG Firmware Build Version….

    I already tried to update the FTDI drivers, try to restart my computer, reset the TinyG board, change USยงB cable. Nothing works.

    Updating firmware gives me an error :

    C:\Program Files\arduino-1.0.3\hardware\tools\avr\bin>avrdude.exe -p x192a3 -c
    vr109 -b 115200 -P COM5 -U flash:w:tinyg.hex

    Connecting to programmer: .
    Found programmer: Id = “XBoot++”; type = S
    Software Version = 1.7; No Hardware Version given.
    Programmer supports auto addr increment.
    Programmer supports buffered memory access with buffersize=512 bytes.

    Programmer supports the following devices:
    Device code: 0x7b

    avrdude.exe: AVR device initialized and ready to accept instructions

    Reading | ################################################## | 100% 0.01s

    avrdude.exe: Device signature = 0x1e9744
    avrdude.exe: NOTE: FLASH memory has been specified, an erase cycle will be perf
    rmed
    To disable this feature, specify the -D option.
    avrdude.exe: erasing chip
    avrdude.exe: reading input file “tinyg.hex”
    avrdude.exe: input file tinyg.hex auto detected as raw binary
    avrdude.exe: writing flash (204800 bytes):

    Writing | ################################################## | 100% 26.94s

    avrdude.exe: 204800 bytes of flash written
    avrdude.exe: verifying flash memory against tinyg.hex:
    avrdude.exe: load data flash data from input file tinyg.hex:
    avrdude.exe: input file tinyg.hex auto detected as raw binary
    avrdude.exe: input file tinyg.hex contains 204800 bytes
    avrdude.exe: reading on-chip flash data:

    Reading | ################################################## | 100% 26.20s

    avrdude.exe: verifying …
    avrdude.exe: verification error, first mismatch at byte 0x30000
    0x6c != 0x0d
    avrdude.exe: verification error; content mismatch

    avrdude.exe done. Thank you.

    in reply to: tool height probe and center finder functionality #4399
    psyko
    Member

    Hi folks,

    Any news on this subject ?
    I’d like to use a tool length sensor such as this http://tinyurl.com/l88xufm

    I guess, it would be possible by reversing the Z axis and do a Z homing only, but that is definitely not clean ๐Ÿ™‚

    Thanks

Viewing 6 posts - 31 through 36 (of 36 total)