Red flashing light when trying to adjust settings?

I am post processing from HSMXpress.
cnc.js popped up questions saying ‘There is a resumable error. Would you like to continue running?’. I have since found the setting to ‘ignore resumeable errors’.

The homing and limit switches work fine. The machine homes itself properly, and the limit switches kill it if they are tripped. Everything actually work brilliantly with no jitters or odd behavior – until I try to change a setting.

I am seeing errors at startup that I don’t remember (but I wasn’t paying attention in the past because it all worked great).

This is what the console shows when I connect:

————————————————————–

CNCjs 1.9.20 [TinyG]
Connected to COM4 with a baud rate of 115200
feeder> {ej:1}
feeder> {jv:4}
feeder> {qv:1}
feeder> {sv:1}
feeder> {si:100}
{“r”:{“jv”:4},”f”:[1,0,7,7333]}
{“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}}
{“r”:{“qv”:1},”f”:[1,0,7,6003]}
{“r”:{“sv”:1},”f”:[1,0,7,9250]}
{“r”:{“si”:100},”f”:[1,0,9,2707]}
feeder> {spe:n}
{“r”:{“spe”:null},”f”:[1,100,8,8836]}
{“err”:{“code”:100,”msg”:”Unrecognized command or config name”}}
feeder> {spd:n}
{“r”:{“spd”:null},”f”:[1,100,8,6786]}
{“err”:{“code”:100,”msg”:”Unrecognized command or config name”}}
feeder> {spc:n}
{“r”:{“spc”:null},”f”:[1,100,8,4736]}
{“err”:{“code”:100,”msg”:”Unrecognized command or config name”}}
feeder> {sps:n}
{“r”:{“sps”:null},”f”:[1,100,8,704]}
{“err”:{“code”:100,”msg”:”Unrecognized command or config name”}}
feeder> {com:n}
{“r”:{“com”:null},”f”:[1,100,8,2342]}
{“err”:{“code”:100,”msg”:”Unrecognized command or config name”}}
feeder> {cof:n}
{“r”:{“cof”:null},”f”:[1,100,8,4826]}
{“err”:{“code”:100,”msg”:”Unrecognized command or config name”}}
feeder> {sr:{stat:t,line:t,vel:t,feed:t,unit:t,coor:t,momo:t,plan:t,path:t,dist:t,admo:t,frmo:t,tool:t,posx:t,posy:t,posz:t,posa:t,posb:t,posc:t,mpox:t,mpoy:t,mpoz:t,mpoa:t,mpob:t,mpoc:t}}
feeder> {sys:n}
feeder> {mt:n}
feeder> {pwr:n}
feeder> {qr:n}
feeder> {sr:n}
{“r”:{“sr”:{“stat”:true,”line”:true,”vel”:true,”feed”:true,”unit”:true,”coor”:true,”momo”:true,”plan”:true,”path”:true,”dist”:true,”admo”:true}},”f”:[1,100,181,722]}
{“err”:{“code”:100,”msg”:”Unrecognized command or config name”}}
{“r”:{“sys”:{“fb”:440.20,”fv”:0.970,”hp”:1,”hv”:8,”id”:”8U1122-MUJ”,”ja”:100000,”ct”:0.0100,”sl”:0,”st”:1,”mt”:2.00,”ej”:1,”jv”:4,”js”:1,”tv”:1,”qv”:1,”sv”:1,”si”:100,”ec”:0,”ee”:0,”ex”:1,”baud”:5,”net”:0,”gpl”:0,”gun”:1,”gco”:1,”gpa”:2,”gdi”:0}},”f”:[1,0,8,1385]}
{“r”:{“mt”:2.00},”f”:[1,0,7,1467]}
{“r”:{“pwr”:{“1″:0,”2″:0,”3″:0,”4″:0}},”f”:[1,0,8,9987]}
{“r”:{“qr”:32},”f”:[1,0,7,7766]}
{“r”:{“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}},”f”:[1,0,7,3689]}
>

——————————————————————-

And this is what resumeable errors look like:

{“r”:{},”f”:[1,0,9,4402]}
{“sr”:{“posz”:0.000}}
{“qr”:32}
> G2 X-0.4143 Y-0.0886 I0. J0.0554
{“err”:{“code”:155,”msg”:”Arc specification error”,”line”:41,”data”:”G2 X-0.4143 Y-0.0886 I0. J0.0554″}}
> X-0.3664 Y-0.0609 I0.048 J-0.0277
{“err”:{“code”:155,”msg”:”Arc specification error”,”line”:42,”data”:”X-0.3664 Y-0.0609 I0.048 J-0.0277″}}
> G3 X0.1571 Y0.0221 I0. J0.0554
{“err”:{“code”:155,”msg”:”Arc specification error”,”line”:45,”data”:”G3 X0.1571 Y0.0221 I0. J0.0554″}}
> X0.1092 Y0.0498 I-0.048 J-0.0277
{“err”:{“code”:155,”msg”:”Arc specification error”,”line”:46,”data”:”X0.1092 Y0.0498 I-0.048 J-0.0277″}}
> G2 X-0.4205 Y0.1329 I0. J0.0554
{“err”:{“code”:155,”msg”:”Arc specification error”,”line”:48,”data”:”G2 X-0.4205 Y0.1329 I0. J0.0554″}}
> X-0.3726 Y0.1605 I0.048 J-0.0277
{“err”:{“code”:155,”msg”:”Arc specification error”,”line”:49,”data”:”X-0.3726 Y0.1605 I0.048 J-0.0277″}}
> G3 X0.3303 Y0.2436 I0. J0.0554
{“err”:{“code”:155,”msg”:”Arc specification error”,”line”:53,”data”:”G3 X0.3303 Y0.2436 I0. J0.0554″}}
> X0.2824 Y0.2713 I-0.048 J-0.0277
{“err”:{“code”:155,”msg”:”Arc specification error”,”line”:54,”data”:”X0.2824 Y0.2713 I-0.048 J-0.0277″}}
> G3 X0.4205 Y0.4651 I0. J0.0554
{“err”:{“code”:155,”msg”:”Arc specification error”,”line”:61,”data”:”G3 X0.4205 Y0.4651 I0. J0.0554″}}
> X0.3726 Y0.4928 I-0.048 J-0.0277
{“err”:{“code”:155,”msg”:”Arc specification error”,”line”:62,”data”:”X0.3726 Y0.4928 I-0.048 J-0.0277″}}
client> {“qr”:””}
{“r”:{“qr”:32},”f”:[1,0,10,9617]}

Thanks for the reply.

The resumable errors problem is fixed – it was a decimal precision problem as you predicted, and is no longer a problem.

This is what the problem is now:
When I connect a console to the TinyG, I get errors that I don’t remember happening with my previous TinyG. I am working now with a new TinyG – order #5309, and the startup errors are shown in the previous posting above.

The TinyG acts like it has come up okay, but when I try to change a $tr setting (to tweak travel resolution for example), the TinyG stops and goes into “flashing red light mode”. A power cycle brings the TinyG back to working again – until I again try to change a $tr setting.

I don’t believe that there is anything physically wrong with the TinyG, it homes and moves and runs Gcode as long as no $tr settings are changed, but it acts like something is wrong with the code on the board.

Should I run the Updater again to reload software? Or is it a firmware problem?

Thanks!

I’m trying to tweak the travel resolution, so I have a caliper clamped to the rail to measure movement of the carriage. (not running G code, just moving an axis).

I turn on the rig, request a movement, look at the actual movement, then issue a different $tr value, and request the movement again to measure the change.

When I send the $tr command, it appears to work, but when I request a movement, that TinyG goes into red flashing mode. But it does come back after a power cycle.

I will try to use Coolterm instead of cncjs to see if anything is different.