forum.cncdrive.com

Hi,

When does the AXBB-E return the value NaN for uc100.stat->feed? The Stat.OriginalFeed is returned correctly the feed that i have sent
Because i see sometimes this, and the machines just halts, it has commands in the puffer to execute, but it does not execute them, the problem appears randomly, in the sense that sometimes i load the file ant hit start, and the machine just halts at a particular line, other times it passes that line and works ok, and it finds another line and just halts and shows NaN for the feed.

Another time the board returned the Current ID (that is executed) (of the command in the puffer) to be 1075126296 (strange that the number is very close to 2^30) but the id sent for that command was 2056. Another time the board returned other strange Current ID, also very large number (but very simillar to this one). I have made my software to be tolerant to this huge Current ID, because if they are larger that the number of commands in the file they are just ignored. I have logged the id-s sent by my software and received from the board and compared the files, that is how i have found this problem...

I have asked ChatGPT about the last problem, and he said that it could be a memory access problem... i cant find that conversation on the chat to paste it here it was several months ago...

I have several 230v appliances close to the axbb-e board... some pneumatic valves, and a VFD. Also from the pin 1 (charge pump) i supply the ground for a small relay board that consumes 260ma when all 4 relays are on. The 5v supply can output 10 amps. It may be because of the electric interference? but why does it stop at the same line for a particular file? the problem apeared on multiple files, but on diferent location in the file. It is like some memory cells in the board are defective?

Dan

The serial number of the axbb-e is: ca18a2 ; FWversion: 1005 ; HWversion: 1 ; DLLversion: 2182
We use the machine almost daily...
I have changed the computer but it did not solved the problem (if anyone will try to suggest this option)...

I have found the problem, the CAM software has written on the the line 2415 G19 and after that all necessary parameters, but on line 5526 he written G3 and some parameters, the line 5527 and 5528 had the same values for Y, Z and R, so when my software tried to compute J and K, it couldn't. And sent to AXBB-e board NaN (or nothing) for J and K so the board just stooped the movement.

And i discovered that the semi random problem was because of a temperature sensor not calibrated below 20C, funny thing is that we did not had temperature below 20C until now in the workshop.

So there were two separate problems, producing same symptoms. Very confusing.

But the problem with the strange ID returned by the board is still there, but is manageable.