Vinculum VNC1L Vdrive2 module problems

Hello everyone! I have a problem with Vdrive2 module...When I send the short command set (SCS) $10 or 0x10 (I've tried both of them) to set the module in SCS mode I always receive the message "Bad Command". The module is working corectly when I test synchronization (I send and receive "e" messages). The firmware on Vdrive2 is 02.08 Vdapf, I'm using an USB stick A-data of 2 GB.
Does anyone knows what is the problem?Please help me, it's urgent...Thanks!

PS: I can set the module succesfulyy in short command mode by sending "SCS" command but if I try e.g the DIR command =in SCS mode with 0x01(or $01)...the module returns BC (Bad Command).+ I have to set the VDRIVE2 in SCS mode from ECS (default mode)by sending the command in short format ($10 or 0x10).

Take a look at this:
http://www.picbasic.co.uk/forum/showthread.php?t=7700
I think it is the same firmware, I get confused with FTDI's numbers and such. Just about as bad as their documentation.

Quote:

---

Originally Posted by mackrackit

Take a look at this:
http://www.picbasic.co.uk/forum/showthread.php?t=7700

---

Hey Dave, you must have missed the part about it being URGENT!!!:D
With something this important, who has time to read! Give me the answer NOW

Signed...
The_Anti_Virus :D

Quote:

---

Originally Posted by skimask

Hey Dave, you must have missed the part about it being URGENT!!!:D
With something this important, who has time to read! Give me the answer NOW

Signed...
The_Anti_Virus :D

---

Who has time to read or post the problem code?
My crystal ball is a little fuzzy today, so I did not want to venture that it might be a syntax problem or the lack of a carriage return or ...

Quote:

---

Signed...
The_Anti_Virus :D

---

I like your new signature !

Quote:

---

Originally Posted by mackrackit

Take a look at this:
http://www.picbasic.co.uk/forum/showthread.php?t=7700
I think it is the same firmware, I get confused with FTDI's numbers and such. Just about as bad as their documentation.

---

I've read the documentation from http://www.picbasic.co.uk/forum/showthread.php?t=7700 before posting here a new thread...I've verified the problems with RTS and CTS but there are all correctly set and I send a CR after each command ...the module it's communicating with the USB stick...because the led of the USB stick it's blinking when I run the code, and as I post previously a simply test of sending a CR and verifying the answer(D:\) confirm that the USB stick it's present and the synchronization messages are working too (I've tried also command in ECS mode and it's working) . I don't know why I cannot set the module in short command mode (SCS) and always returns Bad Command. I will appreciate if anyone has any ideas what I have to do or what it's the problem with the module. Thanks!

Again, with out seeing your code it makes it difficult to find the problem.

Here is a couple of things to look for ( I have not used the short set, and I do not have time to set one up at the moment).

Code:

---

SEROUT2 VinRXD,8588,["OPR ",X1,".DAT",13]

---

The above is ECS format to open a file with the *.DAT extension. X1 is a variable from an array with different file names.

I would guess the same code in SCS format would look like

Code:

---

SEROUT2 VinRXD,8588,[0E,20,X1,".DAT",0D]

---

One of the confusing things from the data sheet. The DS says "." is a space. Using ECS the "." is "," as in my above code. So I am not sure if there is a comma between 0E and 20 or just a space.

Another thing, are you using ASCll or binary values?

If you can get it to work in ECS, why do you want SCS?

I'm using Ascii values in ECS mode (it's working, as I said) and I'm have to use Binary values to set from ECS mode in SCS mode, and then I have to send commands in SCS mode. I can't post the code because the project is too big (C/C++ project-I'm working with an Embedded 386SX CPU ISA Half Size SBC Series).I was thinking that someone has encountered a bug about SCS mode...

Good luck, I can not help with C, most of us here use PIC BASIC. Guess that is why this forum is named MELabs PICBASIC Forums .

I will suggest contacting FTDI, their support is pretty good.

Ok..thanks! (I've write here because it's the only forum where someone writes about Vdrive2) :(

Quote:

---

Originally Posted by the_virus

Ok..thanks! (I've write here because it's the only forum where someone writes about Vdrive2) :(

---

That is interesting. I thought they were more popular.

I have a project coming up were I will be using a VDIP1. When I get started on it I will give shorts a try (still do not see the advantage) and post what happens here.