Hello Guest it is December 21, 2024, 11:47:42 AM

Author Topic: Macropump problem?  (Read 12518 times)

0 Members and 1 Guest are viewing this topic.

Offline mhdale

*
  •  130 130
  • Knowledge is the Treasure.
    • Black Dragon Technologies
Re: Macropump problem?
« Reply #10 on: August 18, 2007, 11:25:14 PM »
Brian,
I Think my Macropump is working..... But I need to get a Grex hooked up on my tests system so I can Check Inputs as Hotkeys dont work in flash. So I will let you know when I get that setup.
Thanks

Mike
Re: Macropump problem?
« Reply #11 on: August 20, 2007, 09:33:37 PM »
I tested your code and it was not working... Please use the code that I posted and test in the 1024.set file Then after you have seen it work in that screen set test it in Flash.

thanks
Brian
Fixing problems one post at a time ;)

www.newfangledsolutions.com
www.machsupport.com

Offline mhdale

*
  •  130 130
  • Knowledge is the Treasure.
    • Black Dragon Technologies
Re: Macropump problem?
« Reply #12 on: August 21, 2007, 11:15:23 AM »
Brian, I COULD HUG You! Except it would be UN-MANLY ;D Thanks Your code works great! I am getting a response out of my Screenset and hopefully will get this wrapped up this week!! THANK YOU! THANK YOU!!!
Mike
Re: Macropump problem?
« Reply #13 on: August 22, 2007, 03:46:14 PM »
Cool :) I was thinking that would fix your trouble

Thanks
Brian
Fixing problems one post at a time ;)

www.newfangledsolutions.com
www.machsupport.com
Re: Macropump problem?
« Reply #14 on: November 07, 2007, 05:58:19 PM »
Hello all,
may be a bit off topic, but searched for "ActivateSignal":

My problem is this: I just installed a 2nd PCI printer port to my PC, now wanted to test the signals.
I configuren Mach's outputs #10...#15 to Port 2 Pin 1...6.

Q: How can I Activate and Deactivate these outputs by a macro? I tried "ActivateSignal(10)" but compiler gave me syntax error. What is the proper syntax? The manual/wiki reads that an integer must be in the brackets. But which one e.g for Output#10 ?

Thanks for helping an beginner in macro-programming.
Regards
Holger

Offline poppabear

*
  • *
  •  2,235 2,235
  • Briceville, TN, USA
Re: Macropump problem?
« Reply #15 on: November 07, 2007, 09:49:00 PM »
Holger,

Use:

ActivateSignal(OUTPUT10)       'the all caps for output is needed, download the VB off the wiki for signal names
DeActivateSignal(OUTPUT10)

Scott


Hello all,
may be a bit off topic, but searched for "ActivateSignal":

My problem is this: I just installed a 2nd PCI printer port to my PC, now wanted to test the signals.
I configuren Mach's outputs #10...#15 to Port 2 Pin 1...6.

Q: How can I Activate and Deactivate these outputs by a macro? I tried "ActivateSignal(10)" but compiler gave me syntax error. What is the proper syntax? The manual/wiki reads that an integer must be in the brackets. But which one e.g for Output#10 ?

Thanks for helping an beginner in macro-programming.
Regards
Holger
fun times
Re: Macropump problem?
« Reply #16 on: November 08, 2007, 09:34:11 AM »
Thank you Scott, I overlooked just this page in the Wiki.

These VB Constants are related to the designations in the "Config - Ports and Pins"-Menu? There it reads Output #10 and ActivateSignal(OUTPUT10) will switch just this pin?

Thanks
Holger
Re: Macropump problem?
« Reply #17 on: November 08, 2007, 04:00:18 PM »
Thanks again, I just tested this ActivateSignal(...) positive!

How often will WinXP change the address of this PCI printer port card? How to fix it to a permanent address? Mine was different from yesterday, when I installe the card.

Regards
Holger

Offline Hood

*
  •  25,835 25,835
  • Carnoustie, Scotland
Re: Macropump problem?
« Reply #18 on: November 08, 2007, 06:29:17 PM »
XP should only change the address if you add other PCI cards or move that one to a different PCI slot.
Hood
Re: Macropump problem?
« Reply #19 on: November 09, 2007, 03:27:18 AM »
Hello Hood,
I'll keep an eye on this. After the initial tests on the printer port I really installed an USB-card, then tested only the USB matters (camera window in mach). So this was the reason surely.
btw, Mach did not show any problem with the address in the 0x4000 or ox7000 range.
Thanks & Regards
Holger