Orchid V4, V4+ Programing Tool Support

CongoBlue

Hi. Having previously programmed my Orchid v4 using CWClient, I'm now attempting to update it using this spreadsheet. The modem in the PC can successfully dial an ISP, and I believe I have configured the spreadsheet correctly, however, when I attempt to send any commands to the Modem from the spreadsheet, Excel (2007) simply hangs and becomes unresponsive, requiring a Force Quit.

Can anyone help?

Thanks!

CongoBlue

Fixed it! Discovered 'Advanced Reset Required' set to 1. Set to 0 and Excel can successfully dial the modem now.

However, I seem to have another problem. The Orchid doesn't seem to be accepting any of the codes. I've tried clearing the routing table & carriers for example, yet the dialler still works as it it has the old tables loaded. The thing that alerted me to this was that even though it is the weekend, the dialler is still following the old rule of sending mobile calls via 18185 instead of 18185's Cable Access number.

I have sent the time codes & off-peak codes.

Any suggestions?

CongoBlue

Following a little more investigation, I have discovered that the Orchid is indeed accepting manually dialled codes, and I have managed to clear the Routing Table and Carrier Table successfully. The problem appears to be that Excel is not able to complete the dialing of each code.

I tested this by entering my mobile number into a cell and clicked 'Dial Single Table Entry". Listening to the codes dialled, is is only dialling the first 9 digits before stopping and haging up. So for example, if the number were 07123 456 789, it is only dialing 07123 456 7.

Very odd...

FJSRiDER

CongoBlue wrote: »

The Orchid doesn't seem to be accepting any of the codes. I've tried clearing the routing table & carriers for example, yet the dialler still works as it it has the old tables loaded. The thing that alerted me to this was that even though it is the weekend, the dialler is still following the old rule of sending mobile calls via 18185 instead of 18185's Cable Access number.

I have sent the time codes & off-peak codes.

Any suggestions?

I discovered this until I ran 'Clear Routing Table', 'Clear Carrier Table' and 'Set Unit Non Managed' all together - so don't know which solved it - but I suspect if you have not done the latter it could be that....

CongoBlue

Yes I did run those commands manually at one point, which seems to be what got me to this point. Still a bit mystified as to what is causing the other problem with Excel not managing to complete the dialling of commands..

FJSRiDER

CongoBlue wrote: »

Yes I did run those commands manually at one point, which seems to be what got me to this point. Still a bit mystified as to what is causing the other problem with Excel not managing to complete the dialling of commands..

I'd guess, if the old codes are still working, that you have not actually managed to get those commands to work....?

CongoBlue

CongoBlue wrote:

Following a little more investigation, I have discovered that the Orchid is indeed accepting manually dialled codes, and I have managed to clear the Routing Table and Carrier Table successfully. The problem appears to be that Excel is not able to complete the dialing of each code.

I'm past any problems with the Orchid itself.. issue now seems to be modem related..

FJSRiDER

CongoBlue wrote: »

I'm past any problems with the Orchid itself.. issue now seems to be modem related..

If it is any help (and I doubt it is!) mine seemed to be computer related. Changed the computer I was using to run the spreadsheet and the Orchid seemed to set-up fine - once I had cleared the tables and set it to be non-managed.

Over Christmas I did my old mothers Orchid first go - after I borrowed my brothers laptop, opened the spreadsheet from a pen drive, changed the COM port setting to suit his Viao, set the dialling code and ran the spreadsheet. The 18185 account appears to show that her phone is dialling correctly (listing only daytime calls and none in the evening/weekend so far) so I guess it is all okay!

CongoBlue

Managed to fix it. Changed the macro slightly;

While Timer < starttime + (Len(ModemCommand) * 0.2) + WAITSECONDS

Changed to;

While Timer < starttime + (Len(ModemCommand) * 0.3) + WAITSECONDS

Allowing more time to complete each dial command. Works now!

KevinLawry

Sorry, I've been away for a while over the holidays.

There should be no need to change the macro, the setting 'Post Dial Pause' on the settings page should have the same effect if you increase it slightly