[d2bdesign]

Hi everyone,

I'm working on attaching a mister to my Multicam 1000 Series (actually an airbrush, but I'm attempting to control it through the mister output). So far, I've been able to test the functionality of the port on the main air manifold by moving the connecting pin from the dust collector solenoid to the port associated with the mister. Shoutout to Maurice at MCP Services for the help!



I tested the functionality of the mister using the "Mister Test" on the pendant (by pressing Shift+9), and confirmed that the mister port was addressable.

However, I'm having some trouble activating the solenoid using M code. I cross-referenced the M codes that were mapped on JobServer>Program Settings>CNC>Mcodes with those listed in the Multicam Manual, and inserted them into a simple .cnc file to test their functionality. (I attached one of the .cnc files for reference, and my Mcode settings) I was unable to trigger the solenoid with the following Mcodes:
M07, M08, M09, M14, M26, M27, M38 & M48


After reading through the "Software Ports" section of the manual (also attached), I tried using:
G98 P136 D1 to set the mister configuration to enabled.

I also created a new Mcode M24 in the Program settings and assigned it to device 201 (listed at Mister Output on p.9 of the attached manual), and inserted it into a .cnc file, but it was also unsuccessful.

It seems that the solution would be to determine which device is associated with the 'mister output' port, map an unused Mcode to that device, and call that Mcode in a .cnc file. Does anyone know how to identify the device number? Or is there another way to address a specific port on the manifold?

The machine specs:
Multicam 1000 series with an HP4 controller and a v 8.02 ATC
Running Productivity Software Suite v 3.9 (from 2003)

Thanks in advance for any help!

[Sanvej]

Hi

Did you work it out? Is your mister working properly?

[d2bdesign]

Hi Sanvej,

Yes it is!



We worked with a software engineer at Multicam, who helped us identify some of the issues. He upgraded our firmware and added a patch that correlated pins on the RIO board with devices in the software. We connected the solenoid to another port on the manifold that was associated with a specific device number. Here's our pinout:

DCN 250 – Output #7, pin 3
DCN 251 – Output #8, pin 5
DCN 253 – Output #10, pin 9

In the end, we mapped M65 and M66 to device 250 to turn the solenoid on/off. The M-codes will activate the pin in the job file, but there are a few things to be aware of:

1) If you pause/cancel the job with the solenoid open it will stay open after the job has ended

2) You can test the functionality of the solenoid by typing the following into the Motion Mechanic terminal:
1_250_tset_dcn (turns it ON)
0_250_tset_dcn (turns it OFF)

The above only tests the correlation between the device and the pinout on the RIO. Ie. it doesn't check the relationship between the Mcode and the device.

Good luck!