Bad duet module?
Draugar
Junior Member
Hi,
I have an issue with the Epson_Video_Projector_EB-G7000W_1.0.0 module, it will not start. I have tried replacing it wt the EB-1970W which works.
A REINIG gives:
Line 592 (12:00:06):: DDD.physicalDeviceOffline: 5001:1:0 is offline
Line 593 (12:00:06):: (Reader=749028432 writer=743654480)- CMessagePipe::Max = 50
Line 594 (12:00:10):: DDD.handleTimerEvent: dpd didn't exist
(Note: I am going to create 10 virtual devices to control 10 physical projectors, is there anywhere this will be a !#@$ idea? The other module worked, both XDD.)
I have an issue with the Epson_Video_Projector_EB-G7000W_1.0.0 module, it will not start. I have tried replacing it wt the EB-1970W which works.
A REINIG gives:
Line 592 (12:00:06):: DDD.physicalDeviceOffline: 5001:1:0 is offline
Line 593 (12:00:06):: (Reader=749028432 writer=743654480)- CMessagePipe::Max = 50
Line 594 (12:00:10):: DDD.handleTimerEvent: dpd didn't exist
(Note: I am going to create 10 virtual devices to control 10 physical projectors, is there anywhere this will be a !#@$ idea? The other module worked, both XDD.)
DEFINE_DEVICE
dvTPMain = 10001:1:0 // MSD-701L
dvProj1 = 5001:1:0
dvProj2 = 5001:2:0
dvProj3 = 5001:3:0
dvProj4 = 5001:4:0
dvProj5 = 10101:1:0 // EXB1
dvProj6 = 10101:2:0 // EXB1
dvProj7 = 10102:1:0 // EXB2
dvProj8 = 10102:2:0 // EXB2
dvProj9 = 10103:1:0 // EXB3
dvProj10 = 10103:2:0 // EXB3
vdvProj1 = 41001:1:0
vdvProj2 = 41002:1:0
vdvProj3 = 41003:1:0
vdvProj4 = 41004:1:0
vdvProj5 = 41005:1:0
vdvProj6 = 41006:1:0
vdvProj7 = 41007:1:0
vdvProj8 = 41008:1:0
vdvProj9 = 41009:1:0
vdvProj10 = 41010:1:0
#INCLUDE 'SNAPI.AXI'
DEFINE_FUNCTION fnPulse(INTEGER nChannel)
{
PULSE [vdvProj1,nChannel]
PULSE [vdvProj2,nChannel]
PULSE [vdvProj3,nChannel]
PULSE [vdvProj4,nChannel]
PULSE [vdvProj5,nChannel]
PULSE [vdvProj6,nChannel]
PULSE [vdvProj7,nChannel]
PULSE [vdvProj8,nChannel]
PULSE [vdvProj9,nChannel]
PULSE [vdvProj10,nChannel]
}
DEFINE_FUNCTION fnSetInput()
{
SEND_COMMAND vdvProj1,"'INPUT-HDMI'"
SEND_COMMAND vdvProj2,"'INPUT-HDMI'"
SEND_COMMAND vdvProj3,"'INPUT-HDMI'"
SEND_COMMAND vdvProj4,"'INPUT-HDMI'"
SEND_COMMAND vdvProj5,"'INPUT-HDMI'"
SEND_COMMAND vdvProj6,"'INPUT-HDMI'"
SEND_COMMAND vdvProj7,"'INPUT-HDMI'"
SEND_COMMAND vdvProj8,"'INPUT-HDMI'"
SEND_COMMAND vdvProj9,"'INPUT-HDMI'"
SEND_COMMAND vdvProj10,"'INPUT-HDMI'"
}
DEFINE_START
DEFINE_MODULE 'DeviceDriverEngine' Proj1 (vdvProj1 , dvProj1, projXDD)
DEFINE_MODULE 'DeviceDriverEngine' Proj2 (vdvProj2 , dvProj2, projXDD)
DEFINE_MODULE 'DeviceDriverEngine' Proj3 (vdvProj3 , dvProj3, projXDD)
DEFINE_MODULE 'DeviceDriverEngine' Proj4 (vdvProj4 , dvProj4, projXDD)
DEFINE_MODULE 'DeviceDriverEngine' Proj5 (vdvProj5 , dvProj5, projXDD)
DEFINE_MODULE 'DeviceDriverEngine' Proj6 (vdvProj6 , dvProj6, projXDD)
DEFINE_MODULE 'DeviceDriverEngine' Proj7 (vdvProj7 , dvProj7, projXDD)
DEFINE_MODULE 'DeviceDriverEngine' Proj8 (vdvProj8 , dvProj8, projXDD)
DEFINE_MODULE 'DeviceDriverEngine' Proj9 (vdvProj9 , dvProj9, projXDD)
DEFINE_MODULE 'DeviceDriverEngine' Proj10 (vdvProj10 , dvProj10,projXDD)
BUTTON_EVENT[dvTPMain,0]
{
PUSH:
{
SWITCH(button.input.channel)
{
CASE 1:
{
PULSE[vdvProj1,27]
IF(!nProjStatus)
{
nProjStatus = 1
TIMELINE_CREATE(WaitTL, TL_CT, 1,TIMELINE_RELATIVE, TIMELINE_REPEAT) //timer page on touchpanel
}
fnPulse(PWR_ON)
WAIT ProjTimer
fnSetInput()
}
CASE 2:
{
PULSE[vdvProj1,28]
IF(nProjStatus)
{
nProjStatus = 0
TIMELINE_CREATE(WaitTL, TL_CT, 1,TIMELINE_RELATIVE, TIMELINE_REPEAT) //timer page on touchpanel
}
fnPulse(PWR_OFF)
}
CASE 3:
{
SEND_COMMAND dvTPMain,"'@PPN-TL_6;Meny'"
TIMELINE_CREATE(StatusTL, TL_CT2, 1,TIMELINE_RELATIVE, TIMELINE_REPEAT) //timer page on touchpanel
}
CASE 4:
{
TIMELINE_KILL(StatusTL)
}
}
}
}
Comments
-
Have you tried increasing the duet memory? Also how come your using a module for that kind of display?
-
There are some Duet modules with known issues. I seem to remember some of the Epson duet modules were written by Epaon and don't work. With Epson since they're protocol is the same, it's a good idea to just try another one.
-
Problem neglected!
I did try to amp up the duet memory to 128M with no results.
I ended up skipping the cool part (having a small service menu with lamp counters etc.), and just sent the hex to each projector instead. Sorry for late reply, butthanks for answers
Categories
- All Categories
- 2.5K AMX General Discussion
- 922 AMX Technical Discussion
- 514 AMX Hardware
- 502 AMX Control Products
- 3 AMX Video Distribution Products
- 9 AMX Networked AV (SVSI) Products
- AMX Workspace & Collaboration Products
- 3.4K AMX Software
- 151 AMX Resource Management Suite Software
- 386 AMX Design Tools
- 2.4K NetLinx Studio
- 135 Duet/Cafe Duet
- 248 NetLinx Modules & Duet Modules
- 57 AMX RPM Forum
- 228 MODPEDIA - The Public Repository of Modules for Everyone
- 943 AMX Specialty Forums
- 2.6K AMXForums Archive
- 2.6K AMXForums Archive Threads
- 1.5K AMX Hardware
- 432 AMX Applications and Solutions
- 249 Residential Forum
- 182 Tips and Tricks
- 146 AMX Website/Forums