7i92 and G540 combination?

P.J.B.C wrote:

I gave it 15 minutes and played some movies and music it seems to keep a solid average...
 

File Attachment:

File Name: packetstatistics.txt
File Size:0 KB

 

OK tmax of 10 ms is unusable. Not sure where this latency is coming from.
Do you have all power saving options disabled in the BIOS? (C states >1, turbo modes etc)
 

So i disabled s3 sleep and got rid of the peak...
I ran it for twenty minutes and got this...

 

I am not sure if i did get a faint glow when i first hooked up the G540...
All i can imagine is that i have strained a cold solder joint while switching the charge pump on and off...
there are a few small looking solder joints...
I'll get on to that and see how it goes...

I'm afraid it is not the board... I got a new one sent out overnight and it problems are the same...
 

Are there any commands in mesaflash that might be relevant to my confusion...?
I seem to remember back when i first got the mesa card that i went through a lengthy process to set it up...
Could i have locked it up, or something? Maybe set it in place and forgotten about it...

What actual issue do you have now?

well there is nothing wrong with the Ping and the FPGA has been flashed, I can count on the dim glow of the fault light as being my own ignorance.
I just can't see how there could be much more to it... I've got a clear mind as to the settings in the pncconf.
I thought that i would go through the setting one more time, logging in and out each time.
And i found that with the charge pump back on, it responds to a inverted chargepump and a normal e-stop setting,
however the power on command flashes the all good for a second and then returns to a fault light.
Also reading the error (Could not switch the machine on, is limit switch activated?)
and the only input is the e-stop... Do you need limits to latch the power on?

Can you start LinuxCNC and post the results of

halcmd show all > all.txt

Here?

yeah, I'm not getting anything...
and then i went with the string : halcmd show all
and got much more than i could copy out manually.
is there a better choice of words..

halcmd show all > all.txt

(which will create a file "all.txt" with a list of all hal pins, parameters, and signals
with their values)

and then post the file "all.txt" here