Re: [Emc-users] Anybody here tried the Odroid C2?

[Gene Heskett]

On Tuesday 15 November 2016 16:01:32 Gene Heskett wrote:

> On Tuesday 15 November 2016 12:19:15 Jeff Epler wrote:

And I snipped in order that a status report wouldn't be 3 pages in the 
weekly paper.

I had a heck of a time trying to get a usable display out of the 
odroid-c2, until I googled for the specs of the monitor I am going to 
use, and discovered the darned things highest native display is only a 
1366x768. Reset it for that in /boot/boot.ini by sticking the micro-sd 
in a r/w dongle, waiting for wheezy on the old Dell to auto-mount it, 
then used a root session of nano to select it. Plugged the card back, 
in, powered it up and got a perfect 1366x768 image.

But the odroid needs a bigger can of nitrous to do it real well, the 
default display cycle was set for 50 milliseconds.  And I could see 
traffic on the cat5's leds at about that rate, while the monitors update 
rate was perhaps 3 times a second, so the motion displayed was obviously 
jerky.

But it works, and there is room to crank up the odroid's clock as its 
only running at 1.5 GHz. With a fan on its heat sink, it can go to about 
2.1GHz.

So I am also going to slow down the display polling interval on the 
theory that X will not have to throw away so much data, and will use 
that time gained to speed up the display.  There ought to be a happy 
middle ground.

Any way, I've found a power cord for the odroid, and its screwed to an 
couple bars of HDPE, the bottom wet with Go-2, and clamped in place on 
the inside of the door of this big old recycled steel box.  I may have 
some questions later because the odroid is running ubu 16.04 LTS, which 
means I had to get out my stockmans knife and make a steer out of 
network-mangler, by setting it so _I_ am the only one who can setup a 
resolv.conf that N-M can't tear down.  That puts a big smile on my face, 
setting up a static network that N-M cannot destroy.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 

--
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] Waiting for cycle start in MDI command

[andy pugh]

On 21 November 2016 at 11:49, Alexander Rössler  wrote:
> It is a custom UI which I'm building.

In the case of the "Touchy" interface you need to press the "cycle
start" button to run an MDI command. The effect of the button depends
on which tab the UI is showing.

-- 
atp
"A motorcycle is a bicycle with a pandemonium attachment and is
designed for the especial use of mechanical geniuses, daredevils and
lunatics."
— George Fitch, Atlanta Constitution Newspaper, 1916

--
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] Waiting for cycle start in MDI command

[Alexander Rössler]

On 2016-11-21 11:19, andy pugh wrote:
> On 21 November 2016 at 09:48, Alexander Rössler  
> wrote:
>> I have the following problem:
>> The machine requires the user to press a cycle start (physical button)
>> on the machine before executing an MDI command.
> 
> Which UI are you using? Perhaps you can just make the "Execute" button
> invisible?
It is a custom UI which I'm building.

The idea is that the user has to press cycle start after entering the 
MDI command.

1. enter MDI and accept (clicking execute or pressing return)
2. press cycle start on the machine
3. run MDI command

for normal programs I just add the wait-for-cycle-start GCode to the 
start of the program. For MDI commands it is more complicated it seems.

Of course, I could handle everything in the UI. However, since this is a 
safety critical feature I think it would be better to implement this in 
HAL or as GCode command.

> 
> Or am I misunderstanding the problem?

--
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] Waiting for cycle start in MDI command

[andy pugh]

On 21 November 2016 at 09:48, Alexander Rössler  wrote:
> I have the following problem:
> The machine requires the user to press a cycle start (physical button)
> on the machine before executing an MDI command.

Which UI are you using? Perhaps you can just make the "Execute" button
invisible?

Or am I misunderstanding the problem?

-- 
atp
"A motorcycle is a bicycle with a pandemonium attachment and is
designed for the especial use of mechanical geniuses, daredevils and
lunatics."
— George Fitch, Atlanta Constitution Newspaper, 1916

--
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

[Emc-users] Waiting for cycle start in MDI command

[Alexander Rössler]

Hi all,

I have the following problem:
The machine requires the user to press a cycle start (physical button) 
on the machine before executing an MDI command.

So far I have used a remap command to achieve this. Basically, I prefix 
this command to all MDI commands executed by the user. E.g.:
M100 G0 X100

The M100 command waits for a digital input to toggle and aborts if it 
does not happen in a certain time frame.

However, some GCode words take precedence over my remap command. In 
particular the S and T words.

I have tried to use a Python prolog instead, which seems to always be 
executed before the other words in the MDI line. However, I cannot wait 
for something in the prolog because it freezes the interpreter. 
According to the docs one can use yield to pause a Python remap command. 
I also have tried this, but it seems the interpreter continues the 
execution after the prolog, which makes this approach useless for me.

So my question here: Is there any other way to achieve this?

I see following possible solutions to solve this problem:
* create small multi-line programs from the MDI commands
* handle wait-for-cycle-start in the UI

Both solutions sound very hacky to me. Does anyone know any other method 
to delay the execution of MDI commands? The MDI commands are entered by 
the user, so I cannot use halui in this case.

Cheers,
Alexander

--
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users