USIfAC II, technical problems & support [MERGED with Plus-related posts from original thread]

[ikonsgr]

Attached is the section where it says how to disable the USB auto detection, but there is no mention about it stopping serial comms from working. Would it be possible when using |USB to set this function and then |EN or |EN2 to disable?

I think you misunderstood something: you can't use serial/bluetooth/wifi connection when usb mode is enabled, so what you ask is pointless anyway. You see, USIfAC II board has only one real hardware serial port to service all type of connections, so you can only use one connection at a time, e.g.  if you use serial port for connecting to  a usb stick, you can't use it for anything else at the same time.

 

Any comments on running |TER more than once? It seems to lock up the CPC and put it in a bad state

|TER is actually a Basic program, so after issuing |TER command for the 1st time, you don't need to re-issue it (for example after giving |EN), you can just give RUN and it will load again without problems

[darkhalf]

I think you misunderstood something: you can't use serial/bluetooth/wifi connection when usb mode is enabled

I understand this. You either use USB or serial but not both.

so what you ask is pointless anyway

This is where I disagree. When removing the USB stick and only using serial (like what I was doing) it hangs for 5 seconds, and then as you mention before it will reset the baud rate each reset.

So if I want to use serial then either
1. disable USB (either using |USB again to turn it off) or
2. enable serial using |EN

Then either RSX should issue an out command to prevent the 'reset' baud rate for USB, until |USB is reissued to turn it back on again

Otherwise users have to remember to enter this in manually between these two modes

You see, USIfAC II board has only one real hardware serial port to service all type of connections

Once again I get that. I've designed logic boards to remap ECUs using USB communications with a 6802 microcontroller, so I understand this stuff very well

[darkhalf]

|TER is actually a Basic program, so after issuing |TER command for the 1st time, you don't need to re-issue it (for example after giving |EN), you can just give RUN and it will load again without problems

Thanks that is good to know. So running |TER a second time to check something was actually trying to reload the BASIC program, which is why it froze.

How come you removed the BAUD rate setting from the program? The manual has an (older) image showing BAUD settings as part of this terminal program.

Also I tried the partition program you mentioned in previous posts, and I had a USB stick with 256MB partition which was there, deleted it and now the USB stick is no longer recognised (!) so I'm thinking there is a problem with that program which has corrupted my USB stick. Strange. Managed to fix it with AMOEI partition manager, which recognised the stick

[ikonsgr]

@darkhalf, the |EN command does not enable serial connection, it actually enables the "direct file" mode on any kind of connection (usb, serial, wifi), e.g. access files using CAT,LOAD,RUN,SAVE commands (mind also that even if direct mode is disabled, you can still access files/dirs using the |CAT command).
Now, to perform non trivial or more "complex" procedures, (like swapping "on the fly" from usb mode to serial mode and vice versa, you obviously want, or even the weird sequence of "Run |TER, run |SET, run |EN then run |TER" you mentioned before, btw why on earth someone want to do that? ), it's better to use OUT &FBD1,X "direct communication" with the board, and not RSX commands (which are designed for making life easier for the casual Amstrad user, and in most cases  perform batch procedures and not specific functions). So the easiest way to swap between usb and serial modes is:
For swap from usb to serial mode:
OUT &FBD1,51 this will enable/disable usb mode WITHOUT deactivating the "direct file" mode as with |USB
OUT &FBD1,16  this will set serial port speed to 115200bps without needing to execute |SET command

For swap back to usb mode:
OUT &FBD1,51
OUT &FBD1,22  set serial port speed to 1000000bps for usb device communication

For setting all available serial port speeds you should give OUT &FBD1,X where X is:
10: Set serial speed to 300bps
11: Set serial speed to 2400bps
12: Set serial speed to 9600bps
13: Set serial speed to 19200bps
14: Set serial speed to 38400bps (useful for setting Bluetooth module)
15: Set serial speed to 57600bps
16: Set serial speed to 115200bps (the usually default speed for Wifi Modules)
17: Set serial speed to 230400bps
18: Set serial speed to 460800bps
19: Set serial speed to 576000bps
20: Set serial speed to 31250bps useful for connecting MIDI devices
21: Set serial speed to 921600 (max speed using wireless Bluetooth modules)
22: Set serial speed to 1000000bps(connection speed for usb storage device)
23: Set serial speed to 1065600bps(max speed for serial cable/Wifi module)

Btw, this list is also mentioned in User's Guide 

p.s. about the partition program, did you check partition_manager_guide.doc? Using this simple procedure i manage to "revive" some non working usb sticks when they were formatted using windows.

[darkhalf]

|TER, run |SET, run |EN then run |TER" you mentioned before, btw why on earth someone want to do that?

This sequence I've needed to run to |SET to configure the bluetooth to 38400bps, and then |TER to check AT commands setup. After the communications in 'direct mode' to the PC. Then back to |SET to configure to 115200, then |TER to check communications at 115200. Finally I change the PC to 'direct mode' and then |CAT

I've noticed when restarting the CPC, then if I just |CAT  I then get the 'PC is not responding message'. So then I |SET 115200 and |TER in 'Terminal' mode on the PC and 'hello' to make sure comms is good. Then back out of terminal to |CAT to get communications. Hopefully that 'use case' makes sense'

Also if I power off the CPC, I have to make sure to disconnect/reconnect the PC side. Since PC bluetooth lost connection with HC05.

|EN command does not enable serial connection, it actually enables the "direct file" mode on any kind of connection (usb, serial, wifi)

Okay got it. My bad. I missed that detail

So only if you enable/disable via |USB could you then also OUT &FBD1,92 or 93?

For setting all available serial port speeds you should give OUT &FBD1,X where X is..

Yeah read this, but am lazy and like to use RSX where possible 

p.s. about the partition program, did you check partition_manager_guide.doc?

So I've not seen that yet. Could you please link it here? I've spent a while looking here on it but cannot find it in any USIFAC threads

btw I did use AMOEI Partition manager on my stick and repartition to 256MB (FAT formatted) and put a test game on that, and that loaded and ran okay 

Still curious why both USB sticks used in older firmware versions but stopped working in later versions. There must be something in the partitioning done by windows that the USB module or firmware doesn't like any more, but is fine with these partitioning programs

[ikonsgr]

This sequence I've needed to run to |SET to configure the bluetooth to 38400bps, and then |TER to check AT commands setup. After the communications in 'direct mode' to the PC. Then back to |SET to configure to 115200, then |TER to check communications at 115200. Finally I change the PC to 'direct mode' and then |CAT
I've noticed when restarting the CPC, then if I just |CAT  I then get the 'PC is not responding message'. So then I |SET 115200 and |TER in 'Terminal' mode on the PC and 'hello' to make sure comms is good. Then back out of terminal to |CAT to get communications. Hopefully that 'use case' makes sense'
Also if I power off the CPC, I have to make sure to disconnect/reconnect the PC side. Since PC bluetooth lost connection with HC05.

For communication with Wifi/Bluetooth Modules, i recommend to use |COM, which is a small Terminal designed specifically for this task (e.g. giving AT commands). |TER was the first utility i made back at the early days of developing USIfAC ,mainly for testing basic communications with the PC, but after developing the direct mode on windows utility (and |COM utility on CPC), nowadays is practically useless (i left it mainly for legacy reasons), unless you want to chat with your PC  Btw, you would already knew all this, if you have checked user's guide or at least took a look at |HELP 

So only if you enable/disable via |USB could you then also OUT &FBD1,92 or 93?

OUT &FBD1,92 or 93 only enables/disables the "auto usb" function upon cold booting, e.g. directly set to usb mode and avoid giving |USB command after a cold boot.

Still curious why both USB sticks used in older firmware versions but stopped working in later versions. There must be something in the partitioning done by windows that the USB module or firmware doesn't like any more, but is fine with these partitioning programs

I agree, most probable, microsoft once again FUCKED UP compatibility and functioning of many devices with newer windows versions....
 
btw, here you can find active partition manager guide doc: https://www.dropbox.com/scl/fi/wh6fzc4m4rzmtwf05w5kv/PartManFree-Setup.zip?rlkey=azfist635nq6j2w2k655yomqh&dl=0

[crabfists]

Hello. I received a Ulifac II v5 last December. It has the resistor fix applied but I cannot get it to boot unfortunately.

I am trying to use it with a late revision 464. At first, the CPC was booting normally and not showing the board's boot message. After doing OUT &FBD2,5 the CPC gets stuck after the (C)1985 copyright message.

I've cleaned the edge connector thoroughly but that didn't help.

I don't have another CPC to test it on, or another expansion card I can test.

Any help would be gratefully received.  
Thanks

[ikonsgr]

Hello. I received a Ulifac II v5 last December. It has the resistor fix applied but I cannot get it to boot unfortunately.

I am trying to use it with a late revision 464. At first, the CPC was booting normally and not showing the board's boot message. After doing OUT &FBD2,5 the CPC gets stuck after the (C)1985 copyright message.

I've cleaned the edge connector thoroughly but that didn't help.

I don't have another CPC to test it on, or another expansion card I can test.

Any help would be gratefully received. 
Thanks

If you have the latest cost down amstrad 464 with ASIC ,i think this specific board, had some compatibility issues, especially with the c3 ram config mode.
Anyway, first i suggest to use fine sand paper to rub the edge connector, in order to remove any oxidation/corrosion (which usually is invisible to naked eye) .Then you can try to update firmware with a usb2serial cable: https://www.dropbox.com/scl/fi/dkq6kljf77gt2soito61h/ULIFAC_4.zip?rlkey=yff8mdbk8hqcw61oaj74h12vr&dl=0
Check user's guide for more details
If these fail, you can return board for further investigation.

[crabfists]

Hello. I received a Ulifac II v5 last December. It has the resistor fix applied but I cannot get it to boot unfortunately.

I am trying to use it with a late revision 464. At first, the CPC was booting normally and not showing the board's boot message. After doing OUT &FBD2,5 the CPC gets stuck after the (C)1985 copyright message.

I've cleaned the edge connector thoroughly but that didn't help.

I don't have another CPC to test it on, or another expansion card I can test.

Any help would be gratefully received. 
Thanks

If you have the latest cost down amstrad 464 with ASIC ,i think this specific board, had some compatibility issues, especially with the c3 ram config mode.
Anyway, first i suggest to use fine sand paper to rub the edge connector, in order to remove any oxidation/corrosion (which usually is invisible to naked eye) .Then you can try to update firmware with a usb2serial cable: https://www.dropbox.com/scl/fi/dkq6kljf77gt2soito61h/ULIFAC_4.zip?rlkey=yff8mdbk8hqcw61oaj74h12vr&dl=0
Check user's guide for more details
If these fail, you can return board for further investigation.

Yes, it is the cost down 464 board. I did read the manual but I couldn't see a mention of this compatibility issue.

I have thoroughly cleaned the edge connector with a fibreglass pen.

I bought the board last December. Will it not have the latest firmware on it? Is there a newer firmware that will fix the compatibility issue?

I'll probably try to get hold of a 464 board that is not the cost reduced one.

[ikonsgr]

Yes, it is the cost down 464 board. I did read the manual but I couldn't see a mention of this compatibility issue.
I have thoroughly cleaned the edge connector with a fibreglass pen.
I bought the board last December. Will it not have the latest firmware on it? Is there a newer firmware that will fix the compatibility issue?
I'll probably try to get hold of a 464 board that is not the cost reduced one.

Well,i didn't know that such 464 version existed until a couple of weeks ago that someone having the same board mentioned me this Ram configurations compatibility issues (although i can't verify that ULIfAC board has issues with it too) 
Now, the board has the latest firmware but for some reason it might be damaged, that's why i suggest to reflash firmware. But if you can find another CPC, it's better to test board with it first, to verify that it works ok, and the problem is with the specific board only.
Btw, did you try the "auto rom mounting" feature? This will automatically load roms and reset to dual ram/rom mode upon cold booting (before reaching the freezing point you described, just before Ready prompt). It's very easy to do it, check here: https://www.dropbox.com/scl/fo/ufddkml9c39fvfazyfcvk/h?rlkey=3n6jnkewqjuiw6utzhbwfx5ue&dl=0

[harzretro]

Shit, i don't know if i bricked my ulifac V3 ...
I wanted to make some more tests with symbos with my 464.

And i don't know why, but now the system don't use the ulifac anymore, also not my 6128. Starting don't show any message. The reset button and the halt button wirk. Also the rom button make a reset 

The connectin is good, it workes before and the v5 works.

I've the feeling that there is some blocking unside the ulifac that it don't want to start anymore... :/

Is there any help??

[harzretro]

Ohh, i think the last command i used was |464
like described in the manual to access a disk image

[harzretro]

Ahhh, should read better the manual:
An out &fbd2,5 resolved the problem!

[ikonsgr]

Ohh, i think the last command i used was |464
like described in the manual to access a disk image

|464 is kind of obsolete command (i left it for legacy reasons only), you don't need to use it anymore with ULIfAC board. This is useful with USIfAC II, in order to enable dsk image access mode on CPC 464, as it enables amsdos/parados emulation.
On CPC 464 with ULIfAC (that has a rom board) , you just give |6128, and then, access images directly as with CPC 6128 (using |FDC instead of |464)

[unay]

@ikonsgr

Hi friend,

I have a Schneider CPC6128 with centronics connection, and an Amstrad CPC464 with edge connection. I also have EDGE connector cable and CENTRONICS connector cable.

When i plug the ulifac on 464 it works Fine.
But it doesnt work with Schneider 6128. First; never get the boot message. Sometimes it opens regular schneider 128k screen, sometimes its freezing. I tried to OUT &FBD2,5 then it says "Ready" but notging change. Reset button seem works, also Pause button works too. But when i try the other buttons its freezing or get completly blank screen. And nothing can help (power off and on etc.) Unless completly of the power and un plug the ulifac. I have cleaned up the centronics slot (also, i dont know this helps but external floppy drive works Will with fdd port also centronics)

I have added some photos

[vasilisk]

I only have edge connector cpc. I had similar problems and it turns out that the edge connector of ulifac was not tight enough when inserted in. I changed the edge connector from the usifac that I had, which was more robust and ulifac worked immediately. I also cleaned thoroughly the cpc side.
On the left is ulifac with usifac connector. And on the right usifac with ulifac connector.
Maybe it was my cpc because not many people had problems.

@ikonsgr 
 Personal opinon, left connector is better than the right.

[GUNHED]

Time to move all CPCs to Centronics connectors! All problems will be gone then! 

[unay]

@ikonsgr

Hi friend,

I have a Schneider CPC6128 with centronics connection, and an Amstrad CPC464 with edge connection. I also have EDGE connector cable and CENTRONICS connector cable.

When i plug the ulifac on 464 it works Fine.
But it doesnt work with Schneider 6128. First; never get the boot message. Sometimes it opens regular schneider 128k screen, sometimes its freezing. I tried to OUT &FBD2,5 then it says "Ready" but notging change. Reset button seem works, also Pause button works too. But when i try the other buttons its freezing or get completly blank screen. And nothing can help (power off and on etc.) Unless completly of the power and un plug the ulifac. I have cleaned up the centronics slot (also, i dont know this helps but external floppy drive works Will with fdd port also centronics)

I have added some photos

By the way when i try to access floppy (with schneider) its freezing again. Is it possible that ulifacs floppy controller and schneiders internal floppy controller conflicts?

[ikonsgr]

@unay try giving |SM,1 on CPC 464 to change ULIfAC to 6128 mode, and then try it on the CPC 6128.
 If this is the 6128 that you revived after fixing cutting traces, then it might have more problems regarding the expansion connector too.

[ikonsgr]

Personal opinion, left connector is better than the right.

Unfortunately the edge connector on the left was from a batch i got from UK a few years ago, which unfortunately i can't find any more (at least not at insane prices...)
The other one at the right, must be from a batch of connectors i got from taiwan which indeed were a bit loose upon plugging, but in the last couple of years i have found a new supplier that has edge connectors similar to the right one, but the pins inside are tighter and plug much better, almost like the left one   

[unay]

@unay try giving |SM,1 on CPC 464 to change ULIfAC to 6128 mode, and then try it on the CPC 6128.
 If this is the 6128 that you revived after fixing cutting traces, then it might have more problems regarding the expansion connector too.

Thanks, i'll try |SM. By the way this one is diffirent 6128.

[unay]

@unay try giving |SM,1 on CPC 464 to change ULIfAC to 6128 mode, and then try it on the CPC 6128.

I tried  |SM,1 it says "664/6128 mode on". But it didnt change the results on 6128. I still get strange images. Any other suggestions? I'll check the centronics pins with a multimeter later.

[McArti0]

First image is BASIC ROM?

[unay]

First image is BASIC ROM?

Every time i try to reset or switch of and on the power diffirent images are appearing. Sometimes basic appearing sometimes these images... But never ulifacs boot message appears.
 

[McArti0]

You must check the continuity of all edge connector lines with an ohmmeter with the CPC turned off and the ULIFAC installed.
You have easy access to the top lines. It's worse with the bottom lines. You need to find them on the pins of the GA40010 and other systems according to the schem. Good luck. Start on the right side.