bvi8370

Forum Replies Created

Viewing 9 posts - 1 through 9 (of 9 total)
  • Author
    Posts
  • August 10, 2015 at 9:38 pm in reply to: TinyG won't boot: SpDir light flashing constantly #8209
    bvi8370
    Member

    I’m not sure if this might shed light on the problem I’m having, but the code below is what I see when I reconnect to chilipeppr. There are green checks next to every line before {“mt”:””}. After that there are yellow checks and the buffer stops responding. I hope Synthetos will not burn me on this one. Even though I bought the board just over a month ago. I’ve yet to cut the first part using it.

     {"ej":1}
 {"js":1}
 {"sr":""}
 {"sv":1}
 {"si":250}
 {"qr":""}
 {"qv":1}
 {"ec":0}
 {"jv":1}
 {"hp":""}
 {"fb":""}
 {"mt":""}
 {"sr":{"line":t,"posx":t,"posy":t,"posz":t,"vel":t,"unit":t,"stat":t,"feed":t,"coor":t,"momo":t,"plan":t,"path":t,"gc":t,"dist":t,"mpox":t,"mpoy":t,"mpoz":t}}
 $$
 {"ej":""}
    August 10, 2015 at 2:15 pm in reply to: TinyG won't boot: SpDir light flashing constantly #8206
    bvi8370
    Member

    I haven’t installed limit switches yet. I went ahead and filled out the product support request form.

    • This reply was modified 9 years, 3 months ago by bvi8370.
    August 8, 2015 at 9:19 pm in reply to: TinyG won't boot: SpDir light flashing constantly #8189
    bvi8370
    Member

    No luck after adding -e to the install string. I’ll email Synthetos to see what can be done.

    Thank you again. Your efforts are definitely appreciated.

    August 8, 2015 at 5:38 pm in reply to: TinyG won't boot: SpDir light flashing constantly #8186
    bvi8370
    Member

    Here’s the cmd I’m using:

    avrdude -p x192a3 -c avr109 -b 115200 -P COM3 -U flash:w:tinyg-master-440.18.hex

    It looks the same as the one in the link you provided.

    Both methods, avrdude and the updater return the same messages.

    This one is worrisome:

    avrdude.exe: verification error; content mismatch

    This seems like a long shot, but I’m using a Tinyg post processor script that looks to be dated:

    +================================================
+                                                
+ G Code - Vectric machine output configuration file   
+                                                
+================================================
+                                                
+ History                                        
+                                                
+ Who      When       What                         
+ ======== ========== ===========================
+ Saci     24/09/2012 Written                      
+================================================

POST_NAME = "TinyG (mm) (*.tap)"

FILE_EXTENSION = "tap"

UNITS = "MM"

+------------------------------------------------
+    Line terminating characters                 
+------------------------------------------------

LINE_ENDING = "[13][10]"

+------------------------------------------------
+    Block numbering                             
+------------------------------------------------

LINE_NUMBER_START     = 0
LINE_NUMBER_INCREMENT = 10
LINE_NUMBER_MAXIMUM = 999999

+================================================
+                                                
+    Formating for variables                     
+                                                
+================================================

VAR LINE_NUMBER = [N|A|N|1.0]
VAR SPINDLE_SPEED = [S|A|S|1.0]
VAR FEED_RATE = [F|C|F|1.1]
VAR X_POSITION = [X|C|X|1.3]
VAR Y_POSITION = [Y|C|Y|1.3]
VAR Z_POSITION = [Z|C|Z|1.3]
VAR X_HOME_POSITION = [XH|A|X|1.3]
VAR Y_HOME_POSITION = [YH|A|Y|1.3]
VAR Z_HOME_POSITION = [ZH|A|Z|1.3]

+================================================
+                                                
+    Block definitions for toolpath output       
+                                                
+================================================

+---------------------------------------------------
+  Commands output at the start of the file
+---------------------------------------------------
begin HEADER

""
"( Vectric Aspire post-processor for TinyG mm-no-arc )"
"( [TP_FILENAME] )"
"( File created: [DATE] - [TIME])"
""
"( Material Size: X= [XLENGTH], Y= [YLENGTH], Z= [ZLENGTH])"
""
"(Toolpaths used in this file:)"
"([TOOLPATHS_OUTPUT])"
""

"T[T] M6"
"G21G17G90"
"G0[ZH]"
"G0[XH][YH]"
"M3 [S]"

+---------------------------------------------------
+  Commands output at toolchange
+---------------------------------------------------

begin TOOLCHANGE

"M0"
"T[T] M6"
"M3 [S]"

+---------------------------------------------------
+  Commands output for rapid moves 
+---------------------------------------------------
begin RAPID_MOVE

"G0[X][Y][Z]"

+---------------------------------------------------
+  Commands output for the first feed rate move
+---------------------------------------------------
begin FIRST_FEED_MOVE
"G1[X][Y][Z][F]"

+---------------------------------------------------
+  Commands output for feed rate moves
+---------------------------------------------------
begin FEED_MOVE
"[X][Y][Z]"

+---------------------------------------------------
+  Commands output for a new segment - toolpath
+  with same toolnumber but maybe different feedrates
+---------------------------------------------------

begin NEW_SEGMENT
""
"([TOOLPATH_NAME])"
""
"M03 [S]"

+---------------------------------------------------
+  Commands output at the end of the file
+---------------------------------------------------
begin FOOTER
"M5"
"M9"
"G0[ZH]"
"G0[XH][YH]"
"M2"
""

    I there anyway this would cause the board to malfunction? Everything was fine before I attempted to load the g-code using this post processor.

    Thanks for your help!

    • This reply was modified 9 years, 3 months ago by bvi8370. Reason: posted incorrect post processor used
    August 8, 2015 at 2:37 pm in reply to: TinyG won't boot: SpDir light flashing constantly #8184
    bvi8370
    Member

    This issue just popped up for me as well. I upgraded to 440.16 a couple weeks ago and finally got my spoilboard installed last night. Everything was running fine – jogging, test cutting the Chilipeppr logo and grim reaper gcode I found somewhere.

    Today’s task was to level the spoilboard to the cutter in preparation to cut the t-track slots. I laid out the spoilboard in vcarve pro, created the tool paths and attempted to load them into Chilipeppr. Chilipeppr proceeded to buffer 10000 lines. As it was loading, there were numerous strange symbols for each line displayed in the feedback window. I checked the code in notepad++. It looked normal but I went ahead and resaved it to make sure it was just plain text. I tried the code in Chilipeppr again but the same thing happened – strange symbols. I looked at the Tinyg and saw the spdir LED flashing continuously. Resetting, power cycling and reseating the USB did nothing.

    At this point I attempted to upgrade the firmware to 440.18 and edge 442.04. Both seemed to write but fail the verify process. Spdir continues to flash.

    Json seems to connect to the Tinyg on COM3, but the buffer in Chilipeppr freezes and each configuration line has a yellow check.

    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 performed
             To disable this feature, specify the -D option.
avrdude.exe: current erase-rewrite cycle count is -269488145 (if being tracked)
avrdude.exe: erasing chip
avrdude.exe: reading input file "tinyg-master-440.18.hex"
avrdude.exe: input file tinyg-master-440.18.hex auto detected as Intel Hex
avrdude.exe: writing flash (118196 bytes):

Writing | ################################################## | 100% 11.10s

avrdude.exe: 118196 bytes of flash written
avrdude.exe: verifying flash memory against tinyg-master-440.18.hex:
avrdude.exe: load data flash data from input file tinyg-master-440.18.hex:
avrdude.exe: input file tinyg-master-440.18.hex auto detected as Intel Hex
avrdude.exe: input file tinyg-master-440.18.hex contains 118196 bytes
avrdude.exe: reading on-chip flash data:

Reading | ################################################## | 100% 14.00s

avrdude.exe: verifying ...
avrdude.exe: verification error, first mismatch at byte 0x0000
             0x0c != 0x00
avrdude.exe: verification error; content mismatch

avrdude.exe done.  Thank you.

    I’m really starting to regret buying the Tinyg…

    Anyone has suggestions?

    July 6, 2015 at 7:36 pm in reply to: Newb Help needed #7944
    bvi8370
    Member

    I received the Meanwell 350 watt PSU today, and I’m happy to report the Tinyg and NEMA23 steppers work flawlessly with it.

    I spent the weekend cutting, threading and assembling 8020 extrusions for the frame and gantry. Now to get a project box to mount the electronics and pick out a spindle. Here’s a photo of the project so far.

    FLA100 build

    I have a local steel fabricator cutting the rails and leadscrew to length. My original plan was to just buy the frame from FLA, but building everything myself has been a lot more gratifying. Nate has the plans and BOM readily available for the FLA100 on his website.

    Thanks for the help troubleshooting!

    Barry

    • This reply was modified 9 years, 4 months ago by bvi8370.
    • This reply was modified 9 years, 4 months ago by bvi8370.
    • This reply was modified 9 years, 4 months ago by bvi8370.
    June 30, 2015 at 9:55 pm in reply to: Newb Help needed #7910
    bvi8370
    Member

    I followed your steps and reset the board. I’m guessing the board had a default config on it, as I never made any changes to the existing config.

    I did a comparison of the previous setup($$) to verify the file did in fact change. Nothing notable was different, just some json feedback parameters. All the feed rates were the same.

    The first test G0 X125 halted after about 5 seconds with the high pitch I’ve come to fear so much. Also, the USB disconnects as soon as the code is executed. That is starting to sound like a power issue.

    I lowered the feed rates for each motor from 800mm/min to 300mm. Pretty much the same result except slower.
    I lowered the feed rates to 100mm and that’s when the PSU took a dump. There was a small pop from the PSU during the G0 X125 test. No smoke but it’s KIA. Maybe the PSU was on death’s door the whole time. I hope the tinyg was unaffected.

    Off to Mouser.com I guess. 8020 extrusions arrived today; linear motion comes tomorrow so it’s kinda late to turn back now!

    By the way, of the two Meanwell PSUs suggested here, which one might be best for my setup?

    Thanks again for your help!

    Barry

    June 29, 2015 at 8:26 pm in reply to: Newb Help needed #7900
    bvi8370
    Member

    I moved the setup to another room to isolate it from the rest of my computer and network gear. I was testing on Win7 x64 but switched to my laptop which is Win10 tech preview. I also installed Teraterm to see if the feedback from $$ was formatted better than Putty – it’s not.

    Moving everything seemed to work briefly but each motor would stop part way through the iterations using G0 X125, G0 Y125 and G0 Z125. The coordinates continued to increment in Teraterm even though the motors had stopped abruptly and were letting of a high pitch(tried all three axes separately and together). At least the Tinyg was reporting the entire test back to Teraterm. However, the reporting stopped after a few tests, and Windows started losing connection to the Tinyg every time I run a test. Windows reports the device has malfunctioned, and I have to pull the power from the wall for everything to reconnect. The fan is not connected.

    The power supply was steady at 24.4V through every test – even when the motors halted. I’m not sure enough voltage is making it to the motors. I tested on the black and green and only saw 2.5V. The motors are 5V. I’m not sure if the 5V is across both windings for a total of 5V.

    I’ve uploaded a couple photos of the board with connections and the PSU.

    Beyond frustrated at this point. Maybe I bought some of the few motors that just don’t work well with Tinyg. Or maybe my Tinyg is a lemon.

    June 28, 2015 at 9:37 pm in reply to: Newb Help needed #7894
    bvi8370
    Member

    cmcgrath5035,

    Here’s the link to the dump file. The firmware version is 440.14. I ran the same g-code in putty, and the results were the same. I did try Chilipeppr before tgFX, but there was no movement from the motors. I probably wasn’t doing something right. The fan was connected to the board, but it’s not a big deal for me to wire it to the extra posts on the power supply. The job is running in air (the tinyg and motors are not mounted to a machine yet).

    Thanks for the help!

    Barry

  • Author
    Posts
Viewing 9 posts - 1 through 9 (of 9 total)