Re: USB/Serial issue
Hello, Working on windows. The function put driverNames is not usable on windows. = Where to get the driverName usable in runrev with the directive open driver xyz? Perhaps there is a solution for runrev on windows with the open driver syntax, but where can I get the driver name from? Regards, Franz Mit freundlichen Grüßen Franz Böhmisch [EMAIL PROTECTED] http://www.animabit.de GF Animabit Multimedia Software GmbH Am Sonnenhang 22 D-94136 Thyrnau Tel +49 (0)8501-8538 Fax +49 (0)8501-8537 Original Messageprocessed by David InfoCenter Subject: USB/Serial issue (19-Nov-2006 3:15) From:J. Landman Gay [EMAIL PROTECTED] To: use-revolution@lists.runrev.com Jean-Jacques Wagner can't seem to post to some of the lists he subscribes to, so has asked me to post this for him. He can read your answers, he just can't generate posts right now. I've told him Rev doesn't natively support USB access but it isn't clear to me what he is using as an interface, so maybe someone has comments about the post below. Hi I use to write/read string through the USB Port using a FTDI device. It seems to me that the serial port write/read commands does not work as it should. a) write to USB open driver name for binary update write var to driver name (read from driver name until empty) close driver name ... ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
Re: USB/Serial issue
Did you try put the driverNames Note the the in there to tell Rev you are looking for a property, not a variable. If that doesn't work (and I haven't tried it on Windows), then I think you can just try COM1:, COM2: etc. Cheers, Sarah On 12/2/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hello, Working on windows. The function put driverNames is not usable on windows. = Where to get the driverName usable in runrev with the directive open driver xyz? Perhaps there is a solution for runrev on windows with the open driver syntax, but where can I get the driver name from? Regards, Franz Mit freundlichen Grüßen Franz Böhmisch ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
Re: USB/Serial issue
Sarah- Friday, December 1, 2006, 4:35:30 PM, you wrote: Did you try put the driverNames The drivernames is documented as being OSX-only. -- -Mark Wieder [EMAIL PROTECTED] ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
Re: Re-4: USB/Serial issue + parallel
Franz- Wednesday, November 29, 2006, 11:58:33 PM, you wrote: In C or Pascal you can directly access the ports where the parallel interface stores the data - any experience whether I can do such things native in runrev? That's not entirely true - you end up going through the hardware abstraction layer on any NT-based OS, or you end up with a gpf. In any event, no, I don't think it's possible natively in rev. You might try shelling out to a VBScript program if that will do it, or crafting a DLL in C as a rev external shim. -- -Mark Wieder [EMAIL PROTECTED] ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
Re-2: USB/Serial issue (FTDI EasySync)
Hello, I am writing a program in runrev communicating with an acoustic analyser via RS232 (functions properly) and now work in communicating to a USB relais for regulating the dc in the object we make the measurement on. After reading this message and the docu I am not sure: Can I use USB universal serial bus in runrev or not? The SDKs (dlls, C,C++ and Visual Basic) normally offered with the hardware I cannot use in runrev native. Should I write a Visual Basic wrapper to communicate using the shell? Any ideas and suggestions? Regards, Mit freundlichen Grüßen Franz Böhmisch [EMAIL PROTECTED] http://www.animabit.de GF Animabit Multimedia Software GmbH Am Sonnenhang 22 D-94136 Thyrnau Tel +49 (0)8501-8538 Fax +49 (0)8501-8537 Original Message Subject: Re: USB/Serial issue (20-Nov-2006 6:16) From:Sarah Reichelt [EMAIL PROTECTED] To: use-revolution@lists.runrev.com On 11/19/06, J. Landman Gay [EMAIL PROTECTED] wrote: Jean-Jacques Wagner can't seem to post to some of the lists he subscribes to, so has asked me to post this for him. He can read your answers, he just can't generate posts right now. I've told him Rev doesn't natively support USB access but it isn't clear to me what he is using as an interface, so maybe someone has comments about the post below. Hi I use to write/read string through the USB Port using a FTDI device. It seems to me that the serial port write/read commands does not work as it should. a) write to USB open driver name for binary update write var to driver name (read from driver name until empty) close driver name To trigger physically the write data, (so that the chars are electrically sent through the port) I have to follow the write command with a read statement, which is definitely a wrong praxis. Why? Should the var end with a special char to trigger electrically the send command? b) read from USB open driver name for binary update read from driver name until empty close driver name When the string sent to the USB device from the external device is less than 32 chars, then read is returning the whole string. If the string contents more than 32 chars, the first 32 chars are swallowed by revolution and does not appear on the read result. However in some obscure circumstances, which relates to the timing between the time the string is send from the external device and the time the request is send from revolution to read, the hole string is passed to the read result. Does anyone have an idea about this strange but very annoying behavior. OSX ahall have a clean serial port management. I use Mac OSX and 2.7.3. Using a Mac with OS9, HC and the commconnect serial XCMD, the transmission of data to the usb device works perfectly. I use the Rev serial commands with an FTDI EasySync adapter all the time and it works very well. Do you have the latest drivers from FTDI? (They now have universal binaries for Intel as well as PPC Macs). What sort of device are you communicating with? Are the serial parameters set up correctly for this device? My uses don't echo back what is sent, but send a result in response to a command, but I have never seen any problems sending without a receive. If you like to send me an example of your scripts off-list, I'd be happy to have a look and see if I can work out what is going wrong. Cheers, Sarah ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution To: use-revolution@lists.runrev.com ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
Re: Re-2: USB/Serial issue (FTDI EasySync)
On 11/27/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hello, I am writing a program in runrev communicating with an acoustic analyser via RS232 (functions properly) and now work in communicating to a USB relais for regulating the dc in the object we make the measurement on. After reading this message and the docu I am not sure: Can I use USB universal serial bus in runrev or not? The SDKs (dlls, C,C++ and Visual Basic) normally offered with the hardware I cannot use in runrev native. Should I write a Visual Basic wrapper to communicate using the shell? Revolution cannot communicate directly through a USB port. However a USB to serial adapter attached to a USB port does work, because Rev sees it as a serial port, not a USB port. I have encountered the problem where hardware comes with APIs for accessing the USB port and I have never been able to use such things. The only hardware I have been able to access through Rev is hardware with a serial port and a published set of commands for controlling the hardware over the serial interface. If you can control your hardware using shell commands, then that can also be done through Revolution, without having to have a wrapper in any other language. Regards, Sarah ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
USB/Serial issue
Jean-Jacques Wagner can't seem to post to some of the lists he subscribes to, so has asked me to post this for him. He can read your answers, he just can't generate posts right now. I've told him Rev doesn't natively support USB access but it isn't clear to me what he is using as an interface, so maybe someone has comments about the post below. Hi I use to write/read string through the USB Port using a FTDI device. It seems to me that the serial port write/read commands does not work as it should. a) write to USB open driver name for binary update write var to driver name (read from driver name until empty) close driver name To trigger physically the write data, (so that the chars are electrically sent through the port) I have to follow the write command with a read statement, which is definitely a wrong praxis. Why? Should the var end with a special char to trigger electrically the send command? b) read from USB open driver name for binary update read from driver name until empty close driver name When the string sent to the USB device from the external device is less than 32 chars, then read is returning the whole string. If the string contents more than 32 chars, the first 32 chars are swallowed by revolution and does not appear on the read result. However in some obscure circumstances, which relates to the timing between the time the string is send from the external device and the time the request is send from revolution to read, the hole string is passed to the read result. Does anyone have an idea about this strange but very annoying behavior. OSX ahall have a clean serial port management. I use Mac OSX and 2.7.3. Using a Mac with OS9, HC and the commconnect serial XCMD, the transmission of data to the usb device works perfectly. Many thanks for help! Jean-Jacques Wagner -- Jacqueline Landman Gay | [EMAIL PROTECTED] HyperActive Software | http://www.hyperactivesw.com ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
