DiyLightAnimation
Hardware => Lynx EtherDongle => Lynx Conductor => Topic started by: duane.mosley on November 15, 2013,
-
1. load new firmware pickit3
2. format cf card fat32 16kb
3. convert sequence to .seq and audio to .ogg and load to cf card in card reader.
4. create .sho .sch password.dat playlist.dat
5. verify info on cf card and when I install into conductor it's not connecting
playlist.dat
show13.sho
wiz13.seq
wiz
password.dat
testnow.sch
those are the files as they are seen on the cf card. one question I have is it doesn't show the .ogg extension on the cf card, but when I go into the control panel version3 and create the show, it shows the .ogg extension in control panel. windows security has the control panel as having access to the network. I used the ed to run the lights prior to formatting with new conductor firmware.
-
anybody?
-
Don't know if this is the actual problem, but I believe your .seq file and .ogg file must be the exact same prior to the extension. you may also try renaming them just using a single number (i.e. 1.seq and 1.ogg). I seem to remember some people having issues that naming it a single number corrected.
-
You might search some old threads. I remember lots of posts about it. I think some cf socket problems may have been one cause. If flashed back to etherdongle firmware does it still work? I keep one flashed that way to test whether my lights are connected correctly.
Sent from my Thunderbolt using Tapatalk 2.
-
so the ogg and seq file have to have the same name? I think I might remember that too. this conductor worked last year. I didn't use it for my show due to the time sync issue but it did work. I will try naming them the same and see what happens. I have read all posts back to December of last year.
-
If flashed back to etherdongle firmware does it still work? I keep one flashed that way to test whether my lights are connected correctly.
Sent from my Thunderbolt using Tapatalk 2.
yes it worked the lights prior to reprogramming pic for conductor. I have a secondary ED for testing. I use my laptop(show computer) for work so big goal is to get the conductor going this year. is there a test for the socket to make sure it's ok? it did work last year though. I just renamed the seq and ogg to the same name, recreated the show. and still not connecting.
-
This is from rrowan "1) at least one *.seq and/or *.mp3 file on the compact flash (CF) card,
2) created a password, which will create a password.dat file on the CF card,
3) create at least one show, which will create a file *.sho on the CF card, and
4) schedule a show to run, which will create a playlist.dat file on the CF card.
All four of these must be met before the control panel will see the Conductor.
Note:
1) All files names must be 8 characters or less.
2) Do not ever delete or rename any files on the compact flash card. If you do you will have to reformat the CF card and copy your files back to the CF card before the Conductor will play your show(s).
The next step would be to checkout the pins on the CF card reader. First look where the pins are bent at 90 degree to see if any of them are touching each other. Secondly check for any solder bridges on the pins of the card reader on the PCB pads. Then lastly check to see if any of the pins might not be solder on their pad. The easiest way to do that would be to take something like a toothpick and attempt to move each of the card reader pins at the PCB. If any are loose you'll need to solder them".
Many people used a toothpick to check for leads not soldered on the CF socket and had to resolder them. I think one person had to replace the CF socket due to a broken pin. I think someone else had to replace the RTC.
-
As Keith mentioned in all likelihood you'll find a lose pin on the CF card reader being the problem since it looks like all the requirements for V3 Conductor are being met.
Just to clarify the requirements for V3 Conductor are different than the V1 requirements Keith quoted. With the latest version 3 CP and corresponding firmware the *.MP3 audio files have been replaced by *.OGG files (item # 1). Now when a show is scheduled a new schedule file is create *.sch in version 3 (item # 4) and must be present on the CF card. Under the notes item # 2 is no longer applicable and can be ignored since a DOS like file system is being used.
FYI
The *.seq and *.ogg files name do not have to be the same, e.g. a show with a sequence name of Wiz.seq and Wizard.ogg is a valid combination.
Denny
-
i'm just curious as to how it worked last year, after i fixed the cf pins that were loose. was in a cabinet in the garage all year, and now I have a problem with the cf socket? i will check the pins again with a hot iron, but with a pick, none of them are moving. this conductor worked last year.
-
ok, went to the garage, got out the pick and magnifier and no loose pins on the cf socket. I am stumped. I am sure it's something simple that I am missing. this ed worked with old conductor firmware last year. pulled it out this year, flashed pic for ED and it worked the lights. reflashed for the conductor, formatted card a couple different times not connected. since my last post I have:
1 switched cat5 cables just in case, no go
2 turned off windows firewall just to makes sure it wasn't blocking anything
3 checked all pins on cf and everything was solid. took an ohm meter to the pad on the pcb and the pin itself as it 90's up away from pcb and all checked out.
4 reformatted cf card
5 converted mp3 again too ogg in audacity
6 loaded cf card with .ogg and .seq file
7 went to conductor chose Kingston created .sho .sch and password.dat which all created the playlist.dat
8. went to network sharing center and it shows connected to LAN but it is just identifying. should say aetheros something right?
still nothing. I closed ccp and upon opening i got a flash of it waiting for the next show but only for about 2 seconds and then it went to not connected. eject card and it says card error, reinsert the card and nothing changes, just says card error. if i reset the ccp, it comes back to not connected. I will go back in reading the forum and see what I can find about card error messages.
-
Did you do the audio hardware modification? On mine it shows an "unidentified network" but it is still connected. Yours must be connected for at least a little while or you wouldn't have seen the "waiting for next show" or the "card eject". If it stays on "waiting for next show" I think you are connected.
-
Are you connected direct to your computer or through a network?
Try direct to the computer with a cable.
RJ
-
I am connected directly to my computer. sometimes when I connect the cat5 to the computer, it will stay connected but identifying, some times it will keep flashing in and out trying to connect. as of now, the green light on the magjack is staying lit with a slight flash every 5 seconds. network sharing center says identifying no network access.
-
Did you do the audio hardware modification? On mine it shows an "unidentified network" but it is still connected. Yours must be connected for at least a little while or you wouldn't have seen the "waiting for next show" or the "card eject". If it stays on "waiting for next show" I think you are connected.
I have not done the audio hardware modification, when it worked last year, I didn't have any issues with audio. only issue I had last year is some of my songs wouldn't sync properly, couple of my songs played just fine all the way threw and some would get out of sync. I agree that I think I am connected threw the cat5, the network sharing center is showing identifying but no network access. I am starting to think it might be the ogg file not having the ".ogg" extension on the cf card. I converted threw audacity but when I put it on the card, it just shows the name of the file, not the .ogg extension. all the other files have the proper extension on them. but when I access the playlist threw the ccp, it shows the .ogg extension.
-
after doing some reading I went in to disk management to format the cf card and still getting the same results. network sharing is still showing the lan connection so the computer is reading the conductor. what size does the ogg file need to be? audacity just converts but converter lite shows options of 320kbps 256kbps 192kbps 128kbps?
-
Have a similar issue. My blinky pc is xp and used it successfully throughout the entire conductor beta, with the use of a crossover cable. Worked on other stuff and conductor sat on the shelf. Recently loaded new firmware and gave it a go and have the same issues as you. Mag jack blinking every 5 seconds but no go no matter what. Try my win7 box and I have no issues (need firewall off though). I suspect all is good except pc config. Crossover cable, IP address, anti-virus, firewall. Never did it but I thought about reverting to last known working conductor firmware with my xp box and seeing if that fixes it.
-
Have a similar issue. My blinky pc is xp and used it successfully throughout the entire conductor beta, with the use of a crossover cable. Worked on other stuff and conductor sat on the shelf. Recently loaded new firmware and gave it a go and have the same issues as you. Mag jack blinking every 5 seconds but no go no matter what. Try my win7 box and I have no issues (need firewall off though). I suspect all is good except pc config. Crossover cable, IP address, anti-virus, firewall. Never did it but I thought about reverting to last known working conductor firmware with my xp box and seeing if that fixes it.
this conductor worked on this laptop last year. i'm starting to think that it is something to do with my ogg file. there is no .ogg extension on the end of the file in the cf card. there is an extension on the other files .seq .dat .sch .sho but no .ogg I have converted threw audacity and converter lite and neither is producing the extension. when I go into conductor control panel and create a show, it shows the .ogg file so I am stumped.
-
My Win8 machine doesn't show .ogg but it does say it is an ogg audio file under type. I have my folders set to detail view.
-
Just to clarify. Have you tried the etherdongle firmware recently? Because your antivirus and other programs could have updated and changed things since last year. Have you tried both crossover and straight cables? Did you use the Pickit3 Stand Alone Programmer Appver 1.0 to program the Pic instead of the v3 beta or MPLAB? I have read the v3 beta can give the correct checksum but the etherdongle still doesn't work correctly.
-
My Win8 machine doesn't show .ogg but it does say it is an ogg audio file under type. I have my folders set to detail view.
that's the way it looks on mine as well. guess that rules that out. I am stumped then. I have no clue why this thing isn't connecting. can't see it being a cf socket issue if all the pins are solid and it worked last year. the cf card format and files are the only thing I can think of causing my issue. firewall is off so I know it's not that.
-
Perhaps someone in Kentucky is close enough to help troubleshoot. If you didn't use the v3 beta programmer to flash it which more than one person has said gives a correct checksum but still won't work correctly.
-
Perhaps someone in Kentucky is close enough to help troubleshoot. If you didn't use the v3 beta programmer to flash it which more than one person has said gives a correct checksum but still won't work correctly.
lonewolf is about an hour away but not sure if he is using the conductor. I used pickit 3 with v69 firmware to program. if i'm not mistaken the check sum was 0000. I can reflash to etherdongle firmware and it will control the lights.
-
You might try reformatting and start over and rename one .seq to 1.seq and the audio to 1.ogg and drag them to the cf card to be used as a test. I remember some people seemed to have a problem until they did that. Not sure why as I didn't have any problems with filenames once I found out the disk management workaround to get the cf card to format correctly.
-
You might try reformatting and start over and rename one .seq to 1.seq and the audio to 1.ogg and drag them to the cf card to be used as a test. I remember some people seemed to have a problem until they did that. Not sure why as I didn't have any problems with filenames once I found out the disk management workaround to get the cf card to format correctly.
nope, didn't change anything
-
Duane,
A couple of questions to try and narrow down if there is a problem with the Conductor or with the network connection to the Conductor:
1. Does your computer have multiple network connections/adapters?
2. After the initial boot up of the Conductor, what is happening with the lights on the MagJack? Specifically I'm wanting to know of it is blinking consistently every x seconds or does it appear to be rebooting every so often.
3. Since it worked last year, I would assume the Conductor is working OK although you can't get the Control Program(CP) to connect to it. Without a network connection to the Conductor, you won't be able to monitor what's happening on the Conductor, be able to sync. the RT clock to you computer, change audio level, or manually play a show. To test if the Conductor is working you could create a short sequence with a limited number of lights and audio for a show and then schedule that show to run multiple times close to you computer time, assuming the Conductor RT clock is still close to your computer time. Now hook up the hardware/lights and audio to the Conductor and see if it plays the show. If the show is scheduled to run everyday at a certain time it should run if the Conductor is really working. IF this works then we know, as Sam mentioned above, that were dealing with the network or configuration issue.
Denny
-
Silly question: Are you using the program?
Control Panel v3 http://diylightanimation.com/index.php?action=dlattach;topic=11905.0;attach=11695
Rick R.
-
1. yes multiple adapters, the network sharing center shows the unidentified network Atheros Ar8152/8158 PCI-E fast Ethernet
2. magjack light stays constent with a blink every 5 seconds or so. this ED works the lights flash as ED wired as it is.
3. i set up the test show on the cf card for 3:45pm. so far it hasn't started but that doesn't mean it's not working. i will leave it hooked up for the evening to see if the conductor kicks the show on. the clock on the conductor control panel is spot on, but with not connected i understand that the clock on the conductor could very well be off.
and yes control panel V3 with firmware version69
-
6 hours and no blinky
-
You might pm lonewolf and see if he is using a conductor so you can troubleshoot. It kind of sounds like your conductor is constantly rebooting. I saw that if the "allocation size" is not 16 kilobytes for formatting. The RTC part may be malfunctioning but you usually see an RTC error message show up. If I remember right it had to be up off the board not touching anything and the battery inserted correctly. The audio hardware mod also created to stop the conductor from rebooting with certain transmitters so you might try it without an audio cable plugged in to see if it works then.
-
You might pm lonewolf and see if he is using a conductor so you can troubleshoot. It kind of sounds like your conductor is constantly rebooting. I saw that if the "allocation size" is not 16 kilobytes for formatting. The RTC part may be malfunctioning but you usually see an RTC error message show up. If I remember right it had to be up off the board not touching anything and the battery inserted correctly. The audio hardware mod also created to stop the conductor from rebooting with certain transmitters so you might try it without an audio cable plugged in to see if it works then.
I pm'd keith,. this conductor worked last year. I started testing with it and it was loosing time on a few songs but on a few others it was rock solid. all on the same show and schedule file. my show was running solid on vixen scheduler so I put the conductor in the cabinet and it didn't move, get bumped, dropped or anything heavy stacked on it. I pulled it from the cabinet last week for the first time in 11 months, flashed it for etherdongle so I could test due to high channel count(I now have a back up ed for testing), made sure it worked as ED and controlled the lights. formatted cf card to fat32 16kb flashed pic with new v69 firmware, deleted existing conductor control panel and downloaded version 3. the first night I really put effort into getting it going this year, I did see a brief flash of it waiting for show meaning that it connected for that brief moment. then I was getting a card error when I pulled the card out of the conductor. no audio connection has been made yet this year during my testing issues. no RTC error, but if the conductor isn't connecting, then how could the control panel read the RTC error? I would assume that it couldn't do so. in network sharing center it shows the connection being solid, it has had moments where it was flashing in and out like the conductor could have been rebooting, but for the most part it stays solid. green light on magjack stays lit with a brief flash every 5 seconds or so. I've tried different cat5 cables so that isn't the case.
-
What version of the Pickit3 software are you using?
If you are using version 3, everything will flash OK and appear to be working including the lights on the magjack. However, you will not have any output to your lights and the conductor will constantly reboot.
Make sure that you are using version 1 of the Pickit3 standalone programming app found here:
http://www.diylightanimation.com/wiki/index.php?title=Software#PIC_Programming (http://www.diylightanimation.com/wiki/index.php?title=Software#PIC_Programming)
-
i have not downloaded any new versions of the pickit3. it is the same version that was downloaded last year. no where in the pickit program do I see anything about what version it is. all of my smart string devices work just fine. the ED works just fine.
-
Tell us about the IP settings for the LAN. Maybe try a static IP?
What OS is PC?
-
if you are using Antivirus software, you might want to try to temporarily disable it and test. Also if you are running the Windows firewall, you might want to try to disable that as well.
-
firewall is off. anit-virus is Microsoft security essentials(free)
OS is windows 7
how do I find the static ip address for the concuctor to enter it into my network? I remembered how to get into my router and I believe that is where the change needs to be done
-
Give it a shot. http://www.howtogeek.com/howto/19249/ (http://www.howtogeek.com/howto/19249/) My win7 box doesn't need it but XP does. Worth a shot.
-
I just reread this thread and in reply 29 I see that it looks like you were connected successfully for a brief period of time because you got a "card error" message. I also saw where Keith asked if you have tried a "cross-over cable". I may have missed it but I didn't see a response on his question. As I was rereading this your condition sounds very similar to my situation I originally had. I was using a laptop with an Atheros adapter and sometimes the Conductor would connect and sometimes not (probable 90% it didn't). I then tried a cross-over cable and bingo to now works every time with my laptop.
In my case I had tried the Conductor on another computer and it worked every time so I knew the Conductor was OK.
If you have another computer, have you tried the Conductor on it?
Denny
-
I was under the impression that I didn't need a cross over cable with my newer laptop with windows7? if I use a crossover cable and it don't need one, won't it fry my conductor? how do I locate the static ip for the conductor?
-
Try setting your ip to 192.168.1.10 and you subnet to 255.255.255.0. You can leave your gateway blank. Only do this when connected directly to the conductor not through your regular network. This makes sure your computer has an ip address in case it get confused since it expects a dhcp server of some type to give it an address. Most computers don't have a problem but some do. I would still try the crossover cable also.
Sent from my Thunderbolt using Tapatalk 2.
-
A crossover cable will NOT hurt the conductor.
-
Try setting your ip to 192.168.1.10 and you subnet to 255.255.255.0. You can leave your gateway blank. Only do this when connected directly to the conductor not through your regular network. This makes sure your computer has an ip address in case it get confused since it expects a dhcp server of some type to give it an address. Most computers don't have a problem but some do. I would still try the crossover cable also. The crossover cable will not hurt the conductor.
Sent from my Thunderbolt using Tapatalk 2.
Sent from my Thunderbolt using Tapatalk 2.
what about the preferred dns server and alternate dns server? when I go to add static ip, it opens up the dns server numbers?
-
I leave blank.
-
i have not downloaded any new versions of the pickit3. it is the same version that was downloaded last year. no where in the pickit program do I see anything about what version it is. all of my smart string devices work just fine. the ED works just fine.
You can find the software version under help and about. It will show the version in the top right corner.
I was only asking about the software version since you said you started having issues after reflashing for the conductor.
The network connection and settings should not be any different for the conductor than they are for the ED. So, if the ED is working but the conductor is not, I would not think that it is a IP, firewall, or other network problem.
-
i have not downloaded any new versions of the pickit3. it is the same version that was downloaded last year. no where in the pickit program do I see anything about what version it is. all of my smart string devices work just fine. the ED works just fine.
You can find the software version under help and about. It will show the version in the top right corner.
I was only asking about the software version since you said you started having issues after reflashing for the conductor.
The network connection and settings should not be any different for the conductor than they are for the ED. So, if the ED is working but the conductor is not, I would not think that it is a IP, firewall, or other network problem.
ok, re flashed the ed to ED firmware and everything works as it should. re flash to conductor firmware(downloaded it again to make sure nothing was wrong with the original file i had) and boom, nothing. again. definitely a conductor isolated issue. I am going to start checking all my connections again. if i manually reboot the conductor, it will flash the conductor time and say waiting for about 3 seconds and then goes to not connected. the conductor clock is 2 hours behind my computer clock so i set a show accordingly and nothing happened.
is there anything different in the firmware between the ed and the conductor on connectivity? they should theoretically connect the same right?
-
Remember that the ED is a one way communication where the Conductor is 2 way. It is possible for a network interface to be able to send multicast packets but not be setup properly to receive them. Firewalls are also good at sending data out but blocking the data coming back, especially UDP packets.
-
Remember that the ED is a one way communication where the Conductor is 2 way. It is possible for a network interface to be able to send multicast packets but not be setup properly to receive them. Firewalls are also good at sending data out but blocking the data coming back, especially UDP packets.
firewalls are off
-
Could a dead RTC battery cause this? I think someone mentioned it. Test battery with a meter? Should be 3V.
-
Could a dead RTC battery cause this? I think someone mentioned it. Test battery with a meter? Should be 3V.
3.06volts dc
-
Well, there you go, too much voltage! ;D
Did you try disabling wifi? I have to on win 7 box.
-
Well, there you go, too much voltage! ;D
Did you try disabling wifi? I have to on win 7 box.
yes, when i disable wifi is when it will actually connect briefly. but it won't do it every time i reboot the conductor manually
-
took a time out from the issue with my conductor to work on some projects that "had" to be done. so the steps I took tonight when firing up the conductor was: disable wifi, plug in cat5 cable, insert cf card, plug in conductor, pull up conductor v3 utility, and poof! it flashed up show waiting, but poof, just as fast went away. I am no computer guru, but I have searched everywhere on my computer for any possible firewall and they are off. both windows firewalls are off, I use security essentials by Microsoft for my antivirus protection, no firewalls there to be disabled. I have checked all custom settings in windows firewall for unicast, outgoing, incoming and all seem like they are in the right position for allowing things to work both ways.
duane
-
Only read about half this stream so this might be way off base. Go into the directory that the conductor software installed to and check the permissions on where the conductor software on the pc may want to write its files. I had this issue tonight with all of the various start address software programs, normally an error will toss but sometimes they just do wierd stuff.
Also check if cf card is write protected.
Sent from my Sony Tablet S using Tapatalk 4
-
Conductor uses Broadcast not unicast traffic.
RJ
-
Conductor uses Broadcast not unicast traffic.
RJ
from what I have described, any ideas on what I should check? I know the CF card is right or it wouldn't flash waiting for that brief second.
-
Did you ever try the crossover cable or setting your ip static? Did you try moving the conductor board to your other etherdongle? You might try another Ethernet card as someone in this thread had problems with a card similar to yours but got around it by using another computer. Did you try disabling your antivirus temporarily as some have firewall capability? I guess you didn't hear back from Lonewolf. Having another computer with a known working conductor unit would narrow it down to conductor or computer. But since your show never ran it sounds more likely the conductor.
-
i am confused by one thing, this conductor worked last year. 3 of the 6 songs i loaded on it ran flawless, it had music timing issues with the other 3 songs but it worked. it has only started causing issues since i downloaded the latest firmware. i just got the conductor control panel v3 downloaded to another pc. plugged every thing in and it wouldn't start recognizing it until i used a crossover cable. i am using a static ip address, LAN connection keeps connecting and disconnecting. windows firewall is off, wifi is disabled, no anitivirus on this machine. OS is XP. one thing is that when i connect to my laptop, the conductor will connect in control panelv3 for about 3 seconds and disconnect, on this other pc, it is not even doing that.
i heard back from lonewolf, he says he doesn't know much about the conductor, that RJ used his for testing and sent it back to him saying it was rock solid, so he hasn't messed with his. i am at a point with my show that i could take the several hour trip(hour 15 minute drive one way plus diagnosing my problem) to see lonewolf if necessary and if he is willing. that i have not asked him.
-
You and I are both having issues and we're both on XP and that is interesting. I used mine the entire time of the conductor beta and it ran flawlessly, then I update to newest firmware and CP and no dice. I never even did anything to the CF card. Can you try reverting to previous firmware and control panel and see how it goes? Plan to try this myself tonight. Anyone have thoughts if it works for us on the previous firmware?
-
FIRST I WANT TO APOLOGIZE TO EVERYONE THAT HAS MADE SERIOUS EFFORT TO HELP ME WITH THIS PROBLEM. AT THE SAME TIME THANK YOU.
I do not know how, or why, or when, I took a metal pick over all of my cf socket pins and nothing moved(while unplugged of course). for some reason there was a toothpick lying on the table today, not sure where it came from or who, we don't have any in the house. but, with that said I took the toothpick over the cf socket pins while the conductor was on and connected and POOF! IT CONNECTED TO THE CONTROL PANEL! HOW THE HECK DID I MISS THAT! I took a metal pick while the conductor was unplugged with a magnifier and nothing moved, SEVERAL TIMES! needless to say I am a man and admit when I am wrong. I screwed up and you guys were pulling your hair out right there with me to help and all I can say is you guys are AWESOME!!
but now the clock will not sync? I pulled the battery and it tested at 3.05v. put the battery back in and the conductor clock starts over at 0 0 0 on Monday. I click on sync time and nothing happens.
-
You and I are both having issues and we're both on XP and that is interesting. I used mine the entire time of the conductor beta and it ran flawlessly, then I update to newest firmware and CP and no dice. I never even did anything to the CF card. Can you try reverting to previous firmware and control panel and see how it goes? Plan to try this myself tonight. Anyone have thoughts if it works for us on the previous firmware?
I do not have a previous version of the firmware. re-check your CF pin sockets. I was blue in the face saying that mine were fine and turned out they weren't
-
Redo your pasword. The system will not accept inputs unless the passwords match. You click the button but nothing happens.
RJ
-
reset the password, everything is working on the conductor end. now i'm having an issue going to lights. might be a sequencing set up issue there, but it works threw my other ED and I know the ED with the conductor worked with the lights as ED so I will trouble shoot. as for the conductor, it is running my test show right now as far as the control panel is concerned so I think it is safe to say that it is working. I will run another test show after I check profiles and see what happens.
-
YEAH!!!
Hope I get lucky with a loose CF card socket...
-
YEAH!!!
Hope I get lucky with a loose CF card socket...
I honestly can't believe I missed it. I hope that is your problem too. now I just have to figure out why I have no blinky! lol
make sure you have a toothpick and slowly graze over the cf pins while the conductor is connected and the cf card is installed. it will kick in if you have a loose cf socket pin. I even put an ohm meter on all the pins at the 90 going to the card and the pad itself on the pcb and they all checked out. really weird. good luck
-
The pressure that you were applying to the pins while making your continuity test was probably pressing it back onto the board making the connection. The only way to really test that is to use needle probes and measure from the socket to the board, avoiding any contact with the pins.
-
To add more confusion, the conductor works fine on my win7 box but not with the XP box I used for the entire beta?! I am just going to see if any worked loose...
-
I would reconnect it back to the WIN7 box and see what happens. If it is still working there then the issue is with the other machine. The Conductor uses multicast which is really not the best protocol for 2 way communications and there may be an issue with how it is being implemented that is not fully compatable with with your XP protocol stack. Is your XP machine fully up to date on its updates?
-
Yep, still works on Win7 but not XP. No CF pins loose... XP is SP3 with auto updates so should be good there. Only variable is a crossover cable I made. Might have gone bad. Maybe all the unplugging from the 67 firmware revisions took its toll. I am not making another (PITA) and asked a tech I know for one. We'll see. Not critical since I can load show from Win7.
-
You can buy them pre-made at just about anyplace that sells cables. Even BestBuy. I always get cables from Monoprice.com. It is just a standard crossover cable. Nothing special like a LOR to DMX conversion cable.
-
Yep, still works on Win7 but not XP. No CF pins loose... XP is SP3 with auto updates so should be good there. Only variable is a crossover cable I made. Might have gone bad. Maybe all the unplugging from the 67 firmware revisions took its toll. I am not making another (PITA) and asked a tech I know for one. We'll see. Not critical since I can load show from Win7.
Well, there is no magic here. If it works on one then it can't be a hardware issue with the Conductor. It looks like an implementation issue. You could try a crossover cable and I would be supprised if that worked but I have learned that anything is possible. Auto-updates don't always catch everything and sometimes things like this are found in the optional updates listed under hardware.
-
Will check for updates. Good idea.