K8400 firmware update times out


#1

My Vertex K8400 is running on version v1.1 and I want to upgrade the printer to v1.4 as is specified in the installation documentation. The USB connection works, I see send and receive message but after a will the communication stops.
What can be the issue, who can help me?

The log starts with: (491 lines)

Binaire sketch-grootte: 128.606 bytes (van een 258.048-byte maximum)
C:\Program Files (x86)\Arduino\hardware/tools/avr/bin/avrdude -CC:\Program Files (x86)\Arduino\hardware/tools/avr/etc/avrdude.conf -v -v -v -v -patmega2560 -cwiring -P\.\COM3 -b115200 -D -Uflash:w:C:\Users\marcel\AppData\Local\Temp\build8457479930067962402.tmp\Marlin.cpp.hex:i

avrdude: Version 5.11, compiled on Sep 2 2011 at 19:38:36
Copyright © 2000-2005 Brian Dean, http://www.bdmicro.com/
Copyright © 2007-2009 Joerg Wunsch

     System wide configuration file is "C:\Program Files (x86)\Arduino\hardware/tools/avr/etc/avrdude.conf"

     Using Port                    : \\.\COM3
     Using Programmer              : wiring
     Overriding Baud Rate          : 115200

avrdude: wiring_open(): releasing DTR/RTS
avrdude: wiring_open(): asserting DTR/RTS
avrdude: Send: . [1b] . [01] . [00] . [01] . [0e] . [01] . [14]
avrdude: Recv: n [6e]
avrdude: Recv: & [26]
avrdude: Recv: . [03]

and ends with:
avrdude: Recv: . [f9]
avrdude: Recv: K [4b]
avrdude: Recv: r [72]
avrdude: Recv: . [a2]
avrdude: Recv: . [fc]
avrdude: Recv:
avrdude: stk500v2_ReceiveMessage(): timeout
avrdude: Send: . [1b] . [01] . [00] . [01] . [0e] . [01] . [14]
avrdude: Recv:
avrdude: stk500v2_ReceiveMessage(): timeout
avrdude: Send: . [1b] . [01] . [00] . [01] . [0e] . [01] . [14]
avrdude: Recv:
avrdude: stk500v2_ReceiveMessage(): timeout
avrdude: Send: . [1b] . [01] . [00] . [01] . [0e] . [01] . [14]
avrdude: Recv:
avrdude: stk500v2_ReceiveMessage(): timeout
avrdude: Send: . [1b] . [01] . [00] . [01] . [0e] . [01] . [14]
avrdude: Recv:
avrdude: stk500v2_ReceiveMessage(): timeout
avrdude: Send: . [1b] . [01] . [00] . [01] . [0e] . [01] . [14]
avrdude: Recv:
avrdude: stk500v2_ReceiveMessage(): timeout
avrdude: stk500v2_getsync(): timeout communicating with programmer

avrdude done. Thank you.


#2

Did you follow all of the instructions in this link?
https://manuals.velleman.eu/article.php?id=31
Also the Arduino software needs to be 1.0.6 or lower.


#3

Hi,

I borrowed a Windows 10 laptop a ran the procedure again as listed in the link.

  • download the vertex version 1.4 dual head,
  • download the FTDI driver, but didn’t install
  • connected the printer and Windows 10 configured the com3 port
  • downloaded the arduino 1.0.6
  • started arduino via Marlin.ino
  • set the serial port to COM3 ( only serial port available)
  • set arduino to Arduino MEGA 2560 or MEGA ADK
  • on the printer, set the jprog jumper

started the up;load and it failed now on

Binaire sketch-grootte: 128.606 bytes (van een 258.048-byte maximum)
avrdude: stk500v2_ReceiveMessage(): timeout
avrdude: stk500v2_ReceiveMessage(): timeout
avrdude: stk500v2_ReceiveMessage(): timeout
avrdude: stk500v2_ReceiveMessage(): timeout
avrdude: stk500v2_ReceiveMessage(): timeout
avrdude: stk500v2_ReceiveMessage(): timeout
avrdude: stk500v2_getsync(): timeout communicating with programmer


#4

That driver is for the communication between windows and the Vertex/Arduino and you didn’t install???

Perhaps could that be the reason for the communication problems.


#5

Can you connect to the printer through Repetier and manually move the head or turn the fans on? If so this would say the driver is find. if not you will need to install the driver.


#6

I installed the repetier software version 1.6.2 inclusive the FDTI driver and without de server.

I tried the manual actions, nothing happend on the printer, but the log showed:

14:31:31.602 : OpenGL version:1.1.0
14:31:31.603 : OpenGL extensions:GL_WIN_swap_hint GL_EXT_bgra GL_EXT_paletted_texture
14:31:31.603 : OpenGL renderer:GDI Generic
14:31:31.603 : Fast VBOs for rendering not supported. Using slower default method.
14:34:47.581 : No start signal detected - forcing start
14:35:28.704 : Communication timeout - reset send buffer block
14:35:57.904 : No start signal detected - forcing start
14:36:39.031 : Communication timeout - reset send buffer block
14:37:19.060 : Communication timeout - reset send buffer block
14:37:59.096 : Communication timeout - reset send buffer block
14:38:39.122 : Communication timeout - reset send buffer block
14:39:19.158 : Communication timeout - reset send buffer block


#7

Check the settings in Repetier.
The com port may be different but the rest should be the same.
Also what do you see in device manager?


#8

Thanks for the info,

My info in dutch looks like


#9

device manager settings in which not the 250000 exits6-11-2018%2016-29-36

6-11-2018%2016-33-50


#10

In device manager mine is set to 9600 8,N,1 no flow control.
However I don’t think the settings in device manager matter.
You could try to set it up like that just for grins.
Do you have a Windows 7 machine you could try it on?


#11

Hi, I have a windows 10 laptop, and I will set the device manager to your values tomorrow,

regards,
Marcel


#12

I tried again a lot of adjustments, but I don’t trust the USB interface on the board now


#13

The reason I asked about Windows 7 is that on Win 10 there were a couple of updates that ripped the USB drivers of a few of the devices.
You should either try to reinstall the drivers or if you have friend with Windows 7 try it on that.


#14

I saw a note from you in a forum message about Octo Pi on Raspberry Pi. I installed this also and I had to same result. Checked an YouTube for the installation and I had the same result. OctoPi saw the USB interface but wouldn’t start communicating.

about windows 10, I spent a lot of time to look into the USB drivers and at the end I had a controlled situation, I switched off the automatic driver download in windows 10.

my issue is also that I don’t have an windows 7 machine around.

Today, I raised a technical issue for how I can test the USB interface on the main board.


#15

If you think it is the control board you can open a ticket in this link.
https://support.velleman.eu/


#16

Yes I opened yesterday ticket 771309 and is now assigned to the repair department.

thanks for the support
Marcel


#17

I wish I could have helped more.
Hope things get better soon.


#18

Hi, I found the issue, iT is hardware relaxed, the port 1 TX , of the FT232 USB driver on the main board wasn’t soldert , so I could move it easily around. I hope I can solder it again.


#19

I don’t know what to tell you.
If you try and fail it could void the warranty.


#20

Hi, the interface is working, I soldert pin 1 , de TX port again and the USB interface was working immediately. Firmware download worked as expected and the Manual control via the repeater also.

Looking to the interface

  • is the com interface is seen in Windows , the communication with the ft232 chip is working,
  • is you got a time- out, then the communication between the ft232 chip and the processor is gone. So this will be a hardware issue.

I was lucky that it concerned pin1 so that I could reach the pin with a soldering iron,

Thanks again with your help