Page 1 of 1

Connection problems

Posted: Wed Jun 30, 2021 10:34 am
by Bas
Hi,

I have connection issues since the latest release, software says the macine is in error state. But it is not as far I can see...

log:

Application Start
Version: 1.0.7849.18043, build date: 06/28/2021 10:01:26
Reading C:\LitePlacer\LitePlacer.Appsettings
Basic Setup tab begin
LoadVideoAlgorithms from C:\LitePlacer\LitePlacer.VideoAlgorithms
UpdateVideoProcessing()
BuildFunctionsList:
Threshold, 70, 0, 0, 0, 0, 0, 0, 0
Invert, 128, 0, 0, 0, 0, 0, 0, 0
Loading temp CAD data file
Loading temp job data file
UpCamera start, moniker= @device:pnp:\\?\usb#vid_5149&pid_13d3&mi_00#6&1f5f5e49&0&0000#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\global
X: 640, Y: 480 at 30fps
X: 160, Y: 120 at 30fps
X: 320, Y: 240 at 30fps
X: 1280, Y: 1024 at 7fps
X: 800, Y: 600 at 7fps
*** Camera started: 35
DownCamera start, moniker= @device:pnp:\\?\usb#vid_5149&pid_13d3&mi_00#7&1c6edbb1&1&0000#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\global
X: 640, Y: 480 at 30fps
X: 160, Y: 120 at 30fps
X: 320, Y: 240 at 30fps
X: 1280, Y: 1024 at 7fps
X: 800, Y: 600 at 7fps
*** Camera started: 34
DownCamera activated
Loading tapes with nozzles data
Reading v2 format file C:\LitePlacer\LitePlacer.TapesData_v2
Loading nozzles data
Reading v2 format file C:\LitePlacer\LitePlacer.NozzlesLoadData_v2
Reading v2 format file C:\LitePlacer\LitePlacer.NozzlesUnLoadData_v2
Reading v2 format file C:\LitePlacer\LitePlacer.NozzlesVisionParameters_v21
Loading nozzle calibration data from C:\LitePlacer\LitePlacer.NozzlesCalibrationData_v3
Connected to serial port COM4
==> M115
Com closing delay:
Done.
Connected to serial port COM4
==> M115
*** Cnc.Connect(), did not find a supported board.
Startup completed.


Any tips to solve the issue here?

Re: Connection problems

Posted: Wed Jun 30, 2021 3:23 pm
by Bas
Looks a bit similar to this post. But I cannot get a response in Coolterm. Only sone data coming in when I hit the reset button:

{"r":{"fv":0.970,"fb":440.20,"hp":1,"hv":8,"id":"5X3848-Q4P","msg":"SYSTEM READY"},"f":[1,0,0,5868]}
{"qr":32,"qi":1,"qo":1}




https://liteplacer.com/phpBB/viewtopic. ... =403#p2654

Re: Connection problems

Posted: Wed Jun 30, 2021 8:15 pm
by KeithM
M115 is an instruction asking the board to report on its firmware. The stock tinyg does not support this instruction.

Re: Connection problems

Posted: Thu Jul 01, 2021 8:18 am
by Bas
So why does the liteplacer software send this command to tinyG? Can I change this in boardsettings? This puzzles me.

I tried to use older software but the problem still exists.

Re: Connection problems

Posted: Thu Jul 01, 2021 1:04 pm
by JuKu
KeithM wrote:M115 is an instruction asking the board to report on its firmware. The stock tinyg does not support this instruction.
But it sends a response that the software knows it comes from TinyG.

Re: Connection problems

Posted: Fri Jul 02, 2021 5:15 pm
by JuKu
Solved via email.

Re: Connection problems

Posted: Fri Aug 06, 2021 10:27 am
by marcin_gajewski
Hi JuKu,

I do suffer the same issue. What's worse, in previous version of SW all works fine, but latest can't connect due to M115 no respond.

I manage to have it working once, when I power cycle PC and went directly to new SW, but after playing with machine and using EMERENCY button (RESET board), it goes to same issue.

Re: Connection problems

Posted: Sun Aug 15, 2021 10:40 pm
by Vbhunt
Thought I do a clean start for the new software. I re-flashed TinyG firmware: Version 0.97 Build 440.20
Started up LitePlacer and got the following:
Application Start
Version: 1.0.7849.18043, build date: 06/28/2021 10:01:26
Basic Setup tab begin
UpdateVideoProcessing()
BuildFunctionsList:
No saved temp CAD data file
No saved temp job data file
Did not find file C:\LitePlacer\LitePlacer.TapesData_v2
Loading nozzles data
Didn't find file C:\LitePlacer\LitePlacer.NozzlesLoadData_v2
Didn't find file C:\LitePlacer\LitePlacer.NozzlesUnLoadData_v2
Didn't find file C:\LitePlacer\LitePlacer.NozzlesVisionParameters_v21
Startup completed.
B: Refresh List
B: Connect
Connected to serial port COM4
==> M115
<== {"r":{"gc":"M115"},"f":[1,132,5,8387]}
<== {"sr":{"posx":0.000,"posy":0.000,"posz":0.000,"posa":0.000,"feed":0.00,"vel":0.00,"unit":1,"coor":1,"dist":0,"frmo":1,"stat":1}}
Com closing delay:
Done.
Connected to serial port COM4
==> M115
<== {"r":{"gc":"M115"},"f":[1,132,5,8387]}
*** Cnc.Connect(), did not find a supported board.
Brought up CoolTerm to see if I could talk to TinyG. Here is result:
{"r":{"fv":0.970,"fb":440.20,"hp":1,"hv":8,"id":"7U4895-GYX","msg":"SYSTEM READY"},"f":[1,0,0,4710]}
M115
tinyg [mm] err: M code unsupported: M115
$$
[fb] firmware build 440.20
[fv] firmware version 0.97
[hp] hardware platform 1.00
[hv] hardware version 8.00
[id] TinyG ID 7U4895-GYX
[ja] junction acceleration 2000000 mm
[ct] chordal tolerance 0.0100 mm
[sl] soft limit enable 0
[st] switch type 1 [0=NO,1=NC]
... ( large number of lines elided }
[g30a] g30 a position 0.000 deg
[g30b] g30 b position 0.000 deg
[g30c] g30 c position 0.000 deg
tinyg [mm] ok>
...
Clearly TinyG is responding. I'm probably doing something really dumb but have been unable to figure out what it is. Any help or suggestions on how to fix my "unsupported board" problem?
Thanks!

Re: Connection problems

Posted: Mon Aug 23, 2021 9:22 am
by JuKu
Background: As you can guess, there is support for another board under the hood, but it is not yet ready for announcement. Therefore, the check is needed. It seems to cause issues, so I'm going to temporarily remove it about now. But that is not the real solution, so I need to fix it properly, for all boards out there. I don't know yet how, but that can wait. For now, plese show the full response to command $ (just a dollar sign), perhaps I can find out why your 440.20 firmware gives a different response than my 440.20. :shock:

I might be able to get out a better software today. If not, it will take towards the end of week.

Re: Connection problems

Posted: Mon Aug 23, 2021 12:52 pm
by JuKu
JuKu wrote: I might be able to get out a better software today. If not, it will take towards the end of week.
I did this quick, hopefully I didn't break anything. viewtopic.php?f=10&t=6448