Forum Replies Created
-
AuthorPosts
-
cmcgrath5035
ModeratorIf you disconnect the fan there should be no load on U8.
You don’t need a fan for an idling tinyG (steppers not running).
So unplug fan, If tU8 stays hot there is a short/miswire on the board or U8 is bad.ModeratorU8 is a Vmot to 12V Linear Regulator.
Are you powering something more than a fan?
SchematicModeratorFW 440.14 is rather dated. Try 440.20
ModeratorThe forum tool “subscribe-to” mechanism is not working, you are not informed of answers to your questions by the tool, you have to keep checking back.
ModeratorI never make a typing mistake ….. 🙂
By the way, your are setting the default json mode
[ej] enable json mode 0 [0=text,1=JSON]
-
This reply was modified 8 years, 11 months ago by
cmcgrath5035.
ModeratorThe intent is that G2 is identical to tinyG as implemented for V8.
In some cases, G2 is a superset where there are new capabilities in G2 not supported by V8 platforms.I am not aware of a “j” command.
Perhaps you are trying to send
{“ej”:0} or {“ej”: 1} ?You’ll have to check with JuKu
ModeratorIs $fb=440.20 ?
ModeratorThis is the Gcode reference section of the Wiki
If capabilities are not described, likely not implemented.
I believe I have seen explicit comment that Looping and O Codes are not supported, but can’t find them at the moment.
ModeratorThis is the first post I recall seeing with A axis homing, so not a lot of experience in the user base.
What FW build are you running on tinyG?
Are they NC or NO switches?ModeratorAdam
Just to be clear; tinyG’s model is that home on Z, sets Z=0 at top of movement range on Z axis.
Z=-1000mm is underground (headed in that direction);
Z=1000 is invalid, beyond the homing and limit switch and headed to the sky.Perhaps you have the polarity set incorrectly on you Z axis motor ?
ModeratorAH so, I missed that detail this time but recall seeing it in the past.
I believe this statement to be true:
The parameter $_mi can be set to any value and tinyG will use it to compute travel per step/microstep and then issue step commands accordingly. So set $1mi=10 if motor #1 is your X axis driver, etc.
This comment is sort of buried in tinyG and tinyG2 documentation.If you are a Chilipeppr user and use the configuretinyG widget, it may barf on the value 10, I’m not sure.
ModeratorBill; Can you point to a reference as to your believe that you need to modify something to interface to your gecko 201X? There has not been much traffic on this particular topic in a long time.
My understanding from seeing thisa long time ago was that FW>412.xy fixed the issue of inadequate step pulse width.
If you are referring tonote that that item is very old by tinyG standards and has not been updated.
I believe I have seen Alden comment that step pule widths are now close to 10us and that they won’t get wider due to hardware/resource limitation.
When I saw your post over at CP, I took a quick look at the gecko specs, which seem a bit sloppy. Inputs 3.3V min to 5Vmax ?? I suspect they are saying that the gecko input can handle 3.3V or 5V logic level inputs, which can be a bit less than 3.3V for a high level and a bit more than 5V for a high level.
ModeratorIn reflashing to 440.18, the parameter $p1pof probably reset to 0.1 (10%).
Set $p1pof=0.0 and the PWM led will go off when spindle off.Back in the days of less sophisticated SPJS, there was a way to hand tune the number of lines delivered in a period of time.
What SPJS version are you running?
Ver 1.83 and now 1.86 are much faster (more efficient use of cpu), SPJS should not be overfilling your tinyG buffers.
Does SPJS run a a limited resource machine?ModeratorI am not a probe user myself yet, but have seen a lot of dialog on the subject.
Your writeup is a bit confusing.
Why are you using the Zmax switch for probing ?; it would appear that the G38.2 code is optimized for probing using the Zmin switch, based on this:-
https://github.com/synthetos/TinyG/wiki/TinyG-Configuration-for-Firmware-Version-0.97#st—switch-type
The mental model for the implementation is a PCB milling machine searching (down) for the surface of the blank board for setting a precise zero.
You may be using tinyG for a totally different sort of application.Be bit careful reading too much into “Flow Control and Footers”; It was last updated Jan 2014 and may not be completely aligned with current FW.
But for sure the issue remains for tinyG that parameter updates, such as $zsx= .., must be done one at a time as serial comms will be blocked during the update.If you have a unique application that does not follow the milling machine mental model, you may need to consider tinyG2, which has no EEPROM and also sports significantly more flexibility on configuring switches.
You may want to pose this question here:
but do expand a bit on your use for Zmax ‘probing’.
ModeratorWhat I do know is that Chilipeppr manages to get this done, even with Gcode files without “Nnumbers”, I believe by adding it’s own.
How it is done is buried in the code.
I don’t believe there is a way for you to set a trigger for tinyG to report on a specific line number, likely because Gcode line numbering is optional and somehwat random. It would seem sniffing the status repot stream is the only way.
You could also post a query to:
-
This reply was modified 8 years, 11 months ago by
-
AuthorPosts
