moeter

Oh, yes, I’m confusing somehting myself here… Lot’s of input circuitry to get 24V active switches working. Anyways, that was setup correctly as NO. (I am using an elexol opto input board, tinyg is wired to the line transceiver directly they only use to drive the leds…)

The thing was, the latch backoff values were too small.

I’m still a bit sad that my suggested fix for this problem hasn’t been built into edge yet. I always have to compile my own version…

Actually I’m not using a “real” JSON parser, because for security reasons I am not allowed to. I am building embedded software, that is controlling TinyG for using it as a more generic robot controlling system.

It’s kinda okay what it returns, and the list of precisions is helpful. But I still reckon it suboptimal, as these responses are the only way to actually check for comm errors, and identical strings would make this more straightforward and faster.

And actually I’m using an EDGE build (435.10) where I fixed this issue myself…

Found it in the sources:

https://github.com/synthetos/TinyG/blob/edge/firmware/tinyg/plan_line.c#L494

-0.99 needs to be closer to -1. Something like -0.9999 should be sufficient, this would include all angles larger than 1°.

• This reply was modified 10 years, 4 months ago by moeter.

Sorry to hear that… but still, this also means, something else is going wrong: If the setup only works if we have the correct power sequence, then most likely we also need the correct power seqence when using the serial interface on the board directly. Am I correct?

As for the cmcgraths suggestion: I have to try on Unix/Linux, but Windows preserves the Handle when a FTDI device is disconnected, but obviously gets no more replies. This is actually okay behaviour. However, if we replug the device, we are still connected to the Null Handle, and even if we replug the device, you get no more answers. Im very interested in your solution, but I have my doubts if that would work on Windows (udev and Windows sounds, well, unlikely).

Actually it would be quite helpful to know how Coolterm notices the connection loss, as it’s the only Windows terminal program, that even takes notice of an unplugged FTDI device.

On another note: what would happen, if we just powered the 3.3V using an arbitrary 3.3V Pin and an external power supply? In my opinion it should either burn everything (or just the lm2594) down or power the logic part of the board, but not the output stage. alden, can you shed some light on this?

Thanks!