cmcgrath5035

Try customerservice@synthetos.com

I have been staring off and on at the spec sheet for dq542ma. It appears to me that setting SW5-SW8 0111, which I would assume means no microstepping, is 400 step per rev.
Are you motors 400 step per rev($sa=0.9)?
Do you consider setting 1101 to be micro steps=8?

I don’t see any spec on min/max input pulsewidth of the step

As an experiment, have you tried cutting drive current by 1/2 to see if it makes a difference?

Paragraph 1 – understand and agree

Paragraph 2 – Understand and agree with you observations on G0.

Have you run your job “in air” above work?
Same 0,0 offset?
In air removes the cutting load, which in you case should be nil.

All I know at the moment.

https://www.synthetos.com/topics/tinyg-wont-boot-spdir-light-flashing-constantly/page/2/#post-9060

There is a potential fix via an updated tinyGUpdater that will manipulate fuses.
I suggest wait 24 hours for it to be tested.
You might want to ping Synthetos for info on where to send just in case

If you are running Atmel Studio(AS), you are likely a windows user.
I agree, that interface is uber complex.
I compile directly on Linux, from a cloned GitHub repo.
I have managed to get some useful results from AS, but don’t ask me to repeat what I did.

Did you actually compile your 86.03? From what source tree?

Are you sure you are level-shifting, not inverting-and-level-shifting with your FETs

If you are using the standard Gshield profile, you could get $fb=78.03 from

http://synthetos.github.io/g2/

BTW, I am really not sure 86.03 is an issue.

This

Drivers are supposedly rated to 200kHz. I’m running at most at 26khz frequency at Vmax.

confuses me. How are you measuring 26kHz and where?

There are two dynamics going on – step pulse rate and step pulse width.
The 200kHz rate is consistent with tinyG2. What is the minimum input pulse width spec on your drivers?

If, as you state, the mechanical position of the spindle is NOT where you believe G54(0,0) is, BUT the CP DRO reads (0,0), then mechanical steps are being skipped; tinyG believes commands have been executed by the drivers but they have not been.
What leads you to say you are not losing steps during cutting?
I am sort of assuming your Gcode has zillions of small moves.

• This reply was modified 8 years, 9 months ago by cmcgrath5035.

That is what I do.
Connect all the shields to a single 18 to 22ga stranded pigtail, slide the pigtail into the tinyG ground connection point (Vmot -).

Stranded wire will survive more flexing than solid wire, if you have to use solid, check it occiassionally

So, you are a Windows user. 7,8,8.1,10, other?
TinyG or TinyG2?

When you plug tinyG into your computer, do you get the beep/pop-up that a new device has been attached.

If you look in control panel-Devices and Printers, or in Device Manager, does tinyG appear anyway and does Windows report “driver OK” or something like that?

SPJS (version = 1.86 or?) also running on Windows.
Just to be precise, the Chilipeppr browser connects to SPJS via a web socket,
SPJS connects to tinyG over a COMx port

No i used the same gcode file that i have used a lot of times that i have saved

OK, but CP does have the ability to statically (whole job) or dynamically modify Fxxx in motion speed settings, by dynamically modifying Fxxx Gcode directives.
Additionally, Auto-Leveling can dynamically modify Z depth.

I’ll assume for now you were not using any of these features.